Model driven Software Engineering
Competency Leader
The use of well-designed architectures will have an important bearing on the ease with which a critical system can be successfully evolved. The system is afforded a measure of future proofing by encapsulating aspects of the system that are both critical and likely to change (encapsulation of criticality). Model-driven architectures allow the specification of a system to be defined as a model that is distinct from the implementation; the intent is that the model is defined in such a way that it is easy to change and such changes can be reflected in the implementation (ideally automatically) in preference to undertaking the more expensive process of changing the implementation itself (Hearnden et al., 2004).
Structural Design Methods describe the intended system based on a decomposition of the structure of that system, e.g., SSADM, Yourdon, and more recently UML. The structure is used to derive the design of the system and describe its functionality in a way that can later be used to drive the implementation.
D. Hearnden, P. Bailes, M. Lawley, and K. Raymond. Automating software evolution. In Software Evolution, 2004. Proceedings. 7th International Workshop on Principles of, pages 95–100, Sept. 2004.
Posters
| Researcher | Title |
|---|---|
| Nour Ali | Model Driven Ambient Aware Software Architectures |











