1 Lecture 4.3a: Metrics Overview (SEF Ch 14) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

Configuration Management
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
GCSS-J Best Agile Practices. 2 LTG Gainey, JS/J4 Ops Sponsor: “I want capability delivered in dog-years!” GCSS-J Program Overview Joint Logistics Environment:
Quality Management System SEETHARAM- Quality Assurance
1 Lecture 3.2: Technical Reviews and Audits (SEF Ch 11) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
CLR 252 Developing Requirements Greg Prothero. Lesson #3: How to Write a Good Requirement Components and Guidelines for writing.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
1 Lecture 2.6: Organization Structures Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
COMP2002 Lecturecopyright DMU 2001 COMP2002 Quality Basics.
Pittsburgh, PA Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
4. Quality Management System (QMS)
National Finance Center’s 2008 Customer Forum EmpowHR 9.0 Billy Dantagnan Teracore.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
ISO 9001 Auditing Practices Group
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Lecture 3.5: Work Dependencies, Scheduling, IMP & IMS (SEF A16A)
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Don Von Dollen Senior Program Manager, Data Integration & Communications Grid Interop December 4, 2012 A Utility Standards and Technology Adoption Framework.
Managing Software Quality
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
1 Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
SMS Operation.  Internal safety (SMS) audits are used to ensure that the structure of an SMS is sound.  It is also a formal process to ensure continuous.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
Lecture 2.3: The Systems Engineering Plan (SEP)
From Research Prototype to Production
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Design FRAME problem solving with the engineering design process F R A M E TEXAS TECH UNIVERSITY T-STEM Center © 2009 Texas Tech University T-STEM Center.
1 Lecture 2.5: Project Planning Overview Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Lecture3 : Change Control Lecturer: Kawther Abas 447CS – Management of Programming Projects.
Different management SESW 108: Program Development and Management Dr. Kazi Abdur Rouf Instructor Settlement Services Worker Certificate Social Service.
Michael deLamare Requirements Management Program Functions R-9.
Configuration Management Non Government Std: EIA Standard-649 “A management process for establishing and maintaining consistency of a product’s performance,
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
1 Lecture 4.3b: Earned Value as the Cost and Schedule Metric (SEF Ch 14) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
ISE 412: Human Factors Engineering Dr. Laura Moody Fall, 2006.
Risk Management 1. Risks and Risk Management Risks are potential events that have negative impacts on safety or project technical performance, cost or.
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
Management of Change ► The health, safety, security, environmental, technical and other impacts of temporary and permanent changes are formally assessed,
AET0012PPT by Dr. Anwar El-Tawil Dr. Anwar El-Tawil Director ISO Programme for Developing Countries QUALITY MANAGEMENT SYSTEM ACCORDING TO.
Bill Fournier Nov 2014 Systems Engineer for Non SE Bill Fournier
Systems Engineering Conceptual System Design. Systems Engineering and Analysis, B.S. Blanchard and W. J. Fabrycky, 3 rd edition, Prentice-Hall, 1998.
Over View of CENELC Standards for Signalling Applications
Lecture 2.1b: DoD Acquisition Process (SEF Ch 2)
1 Lecture 4.2: Risk Assessment, Prioritization and Resource Allocation Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
State of Georgia Release Management Training
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
Stracener_EMIS 7305/5305_Spr08_ Systems Availability Modeling & Analysis Dr. Jerrell T. Stracener, SAE Fellow Leadership in Engineering EMIS 7305/5305.
Week 2 – Risk Planning & Identification. Risk & Risk Management.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Configuration Control (Aliases: change control, change management )
Advanced Software Engineering Dr. Cheng
Today’s Summary Tab 4 Tab 6 Tab 2 Tabs 3 and 5 Defense Acquisition
Session 2 Dr. Dan C. Surber, ESEP
Requirements Executive Overview Workshop Requirements Management Certification Training Mr. Matt Ghormley.
Requirements and Acquisition Management
Requirements and Acquisition Management
Measures of Effectiveness for Supportability
Development Projects / Analysis Projects / On-site Service Projects
Presentation transcript:

1 Lecture 4.3a: Metrics Overview (SEF Ch 14) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

2 (Program) Metrics in Management (Program) Metrics are (quantitative) measurements collected for the purpose of determining project progress and overall condition Metrics are used to manage risk (technical, cost, and schedule) Metrics are collected and reported periodically (to management and the customer) Metrics are measured over time so that changes (trends) can be observed Technical Management requires three types of Program Metrics: Product Metrics: track the development of the product Earned Value: tracks conformance to the planned schedule and costs Management Process Metrics: track management activities DoD Policy requires the identification and tracking of TPMs

3 Product Metrics [1] Product Metrics: Demonstrate progress toward meeting customer requirements Three Types: Operational Performance Life-cycle Suitability Affordability Technical Performance Measurements (TPMs): A set of (5-20) key product performance metrics selected for tracking and periodic reporting to management. Derived from MOPs Generally allocated to CIs Metric Hierarchy: Measures of Effectiveness (MOEs): high-level measures of a system’s ability to achieve operational mission success (See CDD KPPs) Measures of Suitability (MOSs): high-level measures of the extent to which the system integrates will into the operational environment. They generally include supportability, human interface compatibility, and maintainability Measures of Performance (MOPs): high-level physical or functional attributes of the system that relate (trace) to the MOEs and MOSs.

4 Product Metrics [2] Suitability Metrics: Degree to which a system can be placed satisfactorily in field use: Availability, Reliability, Maintainability (RAM) Usage Rates Supportability & Logistics Human Factors, Manpower, Training, & Safety Interoperability, compatibility, transportability Environmental Impact Robustness, Survivability Producibility, Testability, Simplicity … TPMs often include suitability metrics MTBF MTTR Affordability Metrics: LCC drivers: (Development Costs) Production Costs Operational Costs Maintenance Costs Disposal Costs

5 Earned Value (14.2) Earned Value is the standard metric for tracking cost and schedule progress and risk See Separate Briefing on Earned Value

6 Process Metrics (14.3) Management Process Metrics: measurements taken to track process of developing, building and introducing the systems: Examples include: Availability of resources (personnel) Number of new hires Items Completed Customer Satisfaction Trouble Tickets Lines of Code (developed) Complexity ECPs baselined Time to approve documents Number of High Risks Etc. These are important for CMMI

7 Summary Points (14.4) Technical Management requires three types of metrics Product Metrics Earned Value Management Process Metrics Metrics should be reported on a periodic basis The measurement, evaluation, control, and reporting of metrics should be planned to assure proper measurement, evaluation and dissemination TPMs are performance-based product metrics (key technical parameters) that are used to track progress toward meeting the program’s operational requirements Use of TPMs is required by DoDI

8 Technical Performance Measurement (S14-A) [1] See separate TPM briefing