Scribd
Upload
33 views

Lecture 03 Requirements Determination

This document summarizes Lecture 3 of the CSE471 System Analysis and Design course, which covers requirements determination. The lecture objectives are to understand how to create requirements definitions, analyze requirements using various techniques, and understand when to use each technique. The lecture is segmented into requirements specification, gathering techniques like interviews and JAD sessions, and other techniques. Key ideas discussed are truly understanding requirements and challenges in collecting information and finding participants. The analysis phase refines ideas into detailed requirements and models. Requirements can be functional or nonfunctional. Common gathering techniques are interviews, JAD, questionnaires, document analysis, and observation.

Uploaded by

Anan tazwar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
33 views

Lecture 03 Requirements Determination

This document summarizes Lecture 3 of the CSE471 System Analysis and Design course, which covers requirements determination. The lecture objectives are to understand how to create requirements definitions, analyze requirements using various techniques, and understand when to use each technique. The lecture is segmented into requirements specification, gathering techniques like interviews and JAD sessions, and other techniques. Key ideas discussed are truly understanding requirements and challenges in collecting information and finding participants. The analysis phase refines ideas into detailed requirements and models. Requirements can be functional or nonfunctional. Common gathering techniques are interviews, JAD, questionnaires, document analysis, and observation.

Uploaded by

Anan tazwar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Course ID: CSE471

Course Title: System Analysis and Design

Lecture 3: Requirements Determination

Prepared by:
Dr. Muhammad Iqbal Hossain
Assistant professor
Department of Computer Science & Engineering
BRAC University.
Objectives
■ Understand how to create a requirements definition.
■ Become familiar with requirements analysis
techniques.
■ Understand when to use each requirements analysis
technique.
■ Understand what and where to use REQUIREMENTS
ANALYSIS STRATEGIES

2
Segment 1: Requirements Specification
Segment 2: Requirement Gathering Techniques and
Interview
Segment 3: JOINT APPLICATION DESIGN (JAD)
Segment 4: Other Requirement Gathering
Techniques

3
Key Ideas
• The goal of the analysis phase is to truly
understand the requirements of the new system
and develop a system that addresses them.
• The first challenge is collecting and integrating the
information
• The second challenge is finding the right people to
participate.

4
Analysis Phase
• This phase takes the general ideas in the system
request and
• refines them into a detailed requirements definition (this
chapter),
• functional models
• structural models and
• behavioral models

• This becomes the system proposal


• Includes revised project management deliverables,
• feasibility analysis and
• workplan
5
Requirement Specification
• A statement of what
• the system must do or
• characteristics it must have
• Written from business person perspective –
business requirement
• Later requirements become more technical –
system requirement

6
Functional vs. Nonfunctional
• A functional requirement relates directly to a
process the system has to perform or information
it needs to contain.

• Nonfunctional requirements refer to behavioral


properties that the system must have, such as
performance and usability.

7
Functional Requirements
example
Nonfunctional Requirements example
Types of Nonfunctional Requirements

10
11
End of segment 1
Segment 2
REQUIREMENTS ANALYSIS STRATEGIES

12
Requirement Gathering Techniques

• An analyst search for requirements using a variety of techniques


• Make sure that the current business processes and the needs for the new system
are well understood before moving into design.
• Five most commonly used requirements elicitation techniques:
1. Interviews
2. JAD sessions
3. Questionnaires
4. Document analysis
5. Observation.

13
Problem Analysis
• Ask users to identify problems and solutions
• Improvements tend to be small and
incremental
• Rarely finds improvements with significant
business value

14
Root Cause Analysis
• Users are not asked for solutions, but for:
• A list of (prioritized) problems.
• All possible root causes for those problems.
• Analysts investigate each root cause to find:
• Solutions for the highest priority problems.
• Root causes that are common to multiple
problems.

15
Duration Analysis

• Calculate time needed for each process step


• Calculate time needed for overall process
• Compare the two – a large difference indicates a badly fragmented process
• Potential solutions:
• Process integration – change the process to use fewer people, each with
broader responsibilities
• Parallelization – change the process so that individual step are performed
simultaneously

16
Activity-Based Costing
• Calculate cost of each process step
• Consider both direct and indirect costs
• Identify most costly steps and focus
improvement efforts on them

17
Benchmarking

• Studying how other organizations perform


the same business process
• Informal benchmarking
• Common for customer-facing processes
• Interact with other business’ processes as if
you are a customer

18
Technology Analysis

• Analysts list important and interesting technologies


• Managers list important and interesting
technologies
• The group identifies how each might be applied to
the business and how the business might benefit

4 - 19
Activity Elimination
• Identify what would happen if each organizational
activity were eliminated
• Use “force-fit” to test all possibilities

4 - 20
Comparing Analysis Techniques
• Potential business value
• Project cost
• Breadth of analysis
• Risk

4 - 21
Thank you

22

You might also like