Systems and Process Modelling

General characterization

Prerequisites

To have basic knowledge on Software Engineering

Bibliography

Scheer, August-Wilhelm. ARIS—business process modeling. Springer Science & Business Media, 3rd edition, 2012.

Friedenthal, Sanford, Alan Moore, and Rick Steiner. A practical guide to SysML: the systems modeling language. Morgan Kaufmann, 2014.

Software Engineering, I. Sommerville, Addison-Wesley, 10th edition, 2015.

Engineering Software Products: An Introduction to Modern Software Engineering, Ian Sommerville, Pearson,  2020.

Axel van Lamsweerde, Requirements Engineering: From System Goals to UML Models to Software Specifications 1st Edition, Wiley, 2009

Pohl, Klaus, Günter Böckle, and Frank J. van Der Linden. Software product line engineering: foundations, principles and techniques. Springer Science & Business Media, 2005.

Teaching method

In theoretical classes, the theoretical concepts are taught and in laboratory classes, which will be carried out using tools capable of executing the taught models. the subjects taught in previous classes are applied.

At the beginning of the class the students will receive the planning for the topics of the program and the specification of the practical work, A deadline is given for the delivery of the work.

Theoretical classes are given in a classroom equipped with a projector and Powerpoint slides.

The practical classes are held in rooms equipped with computers and projector.

The assessment is divided into the obligatory parts: a practical work delivered in 2 phases; 2 tests. Practical works and essays are done in groups and tests, individually (see evaluation methods).

Evaluation method

The assessment is divided into the obligatory parts: a practical work delivered in 2 phases; 2 tests. Practical works and essays are done in groups and tests, individually. The reports for both phases must be delivered.

• The score is a weighted average of the practical work (Phase I = 20%; Phase II =
30%) and test score (Test 1= 25%, Test 2 = 25%).
• Practical work: A compulsory practical work delivered in two phases, consisting
of 20% (of the final) in Phase 1 and 30% (of the final) in the 2nd Phase. For
frequency, the weighted average of the two phases should be greater than or
equal to 9.5.
• Test: 2 tests worth 25% each of final grade. The student must have an average of
the tests with a minimum grade of 9,5. Otherwise he/she has to do a re-sit
exam, but only if s/he got frequency given by the practical work.
• The final grade is a weighted average of the grades of the test (25% each), of the
1st phase of practical work (20%) and the 2nd phase of practical work (30%).
• The tests are without consultation. The tests will be in person. If it is not
possible, they will go online.

Access to the re-sit exam period is given only to students who have valid frequency, but not passed during continuous assessment, or the students that want to improve their grades.

• During the re-sit exam period, the exam grade replaces the note of the tests, for students with frequency obtained in the semester in which they are carrying out the examination, maintaining the rule of minimum grade of 9.5 values for the exam (replacing the minimum grade of 9,5 on the average of tests), to partially fulfill the criteria for approval.
• Therefore, if the re-sit exam grade is lower than 9,5 the student is not approved, otherwise the final grade is equal to (exam grade + practical work)/2. Students without any assessment during the semester will be classified as "Absent".
• For students with valid frequency obtained in a previous semester, the final grade is equal to (average of the tests, or the grade of the resit exam +  the grade of the practical work in the previous year )/2, where the students try to get approval either during continuous assessment or resit exam period, respectively.

Note the “melhorias” take place exclusively at the “época de recurso”.
• The improvement ("melhoria") of all components can only be made by attending the UC in the academic year immediately after the one in which approval was obtained, submitting the student, in that year, to all components of assessment throughout the period of
classes, needing authorization of the professor for its realization

Subject matter

Introduction to Model-Based Development

• Definition of models and metamodels
• Motivation for using models

Systems Engineering Process

• Definition of fundamental concepts of Systems Engineering
• Activities of the systems development process

Business Process Models with BPMN

• Main concepts
• BPMN notation for modeling BPM business processes
• BMP modeling styles
• Tools for building models in BPMN

SysML models

• Introduction to SysML
• Overview of static and dynamic SysML models
• Transition and mapping of elements from BPMN models to SysML

SYSML structure diagrams

• Requirements diagram
• Block definition diagram
• Internal block diagram
• Package diagram

SYSML behavior diagrams

• Use case diagram
• Activity diagram
• Working machine diagram State
• Sequence Diagram
• Parametric Diagram

Analysis

• Building the Requirements Diagram
• Building Static and Dynamic SysML Models for the Analysis Phase
• Tracing Requirements Diagram Elements to Other Models

Design

• Mapping Requirements Diagram to design phase models
• Refining Static and Dynamic SysML Models for the design phase
• Architectural Views with SysML
• Basic Architectural Patterns with SysML
• Traceability between design models

Modeling for Large-Scale Reuse

• Introduction to Software Product Lines
• Building the Feature Model
• Identifying, modeling and managing variability

Programs

Programs where the course is taught: