Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 COSYSMO Workshop - Survey on Intuitive Judgments (Part III) COSYSMO = 1,000 PM Historical data = 1,100 PM COSYSMO = 100 PM Historical data = 110 PM.

Similar presentations


Presentation on theme: "1 COSYSMO Workshop - Survey on Intuitive Judgments (Part III) COSYSMO = 1,000 PM Historical data = 1,100 PM COSYSMO = 100 PM Historical data = 110 PM."— Presentation transcript:

1 1 COSYSMO Workshop - Survey on Intuitive Judgments (Part III) COSYSMO = 1,000 PM Historical data = 1,100 PM COSYSMO = 100 PM Historical data = 110 PM

2 2 Using COSYSMO – Conceptual Flow COSYSMO Decisions Pertaining to SE Information Needs Information Product Stakeholders Key life cycle decision activities Questions to be answered Requirements, Issues, & Constraints Effort/Cost Estimate Estimation Delivery

3 3 SE Stakeholders Business Unit Manager (Bus Unit) Director of Engineering (DE) Director of Programs (DP) SW Functional Manager (SWM) SE Functional Manager (SEM) Engineering Process Group (EPG) Program Manager (PM) Win Manager (WM) Engineering Staff/Leads (EL) Bus Unit EPG DE DP SEM SWM WM Projects PM EL Proposals Customer Third Parties INCOSE NDIA

4 4 Key Life Cycle Decision Points for SE ISO/IEC 15288 Conceptualize Develop Transition to Operation EIA/ANSI 632 Acquisition & Supply Technical Management System Design Product Realization Technical Evaluation Operational Test & Evaluation Operate, Maintain, or Enhance Replace or Dismantle Contract Award Development ContractO&M ContractAcquisition Systems Engineering LOE Contract DE SEM WM PM DEDP PM DPDEDP SEM WMSEMDEDPPM

5 5 Common Questions How much plan/budget will be needed for SE (to achieve the intent of SE which is the realization of system that fulfills the stated need)? How accurate does it need to be? What is the right amount of systems engineering? –How do I know its not too much? –How do I know its not too little? What type of SE is needed? What are the constraints/issues (e.g., data availability)? Is the SE the same/constant across industries? domains? companies? projects? What is the value in doing systems engineering? –What is the impact if I don’t do it? –Why in systems engineering important?

6 6 Perception is Reality Scope of COSYSMO development effort did not include addressing the needs of individual estimate users at key decision points (milestones) in a project life cycle –What’s the question?, Who asking? and When? The purpose of measurement and estimation is to provide quantified insight to support decision making Reasonably accurate estimates provide the foundation to: –Develop realistic project plans –Support contract negotiations/commitments Effective estimation capability couples the estimate user and estimation model –J. Kane: “The measure of value is when people seek you out” –SMEs (e.g., Gary Thomas) bridge gap, when present!

7 7 COSYSMO Usage and Usability What is needed for COSYSMO to be adopted? Answer: a positive ROI Increased value to decision making activities divided by cost to use and maintain COSYSMO Successful COSYSMO adoption and usage is dependent on the integration of people, processes and tools


Download ppt "1 COSYSMO Workshop - Survey on Intuitive Judgments (Part III) COSYSMO = 1,000 PM Historical data = 1,100 PM COSYSMO = 100 PM Historical data = 110 PM."

Similar presentations


Ads by Google