Software architectural model: Difference between revisions

Revision as of 18:12, 18 March 2008

Revision as of 15:04, 26 April 2008

Line 23:

'''tradeoffs inherent in the structure and design''' - a component is not a tradeoff. Tradoffs rarely translate into an image on the diagram. Tradeoffs are the first principles that produced the design models. When an architect wishes to describe or defend a particular tradeoff, the diagram can be used to defend the position.

'''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 deliverydeliver 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.

==External links==