When setting up this system in an organization, an organization must first understand its current status and then determine its suitability for a particular set of requirements in order to improve its existing processes. Finally, suppliers and other similar organizations with which they do business must determine whether their processes comply with a particular contract.
In this way, thanks to the Software Process Evaluation System, a culture of continuous improvement is established in that organization and the establishment of the necessary systems for the maintenance of this culture is supported. Another benefit of having this system is to motivate the engineering of processes that will meet the business goals of the organization. This means the best use of resources. These explanations show that the first basic principle of ISO 15504 Software Process Evaluation System is to reveal the process capability. That is, to determine the status of the processes to meet the current or anticipated business objectives.
The second important principle of the system is to avoid the difficulties arising from the nature of software products. These difficulties may be abstract, changeable, or human sensitive. Or it may be due to different application areas or the use of different technologies. A software development process is not always traceable.
This is because the design and implementation processes in software studies may not be fully separated. Looking at the results of a recent research, only 32 percent of software projects have been successful. The percentage 44 is hardly completed. Many of these projects have exceeded their costs and many of them have not been completed on time or could be completed with deficiencies. 24 percent of the projects have failed. The project was either canceled before delivery or never used. The ISO 15504 Software Process Evaluation System standard was created by the need for more disciplined development processes to avoid problems with software processes.
