Architects need to capture of the goals that the system is suppose to accomplish for each stakeholder. There are many stakeholders in a project that can be concerned about different aspects of the system. For example, a stakeholder can be concern with functionality of the system, another can be concerned about performance or interoperability or security. It is the role of the architect to create documentations that formally describe the architecture of the system for each stakeholder and their concerns and viewpoints. It is the responsibility of the stakeholder to review the documentation created by the architect to make sure everything is accounted for. Once the architecture is approved, then the software developers and developers can start building the systems.
Examples of stakeholders for a system are: users, operations, maintainers, developers, and suppliers. Previously, system architectures were developed to meet the identified stakeholder's concerns of functionality, interoperability, and performance but recently a new concern of security has arise.
Security goals have to be defined before the architecture of a system is created. Specific security views of the system needs to be created to help guide the design and development phases.
Figure 4-1 is an example of a "Formal architecture terms and relationship" from Harris's CISSP Exam Guide book.
No comments:
Post a Comment