VALUE ENGINEERING IN SW PROCESS IMPROVEMENT. Pasi Ojala, University of Oulu, Finland



Similar documents
F15. Towards a More Mature Test Process. Anne Mette-Hass. P r e s e n t a t i o n

Software Quality Standards and. from Ontological Point of View SMEF. Konstantina Georgieva

2. VALUEAND VALUE ENGINEERING PROCESS

Software Process in Geant4 an overview

The Capability Road Map a framework for managing quality and improving process capability

How To Integrate Software And Systems

STS Federal Government Consulting Practice IV&V Offering

Foredragfor Den Norske Dataforening, den

Engineering a EIA - 632

How To Write Software

Abstract. Heavy vs Light Methodologies: Bulimic or Anorexic? Fernando Brito e Abreu FCT/UNL

ICT Competency Profiles framework Job Stream Descriptions

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

You Want to Use Scrum, You are Told to Use CMMI

IEEE Software Engineering Risk Management: Measurement-Based Life Cycle Risk Management PSM 2001 Aspen, Colorado

A Method for Process Assessment in Small Software Companies

Introduction for Software Configuration Management Training

CMMI: Specific Goals and Practices

Application of software product quality international standards through software development life cycle

How to Upgrade SPICE-Compliant Processes for Functional Safety

SOFTWARE QUALITY MANAGEMENT THROUGH IMPLEMENTATION OF SOFTWARE STANDARDS

1. Verzeichnis der ITIL V3 Service Strategy Prozesse

Software Quality Assurance: II Software Life Cycle

How To Become An Information Technology Consultant

Supplier Training 8D Problem Solving Approach Brooks Automation, Inc.

Testing Automated Manufacturing Processes

PM in construction industry

Controlling Software Acquisition: Is Supplier s Software Process Capability Determination Enough?

<name of project> Software Project Management Plan

TL 9000 and TS16949 Comparison

inoerp Accounts Payable Process Flows inoerp

Enclosure 2 to PfP(CPG/QA)D(2000)006 AQAP-169 (Edition 1)

An ITIL Perspective for Storage Resource Management

Transformation: Corporate Development and IT

Project QA and Collaboration Plan for <project name>

Moving to the Cloud: A Practical Guide Community IT

ITIL. Lifecycle. ITIL Intermediate: Continual Service Improvement. Service Strategy. Service Design. Service Transition

A Guide To The Project Management Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition

Service Desk Level 2 Service Description

VALUE STREAM MAPPING & VM

MTAT Software Engineering Management

Service Desk Level 1 Service Description

2003 Patricia Ensworth Page 1

UML Modeling of Five Process Maturity Models

Axios Systems. IT Service Management Solutions. Asset and Configuration Management - Building the CMDB.

0. 0 TABLE OF CONTENTS

ISO 9001/TL 9000 and CMMI Comparison

Benefits to the Quality Management System in implementing an IT Service Management Standard ISO/IEC

How to survive an Audit

Software Asset Management (SAM) and ITIL Service Management - together driving efficiency

Planning and Surviving a System Upgrade Lessons Learned

CMMI and IBM Rational Unified Process

Future of CMM and Quality Improvement. Roy Ko Hong Kong Productivity Council

PUB (MPI) 1-62 Reference: Gartner Scorecard

CM00 Change Management High Level

Engineering Process Software Qualities Software Architectural Design

Operations Department

A Report on The Capability Maturity Model

The information model at Banco de Portugal: innovative and flexible data solutions 1

SPiCE for SPACE: A Process Assessment and Improvement Method for Space Software Development

APPENDIX C EHS CONTRACTOR QUALIFICATION QUESTIONNAIRE

Software Quality Management

Capability Maturity Model Integratoin (CMMI) and its Assessment Process

NATO Integrated Quality Requirements for Software throughout the Life Cycle

Technical Competency Framework for Information Management (IM)

CAPABILITY MATURITY MODEL INTEGRATION

