SYSTEM REQUIREMENT CHANGES

During requirement modeling, system developers must identify and describe all system requirement.

A system requirement is a xtic or feature that must be included in an infos system to satisfy business
requirements and accepted by the user .

System req fall into 5 categories :

1. Output
2. Input
3. Processes
4. Performance
5. Control

2.5 FACT FINDING (FF)

FF is collect info, various ff include:

1. Survey
2. Interview
3. Questionnaire
4. Document Review
5. Observation

2.5.1 FF OVERVIEW

Typically, this activity begins by asking a series of questions such as

1. What business fxn are supported by the current system?

2. What strategic objective and business req must be supported by the new system ?
3. What are the benefits and Total Cost of Ownership (TCO)?
4. What transaction with the system process?
5. What info do user and manager need from the system?
6. Must the new system interfere with the legal system?
7. What security issues exist?
8. What budget and time table constraint will affect system dev?

2.5.2 What, who, when, where, why,& how

FF involves answers to six familiar questions: what, who, when, where, why & how.

The table below shows some sample Questions.

2.6 QUESTIONNAIRE AND SURVEY

In a project, where it is desirable to obtain input from a large number of people, a questionnaire can be
a variable tool. A questionnaire also called a survey is a document containing a number of standard
questions that can be sent to many individuals. A questionnaire can be traditional form or created as a
fill in form and collect data on the internet or the company intranet.

BRAINSTORMING

Brainstorming refers to a small group discussion of a specific problem, opportunity or issue. This
technique encourages new idea, allows team participation, and enables participants to build on each
other’s input and thoughts. Brainstorming can be structured or unstructured.

Keeping accurate records of interview, facts, ideas and observation, is essential to successful system
development. An analyst should document their work according to the following principle:

 Record info as soon as it is obtained

 Use the simplest recording method possible
 Recording findings in such a way that someone else can understand them
 Organize documentation so related material is located easily.

One type of documentation is a narrative list with simple statement about what is occurring, apparent
problem and suggestion for improvement. Other forms of doc are: Data flow diagrams, Flow chart,
Sample forms & Screen capture.
CHAPTER 2: DATA AND PROCESS MODELING
LEARNING GOALS:

1. Describe data and process modeling concept and tools including data flow diagram, a data
dictionary and process description
2. Draw data flow diagram in a sequence from specific to general
3. Describe the relationship btw logical model and physical model

A logical model shows what the system must do regardless of how it should be implemented
A physical model shows how the system should be constructed

Data and process modeling involves three main tools:

1. Data flow diagrams

2. Data dictionary
3. Process description

2.1 Overview of Data and Process modeling

A Data Flow Diagram (DFD) uses various symbols to show how the system transforms input data to
useful information. Other methods include the Entity Relational Diagram (ERD)

2.2 Data Flow Diagram (DFD)

A DFD is an example of this type of visual explanation of system behavior. It shows how data moves via
an info system but does not show program logic or processing step. A set of data flow diagrams provide
a logical model that shows what the system does and not how it does it.

2.2.1 DFD Symbols

A several version of DFD symbols exists

Garne and Sargon Symbol Yourdon Symbol

symbol

APPLY payt Process

Bank Deposit Data Flow

 Students Data store students

Entitities
costumer Costumer

A Process

A process receives input data and produces output that has a different content. Processes contain the
business logic or business rule which transforms the data and produce the required results

Data flow symbol

A data flow symbol is the path for data to move from one part of the info system to another

Data store symbol

A data store is used in a data flow diaram to represent data that the system stored becsuse one or more
processes need to use the data at s later time. A data store must be connected to processes with a data
flow.

Entity Symbols

A DFD shows only external entities that provides data to the system or receives output from the system.
A DFD shows the boundary of the system and how the system interfaces with the outside world.

Example: A student can register at UB and gets his matriculation

A patient who supplies data to the record medical system

Exercise

= True (process to process)

= True (Process to ext

Entity)
2.3 Creating a set of DFDs

During requirement modeling, interview, questionnaire and other techniques were used to gather facts
across a system, now a graphical model of the info system is created based on the FF result. We will use
a three step process to construct a DFD based on grading systems that instructors use to assign final
grades

2.3.1 Guidelines for Drawing DFDs

These guidelines must be followed:

1. Draw the context diagram that fits on 1 page

2. Use the name of the info system as the process name e.g Grading system
3.

Student FINAL GRADE SUBMITTED WORK student

record system

Gradx syst

Gradx report

Grading parameter

Instructor

FIG CONTEXT DIAGRAM

STEP 1: Draw the context diagram

A context diagram is a top level view of an info system that shows the boundary and scope.

To draw a context diagram, start by placing a single process symbol in the center of the page. This
process represents the entire info system and is identified as process 0. Then place the system entities
around the perimeter of the page and use data flow to connect the entity to the central process
RECALL: A data symbol structure cannot be used in a context diagram.

STEP 2: Draw a level 0 Diagram