Upload
miya
View
43
Download
0
Embed Size (px)
DESCRIPTION
Systems Analysis Project Deliverable 3 Requirements Models. Deliverable 3 Context. You have defined your problem and built a set of activity diagrams that outline what the new/modified information system needs to do. You have defined key functional and non-functional requirements - PowerPoint PPT Presentation
Citation preview
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
INFO415: Systems AnalysisINFO415: Systems Analysis
Systems Analysis ProjectSystems Analysis ProjectDeliverable 3Deliverable 3
Requirements ModelsRequirements Models
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Deliverable 3 ContextDeliverable 3 Context
You have defined your problem and built a set of You have defined your problem and built a set of activity diagrams that outline what the new/modified activity diagrams that outline what the new/modified information system needs to do.information system needs to do.
You have defined key functional and non-functional You have defined key functional and non-functional requirementsrequirements
Its time to logically model the requirements from an Its time to logically model the requirements from an event and object perspective.event and object perspective.
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
ObjectivesObjectives
Your team’s objectives are to:Your team’s objectives are to: Develop an Event Table modeling 4-6 key events the system Develop an Event Table modeling 4-6 key events the system
must respond to. must respond to. Develop a Class diagram that models the objects required to Develop a Class diagram that models the objects required to
support your eventssupport your events Develop a Functional Decomposition DiagramDevelop a Functional Decomposition Diagram Draw a context diagram for each sub-systemDraw a context diagram for each sub-system Draw DFD fragments for each sub-system and combine all Draw DFD fragments for each sub-system and combine all
the DFD fragmentsthe DFD fragments Draw a Decision Table for Decision situationDraw a Decision Table for Decision situation
INFO415: Systems AnalysisINFO415: Systems Analysis
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
deliverablesdeliverables Your audience: your sponsor and the user(s) you Your audience: your sponsor and the user(s) you
interviewed to define requirements. Your models interviewed to define requirements. Your models will also be used by designers to develop physical will also be used by designers to develop physical design documents, but this is a secondary design documents, but this is a secondary consideration. consideration.
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
GradingGrading
Document structure and grammar – 10%Document structure and grammar – 10%
For the proposed systemFor the proposed system Event table– 15%Event table– 15% Class Diagram/descriptions – 20%Class Diagram/descriptions – 20% Functional Decomposition Diagram (3 level hierarchy) – Functional Decomposition Diagram (3 level hierarchy) –
10%10% Context diagram for each sub-system (minimum three Context diagram for each sub-system (minimum three
sub-systems) – 15%sub-systems) – 15% DFD Fragments for each sub-system and combining all DFD Fragments for each sub-system and combining all
the fragments for a sub-system – 20%the fragments for a sub-system – 20% Decision Table for one decision situation – 10%Decision Table for one decision situation – 10%
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Document ContentsDocument Contents
Introduction (couple of paragraphs)Introduction (couple of paragraphs) What’s in this documentWhat’s in this document
Background (1/2 page – 1 page)Background (1/2 page – 1 page) No more than a page – tell reader what has happened to get to this point No more than a page – tell reader what has happened to get to this point
in the project in the project
Remember to Introduce each section Remember to Introduce each section of your document – tell the reader of your document – tell the reader
what to expect!! When presenting a what to expect!! When presenting a model, describe what the symbols model, describe what the symbols
mean!mean!
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Document ContentsDocument Contents
Event Table.Event Table. 4-6 Events – corresponds to the business processes you 4-6 Events – corresponds to the business processes you
modeled using activity diagrams in deliverable 2modeled using activity diagrams in deliverable 2 Use the Event TableUse the Event Table Make sure you introduce the section – describe what is in the Make sure you introduce the section – describe what is in the
table!table!
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Information about Each Event Information about Each Event in an Event Table: in an Event Table: Catalog of Information about Each Use CaseCatalog of Information about Each Use Case (Figure 5-15)(Figure 5-15)
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Document ContentsDocument Contents
Class DiagramClass Diagram Part 1: Diagram.Part 1: Diagram.
> Must have at least 6 classes in your model.Must have at least 6 classes in your model.> At least 1 class must be associative (resolves a many to many At least 1 class must be associative (resolves a many to many
relationship)relationship)> At least 1 class must store information about an event or transactionAt least 1 class must store information about an event or transaction> Label each relationship in two directionsLabel each relationship in two directions> No many to many relationships!No many to many relationships!> Use class cardinality notation from text Use class cardinality notation from text
Part 2: Class Descriptions. For each class provide:Part 2: Class Descriptions. For each class provide:> Description for each class (what information does the class contain?) Description for each class (what information does the class contain?) > Primary Key.Primary Key.> A minimum of 4 non-key attributesA minimum of 4 non-key attributes
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Example:Example:Course Course Enrollment Enrollment Design Class Design Class Diagram Diagram (Figure 5-40)(Figure 5-40)
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Document ContentsDocument Contents
Use a table like the Use a table like the following to document following to document each classeach class
Class NameClass Name Entity XEntity X
DescriptionDescription This entity containing information This entity containing information regarding….regarding….
AttributesAttributes Attribute Attribute Name(s)Name(s)
DescriptionDescription
Primary KeyPrimary Key Key Attribute
(may be more than one attribute)
Describes the attribute
Non-Key Non-Key
AttributesAttributes
Attribute 1 Describe…
Attribute 2
Etc.
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Functional Decomposition Diagram (FDD)Functional Decomposition Diagram (FDD)
Draw an FDD for three levelsDraw an FDD for three levels
Level 1: Proposed SystemLevel 1: Proposed System
Level 2: Sub-systems (minimum three)Level 2: Sub-systems (minimum three)
Level 3: Modules (Sub-sub-systems- minimum three Level 3: Modules (Sub-sub-systems- minimum three
modules for each sub-system )modules for each sub-system )
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Develop Context Diagram for each sub-system Develop Context Diagram for each sub-system (minimum of 3 sub-systems)(minimum of 3 sub-systems)RMO Order-Entry Subsystem RMO Order-Entry Subsystem (Figure 6-11)(Figure 6-11)
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Three Separate DFD Fragments for Course Three Separate DFD Fragments for Course Registration SystemRegistration System
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Combining DFD Combining DFD Fragments to Fragments to Create Event- Create Event- Partitioned Partitioned System ModelSystem Model (Figure 6-8)(Figure 6-8)
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
Decision TableDecision Table
Draw a decision table for one decision-situationDraw a decision table for one decision-situation Summarize complex decision logic Summarize complex decision logic Incorporate logic into the table to make descriptions Incorporate logic into the table to make descriptions more readablemore readable
INFO415: Systems AnalysisINFO415: Systems Analysis
INFORMATION SYSTEMS @ XINFORMATION SYSTEMS @ X
RemindersReminders
Start NOW – there is a large amount of work in this Start NOW – there is a large amount of work in this deliverable.deliverable.
Divide and Conquer! You will struggle if you don’t Divide and Conquer! You will struggle if you don’t do this successfully. Suggest that you:do this successfully. Suggest that you:
Meet initially to divide work and come up with a plan – when Meet initially to divide work and come up with a plan – when wil you meet to review and consolidatewil you meet to review and consolidate
Go off and work individually on your piece of the projectGo off and work individually on your piece of the project Meet to review, as required. Meet to review, as required. Have a final meeting to consolidate.Have a final meeting to consolidate. Assign one person to be responsible for final document edits Assign one person to be responsible for final document edits
– document should read as if written by one person!! This – document should read as if written by one person!! This means you may decide to give one group member less means you may decide to give one group member less modeling work – document consolidation is time consuming.modeling work – document consolidation is time consuming.
Each team member should read the consolidated document, Each team member should read the consolidated document, suggest revisions, before handing the document in.suggest revisions, before handing the document in.