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.