Complex System of Systems (CSoS): Fitness Landscapes and Acquisition Incentives Barry Boehm, USC Symposium on Complex Systems Engineering January 11-12,

Slides:



Advertisements
Similar presentations
Incremental Commitment Spiral Model, Expedited Engineering, and Kanban Jo Ann Lane and Alexey Tregubov USC CSSE Rich Turner Stevens University.
Advertisements

Software Development Life-Cycle Models
Software Life Cycle Requirements analysis System design Program design Program implementation (coding) Unit testing Integration testing System testing.
Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
COMP 474 Software Engineering Professor William L. Honig.
Modeling the Process and Life Cycle CSCI 411 Advanced Database and Project Management Monday, February 2, 2015.
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
University of Southern California Center for Systems and Software Engineering SoS Engineering and the ICM Workshop Overview Jo Ann Lane USC CSSE
1 Software Testing and Quality Assurance Lecture 34 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.
USC CSSE Workshop Overview: Top 3 Software-Intensive Systems Risk Items Barry Boehm, USC-CSSE February 14, 2007
20 September Importance of People Most important factor in the quality of software is the quality of the programmers If your life depended on.
University of Southern California Center for Software Engineering C S E USC 3/8/06©USC-CSE1 Software Acquisition and Life Cycle Management CS577b, Spring.
University of Southern California Center for Software Engineering CSE USC System Dynamics Modeling of a Spiral Hybrid Process Ray Madachy, Barry Boehm,
University of Southern California Center for Software Engineering C S E USC Hardware/Software Human Systems Integration Context and Processes USC-CSE Executive.
University of Southern California Center for Software Engineering C S E USC Barry Boehm, USC USC-CSE Executive Workshop March 15, 2006 Processes for Human.
Agile Requirements Methods CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 26, 2004.
Agile Methodology: The New Wave in Software Development By Patricia Cleary Thesis Hypothesis: The agile methodologies are better than the current methodology.
© 2007 The MITRE Corporation. All rights reserved Approved for Public Release; Distribution Unlimited Potential New Ideas from Complexity Science.
Systems of Systems: Characteristics and Challenges Barry Boehm, USC Center for Systems & Software Engineering October.
University of Southern California Center for Software Engineering C S E USC Barry Boehm, USC DoD Software Engineering S&T Summit August 7, 2001
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering
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 Toronto Department of Computer Science CSC444 Lec04- 1 Lecture 4: Software Lifecycles The Software Process Waterfall model Rapid Prototyping.
Software Development Process
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
The Scrum The Scrum Development Method Vincent Blijleven Method Engineering April 13 th, 2012.
© Blackboard, Inc. All rights reserved. Back to the Feature: An Agile, User-centric Software Development Lifecycle Cindy Barry Senior Product Manager Martha.
CS3300 Fall 2015 Software Development Lifecycles.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 7.1.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa SOFTWARE LIFECYCLE MODELS These slides contain a few.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Software Process Models
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
Architecture in the Life Cycle Stakeholder engagement models.
University of Southern California Center for Software Engineering CSE USC A Case for Anchor Point Milestones and Feasibility Rationales April 2005 Barry.
Process 3a 1 A Spiral Model of Software Development and Enhancement Barry Boehm Computer, May 1988 text pp34-45.
Customer Success Story State of Michigan : MAGI Case Study Beth Long, CGI Don Kosy, Oracle Consulting.
1 Discipline vs. Agility. 2 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors.
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
Recap Systems Philosophy Organization frames Project life cycle IT projects and recent trends Project management process groups 2.
Software Engineering 2003 Jyrki Nummenmaa 1 SOFTWARE ENGINEERING - SOFTWARE LIFECYCLE MODELS These slides contain a few different software lifecycle.
CSCE 240 – Intro to Software Engineering Lecture 2.
 Many models have been proposed to deal with the problems of defining activities and associating them with each other  The first model proposed was the.
#6- Effects of Agile on Pre-Contract Award Subtopics Acquisition Strategy Writing RFP’s allowing for Agile IPM Methodology Evaluating Bidders in Agile.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
Toward A Framework for Implementing Systems Engineering Development for Complex Systems Karl L. Brunson, GWU Thomas A. Mazzuchi, D.Sc., GWU Shahram Sarhani,
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Plan-Driven Processes Emerson Murphy-Hill. The Planning Spectrum 2 Source: Barry Boehm “Get Ready For Agile Methods, With Care,” IEEE Computer, Jan 2002.
Slide 3.1 © The McGraw-Hill Companies, 2002 SOFTWARE LIFE-CYCLE MODELS.
Making Disruption Effective
Software Development Overview
Agile Software Development
Integrating Quality Activities in the Project Life Cycle
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Software Engineering Mujahid Rafiq.
CS 577b: Software Engineering II
Software Engineering Lecture 09 & 10.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Introduction to Software Process Models
Air Force Acquisition Initiatives
Homework #4 due: Thursday, September 29th
Software Development Overview
Presentation transcript:

Complex System of Systems (CSoS): Fitness Landscapes and Acquisition Incentives Barry Boehm, USC Symposium on Complex Systems Engineering January 11-12, 2007 © USC- CSSE

2 Outline  Role of Fitness Landscapes in Complex Adaptive Systems (CAS) –S. Kauffman, At Home in the Universe, Oxford University Press, 1995  CSoS Acquisition Challenges –B. Boehm, “Some Future Trends and Implications for Systems and Software Engineering Processes”, Systems Engineering 9(1), 2006, pp  A Candidate Three-Agent Acquisition Fitness Landscape –D. Reifer and B. Boehm, “Providing Incentives for Spiral Development: An Award Fee Plan”, Defense Acquisition Review 13(1), 2006, pp

3 Role of Fitness Landscapes in CAS  Incentive structures for local behavior  Induce global behavior via adaptation to change Fitness Landscape UniformRandom Survival- Related Global Result GridlockChaosEdge of Chaos Acronym (Metaphor) OWHITS (Ostriches with Heads in the Sand) TRAW (Turkeys Running Around Wild) NOSUFAS (No One-Size- Uniformly-Fits-All Solutions CSoS Acquisition Example MIL-STD-1521B Waterfall, Fixed Price, Build-to-Spec Recursive Acquisition Reform, Total Systems Performance Responsibility Candidate for Discussion: 3-Agent Model

4 CSoS Acquisition Challenges CSoS Objective Candidate Solution ExampleChallenges Avoid Obsolescence Plan-Driven Rapid Development 4-Hour HouseInflexible Adapt to Rapid Change Agile Methods Extreme Programming Unscalable; Buggy Releases Assure Resilience Independent V&VFormal MethodsExpensive

5 Candidate Approach: 3-Agent Model Agent ObjectiveAgent Approach Fitness Landscape/ Incentive Criteria* Build Current Increment Rapid, Stable, Schedule-As- Independent Variable (SAIV), Build to Specs and Plans Meet Milestones/Exercise SAIV; Deliver on Time; Collaboration with Other Agents Assure Resilience Integrated, Independent Verification and Validation Priority-Weighted Identification of Risks and Concerns; Collaboration with Other Agents Prepare for Build of Next Increment Observe, Orient, Decide on Proof-Carrying Rebaselined Specs and Plans Risk/Opportunity Management; Rebaseline Proof Thoroughness; Collaboration with Other Agents * Evaluated by Independent Experts