These key process areas are still in the v3. Yearly assessment allows assessing the progression of the improvements, no matter what best practice framework you are using. This is because it enables you to determine your software maintenance organizations maturity level strength/weaknesses against bet practices. Based on that assessment, you can pinpoint the best starting point for using S3M 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.
Under S3M v2 my organization started with evolution engineering processes such as predelivery, transition and operational support. Does that change with S3M v3?
Posted in .
Dr. Alain April
I am full professor of Software Engineering at the University of Québec in Montréal, in its Software Engineering faculty. I have more than 30 years of Helthcare, Finance/Banking and Telecommunications IT industry experience, especially in Cloud Computing, Big Data, software acquisition, contracts, software quality assurance and business process management. I am more comfortable with open source, practical applications and technology transfer to industry.
Currently I concentrate on research projects. In the past I was the recipient of the ISO award for higher education in standardization in 2011, as well as the chair of the Software Engineering gratuate program and of the Software Engineering departement. I also published Software Engineering Books: Software Maintenance Improvement and Software Quality Assurance.