Download
1 / 4
40 likes | 180 Vues
In week 5's agenda, we'll discuss the significance of architecture documents, specifically the System Architecture Document (SAD), for project stakeholders and participants. We will explore how these documents enhance understanding and collaboration within teams. A case study on flight simulation will aid our discussion. Groups will choose non-simulation applications where the Structural Model pattern is either advantageous or problematic, providing explanations for their choices. We’ll also tackle UML documentation for the Structural Model pattern, creating class and sequence diagrams for enhanced clarity.
E N D
Discussion: who needs an architecture document? In groups, brainstorm • Project participants or stakeholders who might want to see a SAD (system architecture document) • How would it be useful to them?
Case study – flight simulation In groups: • Pick a non-simulation application in which the Structural Model pattern would work well. Explain why you think so. • Pick a non-simulation application in which the Structural Model pattern would not work very well. Explain.
UML for flight simulation In groups: • Imagine you are documenting the Structural Model pattern for a new developer • Draw a class diagram • Draw a sequence diagram • Time permitting, trade diagrams