Audit, Business Risk and Compliance Committee Charter Pact Group Holdings Ltd (Company)

Improve your equity research productivity

Security Touchpoints When Acquiring Software. Dr Carsten Huth Nadim Barsoum Dawid Sroka

ITIL v3 Service Manager Bridge

Service Portfolio Management PinkVERIFY

Software Configuration Management. Wingsze Seaman COMP250SA February 27, 2008

Corporate Quality System Manual. Doc. No.: DOC Revision 5

Managing Software Product Development Key Differences from Service Projects

Software Engineering Tools and Methods

Validating Enterprise Systems: A Practical Guide

MEASURES FOR EXCELLENCE. Software Process Improvement: Management. Commitment, Measures. And Motivation

Software Safety Strategy for US Navy Gun System Acquisition Programs

Herstellerinitiative Software (OEM Initiative Software)

Intrusion Detection from Simple to Cloud

Services Providers. Ivan Soto

AUTOMATED TESTING and SPI. Brian Lynch

Preliminary Reference Guide for Software as a Service (SaaS)

Transcription:

VALUE ENGINEERING IN SW PROCESS IMPROVEMENT Pasi Ojala, University of of Oulu, Finland 7 TH TH November 2003 Helsinki, Finland 20 January 2004 CONTENT OVERVIEW - VALUE ENGINEERING CONCEPT - VALUE vs. CAPABILITY - VALUE ENGINEERING PROCESS VE AS A SW PROCESS IMPROVEMENT TOOL - NEW POSSIBILITIES - CAPABILITY ASSESSMENT OF VE PROCESSES - VE ASSESSMENT OF ALL PROCESSES - VE ASSESSMENT OF A PRODUCT - ENHANCED ASSESSMENT PROCESS FIRST ASSESSMENT - FIRST ASSESSMENT - EXPERIENCES - CONCLUSIONS 2/31

OVERVIEW - VALUE ENGINEERING CONCEPT - VALUE vs. CAPABILITY - VALUE ENGINEERING PROCESS 3/31 VALUE ENGINEERING CONCEPT > VE is a rigorous, systematic effort to improve the value and optimize the life cycle cost of a function or a facility. > VE generates cost improvements without sacrificing the capability levels needed. > Value is defined as: Value = Worth/Cost Worth= how much customer is willing to pay or Least possible production cost Cost= Real production cost 4/31

VALUE vs. CAPABILITY VALUE (+) Do something / Improve Situation is in control CAPABILITY (-) CAPABILITY (+) Do not worry Wasted quality VALUE (-) 5/31 VALUE ENGINEERING PROCESS VALUE STUDY PRE-STUDY Orientation Collect user/customer requirements Complete data file Determine evaluation factors Scope the study Build data models Determine team composition VALUE STUDY Information phase Complete data package Modify scope Function analysis phase Identify functions Classify functions Develop functions models Establish function worth Cost functions Establish value index Select function for study Creative phase Create quantity of ideas by function Evaluation phase Rank and rate alternative ideas Select ideas for development Development phase Conduct benefit analysis Complete technical data package Create implementation plan Prepare final proposals Presentation phase Present oral report POST-STUDY Complete changes Implement changes Monitor status Prepare written report 6/31

VE AS A SW PROCESS IMPROVEMENT TOOL - NEW POSSIBILITIES - CAPABILITY ASSESSMENT OF VE PROCESSES - VE ASSESSMENT OF ALL PROCESSES - VE ASSESSMENT OF A PRODUCT - ENHANCED ASSESSMENT PROCESS 7/31 NEW POSSIBILITIES > Three enhancements: Capability assessments to VE processes VE assessment of all processes VE assessment of a product 8/31

