Loading [a11y]/accessibility-menu.js
1471-2000 - IEEE Recommended Practice for Architectural Description for Software-Intensive Systems | IEEE Standard | IEEE Xplore

1471-2000 - IEEE Recommended Practice for Architectural Description for Software-Intensive Systems


Abstract:

" This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such...Show More
Scope:The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardiz...Show More
Purpose:An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural...Show More

Abstract:

" This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. "
Scope:
The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the "architectural level" of system development. The phrases "ar...
Purpose:
An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
Date of Publication: 09 October 2000
Electronic ISBN:978-0-7381-2519-0
Persistent Link: https://ieeexplore.ieee.org/servlet/opac?punumber=7040

Subscription Options - Standards

References

References is not available for this document.