Requirements Engineering Process 1-Software Requirement-Lecture Slides, Slides of Software Project Management

Download Requirements Engineering Process 1-Software Requirement-Lecture Slides and more Slides Software Project Management in PDF only on Docsity!

1

Requirements Engineering

Process – 1Lecture # 6

2

Requirements Engineering Process

The process(es) involved in

developing system requirements is

collectively known as

Requirements Engineering Process

4

RE Process – Inputs

It includes:•^

Existing system information–

Information about the functionality ofsystems to be replaced

-^

Information about other systems, whichinteract with the system being specified

5

RE Process – Inputs

•^

Stakeholder needs–

Description of what systemstakeholders need from the system tosupport their work

•^

Organizational standards–

Standards used in an organizationregarding system development practice,quality management, etc.

7

RE Process – Outputs

It includes•^

Agreed requirements–

A description of the systemrequirements, which is understandableby stakeholders and which has beenagreed by them

8

RE Process – Outputs

•^

System specification–

This is a more detailed specification ofthe system, which may be produced insome cases

10

RE Process Variability

•^

RE processes vary radically from oneorganization to another, and even within anorganization in different projects

-^

Unstructured process rely heavily on theexperience of the people, while systematicprocesses are based on application of someanalysis methodology , but they stillrequire human judgment

11

Variability Factors - 1

•^

Technical maturity

-^

Disciplinary involvement

-^

Organizational culture

-^

Application domain There are four factors which count towards thevariability of the Requirements EngineeringProcess

13

Variability Factors - 3

•^

Organizational culture–

The culture of an organization hasimportant effect on all business andtechnical processes

•^

Application domain–

Different types of application systemneed different types of requirementsengineering process

14

RE Process - 1

• Begins
  • There is recognition that a problem exists and

requires a solution

• A new software idea arises
  • Ends
    • With a

complete

description of the external

behavior of the software to be built

Requirement Engineering Process has a formalstarting and ending point in the overall softwaredevelopment life cycle.

16

RE Process - 3

•^

Based on the need of individual softwareprojects and organizational needs,requirements engineering processes aretailored

-^

An important point to remember is that “There is no ideal requirements engineering

process!”

17

Two Main Tasks of RE

• Problem analysis
  • Analysis of a software problem
    • Product description
      • Complete specification of the desired external

behavior of the software system to be built.Also known as functional description,functional requirements, or specifications There are two main tasks which needs to beperformed in the requirements engineeringprocess.

19

Problem Analysis - 2

•^

Trading off constraints and organizinginformation

•^

Complete understanding should beachieved

20

Product Description

•^

Make decisions to define the externalbehavior of the software product

-^

Organize ideas, resolve conflicting views,and eliminate inconsistencies andambiguities Product description is another task ofrequirements engineering process. In this taskwe: