262 | Documenting Software Architectures, Views and Beyond.
- Clements, Bachmann, et al.
- 2002
(Show Context)
Citation Context ...ains exactly only information items required by the Standard. Other editions meet the requirements of the Standard and contain additional information used in various documentation approaches (such as =-=[6, 1]-=-). Comments or questions Contact the author Rich Hilliard 〈r.hilliard@computer.org〉 with comments, suggestions, improvements or questions. For more information on ISO/IEC/IEEE 42010, visit the website... |
232 | Viewpoints: A Framework for Integrating Multiple Perspectives in System Development”. In:
- Finkelstein
- 1992
(Show Context)
Citation Context ... refer to model correspondence rules. implementation methods are the means by which to design and build systems using this view. Another approach to categorizing operations is from Finkelstein et al. =-=[2]-=-. The work plan for a viewpoint defines 4 kinds of actions (on the view representations): assembly actions which contains the actions available to the developer to build a specification; check actions... |
80 |
E.: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.
- Rozanski, Woods
- 2005
(Show Context)
Citation Context ...ains exactly only information items required by the Standard. Other editions meet the requirements of the Standard and contain additional information used in various documentation approaches (such as =-=[6, 1]-=-). Comments or questions Contact the author Rich Hilliard 〈r.hilliard@computer.org〉 with comments, suggestions, improvements or questions. For more information on ISO/IEC/IEEE 42010, visit the website... |
25 |
ARES Conceptual Framework for Software Architecture. In:
- Ran
- 2000
(Show Context)
Citation Context ...ultiple models: aspect-oriented style of architecture description: architecture models shared across architecture views can be used to express architectural perspectives [6] and architecture textures =-=[5]-=-. Architecture models can be used as containers for applying architecture patterns or architecture styles to express fundamental schemes (such as layers, three-tier, peer-to-peer, model-view-controlle... |
21 |
Systems and software engineering -- Architecture description,
- ISOIECIEEE
- 2011
(Show Context)
Citation Context ... . . . . . . . . . . . . . . . . . . 15 iiUsing the template ISO/IEC/IEEE 42010, Systems and software engineering — Architecture description, defines the contents of an architecture description (AD) =-=[4]-=-. Figure 1 depicts that contents in terms of a UML class diagram. The AD template in this document defines places for all required information and offers the user some additional guidance on preparing... |
13 | A documentation framework for architecture decisions,” - Heesch, Avgeriou, et al. - 2012 |
Developed at and hosted by The College of Information Sciences and Technology
© 2007-2019 The Pennsylvania State University