Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions - PowerPoint PPT Presentation

About This Presentation
Title:

Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions

Description:

Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions – PowerPoint PPT presentation

Number of Views:106
Avg rating:3.0/5.0
Slides: 15
Provided by: Value453
Category:

less

Transcript and Presenter's Notes

Title: Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions


1
Systems Analysis ProjectDeliverable 2
Gathering System RequirementsInstructions
2
Deliverable Context
  • You have defined a problem area that needs to be
    addressed have defined the scope of your project.
  • Using techniques outlined in class, you will dig
    in to the problem area and define how things are
    done today and how they should be done in the
    future.
  • You will define the functional and technical
    requirements that will be used as input to
    developing system MODELS.

3
Objectives
  • Your teams objectives are to
  • Define the current workflow supporting key
    transactions within the area of the business you
    have chosen to focus on (e.g., Inventory Control,
    Order Processing, etc.)
  • Define the way that the workflow should be
    structured in the future to support processing of
    transactions.
  • Define the most critical functional and technical
    requirements for the parts of the system
    contained within workflow diagrams

4
Deliverable
  • A Word document
  • 11 point Arial font
  • Double spaced 1.25 inch margin top and bottom.
    1 inch left and right.
  • Review comments for Deliverable 1 for document
    structure requirements
  • Your audience your sponsor and the user(s) you
    interviewed to define requirements.
  • Due Monday Nov 6th.

5
Deliverable
  • Document structure and grammar (20)
  • Cover page
  • Section headings
  • Is there an introduction to the document
  • Is there
  • Active tense
  • Good sentence structure, grammar and punctuation
  • Clarity
  • Lack of repetition

6
Deliverable
  • Content (80)
  • Background (10)
  • Current Process Diagrams and narrative (10)
  • Future Process Diagrams and narrative (15)
  • Requirements (35)
  • Results of the information gathering process
    agenda, meeting notes, observations, forms and
    document lists (10)

7
Contents Introduction and Background
  • Introduction (couple of paragraphs)
  • Whats in this document
  • Background (no more than a page)
  • Describes the work you have done so far on the
    project. Present the following
  • Organization and sponsor (just a paragraph!)
  • Problem area you are addressing
  • Scope in terms of data and process
  • Context diagram
  • You are repeating stuff from deliverable 1. Its
    always a good idea to do this with a deliverable
    document. It helps make the document stand
    alone readers do not need to go back and
    review the other document

8
Contents Current Process
  • Using Visio or other drawing tool draw activity
    diagrams (see text pp 133-135) that outlines how
    key transactions are executed today.
  • Be sure to highlight problems with the current
    process in the diagrams.
  • Provide a narrative (paragraph) to go with the
    diagrams.
  • You do not need to document every aspect of the
    process choose 3-5 key business transactions of
    the process. Means 3-5 current activity diagrams.
  • Example. If you are looking at student
    registration, you might develop diagrams for the
    following
  • Determine courses/sections to take
  • Register for courses
  • Generate timetable

9
Contents New Process
  • Construct activity diagrams that describes the
    way that the transactions should be executed in
    the future, with new information system.
  • Provide a narrative to describe the process steps.

10
Content Requirements
  • Document functional and technical requirements
  • You must have at least 12 requirements documented
    (you can have more).
  • At least 4 requirements must be non-functional.
  • At least 4 must be functional related to PROCESS
  • At least 4 must be functional related to DATA

11
Content Requirements
  • Use the following to document each of your
    requirements
  • Remember, these are the detailed requirements
    that support the new process you have defined

Requirement number Assign a number (e.g. F1 or T1)
Requirement title Short Title
Requirement text Short description of the requirement
Requirement type Functional/Data
Requirement details and constraints Specify requirement details Business rules and exceptions
Revision date and reversion number Version1.0
Criticality Must
12
Process
  • Remember you are trying answer 3 basic
    questions

13
Process
  • Use at least 3 fact finding techniques to answer
    questions
  • In an appendix, include the results of these
    techniques
  • Agenda and interview notes
  • Documented results of observation session
  • List of forms and documents reviewed attach
    copies of forms if possible (DO NOT ATTACH
    DOCUMENTS)

14
Before You Begin
  • We will get some practice with diagramming and
    requirements documentation techniques in the next
    week.
Write a Comment
User Comments (0)
About PowerShow.com