13
INFORMATION SYSTEMS @ X INFORMATION SYSTEMS @ X INFO425: Systems Design INFO425: Systems Design Systems Design Project Systems Design Project Deliverable 2 Deliverable 2

INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

Embed Size (px)

Citation preview

Page 1: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

INFO425: Systems DesignINFO425: Systems Design

Systems Design ProjectSystems Design ProjectDeliverable 2Deliverable 2

Page 2: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Deliverable 2 ContextDeliverable 2 Context

You have defined and prioritized your requirementsYou have defined and prioritized your requirements You have defined your deployment You have defined your deployment

environment/implementation alternatives environment/implementation alternatives Now it is time to perform selected design tasks, Now it is time to perform selected design tasks,

including:including: Developing data flow diagram and structure chartDeveloping data flow diagram and structure chart Developing detailed sequence diagramsDeveloping detailed sequence diagrams Developing Design Class diagramDeveloping Design Class diagram Create basic method definitionsCreate basic method definitions

Page 3: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Data Flow Diagrams and Structure ChartData Flow Diagrams and Structure Chart

Based on the event table in deliverable 1, draw the DFD with Based on the event table in deliverable 1, draw the DFD with automation system boundary (refer Figure 10-2)automation system boundary (refer Figure 10-2)

Develop a high-level structure chart using transaction analysisDevelop a high-level structure chart using transaction analysis (refer Figure 10-10)(refer Figure 10-10)..

For one of the event in your event table in deliverable 1 you will 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 create a DFD fragment, exploded view of the DFD, and rearranged view of the DFD (refer Figures 10-11, 10-12, and 10-13).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 Based on the rearranged view of the DFD, develop a first draft of the structure chart using transform analysis (refer Figure 10-of the structure chart using transform analysis (refer Figure 10-14)14)

Page 4: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Sequence DiagramsSequence Diagrams

For each of the events in your event table in deliverable For each of the events in your event table in deliverable 1 you will create a detailed sequence diagram that 1 you will create a detailed sequence diagram that includes :includes :

““Handler” classHandler” class User interface / boundary classUser interface / boundary class Domain classesDomain classes Data access classesData access classes

Page 5: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Design Class Diagram (partial)Design Class Diagram (partial)

Enhance the Domain Class diagram from INFO415 deliverable Enhance the Domain Class diagram from INFO415 deliverable 3 so that it contains all required Domain Classes to handle all 3 so that it contains all required Domain Classes to handle all eventsevents

Add Handler classesAdd Handler classes Add Navigation Visibility (based on your sequence diagramsAdd Navigation Visibility (based on your sequence diagrams

…….which classes need to invoke others?.which classes need to invoke others?

For each Domain Class, add Methods required - based on For each Domain Class, add Methods required - based on sequence Diagram:sequence Diagram:

Send a message Send a message Respond to a message Respond to a message

You DO NOT need to add your boundary or data access You DO NOT need to add your boundary or data access classes to the diagramclasses to the diagram

Page 6: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Method DefinitionsMethod Definitions

For each method on your Class Diagram, create a For each method on your Class Diagram, create a 1 – 2 sentence description of the purpose of each 1 – 2 sentence description of the purpose of each method.method.

Page 7: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

First-Cut Sequence Diagram for the First-Cut Sequence Diagram for the Look Up Item Look Up Item AvailabilityAvailability Use Case Use Case

Page 8: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Adding Data Access Layer for Adding Data Access Layer for Look Up Item AvailabilityLook Up Item Availability Use CaseUse Case

Page 9: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Complete Complete Look Up Item AvailabilityLook Up Item Availability Use Case with View Use Case with View LayerLayer

Page 10: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Complete Complete Maintain Product InformationMaintain Product Information Use Case Use Use Case Use Case with View LayerCase with View Layer

Page 11: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Updated Design Class Diagram Updated Design Class Diagram for the Domain Layerfor the Domain Layer

Page 12: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

Deliverable Deliverable

A Word documentA Word document 11 point Arial font11 point Arial font Double spaced – 1.25 inch margin top and bottom. Double spaced – 1.25 inch margin top and bottom.

1 inch left and right. 1 inch left and right. Good document format – same as previous Good document format – same as previous

deliverabledeliverable

Page 13: INFORMATION SYSTEMS @ X INFO425: Systems Design Systems Design Project Deliverable 2

INFO425: Systems DesignINFO425: Systems Design

INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X

GradingGrading

Document Structure – 10%Document Structure – 10% Document Content – 90%:Document Content – 90%:

Data Flow Diagrams and Structure Chart -20%Data Flow Diagrams and Structure Chart -20% Sequence Diagrams – 30%Sequence Diagrams – 30% Design Class Diagram – 25%Design Class Diagram – 25% Method descriptions – 15% Method descriptions – 15%