SPM Unit-IV

Software requirements gathering

The process to gather the software requirements from client, analyze and document them is
known as requirement engineering. The goal of requirementengineering is to develop and
maintain sophisticated and descriptive 'SystemRequirements Specification' document.

Steps to be followed
Skill sets required
Challenges
Software requirements Metrics

A Metric is a measure of quality, metrics can be used to improve software quality

and productivity and are used to measure software resources, products and
processes. When we collect data for software metrics there should be a description
of the data so that it can be easier for software developers to do their job. Software
metrics give the overall information about the development product, like cost, time
and all phases information. Ideal metrics should be [Everald88]:

Simple Objective Easily obtainable Valid Robust Metrics should measure

what they are intended to measure should

There are many ways of categorizing estimation approaches, see for example. [10][11] The top level
categories are the following:
 Expert estimation: The quantification step, i.e., the step where the estimate is produced
based on judgmental processes.[12]

Formal estimation model: The quantification step is based on mechanical processes, e.g.,
the use of a formula derived from historical data.

Combination-based estimation: The quantification step is based on a judgmental and

mechanical combination of estimates from different sources.
Below are examples of estimation approaches within each category.

Estimation Examples of support of implementation of estimation

Category
approach approach

Analogy-based Formal
ANGEL, Weighted Micro Function Points
estimation estimation model

WBS-based (botto Project management software, company specific activity

Expert estimation
m up) estimation templates

Formal COCOMO, SLIM, SEER-SEM, TruePlanning for

Parametric models
estimation model Software

Size-based Function Point Analysis,[14] Use Case Analysis, SSU

Formal
estimation (Software Size Unit), Story points-based estimation
estimation model
models[13] in Agile software development, Object Points

Group estimation Expert estimation Planning poker, Wideband Delphi

Mechanical Combination- Average of an analogy-based and a Work breakdown

combination based estimation structure-based effort estimate

Judgmental Combination- Expert judgment based on estimates from a parametric

combination based estimation model and group estimation