nocomplexity / architectureplaybook

The Open Architecture Playbook. Use it to create better and faster (IT)Architectures. OSS Tools, templates and more for solving IT problems using real open architecture tools that work!

ArchitecturePlaybook

Smart people have been thinking on how to create IT architectures as long as there has been computers. Ideas come and go, however creating a good architectures can still be complex and time consuming. Especially when you try to invent the wheel for yourself. With this interactive playbook you can create your IT architecture better and faster.

This architecture playbook is divided in the commonly used architecture sections:

Business
Data
Applications and of course
Technology Infrastructure (TI)

This playbook is created for online usage.

HELP?!

The best way to help is share this eBook! So share the link to with your colleagues.

This is a living document and will continue to be updated with more helpful information and examples as they become available.

The latest version of this architecture playbook is always on:

• https://nocomplexity.com/documents/arplaybook/introduction.html

This version is created with Jupyterbook and has also some templates and growing number of notebooks to help you!

I am always searching for good real FOSS tools that make creating complex architectures even more fun!

Send any errors, remarks, suggestions and improvements to: info [at] nocomplexity [dot] com This book is open source. Issues and pull requests are welcome!

architectureplaybook's Issues

Some business architectures templates are not working

Hi,

Thank you for your playbook, it really looks interesting. When I was quickly running through it, I found 2 outdated links :

• Basic business architecture template
• Stakeholder template

Best regards,

Maxime

businessprinciples.rst has dups on 'maximize benefit to the enterprise'?

The businessprinciples.rst has dups on 'maximize benefit to the enterprise'?

Namely, the following two section sharing the same 'statement', and similar 'rationale' and 'implications'.

• Maximise Benefit to the Enterprise (line136-163)
• Maximize Benefit to the complete enterprise (line164-188)

Both sections seem to come from the same commit (a7297f9 circa 2019-11-16), sans cosmetic touchups from two commits (30becd5 and 415549d)

I will be more than happy to put together a patch alone or via collaboration. any insight or context on the original intent(s) would be appreciated.

Issue on page /application-architecture.html

In "Short overview of ISO 25010" -> Security:
There is a duplicate entry for "Confidentiality" and "Compliance" is missing.

See: https://nocomplexity.com/documents/arplaybook/quality.html#security

line 131 in quality.md needs to be rephrased for clarity and to remove grammatical errors

line 131 in quality.md has grammatical errors.

Coming from commit (8f4c2a3 circa 2018-07-10), it says
The material of ISO is unfortunate not open. But since quality matters and ISO 25010 is used heavily for managing quality aspects within business IT systems a short overview.

imho,

• 'unfortunate' should be an adverb ('unfortunately'), in order to modify 'not open'.
• The next sentence can be rephrased for better clarity and more proper grammar.