Model Driven Development Needs More Than Product Models
|
|
- Annis Peters
- 6 years ago
- Views:
Transcription
1 Model Driven Development Needs More Than Product Models Barry Boehm, USC USC-CSE Executive Workshop on MDA Mar. 16 th, /16/2005 USC-CSE 1
2 Nature of Model Clashes Outline Among product, process, property, success models Project examples Distribution of Model Clashes 35-project sample: Al-Said Ph.D. thesis Product-product: 30% of total, 24% of risk Detecting and Avoiding Model Clashes MBASE integration and process frameworks Concurrent engineering of architecture, rqt s, plans Anchor point milestones and Feasibility Rationale Conclusions 3/16/2005 USC-CSE 2
3 Understanding the Tar Pit: Model Clashes Model Clash: An incompatibility among the underlying assumptions of a set of models Process, product, property, and success models Often unrecognized Produces conflicts, confusion, mistrust, frustration, rework, throwaway systems 3/16/2005 USC-CSE 3
4 Process Models Using Models to Visualize Software Facets Success Models Win-Win Business Case Analysis Results Chains Risk Software Warranties Correctness RAD Six Sigma Stories Award Fees Agility JAD QFD Golden Rule Waterfall Spiral RUP XP SAIV CAIV SCQAIV Risk Management Business Process Reengineering CMM s Peopleware IPT s Agile Development Groupware Easy WinWin Experience Factory GQM MBASE, CeBASE COCOMO II COCOTS CORADMO System Dynamics Metrics - ilities COQUALMO Simulation and Modeling Property Models 3/16/2005 USC-CSE 4 Product Models UML XML CORBA COM Architectures Product Lines OO Analysis & Design Requirements Operational Concepts Domain Ontologies COTS GOTS
5 Model Clash Example: Waterfall and COTS - e.g., DoD-STD-2167 and SecDef Perry COTS memo Waterfall Process Model Assumptions System requirements are specifiable in advance They determine the system s capabilities COTS-Based Product Model Assumptions COTS capabilities determine affordability Affordability determines requirements It s not a requirement if you can t afford it 3/16/2005 USC-CSE 5
6 Large Government Waterfall Project Example $100M Required Architecture: Custom; many cache processors $50M Original Cost Original Spec Original Architecture: Modified Client-Server After Prototyping Response Time (sec) 3/16/2005 USC-CSE 6
7 Clashes Among MBASE Models Product Model Process Model Property Model Success Model Product Model Process Model Property Model Structure clash Traceability clash Architecture style clash COTS-driven product vs. Waterfall (requirementsdriven) process Multi-increment development process vs. singleincrement support tools Interdependent multiprocessor product vs. linear performance scalability model Evolutionary development process vs. Rayleigh-curve cost model Minimize cost and schedule vs. maximize quality (Quality is free) 4GL-based product vs. low development cost and performance scalability Waterfall process model vs. "I'll know it when I see it" (IKIWISI) prototyping success model Fixed-price contract vs. easyto-change, volatile requirements Success Model Golden Rule vs. stakeholder winwin 3/16/2005 USC-CSE 7
8 Model Clashes SpiderWeb: MasterNet 3/16/2005 USC-CSE 8
9 Nature of Model Clashes Outline Among product, process, property, success models Project examples Distribution of Model Clashes 35-project sample: Al-Said Ph.D. thesis Product-product: 30% of total, 24% of risk Detecting and Avoiding Model Clashes MBASE integration and process frameworks Concurrent engineering of architecture, rqt s, plans Anchor point milestones and Feasibility Rationale Conclusions 3/16/2005 USC-CSE 9
10 Model Clashes Occurrence Probability & Severity: 35 Projects RAD Sample Assumptions Developer needs extensive, on demand user/customer interaction User/Customer are available at limited times S Dev User/ Cust M SS SS OP 0.86 SV H User/Customer are free to add/modify the system requirements during the system implementation User/ Cust PD 0.46 H Changes/additions to system requirements require extra budget and schedule Dev PP 3/16/2005 USC-CSE 10 S: Stakeholder; M: Model; OP: Occurrence Probability; SV: Severity
11 Clash Types and their Contribution to Project Risk Success- Property Success- Product Success- Success Product- Property Process- Property Property-Product- Property Product Process- Process Product- Process % of Clashes % of Risk Success- Process Majority of research (product-product) addresses minority of risk 3/16/2005 USC-CSE 11
12 Inter and Intra Model Clashes and their Contribution to Project Risk 100 Distribution of Inter and Intra Model Clashes Contribution of Inter and Intra Model Clashes to Risk 100 % Total Model Clashes % 80 53% 60 55% % Total Risk % 0 0 Inter Model Clashes Intra Model Clashes Inter Model Clashes Intra Model Clashes Inter model clashes caused majority of risk 3/16/2005 USC-CSE 12
13 3/16/2005 USC-CSE 13
14 Nature of Model Clashes Outline Among product, process, property, success models Project examples Distribution of Model Clashes 35-project sample: Al-Said Ph.D. thesis Product-product: 30% of total, 24% of risk Detecting and Avoiding Model Clashes MBASE integration and process frameworks Concurrent engineering of architecture, rqt s, plans Anchor point milestones and Feasibility Rationale Conclusions 3/16/2005 USC-CSE 14
15 MBASE Integration Framework Life cycle anchor points Risk management Key practices Process models Business case IKIWISI Stakeholder win-win Process entry/exit criteria Success models Planning and control Milestone content Evaluation and analysis Property models Cost Schedule Performance Reliability Product evaluation criteria Product models Domain model Requirements Architecture Code Documentation 3/16/2005 USC-CSE 15
16 MBASE Process Framework determine the relevance of Stakeholders WinWin Spiral Process Life Cycle Architecture Package Plan in LCA Package set context for IPM 1 Domain/ Environment Models provide parameters for Conceptual Product Models are refinements of intermediate Product Models reify Reified Product Models Property Models IPM n identify, prioritize Success Models Provide evaluations for impose constraints on guide progress in selecting, and reifying enable satisficing among serve and satisfy Process Models provide parameters for 3/16/2005 USC-CSE 16
17 Spiral Anchor Points Enable Concurrent Engineering I R R L C O L C A C C D I O C P R R 3/16/2005 USC-CSE 17
18 Need Concurrently Engineered Milestone Reviews Life Cycle Objectives (LCO); Life Cycle Architecture Package (LCA) Operational Concept System Prototype(s) System Requirements System and Software Architecture Elaboration of system objectives and scope by increment Elaboration of operational concept by increment Exercise range of usage scenarios Resolve major outstanding risks Elaboration of functions, interfaces, quality attributes, and prototypes by increment - Identification of TBD s (to be determined items) Stakeholders concurrence on their priority concerns Choice of architecture and elaboration by increment - Physical and logical components, connectors, configurations, constraints - COTS, reuse choices - Domain architecture and architectural style choices Architecture evolution parameters 3/16/2005 USC-CSE 18
19 Need Concurrently Engineered Milestone Reviews Life Cycle Objectives (LCO); Life Cycle Architecture Package (LCA) 2 Life-Cycle Plan Feasibility Rationale Elaboration of WWWWWHH* for Initial Operational Capability (IOC) Partial elaboration, identification of key TBD s for later increments Assurance of consistency among elements above All major risks resolved or covered by risk management plan. *WWWWWHH: Why, What, When, Who, Where, How, How Much 3/16/2005 USC-CSE 19
20 LCO (MS A) and LCA (MS B) Pass/Fail Criteria A system built to the given architecture will Support the operational concept Satisfy the requirements Be faithful to the prototype(s) Be buildable within the budgets and schedules in the plan Show a viable business case Establish key stakeholders commitment to proceed LCO: True for at least one architecture LCA: True for the specific life cycle architecture; All major risks resolved or covered by a risk management plan 3/16/2005 USC-CSE 20
21 Conclusions Need to address model clashes among product, process, property, and success models A major hidden source of project failures Product-product clashes: 30% of total, 24% of risk Best to concurrently engineer operational concept, requirements, architecture, plans, feasibility rationale Win-Win spiral model and anchor point milestones enable controlled concurrent engineering Life Cycle Architecture Package vs. standalone architecture 93% success rate of on-time client satisfaction on campus e- services projects 3/16/2005 USC-CSE 21
Value Model Clash Analysis
Value Model Clash Analysis Mohammed Al-Said Annual Research Review USC-CSE March 2003 Research Overview Problem Currently, many software models exist Each model is based on certain assumptions Many software
More informationComplex Systems of Systems (CSOS) : Software Benefits,Risks,and Strategies
Complex Systems of Systems (CSOS) : Software Benefits,Risks,and Strategies Barry Boehm, USC Vic Basili, Fraunhofer Maryland SIS Acquisition Conference January 28, 2003 10/22/02 USC-CSE 1 Complex Systems
More informationCOCOMO II and Model-Based (System) Architecting and Software Engineering (MBASE)
COCOMO II and Model-Based (System) Architecting and Software Engineering (MBASE) Barry Boehm, USC COCOMO/SCM Forum Tutorial October 24, 2000 boehm@sunset.usc.edu http://sunset.usc.edu/research/mbase Outline
More informationTeaching the Elephant to Dance: Agility Meets Systems of Systems Engineering and Acquisition
Barry Boehm University of Southern California boehm@sunset.usc.edu Teaching the Elephant to Dance: Agility Meets Systems of Systems Engineering and Acquisition Keynote, GSAW 2005 March 3, 2005 Outline
More informationBarry Boehm, USC-CSE IBM T. J. Watson Presentation August 13, 1999
Developing and Integrating Software/System Product, Process, Property, and Success Models Barry Boehm, -CSE IBM T. J. Watson Presentation August 13, 1999 Boehm@sunset.usc.edu http://sunset.usc.edu 7/28/99
More informationAvoiding Overruns in the Specification of Non-Functional Requirements
Avoiding Overruns in the Specification of Non-Functional Requirements Barry Boehm, USC CSSE GSAW 2016 March 2, 2016 Summary: Avoiding NFR Overruns The Multiplicative Effect of NFRs on Cost Response-time
More informationThe MBASE Life Cycle Architecture Milestone Package No Architecture Is An Island
The MBASE Life Cycle Architecture Milestone Package No Architecture Is An Island Barry Boehm, Dan Port, Alexander Egyed, and Marwan Abi-Antoun Center for Software Engineering, University of Southern California,
More informationParallel Development and The Incremental Commitment Spiral Model (ICSM)
Parallel Development and The Incremental Commitment Spiral Model (ICSM) Barry Boehm, USC ARR 2018, March 13, 2018 Outline Current and future process challenges The Four D s: Dynamism, Dependability, Doubtfulness,
More informationCSE Annual Research Review. Group 2 Creating Lean Disciplined Methods & Synthesizing Hybrid Agile/Disciplined Methods
CSE Annual Research Review Group 2 Creating Lean Disciplined Methods & Synthesizing Hybrid Agile/Disciplined Methods A Winsor Brown AWBrown@sunset.usc.edu & USC Group2Outbrief.doc 1 of 1 v 0.7 04/02/00
More informationThe MBASE* Life Cycle Architecture Package -and Relations to the Draft DoD 5000 Series. Barry Boehm, USC GSAW 2000 Keynote February 23, 2000
The MBAS* Life Cycle Architecture ackage -and Relations to the raft o 5000 Series Barry Boehm, USC GSAW 2000 Keynote February 23, 2000 boehm@sunset.usc.edu http://sunset.usc.edu/mbas *Model Based (System)
More informationValue-Based Verification and Validation Guidelines
Value-Based Verification and Validation Guidelines Keun Lee, Monvorath Phongpaibul, Barry Boehm Center for Software Engineering, University Southern California {keunlee, phongpai, boehm}@usc.edu Technical
More informationIn his keynote address at the 1996
In his keynote address at the 1996 International Conference on Software Engineering, Tom De Marco summarized the work of the great military analyst Karl Von Clausewitz on the interplay of armor and mobility
More informationCOCOMO II Status and Extensions. Barry Boehm, USC COCOMO / SCM Forum #13 October 7,1998. Outline
COCOMO II Status and Extensions Barry Boehm, USC COCOMO / SCM Forum #13 October 7,1998 1 Mt98 WSCCSE 1 Outline COCOMO 11.1 998 Status and Plans Overview of Extensions COTS Integration (COCOTS) Quality:
More informationCOSYSMO: Constructive Systems Engineering Cost Model
COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual Research Review February 6, 2001 Outline Background Scope Proposed Approach Strawman Model Size & complexity Cost & schedule
More informationA Value-Based Process For Achieving Software Dependability
A Value-Based Process For Achieving Software Dependability LiGuo Huang, Barry Boehm University of Southern California {liguohua, boehm}@sunset.usc.edu USC-CSE 1 Objectives of NASA HDCP Develop NASA mission-relevant
More informationA Data Item Description for System Feasibility Evidence
A Data Item Description for System Feasibility Evidence Barry Boehm, Jo Ann Lane, Supannika Koolmanojwong, USC Richard Turner, Stevens NDIA Systems Engineering Conference October 24, 2012 Summary Schedule-based
More informationSynthesis of Existing Cost Models to Meet System of Systems Needs
Paper #128 Synthesis of Existing Cost Models to Meet System of Systems Needs Jo Ann Lane University of Southern California Center for Software Engineering 941 W. 37th Place, SAL Room 328 Los Angeles, CA
More informationEvidence-Based Software Processes
Evidence-Based Software Processes Barry Boehm 1, and Jo Ann Lane 1 1 University of Southern California 941 W. 37th Street Los Angeles, California, 90089 USA 1-213-740-8163 {boehm, jolane} at usc.edu Abstract.
More informationSoftware Architecture Challenges for Complex Systems of Systems
Software Architecture Challenges for Complex Systems of Systems Barry Boehm, USC-CSE CSE Annual Research Review March 6, 2003 (boehm@sunset.usc.edu) (http://sunset.usc.edu) 3/18/03 USC-CSE 1 Complex Systems
More information5) A work breakdown structure is a list of tasks broken down to small manageable activities. Answer: TRUE Diff: 2 Page Ref: 42
Project Management: Process, Technology, and Practice (Vaidyanathan) Chapter 2 Process and Methods 2.1 True False 1) A procedure defines how to do a task. Diff: 1 Page Ref: 38 2) A business process is
More informationWhen Does Requirements Volatility Stop All Forward Progress?
When Does Requirements Volatility Stop All Forward Progress? Practical Software and Systems Measurement User s Group Conference Golden, Colorado July 2007 Jo Ann Lane and Barry Boehm University of Southern
More informationGoals of course. Themes: What can you do to evaluate a new technique? How do you measure what you are doing?
MSWE 607: Software Life Cycle methods and Techniques Instructor: Professor Marvin V. Zelkowitz Office: 4121 AV Williams Phone: 405-2690 or 403-8935 (Fraunhofer Center) Email (Best way to contact) mvz@cs.umd.edu
More informationUsing the Spiral Model and MBASE to Generate New Acquisition Process Models: SAIV, CAIV, and SCQAIV
Using the Spiral Model and MBASE to Generate New Acquisition Process Models: SAIV, CAIV, and SCQAIV Barry Boehm, Dan Port, Li-Guo Huang, and Winsor Brown University of Southern California October 2001
More informationEvidence-Based Software Processes
Evidence-Based Software Processes Barry Boehm and Jo Ann Lane University of Southern California 941 W. 37th Street Los Angeles, California, 90089 USA 1-213-740-8163 {boehm,jolane}@usc.edu Abstract. Many
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationSoftware Engineering Economics
Software Engineering Economics (CS656) VBSE Jongmoon Baik Value-Based Software Engineering (VBSE) 2 1 Example: Software Testing Assume You re the manager of a $2M S/W project, Vendor (ATG) Proposition
More informationAgility in Defense SE & Acquisition: Some Critical Success Factors
Agility in Defense SE & Acquisition: Some Critical Success Factors Barry Boehm, USC NDIA SE Conference October 30, 2014 10/30/2014 1 Summary Agile Defense SE & Acquisition and BBP 3.0 Better Buying Power
More informationFeasibility Rationale Description (FRD)
Feasibility Rationale Description (FRD) A. Description 1. Purpose The purpose of the Feasibility Rationale Description (FRD) is to ensure that the system developers have not just created a number of system
More informationUSC-CSE Annual Research Review 2000 DEMONSTRATION GUIDE
USC-CSE Annual Research Review 2000 DEMONSTRATION GUIDE USC Center for Software Engineering Department of Computer Science Annual Research Review February 8-1 1,2000 USC-CSE Annual Research Review: 1999
More informationSoftware Engineering QUESTION BANK
Software Engineering QUESTION BANK UNIT - 1 1. What is software? Explain the two fundamental types of software products. 2. What is software engineering? What is the difference between software engineering
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More information03. Perspective Process Models
03. Perspective Process Models Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2017 Prescriptive Process Models advocates an orderly approach to software
More informationProcesses. Object Orientated Analysis and Design. Benjamin Kenwright
Processes Object Orientated Analysis and Design Benjamin Kenwright Outline Review What are Processes? Why are they important in Object Orientated Analysis and Design Conclusion and Discussion Summary Revision
More informationSystems Cost Modeling
Systems Cost Modeling Affiliate Breakout Group Topic Gary Thomas, Raytheon 0 1900 USC Center for Software Engineering Sy~C~stModelingBreakoutTopicVisual-v0-1 vl.o - 10/27/00 University of Southern California
More informationCOSOSIMO Parameter Definitions Jo Ann Lane University of Southern California Center for Software Engineering
Constructive System-of-Systems Integration Cost Model COSOSIMO Parameter Definitions Jo Ann Lane University of Southern California Center for Software Engineering jolane@usc.edu Introduction The Constructive
More informationExplore Comparative Analysis Software Development Life Cycle Models
Explore Comparative Analysis Software Development Life Cycle Models Anshu Mishra Assistant Professor, Department of Information Science and Engineering Jyothy Institute of Technology, Bangalore Abstract-The
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationLife Cycle Plan (LCP)
Life Cycle Plan (LCP) < LEMA Pilot School Integrated Family Accountability System> PROJECT TITLE LEMA FAMILY ACCOUNTABILITY SYSTEM TEAM NO #04 TEAM MEMBERS & ROLES NAME ROLES Teawon Han Project Manager
More informationMajor attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
More informationDRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors
1.1. Cost Estimation Models Parametric cost models used in avionics, space, ground, and shipboard platforms by the services are generally based on the common effort formula shown in Equation 1. Size of
More informationCORADMO and COSSEMO Driver Value Determination Worksheet
1. COCOMO Stage Schedule and Effort MODEL (COSSEMO) COSSEMO is based on the lifecycle anchoring concepts discussed by Boehm 3. The anchor points are defined as Life Cycle Objectives (LCO), Life Cycle Architecture
More informationSoftware Engineering Modern Approaches
Software Engineering Modern Approaches Chapter : Software Process Eric Braude and Michael Bernstein Maintenance Testing The Software Development Lifecycle Implementation Design Phase most relevant to this
More informationThe Software Life Cycle
Inception Software Increment Communication Planning Production The Software Life Cycle Software Engineering Deployment Andreas Zeller Saarland University Modelling Elaboration Transition Construction Construction
More informationChapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
More information3. Comparison of Above Described SDLC Models
123 3. Comparison of Above Described SDLC Models Waterfall Model is little hard to manage due to the rigidity of the model as each phase has specific deliverables and a review process. It works well for
More informationCurrent and Future Challenges for Ground System Cost Estimation
Current and Future Challenges for Ground System Cost Estimation Barry Boehm, Jim Alstad, USC-CSSE GSAW 2014 Working Group Session 11F Cost Estimation for Next-Generation Ground Systems February 26, 2014
More informationIntroduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More informationSoftware Cost Estimation Issues for Future Ground Systems
Software Cost Estimation Issues for Future Ground Systems Nancy Kern Software Engineering Department ETG/RSD The Aerospace Corporation Outline ➊ Background ➋ Software Cost Estimation Research OO Software
More informationChapter 3 Prescriptive Process Models
Chapter 3 Prescriptive Process Models - Generic process framework (revisited) - Traditional process models - Specialized process models - The unified process Generic Process Framework Communication Involves
More informationESD/MITRE Software. Proceedings May 6-7, Acquisition SYMPOSIUM
ESD/MITRE Software Acquisition SYMPOSIUM Proceedings May 6-7, 1986 An ESD/lndustry Dlologue... ----- Barry W. Boehm Chief Engineer, Software System Division TRW Defense Systems Group are at best accurate
More informationUsing the Incremental Commitment Model (ICM) to Help Execute Competitive Prototyping (CP) Charts with Notes
Using the Incremental Commitment Model (ICM) to Help Execute Competitive Prototyping (CP) Charts with Notes Barry Boehm and Jo Ann Lane University of Southern California http://csse.usc.edu Outline Motivation
More information7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
More informationSoftware Life Cycle. Main Topics. Introduction
Software Life Cycle Main Topics Study the different life cycle models Study the difference between software maintenance and evolution Study product line engineering as a design methodology 2 Introduction
More informationAUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT
AUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT Preface. Features and Organization. Practice Descriptions. Intended audience. Acknowledgements. Permissions. Disclaimer. 1. The Case for
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers UNIT 1 1. What are software myths Answer: Management myths: We already have a book
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationSystem-of-Systems Influences on Acquisition Strategy Development
System-of-Systems Influences on Acquisition Strategy Development Rita Creel Robert J. Ellison June 23008 ABSTRACT: An acquisition strategy is a top-level roadmap that focuses on highlighting and managing
More informationSoftware Development Methodologies. CSC 440: Software Engineering Slide #1
Software Development Methodologies CSC 440: Software Engineering Slide #1 Topics 1. The Waterfall Model 2. Agile Software Development 3. The Unified Process 4. Object-Oriented Analysis and Design 5. The
More informationversion NDIA CMMI Conf 3.5 SE Tutorial RE - 1
Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria
More informationCS350 Lecture 2 Software Dev. Life Cycle. Doo-Hwan Bae
CS350 Lecture 2 Software Dev. Life Cycle Doo-Hwan Bae bae@se.kaist.ac.kr Whose Drawings? Watts Humphrey, SE is Religion and Philosophy. Just Follow me! CS350 Software Engineering, SoC, KAIST 2 What is
More informationName: DBA COCOMO. Presenter(s): Janet Chu. Objective: Database version of the COCOMOll with additional functionalities.
Demonstration Guide - USC-CSE COCOMOISCM 18 Name: DBA COCOMO Presenter(s): Janet Chu Objective: Database version of the COCOMOll 2000.3 with additional functionalities. Rationale: This software is intended
More informationThe Fourth Principle: Evidence and Risk-Based Decision Making
4 The Fourth Principle: Evidence and Risk-Based Decision Making Look before you leap Anonymous proverb He who hesitates is lost Anonymous proverb The Third Principle emphasizes having a variety of systems
More informationNext Generation Trends:
Next Generation Trends: Systems and Software Engineering Barry Boehm, USC-CSSE http://csse.usc.edu CSSE Annual Research Review April 15, 2015 4/15/2015 1 Motivation What helped me most in becoming a good
More informationValue-Based Software Engineering Barry Boehm University of Southern California
ACM SIGSOFT Software Engineering Notes vol 28 no 2 March 2003 Page 1 Value-Based Software Engineering Barry Boehm University of Southern California boehm@sunset.usc.edu Abstract Much of current software
More informationSoftware Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationThe Software Life Cycle
Production Inception The Life Cycle Engineering Modelling Andreas Zeller Saarland University Elaboration Transition A Crisis Denver International Airport (DIA) started in 1989 53 sq miles Planned: 1.7
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationTopics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationUSC-CSE Annual Research Review. Los Angeles, CA March 12, 2003
USC-CSE Annual Research Review Los Angeles, CA March 12, 2003 Background Two approaches to software development Disciplined (SW-CMM, document-based, heavy process) Agile (XP, tacit knowledge, light process)
More informationMIS Systems & Infrastructure Lifecycle Management 1. Week 10 March 24, 2016
MIS 5203 Lifecycle Management 1 Week 10 March 24, 2016 Study Objectives Software Development Processes contd. Alternate Software Development Methodologies 2 Alternate Software Development Methodologies
More informationMODULE Explain briefly the different types of system models that might be created during the system analysis phase. 2. Write short notes on
15CS42: SOFTWARE ENGINEERING QUESTION BANK MODULE 1. 1. What is software? Explain the two fundamental types of software products. 2. What is software engineering? What is the difference between software
More informationThe software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
More informationArchitecture Based Analysis of System ility Synergies and Conflicts
Architecture Based Analysis of System ility Synergies and Conflicts Barry Boehm, Jo Ann Lane, USC Kevin Sullivan, U. Virginia NDIA Systems Engineering Conference October 30, 2013 10 30 2013 1 Outline Critical
More informationThe Product and the Process The Product The Evolving Role of Software Software Software: A Crisis on the Horizon Software Myths Summary References
The Product and the Process The Product The Evolving Role of Software Software Software: A Crisis on the Horizon Software Myths Further Readings and Information Sheets The Process Software Engineering
More informationIngegneria del Software Corso di Laurea in Informatica per il Management
Ingegneria del Software Corso di Laurea in Informatica per il Management Software process model Davide Rossi Dipartimento di Informatica Università di Bologna The task of the software development team
More informationPrinciples for Successful Systems Engineering
Available online at www.sciencedirect.com Procedia Computer Science 8 (2012) 297 302 New Challenges in Systems Engineering and Architecting Conference on Systems Engineering Research (CSER) 2012 St. Louis,
More informationSoftware Risk Management
Software Risk Management Outline What is Software Risk Management? What can it help you do? When should you do it? How should you do it? What are its new trends and opportunities? Conclusions Top-10 Risk
More informationSoftware Process. Overview
Software Process Overview What is software process? Examples of process models Unified Process (UP) Agile software development N. Meng, B. Ryder 2 1 Software Process Definition [Pressman] a framework for
More informationCOCOMO Suite Methodology and Evolution
Software Engineering Technology COCOMO Suite Methodology and Evolution In the late 1970s and the early 1980s as software engineering was starting to take shape, software managers found they needed a way
More informationSpiral Lifecycle Increment Modeling for New Hybrid Processes
Spiral Lifecycle Increment Modeling for New Hybrid Processes Raymond Madachy, Barry Boehm, and Jo Ann Lane University of Southern California Center for Software Engineering, 941 W. 37th Place, Los Angeles,
More informationSYLLABUS. What is Agility, What is an Agile Process, Agile Process Models.
Contents i SYLLABUS UNIT - I CHAPTER - 1 : INTRODUCTION TO Introduction to Software Engineering. CHAPTER - 2 : A GENERIC VIEW OF PROCESS Software Engineering, Process Framework, CMMI, Process Patterns,
More informationOracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM. An Oracle White Paper April 2012
Oracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM An Oracle White Paper April 2012 OUM Implement Core Workflow White Paper Introduction... 3 OUM is Iterative...
More informationOrganising Requirements
Requirements Organisation, Analysis and Evolution Software Requirements and Design CITS 4401 Lecture 20 CITS4401 Software Requirements and Design 2 Viewpoints Organising Requirements Interactor viewpoints:
More informationWorkshop Summary. Process Support of Software Product Lines
Workshop Summary 10 th International Software Process Workshop (ISPW 10): Process Support of Software Product Lines Barry Boehm, USC ISPW Program Chair (To appear in ISPW 10 Proceedings, IEEE, 1997) 1.
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationSoftware Engineering in the Agile World. Table of contents
Table of contents Chapter 1 14 Software Engineering 14 1.1 Introduction 14 1.2 No standard software engineering methodology 14 1.3 Waterfall methodology 15 1.3.1 Software development under Waterfall model
More informationAddressing New Technologies
c S I E 1 a COCOMO 2.0: Addressing New Technologies Barry Boehm I I th COCOMOISCM Forum October 10,1996 Barry Boehm - 1 C I S I E I Outline + Candidate Software Silver Bullets + Likely Future Software
More informationCS 320 Introduction to Software Engineering Spring February 01, 2017
CS 320 Introduction to Software Engineering Spring 2017 February 01, 2017 Recap: software development process Activities and steps Requirements engineering Design and architecture Implementation Verification
More informationCSCI 510 Final Exam, Fall 2017 v10 of solution & rubric Monday, December 11, questions, 300 points
CSCI 510 Final Exam, Fall 2017 v10 of solution & rubric Monday, December 11, 2017 4 questions, 300 points If registered DEN student, please circle: Yes Last Name: First Name: USC ID: Question 1 (48) Question
More informationValue-Based Software Engineering
Value-Based Software Engineering Barry Boehm, USC CSE Annual Research Review March 18, 2003 boehm@sunset.usc.edu http://sunset.usc.edu Outline Value-Based Software Engineering (VBSE) Overview Motivation
More informationFoundations of Software Engineering. Lecture 16: Process: Linear to Iterative Michael Hilton
Foundations of Software Engineering Lecture 16: Process: Linear to Iterative Michael Hilton 1 Learning goals Understand the need for process considerations Select a process suitable for a given project
More informationUsing the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering
Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering Barry Boehm and Jo Ann Lane University of Southern California Center for Systems and
More informationSoftware Cost Estimation Meets Software Diversity
Software Cost Estimation Meets Software Diversity Barry Boehm, USC STC 2017 Keynote September 26, 2017 Outline Sources of Software Diversity A Short History of Software Estimation Accuracy Process, Product,
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationSoftware Technology Conference
30 April 2003 Costing COTS Integration Software Technology Conference Salt Lake City Linda Brooks 1 Objective Provide a roadmap for doing an estimate for a Commercial Off-the-Shelf (COTS) software intensive
More informationSoftware Estimation 25 Years and Still Guessing
Software Composition Technologies Helping People Gain Control of Software Development Software Estimation 25 Years and Still Guessing Raymond Boehm Voice: 732.906.3671 Fax: 732.906.5728 www.softcomptech.com
More informationPertemuan 2. Software Engineering: The Process
Pertemuan 2 Software Engineering: The Process Collect Your Project Topic What is Software Engineering? Software engineering is the establishment and sound engineering principles in order to obtain economically
More informationLife Cycle Plan (LCP)
Life Cycle Plan (LCP) City of Los Angeles Public Safety Applicant Resource Center Team No. 09 Team members and roles: Vaibhav Mathur Project Manager Preethi Ramesh Feasibility Analyst Arijit Dey Requirements
More informationRequirements Organisation, Analysis. Software Requirements & Project Management CITS3220
Requirements Organisation, Analysis and Negotiation Software Requirements & Project Management CITS3220 Organising Requirements Viewpoints Interactor viewpoints: people or other systems that interact
More information