Software architectural model: Difference between revisions

Revision as of 20:50, 28 February 2007

Revision as of 02:53, 2 April 2007

Line 11:

'''diagram''' - In general, a model may refer to ''any'' abstraction that simplifies something for the sake of addressing a particular viewpoint. This definition specifically subclasses 'Architectural Models' to the subset of model descriptions that are represented as diagrams.

'''standards''' - Standards work when everyone knows them and everoneeveryone uses them. This allows a level of communication that cannot be achieved when each diagram is substantially different from another. UML is the most often quoted standard.

'''primary concern''' - It is easy to be too detailed by including many different needs in a single diagram. This should be avoided. It is better to draw multiple diagrams, one for each viewpoint, than to draw a 'mega diagram' that is so rich in content that it requires a two-year course of study to understand it. Remember this: when building houses, the architect delivers many different diagrams. Each is used differently. Frequently the final package of plans will include diagrams with the floor plan many times: framing plan, electrical plan, heating plan, plumbing, etc. They don't just say: it's a floor plan so 100% of the information that CAN go on a floor plan should be put there. The plumbing subcontractor doesn't need the details that the electrician cares about.