Presentation on theme: "Requirements Volatility Amount of change to the requirements once they are baselined. Can be measured in various ways. Use GQM to determine the precise."— Presentation transcript:
Requirements Volatility Amount of change to the requirements once they are baselined. Can be measured in various ways. Use GQM to determine the precise metric.
Analyze (The product or process under study) Initial requirements elicitation For the purpose of (Motivation (why) -Understanding, controlling, or improving the object) 1.Understanding effectiveness of requirements elicitation 2.Controlling Change Management With respect to (The quality focus of the object that the measurement focuses on) Growth of requirements after baseline From the viewpoint of (The people that measure the object) Change management board In the context of (The environment in which the measurement takes place) Change requests/management process 1. Develop a measurement goal.
Tip – Requirements volatility –what questions need to be answered with respect to Requirements Volatility? Q1: How many change requests were made per day/week/month? Q2: How many change requests were accepted per day/week/month? Q3: To what extent did the baseline requirements specification change? Q4: What is acceptable in terms of change to requirements? 2. Generate questions that define the goal as completely as possible in a quantifiable way
Measure Direct or Derived UnitPossible values M1 Requirements added to baseline Direct Integer 3, 6 M2 Requirements deleted from baseline Direct Integer 4, 5 M3 Requirements amended from baseline Direct Integer 5,8 M4 Total number of changed requirements Derived Integer 10. 15 M5Percentage change to original number of baseline requirements DerivedReal12.5, 3.0 3. Specify the measures needed to be collected to answer those questions - To what extent did the baseline requirements specification change?
Direct Measure ment Number Role (Person who collects) When? Frequency? Medium (Tool or Form to be used for collection) M1 CR Board secretary 4.00pm Daily for duration of project Form 23GE M2 CR Board secretary 4.00pm Daily for duration of project Form 23GE M3 CR Board secretary 4.00pm Daily for duration of project Form 23GE 4. Develop mechanisms for collection of direct measures
Derived Measurem ent Number Source Measures Role (Person who collects) When? Frequency?How is measure derived? M4 M1, M2, M3 CR Board Chairperson 5.00pm Daily for duration of project M1+M2+M3 M5 M3, Original number of baseline requireme nts CR Board Chairperson 5.00pm Daily for duration of project (M4/Total)*100 5. Develop mechanisms for derivation of derived measures
% = the additional requirements as a percentage of the original baseline of 300. This figure might only count changes to the original 300 baselined requirements. Weeks12345678910 Added to Baselin6798155538 Deleted from Baseline0057833652 Modified from Baseline61046376352 Total12171821121514 1312 %4667455544 Initial baselined requirements300 Planned Threshold
Weeks12345678910 Added6798155538 Deleted0057833652 Modified61046376352 Total12171821121514 1312 CumTotal312329347368380395409423436448 Initial baselined requirements300 CumTotal is simply a cumulative total of the changes made in addition to the original baseline. This includes changes that are made to the already changed requirements Planned growth ceiling
Of course the metric might measure a change in different ways For example if five requirements are modified, two new requirements are added, and two other requirements are deleted, you might regard the number of requirements as unchanged even though a significant amount of change has occurred It all depends on the question for which the metric is providing data