| architectural modelling | follows these steps iteratively: - Sketch an outline of the architecture, based on the principal requirements and use cases. Determine the main components that will be needed, such as databases, particular hardware devices and the main software subsystems. Choose architectural patterns.
- Refine the architecture by identifying the main ways in which the components will interact, and by identifying the interfaces between them. Decide how each piece of data and functionality will be distributed among the various components. Determine if you can re-use an existing framework.
- Consider each use case and adjust the architecture to make it realizable
- Mature the architecture as you define the final class diagrams and interaction diagrams
|  |
| has challenge is to produce a relevant and synthetic picture of a large and complex system | |
| is a subtopic of 9.4 - Software Architecture | |
| is performed by architectural modeller | |
| is a kind of modelling | |
| uses UML diagrams | |
| modelling | can be performed using - diagrams
- semi-formal or formal languages that express the information systematically or mathematically
| |
| is a particularly difficult skill | |
| is not emphasized as part of education programs | |
| may be used during design | |
| may be used during requirements analysis | |
| process | see also process^2 | |
Object Oriented Software Engineering View all facts Glossary Help
