Developing Technology Architecture views

by Syed Suhail Ahmad, enterprisestewards.ning.com
March 5th 2011 9:34 AM

Architecture views are representations of the overall architecture that are meaningful to one or more stakeholders in the system. These views represent various stakeholder's concern and must be developed for each stakeholders to address their concerns. I have summarized some Technology Architecture views in the diagram below that can be used in any EA engagement . I think following 5 views are important to address the stakeholders concern:

Execution Architecture view- This view represents a collection of technology capability to support applications/services at run time. For example, message & routing , application connectivity, rules management etc
Development Architecture view - This view represents a collection of technology capability to support the application development process, commonly used during the SDLC process. For example, environment management, release management etc
Operational Architecture view -This view represents a collection of technology capability to support the business applications up and running. For example, service delivery, IT asset management, and SLA etc.
Technology Standard view- This view represents a collection of technology capability to support the agreed standard and compliance.
Project Portfolio view- This view represents a collection of technology capability which are impacted by a planned and existing projects.

Are there any other technology views that can be added to the list above?