Deliverable #9 – Detail Design Subsystem Design and Realization ALL of your design class model elements must have the package or subsystem they are associated with in with the class header as shown in lecture 33 (think: University Artifacts). Packages and Subsystems should have a stereotype indicating the layer in which they reside. Sequence Diagrams may require UML Notes to clarify interactions. Use them as necessary. Ensure you list the text of the Use Case Specification in the left margin (column?) of each sequence diagram.

Deliverable #9 - Traceability The second major part of this deliverable is to realize traceability of each function captured in Use Cases and in the Analysis Model here in the Design Model. It one thing to have traceability from Use Cases to analysis classes. It is quite another thing to trace analysis class traceability into the Design Model, as realized in subsystems, packages, classes, and in layers. Please note that this is a major undertaking for this deliverable and will take time!

Deliverable #9 – Iteration Plan due: 28 March 2012 This is to be a comprehensive treatment of iterations starting with the Construction Phase. This should be based on scenarios in Use Cases. It should not be supporting activities such as refining the database, developing stored procedures, etc. It is used to track the development of the application and is an essential tool used to determine if we are on schedule. You may use any reasonable format, but remember, each iteration has most of the core disciplines as activities! (requirements, analysis and design, testing, implementation, configuration, environment, program management, etc.)

Deliverable #9 - Questions These are questions whose answers are to accompany this deliverable. You may answer these in a Word document. STUDY these questions and answers. Ensure that they are complete, as you will see them again! What is a proxy class and what is its purpose? What do we mean by a dependency? What are the pros and cons of dependencies? What is an association and how does it differ from a dependency? Under what circumstances is the modeling of only a subsystem interface sufficient in a sequence diagram? In behavioral modeling, when must the interface be realized? How is it done? What kind of model(s) is/are used to capture the details of the inner workings of a subsystem? Why should dependencies on a subsystem be on the subsystem interface?