IEEE 1471-2000 pdf download Recommended Practice for Architectural Description of Software-Intensive Systems
Each viewpoint is specified by :
– Viewpoint name
– The stakeholders addressed by the viewpoint
– The stakeholder concerns to be addressed by the viewpoint
– The viewpoint language, modeling techniques, or analytical methods used
– The source, if any, of the viewpoint (e.g., author, literature citation)
♦ A viewpoint may also include :
– Any consistency or completeness checks associated with the underlying method to be applied to models within the view
– Any evaluation or analysis techniques to be applied to models within the view
– Any heuristics, patterns, or other guidelines which aid in the synthesis of an associated view or its models
Viewpoint name: Capability
♦ Stakeholders:
– The client, producers, developers and integrators
♦ Concerns:
– How is functionality packaged?
– How is it fielded?
– What interfaces are managed?
♦ Viewpoint language
– Components and their dependencies (UML component diagrams)
– Interfaces and their attributes (UML class diagrams)
♦ Source: also known as Static, Application, Structural viewpoints
The Capability View covers all system functionality for operating on data
♦ Capabilities are fielded using a 5‑tier layered organization with interfaces between pairs of layers
– Each layer is a capability
– Entire stack is a deployable capability
♦ Capabilities can serve other capabilities
Viewpoints are not system specific, unlike the stakeholders and views
♦ Hence, an active architect may be able to reuse viewpoint descriptions
♦ Equivalently, the viewpoints can be included by reference
♦ No particular architecture description languages
♦ No required views or models
♦ No required formal consistency or completeness criter

Share on Facebook

Post on X

Follow us

Save