CAPABILITY ASSESSMENT OF VE PROCESSES > The enhanced assessment model is defined to include following new processes: VAL.1 Information collection VAL.2 Function analysis VAL.3 Being Creative VAL.4 Evaluation VAL.5 Development VAL.6 Presenting results > Value was defined as: Value = Worth/Cost Worth= how much customer is willing to pay or Least possible production cost Cost= Real production cost 9/31 VE ASSESSMENT OF ALL PROCESSES VALUE ENGINEERING BOOTSTRAP 3.2 VAL.1 Information collection VAL.2 Function analysis VAL.3 Being Creative VAL.4 Evaluation VAL.5 Development VAL.6 Presenting results LIFE CYCLE DEPENDENT ORGANIZATION ORG.1 Business engineering ORG.2 Human Resource Management ORG.3 Infrastructure Management METHODOLOGY LIFE CYCLE INDEPENDENT TECHNOLOGY TEC.1 Technology Innovation TEC.2 Technology Support for Life Cycle Processes TEC.3 Technology Support for Life Cycle Independent Processes Tool integration PROCESS RELATED ENG.1 System Requirements Analysis ENG.2 System Architecture Design ENG.3 Software Requirements Analysis ENG.4 Software Architecture Design ENG.5 Software Detailed Design ENG.6 Software Implementation and Testing ENG.7 Software Integration and Testing ENG.8 System Integration and Testing ENG.9 Maintenance ENG.10 Migration ENG.11 Retirement MANAGEMENT MAN.1 Project management MAN.2 Quality Management MAN.3 Risk Management MAN.4 Subcontractor Management SUPPORT SUP.1 Documentation SUP.2 Configuration Management SUP.3 Quality Assurance SUP.4 Verification SUP.5 Validation SUP.6 Joint Review SUP.7 Audit SUP.8 Problem Resolution PRO.1 Process definition PRO.2 Process Improvement CUSTOMER SUPPLIER CUS. 1 Aquisition CUS.2 Customer need mgnt CUS.3 Supply CUS.4 Software Operation CUS.5 Customer Support 10/31

VE ASSESSMENT OF A PRODUCT > Product assessment is done using normal VE process: VAL.1 Information collection VAL.2 Function analysis VAL.3 Being Creative VAL.4 Evaluation VAL.5 Development VAL.6 Presenting results > Functions are defined as product parts > Costs are assigned to functions and their subfunctions 11/31 ENHANCED ASSESSMENT PROCESS Pre- Assesment Briefing PREPARATION Initialization VE function analysis* Assessment team Identification Collecting Supporting Material Planning & Scheduling Defining Confidentiality Agreement EXECUTION Opening SPU Project Briefing Evaluation Final Assessment Assessment Assessment Feedback Assessment Sessions Report Preparation ReportPreparation VE STUDY, IMPROVEMENT PLANNING AND EXECUTION Orientation ** Information ** Function Analysis ** Creative phase Evaluation Development Presentation End of enhanced BOOTSTRAP Assessment * Used in value based focusing. ** Not needed in value based focusing. Activation of the SPI Process Progress Check 12/31

FIRST ASSESSMENT - FIRST ASSESSMENT - EXPERIENCES - CONCLUSIONS 13/31 FIRST ASSESSMENT > The first assessment using enhanced BOOTSTRAP assessment method was performed in summer of 2003. > It was a full assessment and included capability level calculations for all processes described in enhanced assessment model and process > Cost, worth and value were calculated as an ad hoc basis for certain processes. 14/31

EXPERIENCES > Experiences of the first assessment pointed out that the enhanced BOOTSTRAP assessment model works in practice. > Capability levels can be calculated for Value engineering processes as well as cost, worth and value. > In calculating cost, worth and value practical problems might rise if a company does not have sophisticated cost accounting systems. 15/31 CONCLUSIONS > The enhanced BOOTSTRAP assessment model still needs more development work > The relationship between VE processes and existing processes in capability based assessment methods needs more definition work as well as capability levels definition > The value dimension added possibilities to evaluate the level how well company and it s projects seek value improvement possibilities in their processes > Evaluating the value processes put people to think the value which is the starting point for for improvement work 16/31