Object Oriented Software Engineering   View all facts   Glossary   Help

subject > representation > document > architectural model

architectural model (software architecture^3)
subject			fact

architectural model	assists with integrating the work of individual people to form the final system planning and co-ordination of the work of developing a complex software system which is distributed among a large number of people planning the evolution of the system, such as subsystems that are envisioned to be part of a future release
	can be used to communicate with customers
	contains information about the interfaces and dynamic interactions among the subsystems
	defines the terms that people use when they communicate with each other about lower-level details
	has definition The document produced as a result of performing software architecture
	has purpose To enable everyone to better understand the system To allow people to work on individual pieces of the system in isolation To prepare for extension of the system To facilitate reuse and reusability
	is a subtopic of 9.4 - Software Architecture
	is a kind of document
	may be expressed as several different views such as The logical breakdown into subsystems, often shown using package diagrams The dynamics of the interaction among components at run time, expressed using interaction or activity diagrams The data that will be shared among the subsystems, expressed using class diagrams The components that will exist at run time, and the machines or devices on which they will be located, expressed using component and deployment diagrams
	must be stable which means that the new features can be easily added with only small changes to the architecture
	should be generic to ensure reusability
	shows each system component, encouraging reuse
	is a synonym of software architecture^3
document	should be written for a particular audience

Kinds of architectural model :

• first draft of architectural model (4 facts)