How Architecture Serves Operational Purpose?
High Level Architecture Modeling and Design helps and makes the communication easier between organizations and many times helps communication towards customers when explaining the benefits or evolution roadmap. The reduction in detail makes it easier to grasp the assignment of significant system responsibilities to high-level structures. Moreover, it satisfies the constraint that, though seemingly trivial, has important implications for communication - even large and complex architectures can be translated using presentation slides, white papers and word descriptions.
System Context View helps and makes the designers and developers to understand the overall system. In large and complex systems, designers and developers cannot efficiently understand the all details of the entire system. They need a detailed understanding of the more narrowly-scoped areas (e.g. functional group) of the system that they work on. Without an understanding of the responsibilities and dependencies of the higher-level structure with entities and components, the development and optimization of the substructures will tend to result in a sub-optimal system and leads easily adding a more complexity and overhead to the system itself. This is important from the system characteristics (behavior) point of view, like performance, as well as effort in system integration and maintenance point of view.
Work Allocation With Needed Competences comes easier to manage where architectures decompose the system into substructures (modules, design blocks, system components) that are relatively independent, having a clear responsibilities, and communicate with each other through a limited number of well-defined interfaces, the development work can be partitioned effectively. This allows parallel development work to proceed in relative independence between integration points. This is especially important in large projects, or programs where the teams are geographically located in different sites or when the third-party developers are used.
Competence Development comes a more clear from focus point of view, especially in medium and large -sized companies as e.g. “Competences in the House” or “Competence(s) in the Site” and it also enables a more efficient competence transfer among developers as “Competence in the Team”.
Organizational Development with independence and focus makes development more efficient. The system level architecture can be viewed as the dual of designing the organizational architecture (structure).