As the Software Process Engineering Metamodel (SPEM) version 2.0 moves towards adoption as an available specification, I wanted to share some background on SPEM in general and version 2.0 in particular. SPEM 2.0 is currently available as a final adopted specification and is expected to be finalized as an available specification by end of 2007.

Osellus was one of the earliest adopters of SPEM. Realizing early, the value of a standard process meta-model that results in interoperable process models across methodologies and mixed-technology enactment environments, its flagship product IRIS Process Author is built on SPEM 1.1. Most organizations adopting SPEM 1.1 move forward from a “no-standards” approach to modeling to a methodology agnostic industry standard approach to modeling. As process mature organizations started adopting SPEM 1.1 they uncovered many areas of improvement in the metamodel. Many of these deficiencies became the basis for a SPEM 2.0 RFP - re-using process elements and process workflow, support for process enactment, support for process metrics, better explanation of terms used in the metamodel. The final adopted specification has been able to address many of these areas of improvement and is expected to attract a wide industry support.

As I understand Osellus is committed to making IRIS Process Author SPEM 2.0 compliant as soon as the specification is finalized as an available specification. Currently available as a final adopted specification, SPEM 2.0 is expected to be finalized as an available specification by end of 2007.

Osellus plans to support SPEM 2.0 and go beyond it. In adopting SPEM 2.0, Osellus will choose to redress the concerns around the over-complexity and the lack of enactment in the metamodel. This will result in a wider participation and successful adoption by process practioners as well as support mixed-technology environments such as Microsoft VSTS and IBM Jazz.

Rather then forcing users to struggle with over-complicated terminology and unnecessary packaging such as the concept of method plugins, configurations and the variability mechanisms, IRIS Process Author will abstract this complexity through a simple user interface. IRIS Process Live will provide full enactment support for the modeled software processes enabling successful delivery of software projects. As I have noted in the past, it is not possible to come up with a sustainable process definition without enacting it in real projects. Unless project teams try to enact the defined processes, they cannot uncover process gaps. It is during process enactment that teams would uncover what is missing in their processes. Lessons learned as part of a successful or unsuccessful implementation would provide rich data to improve these processes and institutionalize the lessons across the enterprise. Compliancy reporting would mean teams can self-audit how far/away are they from meeting the compliance points as laid out in the defined process. Finally, with data-based process interventions and the empowerment of project practioners the chances of project success keep getting higher with successive implementations.

Last 5 posts by Kamal Ahluwalia

• Is my process true to my methodology of choice? - January 7th, 2008
• EPF – Failing grade on collaboration - January 2nd, 2008
• Governance Webinar Recording - December 7th, 2007
• Webinar - Effective Software Development Governance - November 28th, 2007
• IRIS Process Central is here... - November 19th, 2007

This entry was posted on Monday, June 18th, 2007 at 11:46 am and is filed under General. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.