Goal
Understanding the mutual impact software and business have on each other. Viewing the software engineering process as an open ended process: continuing after transition not only via technical maintenance but far more relevant via embedded usage, improved alignment and co-evolution.
Description
Starting from a historical overview of software engineering, its goals and its principles, we address the relevance of modeling software as well as its organizational habitat. UML as state-of-the-art in software modeling is discussed, with extra attention for consistency, both structural and dynamic. Architectures and patterns are presented in relation to modeling. The architectural framework of ArchiMate is introduced to underline the importance of language homogeneity in modeling software and business. The software engineering process and models for it are discussed, from waterfall to RUP. CMMI, an approach to improve the software engineering process, is introduced; in particular, CMMI’s two upper levels are related to the Demming cycle for business process improvement. Via the Demming cycle then, improving the usage of software comes into view as part of overall business process improvement, an example of co-evolution.
Method
Lectures mainly, some supervised collective assignment work.
Examination
Written, but the retake is an oral exam.
Material
The book of Martin Fowler: UML Distilled: A Brief Guide to the Standard Object Modeling Language. 3rd edition. Addison Wesley, 2004.Furthermore, copies of transparencies and of papers.
Remarks
Active involvement, assignments, student presentations.