Enhancing Requirements and Change Management Through...

8/13/2019 Enhancing Requirements and Change Management Through...

1/15

Enhancing Requirements and ChaManagement through

Process Modelling and Measurem

Teacher: Vctor Betancourt

Member: Tamara Macaya T.


2/15

Introduction

Aim:Improving the effectiveness of requirements management

development and maintenance.

Focus:

Quantitative assessment of the impact of requirements ch

quantitative estimation of costs of the development activities

Based in:

Enhanced traceability and process measurement


3/15

The problem detected isIndustrial software-intensive systems are affected by

requirements changes. This change can happen during any pproduction cycle and have strong effects on a variety of temanagerial aspects.

Also:

Procurers >aim at more effective management of contractual p

suppliers >perceive requirements management as a competitivand a way to business. They must fully understand the process.

In the development of software, most of the tools do not off

support to the structuring of information


4/15

SolutionImplementation of an explicitly model that information accor

adopted product and process models. In this way a rmanagement tool becomes process and product aware, withadvantages.

The authors believe that is essentialthat the structure of the information

reflects goals and methods of thedevelopment organization.


5/15

BenefitAwareness of the process model adds further value, enablin

investigate and understand the causal relations underlying trace

More precise qualitative and quantitative reasoning about thamount of work to be carried out.


6/15

Modelling traceability according to the

Product and ProcessThere are 2 types of traceability models:

1. Product-based traceability model

Can span from user (change) requests to user and system requir

Properties:

Enable the description of artifacts(type and at the instance level).

Enable the definition of attributescharacterizing the various artifact typ

Enable the definition of multiple types of relationships among ardifferent semantics, some (or all) of which constitute itsbasis.

Enable the instantiation of relationships holdingamong artifact instanc

Allow to vary the level of abstraction and granularity of the prodaccording to the amount and precision of available traceability information.


7/15

Modelling traceability according to the

Product and Process2. Process-based traceability

It Can cover the whole development (and maintenance) process, as

the management process. The human resources have paramount i

One of the process formalisms that suit our needs is IDEFo. For exa

In this model, the activities are related through the flow of thoutput and resources employed by the various activities are expli

with their properties


8/15

Measuring the Development Process foQuantitative Requirements Managemen

Aim:

Characterize the elements of the models in order to support

analysis. For this identifies:

every input, outputand resource type used;

The activity itself, to take into account variations in the way

can be performed, due to development techniques, tools, etc.Example

Figure: An activity of the process model.


9/15

Quantitative Estimation of Impact and

1. Impact evaluation

The effects involve activities to be carried out to accomplish the chartifacts to be manipulated by those activities. The structurfunctions is:

O = f(I, R, A) Where O, I, RandAare vectors (contain values for releOutput Inputs ResourcesActivity

Impact evaluation takes in count the following arguments: Sizeof the new code, old code and design

Complexity of the new code, old code and design

Experience and domain knowledgeof the C programmer

Clarity of design

Programming environmentand coding conventions


10/15

2. Cost estimation

It works much like impact evaluation. These functions have structure :

C = f(I, R, A, O) Where: Cost, Output, Inputs, Resouare vectors

Cost functions provide estimations of the cost of each activity

must be carried out.The partial roll-up of cost of the individual activities also allow

the weight of each software development phase with retotal cost of the change. To assess the overall cost of activities involved, it is sufficient to compose the cost of tactivities involved.


11/15

Implementation and Validation

All the methodology has been embraced and experimented in t

project (SensitivityAnalysis and Change management support Requirements) that is used for impact evaluation and cost estim

Also, the SACHER environment can be employed for estimatiRecorded estimates and actual results are compared a posteriorand cost functions are then refined in order to take into acco

differences.


12/15

Figure: The SACHER environment at work


13/15

Validation

To validate the methodology and SACHER environment, the alaunched initiatives pertaining to industrial software developmthree case studies, one of these in a Small-Medium Entrerprise

Results:

Average estimation error: Costfunctions (between 25% and 30%) onthe first round of the estimation circle

Reasonable error in around 70% ofcases


14/15

Advantages over related work

This approach (product-based and process based- models in

environment to enhancing requirements and Change validaimpact and cost analysis) allows:

To perform different kinds of analysis concerning quantitativrequirements changing.

The underlying process model: Transparentboxapproach. who describe their own process model.

To compute different kinds of impacts.

Evaluating the consequences of any change (occurring inrequirements specification, etc.)


15/15

The methodology presented provides quantitative estimation

requirements changes, including impact and cost analysis. This woapproach that is founded upon traceability in conjunction with knocompliance with measurable models of the software product and proce

The approach greatly emphasizes the importance of capturing anaccount the peculiarities of software development organizations

(changes in design, in requirements specification, etc.).

The SACHER project has embraced the methodology and aims to cosupport it (Estimation Tuning).

Preliminary results indicate that this approach can provide addedtechnical domain, as well as in managing a project and in dev

maintenance contracting (The underlying process model: Tran

Conclusions

Enhancing Requirements and Change Management Through...

Documents

Transcript of Enhancing Requirements and Change Management Through...