The goal of this lab is to start with the creation of a component model.

Lesson outline

• Students will get the feedback about the Design Patterns implemented based on the review from last week. Please, try to fix as many issues as possible. If you do not get already this week, next week you will get the feedback for the additional two patterns implemented last time;
  
• We will follow an approach for the identification of software components from software requirements analysis. The approach is based on 3 macro-phases: 1. identification of components, 2. definition of components interactions, 3. definition of components specifications.
  
• In this seminar, the teacher will have the introduction about the design of software components and will go through the first part: 1. identification of components.
• The task of the students is to apply the approach for the identification of components: dividing classes into packages (within the class diagram). In every package, define both business and system interfaces.
• Students create an early sketch of the component specification architecture as a component diagram (example at page 30 of the slides). The diagram will be refined in the next iterations.
• What to submit in this iteration:
  • One *class diagram with packages and interfaces identified* that can be derived from the reworked design class diagram from previous sessions;
    
  • An initial *component diagram* (similar to the one on page 30 of the slides) - will be refined the next iterations;
    

Note: if you export the diagram as an image *do not take a screenshot* just go to Project->Export->Active Diagram as Image... you can then select the format (jpg/png/etc...) and even export in 300dpi or higher resolution). Alternative way, just go to Tools->Doc Composer drag & drop the diagram and then on the top right Save as PDF...

Please ensure to submit in the homework vault by the deadline of Mon 21.11.22 23:59.

Study materials