What about processes According to Jacobson

[sujonkumar6300]

a process can be considered as a collection of related and highly coupled practices. In this way, the process becomes like a guide to practices whose adoption is a starting point for changing the way of working. One practice can be adopted at a time, leaving the practices already followed unchanged.

To document the practices, he proposes the metaphor of “cards” (electronic and printed). A card contains the summary of the practice, which is accompanied by a guide containing the details.

This proposal did not remain in the pipeline. In March 2010, Ivar Jacobson, Bertrand Spain Mobile Database Meyer and Richard Soley convened the best software engineering gurus to a workshop in Zurich, where they noted that software engineering is “seriously hampered by immature practices.” They all agreed that the specific problems are:

Prevalence of fashions.
Lack of a theoretical basis.
Large number of methods.
Lack of credible experimental validation.
Divide between industry practice and academic research.
They decided to form an initiative under the name Software Engineering Method and Theory (SEMAT) whose main objective is: “To support a process of re-founding Software Engineering based on solid theory, proven principles and best practices.”

At the beginning of 2011, the initiative was transferred to Object Management Group to give it greater institutional support. Everyone is invited to participate.