Why am I writing this 'SEA' book at all.

I have long been unhappy with the Enterprise Architecture methods used by IT people internationally. I have taught my ‘Architecture Engineering’ classes for several years

Selling the certifications, for such poorly crafted architecture methods, is a shame, shared by the agile certification game. These methods are an insult to common sense that says we must take qualities and costs far more seriously in real and large systems. Why are so many people fooled?

The core problem as I see it is that the methods taught and used are no longer good enough for the large scale, complex, changing technology. The central idea that is missing is quantification (of all values, qualities and costs).

Without this tool, too many bad decisions, and costly ones will be made. Quantification is the distinction between arts and crafts on the one hand, and engineering, science, good management, logic, traceability, responsibility on the other hand.

The problem is not new. There comes a threshold of complexity in all disciplines where quantification becomes a necessary tool. The time has come for IT Enterprise

Architecture to really make use of quantification, and not just talk about doing it.

I have written many books about this subject, and they are in the references. But they have not influenced EA so it is time to write a book aimed directly at EA culture, so they have no excuses, that this is some other discipline.

This is probably a hopeless case. The only time things will change is when management will only hire and employ people who can serve their organizations interests better, by being more like engineers. Anyway this is my contribution.

Let me be clear that my objective is to change poor practices. So I would be pleased if anybody would like to copy the ideas in this book in whole or part. The ideas are free. But if any reader wants to commercialize the ideas, in methods packages, training, consulting, apps, so that they are spread effectively. That is welcome. I provide a recipe, you can bake the cakes. Nice if you credit sources, I do, but I won’t sue you for forgetting. 

CONTENTS

Systems Enterprise Architecture (SEA) : The Next Generation, based on Digitization: quantified engineering, values, digital alignment, AI, Net 3.0, Digital Ontologies, Trinities, ValPlan.

Book Outline:

Introduction.

Bringing in Planguage, CE, Engineering, Systems Thinking (not IT), ValPlan, Graphmetrix. Ontology, AI, Digitizaton

1. Value-DrivenArchitecture

2. Architecture E!ciency (AE, ArchEff)

3. Constraint Respect Architecture

4. Architecture Decomposition, and the secret of project success. 5. ArchitecturePrioritization

6. Architecture Value-Stream Delivery

7. ArchitectureRiskManagement

8. ArchitectureEnterpriseAlignment

9. Architecture Organization and

Responsibility.

—————————————— end of Main Presentation. Now Details———- 10. Detailed Value Requirement SEA Language

10.1 The Scale: Detailed Resources Requirements SEA Language

10.2 Points on the Scale. Detailed Resources Requirements SEA Language

1o.3 . Do I do the constraints like Design constraint here. 1.4. 11. Detailed Architecture Specs SEA Language

12. Detailed Impact Estimation SEA Language.

13 Background Specification (Architecture Linkages) ?

References

Glossary subset