Proposed Way Forward for SERC EM Task Barry Boehm, USC-CSSE 30 January 2009.

Slides:



Advertisements
Similar presentations
1 The Systems Engineering Research Center UARC Dr. Dinesh Verma Executive Director January 13,
Advertisements

Strategic Management Revision Prof.Dr. E.Vatchkova.
Prompts Consider the following questions as you build this slide:
E-OCVM (Version 2) Explained Episode 3 - CAATS II Final Dissemination Event Alistair Jackson EUROCONTROL Episode 3 Brussels, 13 & 14 Oct 2009.
Development of a Regional DRM Strategy for the Tourism Sector in the Caribbean Regional Workshop – May 5th, 2009 – Trinidad & Tobago The Sixteen Steps.
Title I Schoolwide Providing the Tools for Change Presented by Education Service Center Region XI February 2008.
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Screen 1 of 24 Reporting Food Security Information Understanding the User’s Information Needs At the end of this lesson you will be able to: define the.
Lecture 12 Reengineering Computer-aided Software Engineering Cleanroom Software Engineering.
SERC Achievements and Program Direction Art Pyster Deputy Executive Director November, Note by R Peak 12/7/2010: This presentation.
Rational Unified Process
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 Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
Proposed Approach to SERC EM Task: Assessing SysE Effectiveness in Major Defense Acquisition Programs (MDAPs) Barry Boehm, USC-CSSE 26 November 2008.
Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team Identification Measures of Success Roles & Responsibilities.
© USC-CSE1 Determine How Much Dependability is Enough: A Value-Based Approach LiGuo Huang, Barry Boehm University of Southern California.
1 Software Testing and Quality Assurance Lecture 14 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Assessing SysE Effectiveness in Major Defense Acquisition Programs (MDAPs): Support Surveys Dan Ingold, USC-CSSE 29 November 2008.
Combining Perceptions and Prescriptions in Requirements Engineering Process Assessment Presented By: Hector M Lugo-Cordero, MS EEL
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
S/W Project Management
Don Von Dollen Senior Program Manager, Data Integration & Communications Grid Interop December 4, 2012 A Utility Standards and Technology Adoption Framework.
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Petter Nielsen Information Systems/IFI/UiO 1 Software Prototyping.
Systems Investigation and Analysis
1 “ Understanding leads to perfection” Author: Herb Isenberg Ph.D A Bird’s Eye View Quality Foundations January 2011.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Work Programme for the specific programme for research, technological development and demonstration "Integrating and strengthening the European Research.
Early Childhood Development (ECD) Scales: Overview & Lessons Learned Dr. Ghazala Rafique Aga Khan University Pakistan Regional Consultative Meetings on.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
CERTIFICATION In the Electronics Recycling Industry © 2007 IAER Web Site - -
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
1 Mid-Term Review of the Hyogo Framework for Action Roadmap to Disaster Risk Reduction in the Americas & HFA Mid-Term Review.
March 26-28, 2013 SINGAPORE CDIO Asian Regional Meeting and Workshop on Engineering Education and Policies for Regional Leaders Programme Evaluation (CDIO.
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects.
Georgia Institute of Technology CS 4320 Fall 2003.
“Strategic technical assistance to improve the effectiveness of African EIA systems” Mark Stoughton, Ph.D. UNECA–CLEAA Experts’ Workshop 12 & 13 April.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Presented by CIDA on behalf of the Task Team on Multilateral Effectiveness.
Request for Proposal (RFP)
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Agile Working Group Agile Method Critical Success Factors.
Product Support Assessment Team (PSAT) Tom Simcik Performance Learning Director – Acquisition Logistics LCL FIPT 14 Nov 08.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Robert Mahowald August 26, 2015 VP, Cloud Software, IDC
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Monitoring and Evaluation in MCH Programs and Projects MCH in Developing Countries Feb 9, 2012.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
T Iteration Demo Tikkaajat [PP] Iteration
Development Team Day 5a October Aim To explore approaches to evaluating the impact of the curriculum on pupil learning.
Review of Effectiveness Measures Evaluation Task Dan Ingold, USC USC-CSSE Annual Research Review March 16, 2009.
Evaluate SE Methods, Processes and Tools Technical Task Plan USC Workshop Los Angeles, CA 16 March 2009.
Brittany Giel University of Florida Ph.D. Candidate Center for Advanced Construction Information Modeling January 8, 2013 Measuring Success - Metrics.
Dr. Kathleen Haynie Haynie Research and Evaluation November 12, 2010.
© 2016 The Aerospace Corporation Agile Fit Check Framework Outbrief Supannika Koolmanojwong Mobasser The Aerospace Corporation USC CSSE Annual Research.
Software Requirements analysis & specifications
Request for Proposal (RFP)
Agile Fit Check Framework Outbrief
CSCI 577b Tasks and Activities
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
ARB Schedule Locations
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Managing Project Work, Scope, Schedules, and Cost
Presentation transcript:

Proposed Way Forward for SERC EM Task Barry Boehm, USC-CSSE 30 January 2009

Proposed Way Forward Iterate coverage matrix Add Personnel Competency EM Revise, circulate survey; analyze results – Follow up with experience interviews Revise EM evaluation template, use to evaluate EMs – Perhaps using Coverage Matrix categories Also evaluate EMs vs. Systemic Analysis Database Develop OpCon(s) for using EM instrument(s) Determine preferred candidate EM combinations for OpCons – Possible result: Artifact-monitoring; evidence taxonomies; specialties (teaming, weapons platforms) Prepare EM instruments for pilot use – Possible result: Refined INCOSE LIs; Refined Macro Risk Tool 01/30/20092

Iterate Coverage Matrix Originators review current ratings Expand rating scale – ** - Strong – * - Adequate – o - Partial – - Missing Reorganize categories – Try for 5x5 – 7x7 range 01/30/20093

Candidate Personnel Competency EMs INCOSE Systems Engineering Certification Framework GsWERC Body of Knowledge SysE portions Nidiffer source 01/30/20094

GsWERC BoK - Requirements 01/30/20095

EM Usage OpCons Planning review vs. execution monitoring Life cycle: Greenfield, Brownfield, O&M Domain: Weapons platform, System of systems, Net- centric services EM type: Artifact-monitoring; evidence taxonomies; specialties (teaming, weapons platforms) 01/30/20096

1/27/04©USC-CSE7 Trilateral Working Group Addressing Early Warning Indicators US, UK, and Australian participants Mix of traditional and emerging indicators Current version a work in progress; seeking community feedback Organized around program goals and critical success factors Focused on readiness for milestone decision reviews

1/27/04©USC-CSE8 Software Acquisition Goals Goal 1. System and software objectives and constraints have been adequately defined and validated. Goal 2. The system and software acquisition strategies are appropriate and compatible. Goal 3. The success-critical stakeholders have committed adequate software capability to perform their software- related tasks. Goal 4. The software product plans and process plans are feasible and compatible. A Feasibility Rationale provides convincing evidence that: Goal 5. Software progress with respect to plans is satisfactory.

1/27/04©USC-CSE9 Critical Success Factors: Goal 1 Goal 1. System and software objectives and constraints have been adequately defined and validated. 1.1System and software functionality and performance objectives have been defined and prioritized. 1.2 The system boundary, operational environment, and system and software interface objectives have been defined. 1.3System and software flexibility and evolvability objectives have been defined and prioritized. 1.4System and software environmental, resource, infrastructure, and policy constraints have been defined. 1.5System and software objectives have been validated for overall achievability within the system and software constraints.

Proposed Way Forward Iterate coverage matrix Add Personnel Competency EM Revise, circulate survey; analyze results – Follow up with experience interviews Revise EM evaluation template, use to evaluate EMs – Perhaps using Coverage Matrix categories Also evaluate EMs vs. Systemic Analysis Database Develop OpCon(s) for using EM instrument(s) Determine preferred candidate EM combinations for OpCons – Possible result: Artifact-monitoring; evidence taxonomies; specialties (teaming, weapons platforms) Prepare EM instruments for pilot use – Possible result: Refined INCOSE LIs; Refined Macro Risk Tool 01/30/200910

Macro Risk Tool Demo 01/30/200911

6/18/08©USC-CSSE12 Macro Risk Model Interface 01/30/200912