Ali Afzal Malik, Supannika Koolmanojwong, Barry Boehm USC-CSSE

Slides:

Advertisements

Similar presentations

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13

Advertisements

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.

University of Southern California Center for Systems and Software Engineering Process Decision Frameworks for DoD and e-Services Projects ASRR 2011 Supannika.

University of Southern California Center for Software Engineering C S E USC Barry Boehm, USC Community-Based Learning Collaborative April 6, 2009 Service.

University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.

University of Southern California Center for Systems and Software Engineering Design-Code Review Preparation Pongtip Aroonvatanaporn CSCI577b Spring 2012.

University of Southern California Center for Systems and Software Engineering SoS Engineering and the ICM Workshop Overview Jo Ann Lane USC CSSE

University of Southern California Center for Systems and Software Engineering Social Networking Technology Usage on Web Service Projects Supannika Koolmanojwong.

Software Effort Estimation based on Use Case Points Chandrika Seenappa 30 th March 2015 Professor: Hossein Saiedian.

University of Southern California Center for Systems and Software Engineering 3/18/2008©USC-CSSE1 Requirements Elaboration Ali Afzal Malik, Barry Boehm,

University of Southern California Center for Software Engineering CSE USC 477 Class Project – HazMat (Hazardous materials) Spring 2003 Feb. 4.

University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.

University of Southern California Center for Systems and Software Engineering Cost Modeling for Commercial Organizations Anandi Hira, USC Graduate Student.

0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.

COSOSIMO* Workshop 13 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE Annual.

University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering (IS&SE) with the Incremental.

Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.

0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Software Architecting On the Acquisition Side.

University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Barry Boehm USC Center for Systems and Software Engineering.

2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.

SERC Security Systems Engineering Initiative Dr. Clifford Neuman, Director USC Center for Computer Systems Security Information Sciences Institute University.

6. & 7. Teams: Technical Specification / Schedule Project Title Team Member 1 Team Member 2 Team Member 3 Team Member 4 Department of Computer Science.

System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.

0-1 Team 1 Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auto-Owners.

University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy

0-1 Team ?? Status Report (1 of 3) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team 1: Auraria.

The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.

University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.

University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.

University of Southern California Center for Systems and Software Engineering 1 WikiWinWin: Rapid Collaborative Requirements Negotiation Using Wiki and.

University of Southern California Center for Systems and Software Engineering GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE1.

CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.

University of Southern California Center for Systems and Software Engineering The Incremental Commitment Spiral Model Electronic Process Guide (EPG) and.

University of Southern California Center for Systems and Software Engineering Incremental Commitment Spiral Model (ICSM) for CS 577 Barry Boehm, Supannika.

University of Southern California Center for Systems and Software Engineering Project Artifacts in each process model Supannika Koolmanojwong October 09,

University of Southern California Center for Systems and Software Engineering Retrospective Analysis Supannika Koolmanojwong October 21,

Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects.

University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.

University of Southern California Center for Systems and Software Engineering Future Challenges for Systems and Software Cost Estimation and Measurement.

University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.

University of Southern California Center for Systems and Software Engineering 7/13/2012(c) USC-CSSE11 USC e-Services Software Engineering Projects.

Software Architectural Assumptions in Software Architecting Chen Yang a,b, Peng Liang a, Paris Avgeriou b a State Key Lab of Software Engineering, Wuhan.

University of Southern California Center for Systems and Software Engineering 577 process CSCI 577a Software Engineering I Supannika Koolmanojwong Mobasser.

University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE CSCI577B 2010 Light Weight Sw Engg for Off-the-Books.

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.

University of Southern California Center for Systems and Software Engineering Milestone Reviews CS 577b Software Engineering II Supannika Koolmanojwong.

University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment: Tracking the.

Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.

Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.

Barry Boehm, USC-CSSE Fall 2011

University of Southern California Center for Systems and Software Engineering 7/23/2010(c) USC-CSSE1 08/21/09 ©USC-CSSE1 USC e-Services Software.

Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.

