INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 3 Requirements Models.

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

PDP 4 – Writing academic Reports. Academic assignments In higher education, assignments are submitted in several formats –Essay –Presentation –Dissertation.
BIS 360 – Lecture Seven Process Modeling (Chapter 8)
Instructions for completing the ES089g term paper.
INFO 425 Week 31 INFO 425 Design Problem I Week 3 – SDS Improvements Glenn Booker.
Chapter 7 Using Data Flow Diagrams
Topics Creating DFD Physical and logical DFD Event driven modeling
Report Writing Goal: Tell the readers about your team’s: –Objectives –Background –Recommendations –Reasons.
Chapter 9 Using Data Flow Diagrams
© Copyright 2011 John Wiley & Sons, Inc.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Data and Process Modeling.  Describe data and process modeling, and name the main data and process modeling techniques.
DCS Goal 5.01 – 5.05 Review. Sections Covered 5.01 – Font Attributes 5.02 – Editing Tools 5.03 – Business Letters 5.04 – Memo and – Simple.
A research proposal is a document written by a researcher that provides a detailed description of the proposed program. It is like an outline of the entire.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
TECHNICAL WRITING November 16 th, Today Effective visuals. Work on Assignment 6.
Chapter 5: Modeling Systems Requirements: Events and Things
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
Data flow diagrams.
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
Data and Process Modeling
Systems Analysis and Design in a Changing World, Fifth Edition
Lesson 7 Guide for Software Design Description (SDD)
Systems Analysis and Design in a Changing World, Fifth Edition
1 Chapter 2 Revision: Documentation DFD System FC.
Chapter 7 Using Data Flow Diagrams
SAD - DFD Context Diagrams
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
6 Systems Analysis and Design in a Changing World, Fifth Edition.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 1 Project Statement of Work Outline.
Effective Communication for Colleges, 10 th ed., by Brantley & Miller, 2005© Chapter 11 Chapter 11 – Slide 1 Reports, Proposals, and Instructions for the.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Systems Analysis and Design in a Changing World, 6th Edition
Introduction To Engineering Bike Lab 1 – 4 Report Agenda: Lab Report Format Team Writing Outline Lab 1 Report.
Senior Project Rough Draft
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 2.
INFO275 Database Management Term Project. Overview Your project will be to define, design and build a functioning database, to support an application.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions.
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 1.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Technical Report Outline Title Page Frontispiece Abstract Table of Contents List of Figures/ List of Tables.
INFORMATION X INFO415: Systems Analysis.
Steps in Writing an Essay
Formal Report Strategies. Types of Formal Reports Informational Presents Info Analytical Presents Info Analyses info and draws conclusions Recommendation.
MT320 MT320 Presented by Gillian Coote Martin. Writing Research Papers  A major goal of this course is the development of effective Business research.
Systems Analysis and Design in a Changing World, Fourth Edition
FINAL PAPER Sociology 1301: Introduction to Sociology.
Is 581 assist Inspiring Minds/is581assistdotcom FOR MORE CLASSES VISIT
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
Business System Development
Sociology 1301: Introduction to Sociology
DATA REQIREMENT ANALYSIS
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Systems Design Project Deliverable 3
Csc354 fall 2016 assignment 3 design spec
Engineering Technical Writing
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 3 Requirements Models

INFO415: Systems Analysis INFORMATION X 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  Its time to logically model the requirements from an event and object perspective.

INFO415: Systems Analysis INFORMATION X Objectives  Your team’s objectives are to:  Develop an Event Table modeling 4-6 key events the system must respond to.  Develop a Class diagram that models the objects required to support your events  Develop a Functional Decomposition Diagram  Draw a context diagram for each sub-system  Draw DFD fragments for each sub-system and combine all the DFD fragments  Draw a Decision Table for Decision situation

INFO415: Systems Analysis INFORMATION X 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 deliverables  Your audience: your sponsor and the user(s) you interviewed to define requirements. Your models will also be used by designers to develop physical design documents, but this is a secondary consideration.

INFO415: Systems Analysis INFORMATION X Grading  Document structure and grammar – 10% For the proposed system  Event table– 15%  Class Diagram/descriptions – 20%  Functional Decomposition Diagram (3 level hierarchy) – 10%  Context diagram for each sub-system (minimum three sub-systems) – 15%  DFD Fragments for each sub-system and combining all the fragments for a sub-system – 20%  Decision Table for one decision situation – 10%

INFO415: Systems Analysis INFORMATION X Document Contents  Introduction (couple of paragraphs)  What’s in this document  Background (1/2 page – 1 page)  No more than a page – tell reader what has happened to get to this point in the project Remember to Introduce each section of your document – tell the reader what to expect!! When presenting a model, describe what the symbols mean!

INFO415: Systems Analysis INFORMATION X Document Contents  Event Table.  4-6 Events – corresponds to the business processes you modeled using activity diagrams in deliverable 2  Use the Event Table  Make sure you introduce the section – describe what is in the table!

INFO415: Systems Analysis INFORMATION X Information about Each Event in an Event Table: Catalog of Information about Each Use Case (Figure 5-15)

INFO415: Systems Analysis INFORMATION X Document Contents  Class Diagram  Part 1: Diagram. >Must have at least 6 classes in your model. >At least 1 class must be associative (resolves a many to many relationship) >At least 1 class must store information about an event or transaction >Label each relationship in two directions >No many to many relationships! >Use class cardinality notation from text  Part 2: Class Descriptions. For each class provide: >Description for each class (what information does the class contain?) >Primary Key. >A minimum of 4 non-key attributes

INFO415: Systems Analysis INFORMATION X Example: Course Enrollment Design Class Diagram (Figure 5-40)

INFO415: Systems Analysis INFORMATION X Document Contents Use a table like the following to document each class Class Name Entity X Description This entity containing information regarding…. Attributes Attribute Name(s) Description Primary Key Key Attribute (may be more than one attribute) Describes the attribute Non-KeyAttributes Attribute 1Describe… Attribute 2 Etc.

INFO415: Systems Analysis INFORMATION X Functional Decomposition Diagram (FDD)  Draw an FDD for three levels Level 1: Proposed System Level 2: Sub-systems (minimum three) Level 3: Modules (Sub-sub-systems- minimum three modules for each sub-system )

INFO415: Systems Analysis INFORMATION X Develop Context Diagram for each sub- system (minimum of 3 sub-systems) RMO Order-Entry Subsystem (Figure 6-11)

INFO415: Systems Analysis INFORMATION X Three Separate DFD Fragments for Course Registration System

INFO415: Systems Analysis INFORMATION X Combining DFD Fragments to Create Event- Partitioned System Model (Figure 6-8)

INFO415: Systems Analysis INFORMATION X Decision Table  Draw a decision table for one decision-situation  Summarize complex decision logic  Incorporate logic into the table to make descriptions more readable

INFO415: Systems Analysis INFORMATION X Reminders  Start NOW – there is a large amount of work in this deliverable.  Divide and Conquer! You will struggle if you don’t do this successfully. Suggest that you:  Meet initially to divide work and come up with a plan – when wil you meet to review and consolidate  Go off and work individually on your piece of the project  Meet to review, as required.  Have a final meeting to consolidate.  Assign one person to be responsible for final document edits – document should read as if written by one person!! This means you may decide to give one group member less modeling work – document consolidation is time consuming.  Each team member should read the consolidated document, suggest revisions, before handing the document in.