SALEIE logo that when clicked will open a new window to access the SALEIE home page.

Strategic ALignment of Electrical and Information Engineering in European Higher Education Institutions

European Union flag.



User guide



Click on the image to the left to select the project website section to go to.

Click on the images to the left and above to select the project website section to go to (Technical Challenge Areas, Student and Staff Support Hub or Governance) OR select the Student and Staff Support Hub below.

Technical Global Challenges Areas Student and Staff Support HUB Higher Education Policy Hub


Higher Education Technical Challenges Hub: Module Specification

ICT04M1 System Analytics and Modeling

pdf version of module specification

Download the module specification

pdf version of module specification








Module name:

System Analytics and Modeling

Scope and form:


Duration (weeks; Hours/week):

15 weeks, 4h/week

Type of assessment:

Oral exam. Each student is given an individual set of assignements and questions, up to 3 questions total, which cover all the learning outcomes of the module. The students have up to 30 minutes to prepare for presenting the answers. All the questions must have atleast partial asnwers. Prerequisite is a passing grade for the presentation and independent work. The presentation is oral, individual and model-based. Each student introduces in 15-20 minutes his/her vision of a business service and its supporting information system to other students, using only a modelling program and the UML model sketches in this program. The presentation gets passing grade, if the main views of the system have presented and discussed with other students and lecturer. The independent work is written and may be individual or collective. The model, documented in this work, must be introduced in the presentation with a passign grade. In the case of a collective work, students have individual responsibilities on certain parts of the work. To get a positive mark (1 or more), all the compulsory parts should be present. There is a list of typical mistakes, which’s existence in the work get the mark down. If there are not listed mistakes in the work, criteria of the mark 4 (very good) are met. Originality of the topic or viewpoint, relevance to practice, and being among first presenters bring the mark up.

Qualified Prerequisites:

Introduction to Information Systems; Modelling

General module objectives:

To give understanding of the role of system analysis in development of information systems.
To teach system thinking and exact express oneself.
To teach contemporary methods, techniques and tools of system analysis.
To teach system analysis as a customer centric view to information systems and their development.
To teach analysis and management of requirements and user interfaces as important part of (conceptual) system analysis
To relate the analysis of requirements and user interfaces to domain modeling, and to different topics of design
To perform a practical work (project) in (conceptual) system analysis
To show interfaces with related subjects

Topics and short description:

Domain analysis. Conceptual modeling. Conceptual frameworks (ontologies). Analysis and architecture: layers, views, lifecycle. Domain vs infrastructure. The (layer of) business model as "pure domain" and conceptual (computing independent) view to IS. The role of system analysis in (traditional and iterative) IS development cycle. Analysis vs. design. Strategic analysis vs. detailed analysis. Traditional (structured) vs. object oriented analysis, agent-oriented analysis, their unity and differences. Business modeling vs. requirements (and user interfaces) analysis. Analysis modeling of objects, processes, events, organization (actors), objectives, interactions. Textual vs. graphical modeling in analysis work. UML: class diagrams, use case diagrams, activity diagrams, state diagrams, sequence diagrams in the context of analysis models. System requirements and use cases, user stories, and user interfaces. From business model to use case model. Different formats for describing use cases. Domain model (in the meaning of static model of domain). Requirements and user interfaces as views (queries) into domain model. System events and operations. Contracts for system operations.Decomposition, management, documenting, versions and change handling of analysis models. Analysis patterns. Process of system analysis (in the framework of iterative development process). From analysis to design.

Learning outcomes:




Recommended literature:

C.Larman, An Introduction to Object-Oriented Analysis and Design and the Unified Process: Applying UML and Patterns, 2001 (or later).
L.Sterling and K.Taveter, Agent Oriented Modeling, The MIT Press, 2009.
J. Heuman, An Introduction to Business Modeling in UML [Online]
M. Fowler, Analysis Patterns: Reusable Object Models, Addison-Wesley, 2005