My fascination with the Architecture Development Method (ADM)

7 Mar 2025

Preamble

This transcript was the result of my reading a LinkedIn post by a member of the Vintage LinkedIn group.

As an Information Architect I am always fascinated by the claims made by theorists about a subject that no one really understands.

In order to explain why the ADM theories will lead to “a failure to communicate” (a quote from the movie Cool Hand Luke) I had to use the Microsoft Copilot AI engine to answer these 10 questions in order to arrive at my Conclusion:

1. Explain Murphy’s Law
2. What is an Architecture Development Method?
3. What other theories can be regarded to be an Architecture Development Method?
4. Can you provide me with one word or a simple phrase that summarises the Architecture Development Method of TOGAF, IBM's BSP, The Zachman Framework, The Federated Enterprise Architecture Framework and the Dept of Defense Framework?
5. Can you provide me with a business requirements theory that is fully integrated and delivers a technological solution that is Iterative, provides Alignment, has a Taxonomy and an Ontology is structured and provides a software solution that was developed with the theory?
6. What are the phases of the Agile theory?
7. What is an Agile Sprint goal?
8. Does not an Agile sprint goal produce a silo solution?
9. On average how many business goals do Agile theorists consider adequate?
10. What mechanism is used in the Agile theory to identify the shared goals when each Agile Sprint only address one or two?

The full article can be read by following this link

Regards

ps I have added this article to the lit in my Summary of Fascinations