Models and Standards for Software Process Improvement

Hi everyone! If you’re reading this post, I’d like to thank you for your time 🙂

In this time I’ll talk about some of the models and standards for Software Process Improvement.

What are Software Process Improvement Models and Standards?

Software Process Improvement methodology is defined as a sequence of tasks, tools and techniques to plan and implement improvement activities to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs.

The following are some of the models and standards existing for the software process improvement.

CMMI

The Capability Maturity Model Integration is a proven set of global best practices that drives business performance through building and benchmarking key capabilities. This models help any organization in any industry build, improve, and measure their capabilities and improve performance.

Maturity levels represent a staged path for an organization’s performance and process improvement efforts based on predefined sets of practice areas. Each maturity level builds on the previous maturity levels by adding a new functionality.

This are the 5 maturity levels:

• Level 1: Initial
  • Unpredictable and reactive. Work gets completed but is often delayed and over budget
• Level 2: Managed
  • Managed on the project level. Projects are planned, performed, measured and controlled.
• Level 3: Defined
  • Proactive, rather than reactive. Organization-wide standards provide guidance across projects, programs and portfolios.
• Level 4: Quantitatively Managed
  • Measured and controlled. Organization is data-driven with quantitative performance improvement objectives that are predictable and align to meet the needs of internal and external stakeholders.
• Level 5: Optimizing
  • Stable and flexible. Organization is focused on continuous improvement and is built to pivot and respond to opportunity and change. The organization’s stability provides a platform for agility and innovation.

To know more about CMMI, visit https://cmmiinstitute.com/

TSP & PSP

«Personal Software Process is a guide to use disciplined personal practices to do a superior software engineering»(Humphrey,1999).

PSP helps software engineers to:

• Improve their approximating and planning skills.
• Make promises that can be fulfilled
• Manage standards of their projects
• Reduce the number of faults and imperfections in their work.

Levels of PSP

• PSP 1
  • Planning of time and scheduling.
• PSP 2
  • Personal quality management, design and code reviews.
• PSP 3
  • Personal process evolution

The Team Software Process (TSP) is an extension of PSP, scaled up for teams. It comes in handy to offer operational procedures and strategies that assist engineers and manager organize projects effectively and produce quality software using disciplined software methods. Its primary objective is creating a team environment that supports disciplined work while still building and maintaining a self directed team.

ISO-15504

ISO/IEC 15504 Standard, also known as Software Process Improvement and Capability Determination (SPICE), is an international standard created to improve the quality of Software processes, it is based on sustainability that software engineers can handle software processes more easily. It is a standard established jointly by the International Standarization Authority and the International Electronic Commission (IEC).

MOPROSOFT

MoProSoft is the Process Model for Software Industry in Mexico, its purpose is to standarize its operation incorporating improved practices in amnagement and software engineering. This model allows to increase the capacity os proviidng qualirty products to organizations and achieve international standards of competitiveness.

Ideal method

Initiating, Diagnosting, Establishing, Acting & Learning

And well, this is all for this post.

If you’ve reached ‘till this point, I’d want to thank you for your time. See you on next posts. 🙂