How many diagrams are needed to create the "Architecture"? 

Can any diagram qualify to be the Architecture? 

We have created 39 diagrams to describe the Architecture, how do we validate that these diagrams are sufficient? 

How do I ensure consistency across the diagrams if it is created by different team members? etc....

These are the common questions that we get to hear. Let's do a simple definition for architecture as suggested by John Zachman.

The Architecture is a 1.structured set of descriptive representations relevant for describing an object and being employed such that 2. an instance of the object can be created and such that the descriptive representations serve as the 3. baseline for changing an object instance.

Almost, all the cases the architecture models are multi-variable, i.e. composites (do you recollect compounds vs. elements in the periodic table). 

As John Zachman defines- single variable models are Architecture models. There are six variables, i.e. data, function, network, role, time and rules. If a model consists of a single variable type, then it's the Architecture model. However, if a model has more than one variable, say a model is having reference to data & function, or other model having a function, data and role references, etc. these are examples of composite models (implementation models). Interestingly, in most cases, models are multi-variable and hence an implementation model. As the number of variables is added to a single diagram, they tend to become less legible and these models more likely to change quickly and become outdated rendering them useless owing to their shorter life span.

Snap! Crackle! Architecture Is Not Same As Details of Implementation!

Duration: 30 minutes