CSCI 639 Topics in Software Engineering Assignment #5 Fall 2008

Assignment #5: Detailed Design (Subsystem Realization )

Subsystem Design and Realization For each subsystem, you are to provide an interaction diagram of at least two responsibilities accommodated by the subsystem from its interface. (lecture 32) No more than one interaction diagram for one subsystem should address accommodating persistency. You should, however, include one that does this. This means that of all your subsystem realizations, you may only show one interaction diagram that addresses persistency. I am thus after you to show a number of realizations that your subsystems must accommodate. You should also present the corresponding communications (collaboration) diagram. Note the differences. For each subsystem, you are also to provide the internal structure of your subsystems, like appropriate slides in lecture 33. This is your VOPC. These are to be fully annotated (dependencies, communications, multiplicities, etc.) You are to annotate via stereotyping which objects are persistent in your modified VOPC as well as any other stereotyping you feel is necessary. (See lectures on class design and persistency)

Subsystem Design and Realization All messages in your sequence diagrams need to be numbered as shown in lecture 32 (numbers and their sub-parts). 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. Extra credit and VERY NICE Touch: Try to list the text of the Use Case Specification in the left margin (column?) of each sequence diagram.

Deliverable #9 – Iteration Plan Revisit your Iteration Plan. In view of this assignment, you may need to revise it a bit. This is to be a comprehensive treatment of iterations particularly 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 continue to use any reasonable format, but remember, each iteration has most of the core and supporting disciplines as activities! (requirements, analysis and design, testing, implementation, configuration, environment, program management, etc.) Again, lots of work…but this is your last assignment for this course.

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. 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? 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?