The goal of this lab is to complete an initial component model that will be the basis of the deployment.

Lesson outline

• The teacher explains the basic principles of component design (slides 1-10 of Component Design).
• The teacher explains software architecture guidelines and how our current models fit the guidelines (slides 8-12 of Architecture design).
  
  • Software Architecture Guidelines - Design Fundamentals at MSDN
  • The iDesign method to Software Architecture by Juval Löwy
  • Clean Architecture by Robert C. Martin
• Students create a new component model following the iDesign/clean/MSDN architecture style. Name components and interfaces in a way that ensures understanding of the model at a glimpse.
• Students document interfaces related to the following use case. More specifically, the GUI component will be specified as a flow of events put as a note on the component diagram. interfaces of corresponding managers, engines, and data access components will be specified as method signatures (with possible pre-, post-conditions, and invariants). 
  • "Project version is uploaded to the system in the form of a zip archive, which contains the project source files. After unpacking the archive, the system verifies that the source files are correct (e.g., they have the correct syntax with respect to the programming language used). If a problem is detected, a notification is sent to the person or external system that uploaded the version to the QualityIS. After the successful upload of the project version, the defined basic analyses will be started automatically."
• Deadline: 2.12. at 06:00.