LECTURE 6 – REQUIREMENT
ANALYSIS
1
•
System Requirements
•
Requirements Analysis Techniques
Software Project Management
Maria Petridou
SYSTEM REQUIREMENTS

System Requirements are all of the capabilities that the new
system must have.
From Planning Phase
The systems request produced in the planning phase lists the highlevel business requirements of the proposed system.
2
Software Project Management
Maria Petridou
SYSTEM REQUIREMENTS
Analysis Phase


The first step in the analysis phase is to develop an analysis strategy in
order to define the system requirements.
The aim is to turn the precise business requirements into precise
system requirements.
Software Project Management
3
Maria Petridou
SYSTEM REQUIREMENTS

The purpose of defining requirements is to provide information for the
next steps in the analysis phase (use cases, process model, data model,
etc.) and to define the scope of the system.

The analysis phase involves:
1. Understanding current system
2. Identifying improvements
3. Define requirements for new system
4
Software Project Management
Maria Petridou
SYSTEM REQUIREMENTS

Stakeholders and system analysts should work in co-operation in
order to determine the system requirements.

Stakeholders – users, sponsors, technical staff.

An analysis strategy consists of requirements analysis techniques
and information gathering techniques.

System requirements are divided in
Functional: Activities the system MUST perform.
( Information & Process)
 Non-functional: Characteristics of the system other than activities
( Performance, Operational, Security, Cultural, Political)

5
Software Project Management
Maria Petridou
SYSTEM REQUIREMENTS

Exercise 1:
Determine which in the following are functional requirements and
which ones are non-functional requirements. (Dennis&Wixom, Ch.4).
-
-
Be accessible to web users
Include the company standard logo and colour scheme
Restrict access to profitability information
Provide management reports
Have 2-second maximum response time for predefined queries, and 10minute maximum response time for ad-hoc queries.
Include sales information that is updated at least daily.
Print additional reports in other languages.
Include actual and budgeted cost information.
6
Software Project Management
Maria Petridou
REQUIREMENTS ANALYSIS TECHNIQUES
Main requirements analysis techniques are the following:
 Business process automation (BPA)
The basic way in which the organisation operates is left unchanged and computer
systems are used to automate some of the work. Focus on automate processes. No
changes to organisation.
 Business process improvement (BPI)
Moderate changes to the way in which the organisation operates in order to
achieve improvements. Focus on improve processes. Moderate changes to
organisation.
 Business process re-engineering (BPR)
Uses new ideas and technology to make major changes to the way in which the
organisation operates. Focus on innovation. Major changes to organisation.
7
Software Project Management
Maria Petridou
REQUIREMENTS ANALYSIS TECHNIQUES
Some other requirement analysis techniques are:
8
Software Project Management
Maria Petridou
REQUIREMENTS ANALYSIS TECHNIQUES
9
Software Project Management
Maria Petridou
REQUIREMENTS ANALYSIS TECHNIQUES
10
Software Project Management
Maria Petridou
REQUIREMENTS ANALYSIS TECHNIQUES

Each requirements analysis technique has different impact on the
project:
Reading: (Dennis&Wixom, chapter 4).
Software Project Management
11
Maria Petridou