FAQs

How does S^3M v3 improve on previous versions?

While much of the content remains the same, a number of new practices were incorporated in S^3M v3.  For example, an organization can use the version 3 mapping to CobiT version 4.1 and ITIL v3. Another example is in the book: Software Maintenance Management: Evaluation and Continuous improvement, where four case studies and ideas are available for those involved in strategic improvement of software maintenance. Each organization will have to determine if the new guidance will benefit their specific software maintenance situations.

Is S^3M v3 really a radical change from models like the CMMi, CobiT and ITIL? We have already spent a lot of time and money following the guidance under these models and are confused as to how we should proceed and are concerned that this new investment will be a waste.

Rest assured: Your investment in CMMi, CobiT and ITIL guidance is well-protected as guidance from the current releases is incorporated in S^3Mv3. S^3M is a complement to these process models as none of them really addresses the needs of the small maintenance organizations. S^3M is easily understood and readily usable by the process improvement staff as it complements a service-centric approach that aims to better align IT services with business strategy.

Under S^3M v2 my organization started with evolution engineering processes such as predelivery, transition and operational support. Does that change with S^3M v3?

These key process areas are still there in v3. At least yearly assessment is always the best place to assess where to improve, no matter what best practice framework you are using, because it enables you to determine your software maintenance organizations maturity level. Based on that assessment, you can pinpoint the best starting point with S^3M guidance. For example, if your organization is mature in its software evolution or correction services, then it's probably time to assess the benefits of process management or support to evolution engineering activities.

I understand that S^3M is a best practices framework and guidance, not a standard.

Yes. Although S^3M is not a standard, it fully maps with ISO/IEC 14764 processes and offers invaluable information to organizations that set out to comply with ISO9001:2000. It provides the guidance for putting the processes in place to meet the ISO/IEC standard in the software maintenance area.

Will there be an ISO standard for S^3M?

S^3M is already referred by the ISO/IEC TR 19759 in the software maintenance chapter. S^3M is identified as a best practices framework that offers guidance on improving software maintenance. A proposal for an ISO/IEC 15504 reference model for software maintenance will be presented to ISO/IEC JTC1 in the future. The issue with ISO 15504 is that the current reference models only address software development. Presenting new perspectives may need long term efforts as the proliferation of models is an issue that must be adressed.

Can only large organizations benefit from S^3M?

Organizations of any size can benefit using S^3M. S^3M has been built to address very small software maintenance to very large software maintenance organizations. But regardless of the size of your organization, success with S^3M depends on the organization's ability to make the business case for implementing S^3M. Some organizations conduct self-assessment and do not involve corporate QA groups. Others must secure executive commitment to conduct assessments and authorize the changes proposed by S^3M.

What do you consider to be the biggest benefit from adopting S^3M?

Minor maintenance account for a large portion of the IT budget. It is a sleeping dragon. It is also key to customer satisfaction. S^3M enables organizations to provide IT services that are better understood, more easily maintained and more cost-effective. It also leverages on your ITIL and CMMi activities.

Caroline Milam, ATX MES/UI Domain Mgr. at Freescale USA: ‘The S^3M model has helped us initiate a process initiative where all other models fail to address the particular issues of software maintenance.’