• Skip to main content
  • Skip to primary sidebar
  • Skip to secondary sidebar
  • Skip to footer

Computer Notes

Library
    • Computer Fundamental
    • Computer Memory
    • DBMS Tutorial
    • Operating System
    • Computer Networking
    • C Programming
    • C++ Programming
    • Java Programming
    • C# Programming
    • SQL Tutorial
    • Management Tutorial
    • Computer Graphics
    • Compiler Design
    • Style Sheet
    • JavaScript Tutorial
    • Html Tutorial
    • Wordpress Tutorial
    • Python Tutorial
    • PHP Tutorial
    • JSP Tutorial
    • AngularJS Tutorial
    • Data Structures
    • E Commerce Tutorial
    • Visual Basic
    • Structs2 Tutorial
    • Digital Electronics
    • Internet Terms
    • Servlet Tutorial
    • Software Engineering
    • Interviews Questions
    • Basic Terms
    • Troubleshooting
Menu

Header Right

Home » Software Engineering » Software Process Assessment
Next →
← Prev

Software Process Assessment

By Dinesh Thakur

The existence of software process does not guarantee the timely delivery of the software and its ability to meet the user’s expectations. The process needs to be assessed in order to ensure that it meets a set of basic process criteria, which is essential for implementing the principles of software engineering in an efficient manner. The process is assessed to evaluate methods, tools, and practices, which are used to develop and test the software. The aim of process assessment is to identify the areas for improvement and suggest a plan for making that improvement. The main focus areas of process assessment are listed below.

  1. Obtaining guidance for improving software development and test processes
  2. Obtaining an independent and unbiased review of the process
  3. Obtaining a baseline (defined as a set of software components and documents that have been formerly reviewed and accepted; that serves as the basis for further development) for improving quality and productivity of processes.

Software process assessment examines whether the software processes are effective and efficient in accomplishing the goals. This is determined by the capability of selected software processes. The capability of a process determines whether a process with some variations is capable of meeting user’s requirements. In addition, it measures the extent to which the software process meets the user’s requirements. Process assessment is useful to the organization as it helps in improving the existing processes. In addition, it determines the strengths, weaknesses and the risks involved in the processes.

                       Software Process Assessment

The process assessment leads to process capability determination and process improvement. Process capability determination is an organized assessment, which analyzes the software processes in an organization. In addition, process capability determination identifies the capabilities of a process and the risks involved in it. The process improvement identifies the changes to be made in the software processes. The software capability determination motivates the organization to perform software process improvement.

Different approaches are used for assessing software process. These approaches are SPICE (ISO/IEC15504), ISO 9001:2000, standard CMMI assessment method for process improvement, CMM-based appraisal for internal process improvement, and Bootstrap,

SPICE (Software Process Improvement and Capability Determination) is a standard used for both process improvement and process capability determination. SPICE provides a framework for assessing the software process and is used by the organizations involved in planning, monitoring, developing, managing, and improving acquisitions. It is carried out in accordance with the International Organization for Standardization (ISO) and International Electro-technical Committee (IEC), which are used together and known as ISO/IEC 15504. The functions of SPICE (ISO/IEC 15504) are listed below.

  1. To develop process-rating profiles instead of pass or fail criteria
  2. To consider the environment in which the assessed process operates
  3. To facilitate self assessment
  4. To ensure suitability for all applications and all sizes of organizations.

SPICE (ISO/IEC 15504) constitutes a set of documents that is used to guide goals and fundamental activities and grade the organization according to its level of capability. In addition, it determines the capability of a process in an organization, based on the results of the assessment of the processes and products. It also develops a maturity model for process improvement. This model is known as SPICE reference model. It is applicable for all processes and comprises following six levels.

  1. Not performed: At this level, the processes are unable to accomplish the required outcomes. Thus, no identifiable products are created.
  2. Performed informally: At this level, the implemented process accomplishes the defined outcomes. It is not planned and tracked; rather it depends on individual knowledge and identifiable products.
  3. Planned and tracked: At this level, the defined process delivers products according to quality requirements within a specified time. The processes and products are verified according to the procedures, standards, and requirements.
  4. Well-defined: At this level, the processes based on software engineering principles which are capable of achieving defined outcomes are used.
  5. Quantitatively controlled: At this level, the performance measures, prediction capability and objective management are evaluated quantitatively. In addition, existing processes perform consistently within the defined limits to accomplish the desired outputs.
  6. Continuously improved: At this level, the existing processes adapt to meet future business goals. For continuous improvement, various kinds of statistical methods are used.

                          SPICE reference Model

