Case Studies

Three case studies for the groups to present and discuss during the practical classes:

First assignment

Presentation

In this assignment, the goal is to analyse the architecture of your case study to prepare a presentation to deliver it during the practical classes.

In the presentation you should identify the major stakeholders of the system and relate them to the architecturally significant requirements. Moreover, you should present the architecturally significant requirements as scenarios (indicating also their type) and identify the tactics used to achieve them.

In your presentation concentrate on the most relevant aspects of the system under study. More specifically, you should present only 3 or 4 architecturally significant requirements, explaining why you selected them.

The presentations should take between 15 and 20 minutes, so that we have time for discussion at the end of the class.

These assignments are to be submitted into Fénix (the PDF of your presentation, including any notes that you may have with each slide) and should be presented during the practical classes of that week. The due date is according to the group/class/system distribution.

Report

In this assignment, the goal is to analyse your colleagues presentations by asking questions during the presentation and writing a report afterwards. The report should identify the positive and negative aspects of your colleagues presentation, and it should not have more than 2 A4 pages, written using Times 12.

The reports are to be submitted into Fénix. The due date is according to the group/class/system distribution.

Second assignment

Presentation

In the second assignment each group should create a presentation that describes the most important aspects of the software architecture of the case study assigned to it. You should depart from the solution for the first assignment, available here: https://antonioritosilva.org/software-engineering-companion/software-architecture/case-studies/.

To describe the software architecture of your case study, you should use the various viewtypes and styles that we have been talking about in the classes. You should include only the architectural diagrams that you think are the most relevant to capture and to describe the architecture of your case, but you must include at least one view from the module viewtype and another view from the component-and-connector viewtype. 

The evaluation of this last assignment will take into account, among other things, specially the two following aspects of your presentation: (1) that you use correctly the software architecture concepts introduced in the theoretical classes, and (2) that you give a reasonable rationale that explains each of the architectural aspects presented. For (2) is fundamental to follow the provided solution for the first assignment.

These assignments are to be submitted into Fénix (the PDF of your presentation, including any notes that you may have with each slide) and should be presented during the practical classes of that week. The due date is according to the above group/class/system distribution.

Report

In this assignment, the goal is to analyse your colleagues presentations by asking questions during the presentation and writing a report afterwards. The report should identify the positive and negative aspects of your colleagues presentation, and it should not have more than 2 A4 pages, written using Times 12.

The reports are to be submitted into Fénix. The due date is according to the group/class/system distribution.