Practical Classes

First class (18th of September) 

In the first practical class, during the week starting on the 18th of September, we will be discussing the following articles:

Note: To access some of these articles you may need to be within the IST's network or go through it (e.g. via a  VPN or the  authenticated proxy).

To ensure a lively and interesting discussion,  you should read the papers previously and make a list of two or three topics that you would like to discuss or to highlight during the class.

Second class

For the second practical class, on September 25,  you have to read two articles: (1) MIcroservices by James Lewis and Martin Fowler; and (2) Scalable Web Architecture and Distributed Systems by Kate Matsudaira. For each one of the articles, identify the software elements and their relations, the properties of both, and how they allow us to reason about the system architecturally significant requirements.

Third class

For the third practical class, on the 2nd of November, we will continue analysing systems according to a software architecture perspective and we will focus on Scalable Web Architecture and Distributed Systems by Kate Matsudaira. Identify the software elements and their relations, the properties of both, and how they allow us to reason about the system architecturally significant requirements.

Fourth class

In the fourth practical class, we will start working on he Graphite case study. Each group should prepare three quality attribute scenarios, focus on performance, and the tactics used to achieve the scenarios, to be discussed during the class. I recommend that you read chapter 8 of SAinP before writing the scenarios. 

Fifth class

In the fifth practical class, we will continue working on he Graphite case study. Each group should prepare three quality attribute scenarios, consider other qualities, like, usabilityavailability, and modifiability, and the tactics used to achieve the scenarios, to be discussed during the class. I recommend that you read the respective chapters of SAinP before writing the scenarios.