Fundamentals of Software Engineering. Instructor: Dr. Kal Bugrara Office: Snell Engineering, Rm 267 Office Hours: Sat: 12:00-2:00 pm Phone

University of Southern California Center for Systems and Software Engineering 1 © USC-CSSE Integrating Case-Based, Analogy-Based, and Parameter-Based Estimation.

University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment Framework Pongtip.

University of Southern California Center for Systems and Software Engineering Core Capability Drive-Through Preparation Pongtip Aroonvatanaporn CSCI 577b.

Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.

University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.

University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.

1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.

Rick Selby Software Products, Northrop Grumman & Adjunct Faculty, University of Southern California Los Angeles, CA Candidate member Main empirical research.

Software Construction

USC e-Services Software Engineering Projects

USC e-Services Software Engineering Projects

An Empirical Study of Requirements-to-Code Elaboration Factors

CSE 498, Collaborative Design

Relating Effort Reporting to Project Estimation

SDLC (Software Development Life Cycle) Role Play

Presentation transcript:

Determining Requirements-to-Code Expansion Factors – The Magical Number Seven? Ali Afzal Malik, Supannika Koolmanojwong, Barry Boehm USC-CSSE {alimalik, koolmano, boehm} @usc.edu Annual Research Review March 17, 2009 3/17/2009 ©USC-CSSE

Cockburn’s Use Case Expansion Levels (Cockburn, Writing Effective Use Cases, 2001) 3/17/2009 ©USC-CSSE

What are the Level-to-Level Expansion Factors? Cloud to Kite Kite to Sea Level Sea Level to Fish Fish to Clam Clam to Lava 3/17/2009 ©USC-CSSE

IBM-UK Expansion Factor Experience Business Objectives 5 Cloud Business Events/Subsystems 35 Kite Use Cases/Components 250 Sea level Main Steps/Main Operations 2000 Fish Alt. Steps/Detailed Operations 15,000 Clam SLOC* 1,000K – 1,500K Lava *(70 – 100 SLOC/Detailed Operation) (Hopkins & Jenkins, Eating the IT Elephant, 2008) 3/17/2009 ©USC-CSSE

Testing Applicability to Small E-Services Projects Graduate level 12 weeks in Fall; 12 weeks in Spring Team size: 6 on-campus, 2 off-campus students Real Clients: Neighborhoods and USC departments 3/17/2009 ©USC-CSSE

Empirical Study 20 projects Architected Agile 2004 - 2006 Custom-development Analyzed Requirements elaboration Effort elaboration Documentation size elaboration 3/17/2009 ©USC-CSSE

Mapping Cockburn Metaphor* Project Data Document(s) Cloud Organizational goals Operational Concept Description Kite Top-level services Sea Level Use cases System and Software Requirements Definition System and Software Architecture Description Fish Main steps Lava SLOC Source code *Clam level skipped. 3/17/2009 ©USC-CSSE

Requirements Elaboration 1 2 Expansion from Cloud to Kite Expansion from Kite to Sea Level 3 4 Expansion from Sea Level to Fish Expansion from Fish to Lava 3/17/2009 ©USC-CSSE

Effort & Documentation Size Elaboration Expansion of Project Effort Expansion of Document Size 3/17/2009 ©USC-CSSE

Expansion Factors Summary Stage Elaboration Factors Number of Requirements Relative Effort Relative Documentation Size Cloud to Kite 1.59 2.30 1.94 Kite to Sea Level 1.10 14.06 7.82 Sea Level to Fish 3.75 1.04 2.60 Fish to Lava 74.27 3.89 6.13 3/17/2009 ©USC-CSSE

Conclusions Magical number seven not a good fit to architected agile projects Fewer actual expansion levels Some confounding factors Student teams motivated to work out details early Wide variation in OTS solution components 3/17/2009 ©USC-CSSE