Object-orientation and object-oriented modelling (OOM) in particular are discussed and put into a historical perspective regarding software engineering. UML 2.0 is covered, although not in every detail. Some insight is provided into possible future integration of new aspects with those addressed by UML already. In addition, the relevance of architecture, components and patterns will be pointed out. Based on UML and also on ArchiMate, various descriptions of software engineering processes will be discussed. Concentrating on the requirements engineering and design phases, using UML for the software system to be developed as well as for the (organizational) environment in which it is going to be used, is being illustrated. Homogeneity of modelling language for all relevant domains will be put forward as a sound basis for studying and understanding consistent integration of software systems and organizations. The relevance of such homogeneity will be underlined by introducing ArchiMate and Integration-Orientation. The relevance of (dynamic) consistency will be strengthened by introducing Paradigm. The combined relevance of such homogeneity and dynamic consistency will be further emphasized by introducing McPal.
Objectives
Software engineering: goals, principles and qualities.
Software (engineering) process and software process modelling.
General UML knowledge.
Modelling of aspects, subsystems, global structures and frequently occurring situations.
Software usage process and software usage modelling: ArchiMate, Integration-Orientation.
Consistency, dynamic consistency in particular.
Coordination as consistent management of dynamic constraints: Paradigm.
Change on-the-fly as coordinated migration based on Just-In-Time (JIT) modelled extensions to an existing model: McPal.