ISO (International Organization for Standardization) established a standard known as ISO 9001:2000 to determine the requirements of quality management systems. A quality management system refers to the activities within an organization, which satisfies the quality related expectations of customers. Organizations ensure that they have a quality management system by demonstrating their conformance to the ISO 9001:2000 standard. The major advantage of this standard is that it achieves a better understanding and consistency of all quality practices throughout the organization. In addition, it strengthens the customer’s confidence in the product. This standard follows a plan-do-check-act (PDCA) cycle, which includes a set of activities that are listed below.

  1. Plan: Determines the processes and resources which are required to develop a quality product according to the user’s satisfaction.
  2. Do: Performs activities according to the plan to create the desired product.
  3. Check: Measures whether the activities for establishing quality management according to the requirements are accomplished. In addition, it monitors the processes and takes corrective actions to improve them.
  4. Act: Initiates activities which constantly improve processes in the organization.

                         Cycle in ISO 9001 : 2000

Note: The standard ISO 9001:2000 enhances the quality of a product by utilizing the processes for continual improvement of the system.

An appraisal examines processes to determine their strengths and weaknesses in an organization. The appraisal used in an organization evaluates the internal processes (series of procedures occurring in the organization) for establishing or updating process improvement. In addition, appraisal includes measuring the process improvement progress by conducting audits of the processes. To conduct an appraisal, a scheme known as SCAMPI was developed by the Software Engineering Institute (SEI).

SCAMPI is used for process improvement by gaining insight into the process capability in the organization. The major advantage of SCAMPI is that it supports process improvement and establishes a consensus within the organization regarding areas where the process improvements are needed. The major characteristics of SCAMPI are listed in Table.

                                                Table SCAMPI Characteristics

Characteristics

Description

Accuracy

Ratings of the organization reflect its capability, which is used in comparison to other organizations. The result of appraisal indicates the strengths and weaknesses of the appraised organization.

Repeatability

Ratings and results of the appraisals are expected to be consistent with another appraisal conducted under comparable conditions (Another appraisal with identical scope will produce consistent result).

Cost/Resources effectiveness

The appraisal method is efficient as it takes into account the organizational investment in obtaining the appraisal results.

