This article presents a model for describing the architecture of software-intensive systems, based on the useof multiple, concurrent views. This use of multiple views allows to address separately the concerns of thevarious ‘stakeholders’ of the architecture: end-user, developers, systems engineers, project managers, etc.,and to handle separately the functional and non functional requirements. Each of the five views is described,together with a notation to capture it. The views are designed using an architecture-centered, scenario-driven, iterative development process.
The IEA's paper points out to a figure that is undeniably wrong. However, this piece of data is not to be found in any of our reports, but only in the media. This event reveals the importance of considering system-wide dynamics as a whole.
Easily create beautiful UML Diagrams from simple textual description. There are also numerous kind of available diagrams. It's also possible to export images in PNG, LaTeX, EPS, SVG.
K. Ehrig, C. Ermel, S. Hansgen, and G. Taentzer. International Conference on Automated Software Engineering, page 134--143. Long Beach, CA, ACM Press, (November 2005)
B. Motik, A. Maedche, and R. Volz. Proc.\ First International Conference on Ontologies,
Databases and Application of Semantics
(ODBASE-2002), (October 2002)
A. Murray, and T. Lethbridge. CASCON '05: Proceedings of the 2005 conference of the Centre for Advanced Studies on collaborative research, page 200--211. IBM Press, (2005)
M. Glinz. IWSSD '00: Proceedings of the 10th International Workshop on Software Specification and Design, page 11. Washington, DC, USA, IEEE Computer Society, (2000)
M. Rosen-Zvi, T. Griffiths, M. Steyvers, and P. Smyth. Proceedings of the 20th conference on Uncertainty in artificial intelligence, page 487--494. Arlington, VA, USA, AUAI Press, (2004)