Analysis of Changes Depend on Use Cases

More documents

Recommendations

Info

Motivation2 Requirements creep or change may cause calamity Cost, Schedule, Quality If given the requirements that are instable at thebeginning <strong>of</strong> s<strong>of</strong>tware development, engineers cando: Figure out the root-causes <strong>of</strong> instable requirements Improve the requirements processes Raise the flexibility <strong>of</strong> s<strong>of</strong>tware designs Can we predict requirements to be changed basedon historical requirements evolution data?
Intuitions3 Requirements which are frequently changed inhistorical versions are also likely to change in thesubsequent versions— Frequency The probability <strong>of</strong> a requirement change may relateto the gaps between versions where changeshappened and the predicting version— Center <strong>of</strong> Change Gravity The probability <strong>of</strong> a requirement change may relateto the gap between the version which a requirement isinitialized and the predicting version — Lifecycle
Page 1: A PREDICTION MODEL FORREQUIREMENTS
Page 5 and 6: Example5Requirements12345Change His
Page 7 and 8: Prediction Approach7 Logistic Regre
Page 9 and 10: Overview of Approa
Page 11 and 12: Data Collection11 added = 2, modifi
Page 13 and 14: Data13 To investigate the performan
Page 15 and 16: Prediction Model15# Model M4 M3 M2
Page 17 and 18: Evaluation - Classification tables1
Page 19 and 20: Percentage Correct19100.00%90.00%80
Page 21 and 22: Feedback from the Company21 Action
Page 23 and 24: 23Thank you!

Analysis of Changes Depend on Use Cases

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?