Process Improvement and CMMI for Systems and Software 1st Edition by Ron Kenett, Emanuel Baker – Ebook PDF Instant Download/Delivery: 1420060503, 9781420060508
Full download Process Improvement and CMMI for Systems and Software 1st Edition after payment
Product details:
ISBN 10: 1420060503
ISBN 13: 9781420060508
Author: Ron S. Kenett, Emanuel Baker
Process Improvement and CMMI for Systems and Software provides a workable approach for achieving cost-effective process improvements for systems and software. Focusing on planning, implementation, and management in system and software processes, it supplies a brief overview of basic strategic planning models and covers fundamental concepts and appr
Process Improvement and CMMI for Systems and Software 1st Table of contents:
SECTION I STRATEGY AND BASICS OF QUALITY AND PROCESS IMPROVEMENT
1 The Strategic Role of Systems and Software Quality
Synopsis
1.1 Basic Strategic Planning
1.2 Strategic Planning Models
1.3 Elements of System and Software Quality
1.3.1 Requirements Establishment and Control
1.3.2 Methodology Establishment and Implementation
1.3.3 Quality Evaluation
1.3.4 Interactions among System Quality Program Elements
1.4 Deployment of Strategic Quality Goals
1.5 Strategic Maps and Balanced Scorecards
1.6 Summary
References
2 Basic Elements of Continuous Process Improvement
Synopsis
2.1 Continuous Improvement Infrastructures
2.2 Process Improvement Projects and Measurement Programs
2.3 Six Sigma (DMAIC and DFSS Methodology)
2.4 Enterprise Knowledge Development (EKD)
2.4.1 EKD Actor and Role Components
2.4.1.1 The Actor and the Actor’s Role
2.4.1.2 The Actor–Role Relationship
2.4.1.3 The Role–Role Relationship
2.4.1.4 Using the Notation
2.4.1.5 Guidelines for the Actor–Role Diagram
2.4.1.6 Examples of Actor–Role Diagrams
2.4.1.7 EKD Role–Activity Diagram
2.5 Organizational Patterns
2.5.1 The Notion of Pattern
2.5.2 Pattern Template
2.6 Summary
References
SECTION II ASSESSMENT AND MEASUREMENT IN SYSTEMS AND SOFTWARE DEVELOPMENT
3 CMMI, People CMM, Personal and Team Software Process, eSCM, ITIL, and ISO Standards
Synopsis
3.1 Capability Maturity Model Integration (CMMI)
3.1.1 History
3.1.2 CMMI
3.1.2.1 Motivating Factors
3.1.2.2 Version 1.1
3.1.2.3 Version 1.2
3.1.2.4 Version 1.3
3.1.3 CMMI for Acquisition (CMMI-ACQ)
3.1.4 CMMI for Services (CMMI-SVC)
3.1.5 SCAMPI Class A Appraisal Methodology
3.1.6 SCAMPI B and C Appraisals
3.2 People CMM
3.3 Personal and Team Software Process
3.3.1 PSP
3.3.2 TSP
3.4 eSourcing Capability Model (eCSM)
3.4.1 Barriers to Successful Sourcing Relationships
3.4.2 eSCM for Service Providers
3.4.3 eSCM for Client Organizations
3.4.4 eSCM Capability Determinations
3.5 Information Technology Infrastructure Library® (ITIL®)
3.5.1 Description
3.5.2 Certification
3.5.3 Connections between ITIL and eSCM
3.6 ISO Standards and Models
3.6.1 ISO 9001
3.6.2 SPICE (ISO 15504)
3.6.3 ISO 12207
3.6.4 ISO 15288
3.6.5 ISO Standard Interrelationships
3.7 Summary
References
4 System and Software Measurement Programs
Synopsis
4.1 Defining Measures for Process Control and Improvement
4.1.1 Size
4.1.2 Defects
4.1.3 Effort
4.1.4 Duration
4.1.5 Cost
4.1.6 Customer Satisfaction
4.2 Effectiveness of Process Measurement Programs
4.2.1 Attributes
4.2.2 Impact Factors
4.2.2.1 Positive Impact Factors
4.2.2.2 Negative Impact Factors
4.2.3 Measuring Impact
4.3 Measurement Program Implementation Steps
4.3.1 Plan/Evaluate Phase
4.3.1.1 Reasons for Implementation
4.3.1.2 Questions to Help Identify Goals
4.3.1.3 Identification of Sponsors
4.3.1.4 Identification of Roles and Responsibilities
4.3.2 Analysis Phase
4.3.2.1 Analysis of Audience and Identification of Target Metrics
4.3.2.2 Definition of Metrics
4.3.3 Implement/Measure Phase
4.3.3.1 Organizing for Just-in-Time Training and Education Processes
4.3.3.2 Reporting and Publishing Results
4.3.4 Improve Phase
4.3.4.1 Managing Expectations
4.3.4.2 Managing with Metrics
4.4 Case Studies
4.4.1 Measurement Program Case Studies
4.4.1.1 An Effective Measurement Program
4.4.1.2 An Ineffective Measurement Program
4.4.2 Beneficial Measurement Examples
4.4.2.1 Example 1: Staffing Profiles
4.4.2.2 Example 2: Software Size
4.4.2.3 Example 3: Problem Report Tracking
4.4.2.4 Example 4: Control Charts of Newly Opened Bugs, by Week
4.4.2.5 Example 5: Control Charts of Closed Bugs, by Week
4.4.2.6 Example 6: A Cost-Driven Dashboard
4.5 Measurement and the CMMI High Maturity Practices
4.5.1 Maturity Level 4
4.5.2 Maturity Level 5
4.5.3 High Maturity Summary
4.6 Chapter Summary
References
SECTION III IMPROVEMENTS AND TESTING OF SYSTEMS AND SOFTWARE
5 System and Software Development Process Improvement
Synopsis
5.1 Implementing System and Software Process Improvement
5.1.1 Developing a Long-Range Action Plan for Process Improvement
5.1.2 Work Environment Factors Affecting Process Improvement Plan Implementation
5.1.2.1 Facilities
5.1.2.2 Software Tools to Facilitate Process Implementation
5.1.2.3 Personnel Resources
5.1.2.4 Management Policies
5.2 Managing Improvement Projects
5.3 Roles and Responsibilities and Specifying Mission Statements
5.4 Criteria for Team Composition
5.5 Launching Improvement Teams
5.6 Managing Improvement Teams
5.7 After Action Reviews
5.8 Summary
References
6 System and Software Testing Strategies
Synopsis
6.1 Designing a Test Strategy
6.1.1 Background
6.1.2 “Pre-Alpha”: Early Testing before Feature Freeze
6.1.3 “Alpha”: Feature Freeze
6.1.4 “Validation and Beta”: Development Is Complete
6.2 Implementing a Test Strategy
6.2.1 Ten Steps for Time-to-Market and Quality Improvement
6.2.2 Build and Development Product Version Plans
6.2.3 Main Phases in the Test Plan
6.2.4 Monitoring and Controlling the Test Process
6.2.5 Defects per Build
6.2.6 Defects by Severity/Status
6.3 Software Cybernetics
6.3.1 Background
6.3.2 Modeling of Incremental Software and System Control
6.3.3 Modeling of Test Processes
6.4 Test Strategy Results
6.4.1 Accumulated Lines of Code and Accumulated Defects per Build
6.4.2 New Defects per Build
6.4.3 New Severity 1 through Severity 3 Defects per Build
6.5 Assessing Testing Effectiveness and Efficiency
6.5.1 The Software Trouble Assessment Matrix (STAM)
6.5.2 A STAM Analysis of Release 7.0
6.5.3 Comparing Releases with a STAM Analysis
6.6 Software Reliability Models
6.7 Summary
References
Appendix: Software Reliability Models
6A.1 Markov Models
6A.1.1 A Case Study of the Lipow Model
6A.2 NHPP Models
6A.2.1 The Goel–Okomoto Model
6A.2.2 The Musa–Okomoto Logarithmic Model
6A.2.3 The Yamada S-Shaped NHPP Models
6A.2.4 The Log-Power Model
6A.2.5 Other NHPP Extensions
6A.3 Bayesian Models
6A.4 Estimation for Model Parameters and Semi-Parametric Control
6A.4.1 Point Estimation for NHPP Model Parameters
6A.4.2 A General Approach for Parameter Estimation
6A.4.3 The Shiryayev–Roberts Semi-Parametric Procedure
References
7 System and Software Beta and Usability Programs
Synopsis
7.1 Planning Beta Programs
7.1.1 Introduction to Beta Planning
7.1.2 Beta Test Standard Operating Procedure
7.2 Beta Test Data Collection and Analysis
7.2.1 Beta Survey Design
7.2.2 Beta Test Survey Data Analysis
7.2.3 Reliability Models
7.3 Beta Test Risk and Usability Analysis
7.3.1 Introduction to Risk Management
7.3.2 Risk Identification
7.3.3 Risk Analysis
7.3.4 Risk Monitoring and Control
7.4 Usability Analysis
7.4.1 Introduction to Usability
7.4.2 A Case Study: Web Usability Analytics
7.4.3 A DSUID Implementation Framework: The Seven Layers Model
7.4.4 DSUID Modeling Techniques
7.5 Determining Readiness Success Criteria
7.5.1 Mapping Goals to Strategic Objectives
7.5.2 Using QFD to Establish Readiness Criteria
7.6 Managing Readiness Reviews
7.7 Summary
References
SECTION IV MANAGING AND REPORTING DATA, AND A COMPREHENSIVE CASE STUDY
8 Data Reporting and Analysis
Synopsis
8.1 Designing a Data Reporting System
8.1.1 Defining the Data to Collect
8.1.2 Establishing the Data Center
8.1.3 Data Collection
8.1.4 Data Storage and Analysis
8.1.5 Data Analysis Procedures
8.2 Operating a Data Reporting System
8.2.1 Staffing
8.2.2 Data Entry
8.2.3 Data Backups
8.2.4 Power Failure Considerations
8.3 Analyzing Data
8.4 Reporting on Findings and Consequences
8.5 Field Data Reporting
8.6 Summary
References
9 Systems Development Management Dashboards and Decision Making
Synopsis
9.1 Introduction to Systems Development Management Dashboard
9.2 A Systems Development Management Dashboard Case Study
9.2.1 Progress
9.2.2 Change
9.2.3 Staff
9.2.4 Risk
9.2.5 Quality
9.3 Additional Metrics at the PMO Level
9.3.1 M1: Profit from New Products and Systems
9.3.2 M2: Cost of Late Launch
9.3.3 M3: R&D Spend
9.3.4 M4: New Product/System Quality
9.3.5 M5: Uniqueness of Products/Systems
9.3.6 M6: Idea Generation Rate
9.3.7 M7: New Product/System Break-Even Time
9.3.8 M8: New Product/System Introduction Rate
9.3.9 M9: Product Standardization
9.3.10 M10: Cost of Quality
9.4 Risk Management and Optimizing Decisions with Data
9.4.1 Uncertainty Models and Risk Management
9.4.2 Bayes Methods in Risk Management
9.4.3 Financial Engineering and Risk Management
9.4.4 Black Swans and the Taleb Quadrants
9.5 Summary
References
10 A Case Study: The Journey of Systems, Inc. to CMMI® Level 5
Synopsis
10.1 Background of Systems, Inc.
10.2 The Systems, Inc. SCAMPI Appraisal
10.2.1 Some Background on the Need for an Appraisal
10.2.2 Appraisal Interviews at Systems, Inc.
10.2.2.1 Middle Management Discussion Group
10.2.2.2 Requirements and Customer Interface Functional Area Representative (FAR) Discussion Group
10.2.2.3 Software Design and Coding FAR Discussion Group
10.2.3 Benchmarking of Systems, Inc.
10.3 Strategic Planning for Process Improvement at Systems, Inc.
10.3.1 The Systems, Inc. Software Development Challenge
10.3.1.1 Scrum at Systems, Inc.
10.3.1.2 The Scrum Process
10.3.1.3 Roles in Scrum
10.3.1.4 Meetings/Activities in Scrum
10.3.1.5 Scrum Artifacts
10.3.1.6 Scaling Scrum in Big Projects
10.3.1.7 EKD, Patterns, and Scrum at Systems, Inc.
10.3.2 The Systems, Inc. Measurement Program
10.4 Summary and Conclusions
People also search for Process Improvement and CMMI for Systems and Software 1st:
what is cmmi process
cmmi process improvement
process improvement and change management
cmmi process management
Tags:
Ron Kenett,Emanuel Baker,Process,Improvement