Strategy 3.2 EAM Foundations Flashcards
What is ISO/IEC/IEEE 42010?
Recommended practice for architectural description of software-intensive systems
scope of ISO/IEC/IEEE 42010?
- software-intenstive systems
- individual systems
- systems of systems
goals of ISO/IEC/IEEE 42010?
- support documentation, explanation,
and communication of architectures - does not provide a graphical notation
Architecture framework of ISO/IEC/IEEE 42010?
predefined set of concerns, stakeholders, viewpoints established to capture common practices for architecture descriptions
How many architectural descriptions should you have?
only one. (current or future target description)
System-of-interest
A system of interest from the perspective of one or more stakeholders. The system could be an application, a subsystem, a service, a product line, a system of systems or an enterprise
Stakeholder
Individual or organization with interest in a system of interest
Concern
Those stakeholders’ interests, which pertain to the development, operation, or other key characteristics of the system
Architecture
Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution
Architecture description
Is a work product used to express one possible architecture for a system of interest.
Does every system have an architecture?
Yes. It might be understood or not, recorded or conceptual
What does the architecture description have to be aligned with?
Stakeholder’s concerns
Architecture view
Expresses the architecture of the system of interest from the perspective of one or more stakeholders to address specific concerns, using the conventions established by its viewpoint. It consists of one or more architecture models.
Architecture viewpoint
Is a set of conventions for constructing, interpreting, using and analyzing one type of architecture view.
Model kind
Defines the conventions for one type of architecture model