Requirement Gathering and

Analysis
Author : Agung Aldhiyat
 Causes of Project Failure

Sources :
Project Failures, Project Management, IT Cortext (2017)
 Three Keys of Project Goal

On
Meet user requirements and needs
Specs

On
Budge Meet budgets allocation
t

On
Meet time schedule
Time

Sources :
Project Management Body of Knowledge
Tuning the
Perspective
 Background of
Requirement Gathering and Analysis

• Mapping a real world problem and Find user needs.

• Requirement analysis is a frontend methodology that allows users

and/or systems analysts to convert a real world problem into a
pictorial diagram or other logical representation that can
subsequently be used by the systems developers and/or
programmers to design an information system.

• Simplifies project management, risk management, and resource

management.

Sources :
Information System Consultant Handbook System Analysis and Design, William S. Davis (1999)
 General Phase of
Requirement Gathering and Analysis

Study Current Business Model Old Logical Model New Logical

Environment System System

Model New Physical

Select Best Design Evaluate Alternative
Environment

Create Structured
Specification

Sources :
Information System Consultant Handbook System Analysis and Design, William S. Davis (1999)
 Study Current Business
Environment

Role Rule Routes Responsibilities

Who do the Access Flow of Who done the

process Restriction business process
and Limitation process
for each
process

Sources :
Business Process Improvement, James Harrington
 Study Current Business
Environment
• Study the flow of current Business Process
• Are the current processes comes with a good output?
• Are the customer needs can be fill?
• How good process use the resources (man, machine, material, money)?
• How long each process take the time?
• How much cost for each process?

Sources :
Business Process Improvement, James Harrington
 Model the Current and Proposed
Logical System

To ensure that your perspective are meets the user perspective

Tools :
• Workflow Diagram
• Rich Picture Diagram
• Business Process Model Notation
• Activity Diagram
• etc

Sources :
Business Process Improvement, James Harrington
 Process Improvement

Making Producing the

Process desired results
Effective
Being able to adapt to
changing customer
and business needs

Making Making
Process Process
Adaptable Efficient

Minimizing the
Sources : resources used
Business Process Improvement, James Harrington
 Process Improvement

Eliminate

E Eliminate the issue process that disturb the process cycle,

or eliminate the process we don’t need.

Simplify
S Keep the process stay simple, or make it simple.

I Integrate
Integrated with the other process if there is a lot of similar process
that have similar input and similar output.

A
Automation
Selected the process that can be automated.

Sources :
Business Process Improvement, James Harrington
 Select Best Process

• Eliminate Errors
• Minimize Delays
• Maximize the use of assets
• Promote Understanding
• Easy to Use
• Customer Friendly
• Adaptable to Customers Changing Needs
• Provide the Organization with a
Competitive Advantage

Sources :
Information System Consultant Handbook System Analysis and Design, William S. Davis (1999)
Finding the
Best Solution
 The Artifact of
System Requirement Gathering and Analysis

• System / Software Requirement

Specification (SRS)
• Requirement Workpapers
• Technical Documentation
• etc

Sources :
Information System Consultant Handbook System Analysis and Design, William S. Davis (1999)