Software architectural model: Difference between revisions

Revision as of 14:49, 17 November 2006

Revision as of 14:53, 17 November 2006

Line 1:

'''Definition''': An Architectural Model (in Software) is a rich and rigorous diagram, creating using available standards, in which the primary concern is to illustrate a specific set of tradeoffs inherent in the structure and design of a system or ecosystem. [[Software Architectarchitect]]s use architectural models to communicate with others and seek peer feedback.

Let's look at that definition a little:

Line 20:

'''system or ecosystem''' - modeling in general can be done at different levels of abstraction. It is useful to model the architecture of a specific application, complete with components and interactions. It is also reasonable to model the systems of applications needed to delivery a complete business process (like order-to-cash). It is not commonly useful, however, to view the model of a single component and its classes as software architecture. At that level, the model, while valuable in its own right, illustrates design much more so than architecture.

[[Category:Software architecture]]

[[Category:Software design patterns]]

[[Category:Information science]]

[[da:It-arkitektur]]

[[de:Softwarearchitektur]]

[[es:Arquitectura software]]

[[fr:Architecture logicielle]]

[[gl:Arquitectura software]]

[[he:ארכיטקטורת תוכנה]]

[[ru:Архитектура программного обеспечения]]

[[fi:Tietojärjestelmäarkkitehtuuri]]

[[zh:软件架构]]