1. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE1 Requirements Elaboration Ali Afzal Malik, Barry Boehm, USC-CSSE Annual Research Review March 18, 2008

2. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE2 Outline Motivation Empirical study Methodology Results Findings Future work References

3. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE3 Motivation Cost estimation - GIGO Cost Model

4. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE4 Research Objectives Early estimation –Use goals Phenomenon of Requirements Elaboration –High-level Goals  Low-level Requirements Characterize cause of variation in elaboration ratios

5. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE5 Requirements Elaboration Levels Use Case Level of Detail Scale (Cockburn, 2001)

6. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE6 Research Approach Related previous work –Agent-based approach (Letier and van Lamsweerde, 2002) –GBRAM (Antón, 1996) How is our work different? –Focus on the process itself Obtain detailed project data Analyze causes of variation

7. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE7 Empirical Study* SE I (Fall) and SE II (Spring) 2004 – 2006 20 real-client, MS-student, team projects Process: MBASE/RUP Project selection –Custom development –Complete documentation *A. Malik, B. Boehm, “An Empirical Study of Requirements Elaboration”, Submitted in 16 th IEEE International Requirements Engineering Conference.

8. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE8 Empirical Study (2) S#YearProjectType 12004Online Bibliographies on Chinese Religions in Western LanguagesWeb-based database 22004Data Mining of Digital Library Usage DataData mining 32004Data Mining from Report FilesData mining 42005Data Mining PubMed ResultsData mining 52005USC Football Recruiting DatabaseWeb-based database 62005Code Generator – Template basedStand-alone application 72005Develop a Web Based XML Editing ToolWeb-based application 82005EBay Notification SystemStand-alone application 92005Rule-based EditorGUI 102005CodeCount™ Product Line with XML and C++Code Counter Tool 112006California Science Center Newsletter SystemWeb-based database 122006California Science Center Event RSVP SystemWeb-based database 132006USC Diploma Order/ Tracking Database SystemWeb-based database 142006USC Civic and Community Relations (CCR) web applicationWeb-based database 152006Student's academic progress web applicationWeb-based database 162006New Economics for Woman (NEW)Web-based database 172006Web Portal for USC Electronic ResourcesWeb-based GUI 182006Early Medieval East Asian TombsWeb-based database 192006USC CONIPMOCost model 202006An Eclipse Plug-in for Use Case AuthoringStand-alone application

9. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE9 Project Process

10. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE10 Methodology Relationship between capability goals and capability requirements Documents and milestones considered –LCO-OCD*: Capability goals at the end of the Inception phase –IOC-SSRD # : Capability requirements at the end of the Construction phase 7 metrics –4 direct –3 derived * Life Cycle Objectives – Operational Concept Description # Initial Operational Capability – System and Software Requirements Definition

11. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE11 Metrics S#MetricDescription 1NCG I Number of initial capability goals 2NCG R Number of capability goals removed 3NCR D Number of delivered capability requirements 4NCR N Number of new capability requirements 5NCG A Number of adjusted capability goals 6NCR A Number of adjusted capability requirements 7EFElaboration Factor

12. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE12 Derived Metrics NCG A = NCG I – NCG R NCR A = NCR D – NCR N EF = NCR A / NCG A

13. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE13 Results S#NCG I NCG R NCR D NCR N NCG A NCR A EF Group 101421011290.75 Outliers 198182760.86 33175221 WUA 165230331 710561551 1123 29101.11 81021228101.25 97484341.33 23094351.67 ICA 205272351.67 177121106111.83 64171362 451146482 1551113482 1430103372.33 VUA 18602056152.5 541123393 1320113284 12621924174.25 11851633134.33

14. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE14 Results (2) (2): 2 data points

15. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE15 Findings -WUA: Well-understood applications -ICA: Intermediate clarity applications -VUA: Vaguely understood applications

16. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE16 Findings (2) Project groups based on EF ranges –WUA: Well-understood applications –ICA: Intermediate clarity applications –VUA: Vaguely-understood applications 11.52 EF 0 WUAICAVUAOutliers EF ranges defining groups

17. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE17 Findings (3) No one-size-fits-all formula for requirements elaboration Knowledge of a project’s type gives a hint about its EF value e.g. all projects in the VUA group are of type “Web-based Database” Benefits of early determination of a project’s group –better estimates –save time and effort

18. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE18 Future Work Relationship between LOS goals and LOS requirements Relationship between current metrics and those provided by architectural documents Relationship between current metrics and software size metrics Analysis of industrial data

19. University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE19 References Books –Cockburn, A., Writing Effective Use Cases, Addison-Wesley, 2001. –Kruchten, P., The Rational Unified Process: An Introduction, Addison- Wesley, 2003. Conference papers –A. I. Antón, “Goal-based requirements analysis”, Proc. of the IEEE Int. Req. Eng. Conf. (RE), 1996, pp. 136–144. –B. Boehm, “Anchoring the Software Process”, IEEE Software 13(4), 1996, pp. 73-82. –E. Letier and A. van Lamsweerde. “Agent-based tactics for goal-oriented requirements elaboration”, Proc. of the IEEE Int. Conf. on Soft. Eng. (ICSE), 2002, pp. 83–93. Miscellaneous –Boehm, B., Klappholz, D., Colbert, E., et al., “Guidelines for Lean Model- Based (System) Architecting and Software Engineering (LeanMBASE)”, Center for Software Engineering, University of Southern California, 2005. –http://sunset.usc.edu/csse/courseroot/course_list.html#577ahttp://sunset.usc.edu/csse/courseroot/course_list.html#577a –http://sunset.usc.edu/csse/courseroot/course_list.html#577bhttp://sunset.usc.edu/csse/courseroot/course_list.html#577b