SCAMPI enables an organization to select and follow an approach for developing a plan for appraisal, which is appropriate for the requirements. These appraisal requirements in CMMI (ARC) comprise criteria for developing, defining, and utilizing the appraisal methods (namely, Class A, Class B, and Class q, which are based on Capability Maturity Model Integration (CMMI) as an improved framework. The objectives of SCAMPI are listed below.

  1. To identify strengths and weaknesses of existing processes in the organization
  2. To specify an integrated appraisal method for internal process improvement
  3. To act as a motivation for initiating and focusing on software process improvement.

SCAMPI is an appropriate tool for benchmarking within the organization. This process emphasizes a rigorous method that is capable of achieving high accuracy and reliability of appraisal results. The major characteristics of classes ‘A’, ‘B’, and ‘C’ are listed in Table. Class ‘A’ assessment method should satisfy all appraisal requirements of CMMI. The major characteristic of Class ‘A’ assessment is a detailed assessment of process (es).With a thorough coverage, the strengths and weaknesses of processes are determined. SCAMPI is a Class ‘A’ assessment method for process improvement.

Class ‘B’ appraisal method should comply with a subset of ARC requirements. As shown in Table, requirements of the Class ‘A’ method are optional for, Class ‘B’. Class ‘B’ assessment helps the organization to gain insight into its process capability. It focuses on areas that need improvement. It does not emphasize detailed coverage and is not efficient for level rating. These types of appraisals are considered efficient for initial assessment in organizations that have just started to use CMMI for process improvement activities. In addition, it is useful in providing a cost effective measure for performing interim assessment and capability evaluations.

                                        Table Characteristics of Appraisal Methods

Characteristic

Class A

Class B

Class C

Amount of relative objectives gathered

High

Medium

Low

Ratings generated

Yes

No

No

Relative resources required

High

Medium

Low

Team size required for appraisal

Large

Medium

Small

Class ‘C’ appraisal methods are inexpensive and used for a short duration. In addition, they provide quick feedback to the result of the assessment. In other words, these appraisal methods are useful for periodic assessment of the projects.

Class ‘B’ and Class ‘C’ appraisals are useful for organizations that do not require generation of ratings. The primary reason for all appraisal methods should be to identify the strengths and weaknesses of the processes for their improvements.

CBA-IPI tool is used in an organization to gain insight into the software development capability. For this, the strengths and weaknesses of the existing process are identified in order to prioritize software improvement plans and focus on software improvements, which are beneficial to the organization. The organization’s software process capability is assessed by a group of individuals known as the assessment team, which generates findings and provides ratings according to the CMM (Capability Maturity Model). These findings are collected from questionnaires, document reviews and interviews with the managers of the organization. Thus, the primary goal of CBA IPI is to provide an actual picture of the existing processes in an organization. To achieve this, the assessment team performs the following functions.

  1. Provides data as a baseline to the organization in order to check its software capability
  2. Identifies issues that have an impact on the process improvement
  3. Provides sufficiently complete findings to the organization. These are used to guide the organization in planning .and prioritizing future process improvement activities.

For an assessment to be considered in CBAIPI, it should satisfy the minimum requirements concerning the assessment team, assessment plan, data collection, data validation, and reporting of the assessment results. These requirements are listed in Table.

                                               Table Requirements in CBA IPI

Requirement

Description

Assessment team

The size of the team should be minimum 4 and maximum 10 individuals. At least one team member should be from the organization.

Assessment plan

Contains goals for the assessment process. In addition, it has a schedule for assessment activities and identifies the resources required to perform the assessment. The assessment plan considers risks and the constraints, which are associated with the execution of the assessment.

Data collection

Data for process assessment is collected in the form of instruments, presentations, and documents.

Data validation

Data is validated using the rules of documentation.

Reporting of assessment

Provides summary of the whole assessment process, which presents both the strengths, and weaknesses of the processes.

The CBA IPI method is similar to SCAMPI as both are used for process assessment in an organization. However, differences do exist between the two approaches. These differences are listed in Table.

                              Table Differences between CBA IPI and SCAMPI

Issue

CBA IPI

SCAMPI

Model based

Capability Maturity Model (CMM)

Capability Maturity Model Integration (CMMI)

Licensing

No

Yes

Authorization

Through training in assessor program

Through training in appraisal program

Cost

Less external cost due to internal resource usage

Costly due to model scope, appraisal complexity, and training

Performance

Less rigorous

More rigorous

Training

Authorized lead assessors

Licensed and with authorized lead appraisers

Note: The CMMI appraisal method provides a consistent rating for organizations to convert their appraisal ratings into a maturity level.

Bootstrap is an improvement on SEI approaches for process assessment and improvement and covers the requirements laid by ISO 9000. This approach evaluates and improves the quality of software development and management process of an organization. It defines a framework for assessing and promoting process improvement. The basic objectives of this approach are listed below.

  1. To support evaluation of the process capability
  2. To identify the strengths and weaknesses of the processes in the organization being assessed
  3. To support the accomplishment of goals in an organization by planning improved actions
  4. To increase the effectiveness of the processes while implementing Standard requirements in the organization.

The main feature of the bootstrap approach is the assessment process, which leads to an improvement in the software development processes. During the assessment, the organizational processes are evaluated to define each process. Note that after the assessment is done, data is collected in a central database. In addition, it provides two questionnaires (forms containing a set of questions, which are distributed to people to gain statistical information): the first to gather data about the organization that develops the software and the second to gather data about the projects.

You’ll also like:

  1. Explain Software Process & Characteristics
  2. Software Process and Life Cycle
  3. Explain Software Configuration Management Process
  4. Criteria for Selecting Software Process Models
  5. Requirements Management Process in Software Engineering
Next →
← Prev
Like/Subscribe us for latest updates     

About Dinesh Thakur
Dinesh ThakurDinesh Thakur holds an B.C.A, MCDBA, MCSD certifications. Dinesh authors the hugely popular Computer Notes blog. Where he writes how-to guides around Computer fundamental , computer software, Computer programming, and web apps.

Dinesh Thakur is a Freelance Writer who helps different clients from all over the globe. Dinesh has written over 500+ blogs, 30+ eBooks, and 10000+ Posts for all types of clients.


For any type of query or something that you think is missing, please feel free to Contact us.


Primary Sidebar

Software Engineering

Software Engineering

  • SE - Home
  • SE - Feasibility Study
  • SE - Software
  • SE - Software Maintenance Types
  • SE - Software Design Principles
  • SE - Prototyping Model
  • SE - SRS Characteristics
  • SE - Project Planning
  • SE - SRS Structure
  • SE - Software Myths
  • SE - Software Requirement
  • SE - Architectural Design
  • SE - Software Metrics
  • SE - Object-Oriented Testing
  • SE - Software Crisis
  • SE - SRS Components
  • SE - Layers
  • SE - Problems
  • SE - Requirements Analysis
  • SE - Software Process
  • SE - Software Metrics
  • SE - Debugging
  • SE - Formal Methods Model
  • SE - Management Process
  • SE - Data Design
  • SE - Testing Strategies
  • SE - Coupling and Cohesion
  • SE - hoc Model
  • SE - Challenges
  • SE - Process Vs Project
  • SE - Requirements Validation
  • SE - Component-Level Design
  • SE - Spiral Model
  • SE - RAD Model
  • SE - Coding Guidelines
  • SE - Techniques
  • SE - Software Testing
  • SE - Incremental Model
  • SE - Programming Practices
  • SE - Software Measurement
  • SE - Software Process Models
  • SE - Software Design Documentation
  • SE - Software Process Assessment
  • SE - Process Model
  • SE - Requirements Management Process
  • SE - Time Boxing Model
  • SE - Measuring Software Quality
  • SE - Top Down Vs Bottom UP Approaches
  • SE - Components Applications
  • SE - Error Vs Fault
  • SE - Monitoring a Project
  • SE - Software Quality Factors
  • SE - Phases
  • SE - Structural Testing
  • SE - COCOMO Model
  • SE - Code Verification Techniques
  • SE - Classical Life Cycle Model
  • SE - Design Techniques
  • SE - Software Maintenance Life Cycle
  • SE - Function Points
  • SE - Design Phase Objectives
  • SE - Software Maintenance
  • SE - V-Model
  • SE - Software Maintenance Models
  • SE - Object Oriented Metrics
  • SE - Software Design Reviews
  • SE - Structured Analysis
  • SE - Top-Down & Bottom up Techniques
  • SE - Software Development Phases
  • SE - Coding Methodology
  • SE - Emergence
  • SE - Test Case Design
  • SE - Coding Documentation
  • SE - Test Oracles
  • SE - Testing Levels
  • SE - Test Plan
  • SE - Staffing
  • SE - Functional Testing
  • SE - Bottom-Up Design
  • SE - Software Maintenance
  • SE - Software Design Phases
  • SE - Risk Management
  • SE - SRS Validation
  • SE - Test Case Specifications
  • SE - Software Testing Levels
  • SE - Maintenance Techniques
  • SE - Software Testing Tools
  • SE - Requirement Reviews
  • SE - Test Criteria
  • SE - Major Problems
  • SE - Quality Assurance Plans
  • SE - Different Verification Methods
  • SE - Exhaustive Testing
  • SE - Project Management Process
  • SE - Designing Software Metrics
  • SE - Static Analysis
  • SE - Software Project Manager
  • SE - Black Box Testing
  • SE - Errors Types
  • SE - Object Oriented Analysis

Other Links

  • Software Engineering - PDF Version

Footer

Basic Course

  • Computer Fundamental
  • Computer Networking
  • Operating System
  • Database System
  • Computer Graphics
  • Management System
  • Software Engineering
  • Digital Electronics
  • Electronic Commerce
  • Compiler Design
  • Troubleshooting

Programming

  • Java Programming
  • Structured Query (SQL)
  • C Programming
  • C++ Programming
  • Visual Basic
  • Data Structures
  • Struts 2
  • Java Servlet
  • C# Programming
  • Basic Terms
  • Interviews

World Wide Web

  • Internet
  • Java Script
  • HTML Language
  • Cascading Style Sheet
  • Java Server Pages
  • Wordpress
  • PHP
  • Python Tutorial
  • AngularJS
  • Troubleshooting

 About Us |  Contact Us |  FAQ

Dinesh Thakur is a Technology Columinist and founder of Computer Notes.

Copyright © 2025. All Rights Reserved.

APPLY FOR ONLINE JOB IN BIGGEST CRYPTO COMPANIES
APPLY NOW