Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Stefan Forssander

dblp:69/929 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2001
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 77% Empirical software engineering · 23%

Topics — the 1 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software process improvement
software process maturity
0.012001
Corrective Maintenance Maturity Model (CM3): Maintainer's Education and Training · ICSE 2001
YearPublicationVenuePosition
2001 Corrective Maintenance Maturity Model (CM3): Maintainer's Education and Training
abstract
What is the point of improving maintenance processes if the most important asset, people, is not properly utilised? Knowledge of the product(s) maintained, maintenance processes and communications skills is very important for achieving quality software and for improving maintenance and development processes. We present CM/sup 3/: Maintainer's Education and Training-a maturity model for educating and training maintenance engineers. This model is the result of a comparative study of two industrial processes utilised at ABB, and of process models such as IEEE 1219, ISO/IEC 12207, CMM, People CMM, and TickIT.
Mira Kajko-Mattsson, Stefan Forssander, Ulf H. Olsson
ICSE2
2000 Software problem reporting and resolution process at ABB Robotics AB: state of practice
abstract
A well-functioning process for reporting, analysing and resolving software problems is an important vehicle for establishing and retaining control over the development and maintenance of software products. In this paper we present such a process, its state of practice and its role within corrective software maintenance. This process is utilized at ABB Robotics AB and is called the System Progress Report process (SPR). The SPR process is the result of our 20 years of work and experience. This paper concludes with our lessons learned and plans for future improvements. Copyright © 2000 John Wiley & Sons, Ltd.
Mira Kajko-Mattsson, Stefan Forssander, Gunnar Andersson II
J. Softw. Maintenance Res. Pract.2