What is SPICE?
SPICE stands for Software Process Improvement and Capability Determination. It can be translated into our language as development of software processes and determination of skill level. The purpose of the SPICE model is to create a common structure for different software process evaluation methods and a common language for evaluation results.
In recent years, technocities have been increasing, the number of companies in the field of information technologies has increased, and the labor force, experience and capital have been increasing the competitiveness of our country. On the other hand, in order to make this rapid development in the information technology sector permanent and sustainable, planning processes, traceability and measurability features should be added to software processes. Project planning, scaling, role sharing, risk planning, procurement, maintenance and repair processes need to be determined and calculated well in order to achieve the objectives of the enterprises.
The SPICE standard, or the ISO 15504 Software Process Assessment System standard, is an internationally recognized software process quality standard designed to improve software processes and to determine the ability levels of each process.
Delivering quality products to customers on time and at expected cost is the common goal of software companies who want to succeed. For this reason, these companies have focused on improving software processes to see how software processes develop and need innovations. Process assessment models are also needed to know the process improvement opportunities and carry out process assessment studies. Although there are several models in the process evaluation of software companies, it is generally based on a widely used model such as SPICE in the world. However, this model covers a wide range and process evaluation models such as Medi SPICE, Automotive SPICE and Enterprise SPICE have emerged over time.
What is ISO 15504 Software Process Evaluation System?
The ISO 15504 standard was prepared jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) and published in 1995. These standards are designed for software companies and aim to improve software development processes. These standards also allow the evaluation of the effectiveness of the processes applied by the companies.
In general, ISO 15504 Software Process Evaluation System is based on project planning process, project management process, software development process and organizational processes which are involved in software development processes.
Information technology sector is an important sector that is developing rapidly in the world and in our country. Software studies are the locomotive of this growth and have a strategic importance. Software companies need process evaluation studies for the following reasons:
- Understand what needs to be done with the need to improve software processes
- Determining the adequacy of processes to prove to customers
- Understand which processes and competencies are important in process evaluation
Software companies can use the evaluation results as follows:
- As a guide to software processes
- As a reference to prove process and process adequacy
- As a training document on employee development
- As a valid reference when comparing itself with other companies
- In-house as a process and process adequacy checklist
The Turkish Standards Institute has published the ISO 15504 standard series developed by ISO under the following headings:
- TS ISO / IEC 15504-1 Information technology - Software process evaluation - Part 1: Glossary of concepts and definitions (canceled)
- TS ISO / IEC 15504-2 ... Section 2: Reference model for process and process capacity (canceled)
- TS ISO / IEC 15504-3 ... Section 3: Evaluation process
- TS ISO / IEC 15504-4 ... Section 4: Guidance for the implementation of assessments
- TS ISO / IEC 15504-5 ... Section 5: Example for the process evaluation model
- TS ISO / IEC 15504-6 ... Chapter 6: Example for the life cycle process evaluation model
- 15504-8 ... Section 8: An exemplary process evaluation model for IT service management
- TS 15504-9 ... Section 9: Target process profiles
- TS ISO / IEC TS 15504-10 ... Section 10: Safety additions
The first two standards that were subsequently revoked were replaced by the following standards:
- TS ISO / IEC 33001 Information technology - Process evaluation - Concepts and terms
- TS ISO / IEC 33002 Information technology - Process evaluation - Requirements for the execution of process evaluation
The term geliştirme software development life cycle Bilgi in the field of information technologies refers to all the phases of the software activities during the production and usage process. In this cycle, basic steps such as analysis, analysis, design, implementation, testing and maintenance are taken. User requirements are constantly changing and evolving. Therefore, this cycle is repeated for new software requirements on the one hand and updates for existing software. In this respect, the fact that software companies have obtained ISO 15504 Software Process Evaluation System certificate or SPICE certificate for short is a great gain.
Now let's briefly look at what the software companies that have this document have achieved in this way:
- A standard structure is established for software processes
- A systematic order is established for the determination of the firm's software capability, evaluation and improvement of software quality
- The company has the opportunity to measure the development of software quality
- A culture of continuous improvement is established in the company and concrete steps are taken to continue this.
- Software processes that meet the objectives of the company are arranged with an engineering approach
- The company's resources are used effectively and correctly
- Software firms find themselves in a more concrete comparison with their competitors
The ISO / IEC 15504 SPICE model is applicable for companies of various sizes and various application areas. It is not interested in the organizational structure or management philosophy of the software company. It also does not rely on a particular software technology or software development method. Because this model sets out the basic requirements for quality software engineering.
