130 likes | 150 Views
Develop data flow diagram, structure chart, sequence diagrams, and design class diagram based on defined requirements and deployment environment alternatives. Create method definitions and diagrams for events. Finalize domain and data access layers for specific use cases. Deliverable in Word document format with specific formatting guidelines. Graded on document structure and content.
E N D
Deliverable 2 Context • You have defined and prioritized your requirements • You have defined your deployment environment/implementation alternatives • Now it is time to perform selected design tasks, including: • Developing data flow diagram and structure chart • Developing detailed sequence diagrams • Developing Design Class diagram • Create basic method definitions
Data Flow Diagrams and Structure Chart • Based on the event table in deliverable 1, draw the DFD with automation system boundary (refer Figure 10-2) • Develop a high-level structure chart using transaction analysis (refer Figure 10-10). • For one of the event in your event table in deliverable 1 you will create a DFD fragment, exploded view of the DFD, and rearranged view of the DFD (refer Figures 10-11, 10-12, and 10-13). • Based on the rearranged view of the DFD, develop a first draft of the structure chart using transform analysis (refer Figure 10-14)
Sequence Diagrams • For each of the events in your event table in deliverable 1 you will create a detailed sequence diagram that includes : • “Handler” class • User interface / boundary class • Domain classes • Data access classes
Design Class Diagram (partial) • Enhance the Domain Class diagram from INFO415 deliverable 3 so that it contains all required Domain Classes to handle all events • Add Handler classes • Add Navigation Visibility (based on your sequence diagrams • ….which classes need to invoke others? • For each Domain Class, add Methods required - based on sequence Diagram: • Send a message • Respond to a message • You DO NOT need to add your boundary or data access classes to the diagram
Method Definitions • For each method on your Class Diagram, create a 1 – 2 sentence description of the purpose of each method.
First-Cut Sequence Diagram for the Look Up Item Availability Use Case
Adding Data Access Layer for Look Up Item Availability Use Case
Complete Maintain Product Information Use Case Use Case with View Layer
Deliverable • A Word document • 11 point Arial font • Double spaced – 1.25 inch margin top and bottom. 1 inch left and right. • Good document format – same as previous deliverable
Grading • Document Structure – 10% • Document Content – 90%: • Data Flow Diagrams and Structure Chart -20% • Sequence Diagrams – 30% • Design Class Diagram – 25% • Method descriptions – 15%