Table 3 Processes definition
From: Investigating measures for applying statistical process control in software organizations
Process | Definition |
|---|---|
Audit | Independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual agreements, or other criteria (ISO/IEC 2017). |
Coding | Transforms specified designs, behavior, interfaces and implementation constraints into actions that create a software system element implemented as a software product or service (ISO/IEC 2017). |
Design | Aims at providing sufficient detailed data and information about the system and its elements to enable the implementation consistent with architectural entities as defined in models and views of the system architecture (ISO/IEC 2017). |
Fixing | Process in which bugs and defects observed in the software are handled and solved to improve the software quality during its development. Differently from the maintenance process, fixing refers to fixing bugs and defects detected before delivering the software to the client (e.g., defects detected during unit tests) (Ghapanchi and Aurum 2011). |
Maintenance | Process responsible for making corrections, changes and improvements to deployed software and elements (ISO/IEC 2017). |
Project Management | Involves activities related to both project planning and project monitoring and control. It establishes and maintains plans that define project activities and provide an understanding of the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan (CMMI Institute 2010). |
Recruitment | Aims to provide the organization with necessary human resources, consistent with business needs (ISO/IEC 2017). |
Requirements Development | Responsible for eliciting, analyzing and establishing customer, product, and product component requirements (CMMI Institute 2010). |
Requirements Management | Its purpose is to manage requirements and to ensure alignment between them and the project’s plans and work products. It includes documenting requirement changes and their rationale and maintaining bidirectional traceability between source requirements, all product and product component requirements, and other specified work products (CMMI Institute 2010). |
Review | Aims to evaluate the quality of a process or product. Involves a person or a group of people examining software processes, software components, a system or its associated documentation to discover potential problems (Sommerville 2006). |
Requirements Analysis | Aims to provide a rigorous basis of data and information for technical understanding in order to aid decision-making across the life cycle (ISO/IEC 2017). |
Testing | Consists in verifying and validating the software by executing it with the purpose of finding defects (Myers 2004). |