Mira Kajko-Mattsson

A Framework for Roles for Development, Evolution and Maintenance of SOA-Based Systems

Development, evolution and maintenance of SOA-based systems demands rethinking of the traditional roles for performing these activities. The key objective of this paper is to present preliminary ideas on the roles required for developing, evolving and maintaining SOA-based systems and to suggest a framework for areas of needed research.

CM/sup 3/: service level agreement

To be able to provide support to the customers in their daily operation, one must not only have an efficient support process, but also an agreement on the types and quality of the services to be provided. Such an agreement is usually called service level agreement (SLA). In this paper, we suggest an SLA model and show how it is realised within four organisations in Sweden. Our model is called CM/sup 3/: SLA, and is part of a major model called CM/sup 3/: SLA/OLA.

Corrective Maintenance Maturity Model: Problem Management

We present our PhD thesis, in which we suggest a process model for handling software problems within corrective maintenance. Our model is called CM/sup 3/: Problem Management.

The state of documentation practice within corrective maintenance

Consistent, correct and complete documentation is an important vehicle for the maintainer to gain understanding of a software system, to ease the learning and/or relearning processes, and to make the system more maintainable. Former studies have shown that documentation is one of the most neglected process issues within software engineering today. The authors check the current state of documentation practice within corrective maintenance in Sweden.

Commonalities in Risk Management and Agile Process Models

On the surface, agile and risk management process models seem to constitute two contrasting approaches. Risk management follows a heavyweight approach whereas agile process models oppose it. In this paper, we identify commonalities in these two process models. Our results show that they have much in common, and that a merge between them is possible.

Infrastructures of virtual IT enterprises

Service quality has become a critical survivability factor. The value of IT-business does not only lie in the products but also in the needs it serves. More and more customers require the IT companies with which they do business to continuously improve the speed and quality of their service. To provide seamless high quality service, the collaborating IT-companies/departments must organize themselves in a way so that they can act as one virtual enterprise providing a single point of contact. In this paper, we study how thirty eight companies belonging to thirty seven independent virtual enterprises have organized themselves in order to provide optimal maintenance service to their customers. Our goal is to provide a basis for future support process models and for future business models. Our results show strongly diversified infrastructures of confluent service organizations. These infrastructures were matched against CM/sup 3/: Roadmap: Organizational Perspective.

Taxonomy of problem management activities

Maintenance categories differ too much in order to be covered by one and the same generic process model. Too general process models do not give enough guidance when building process models and when measuring processes. They often invite subjectivity and imprecision. The authors suggest a detailed taxonomy of the activities for one of the processes essential within corrective maintenance: Problem Management Process. Together with other taxonomies of the processes inherent within corrective maintenance, this taxonomy should constitute a platform for defining corrective maintenance process models and an interim reference model for future measurements of corrective software maintenance.

Outlining a Model Integrating Risk Management and Agile Software Development

Previous studies show that the agile development models implement very few risk management practices. In this paper, we present and evaluate a model integrating the risk management and agile processes. The results show that the model provides a valid solution to address the lack of risk management, however, only in certain types of agile projects.

Evolution and Maintenance of SOA-Based Systems at SAS

As SOA-based systems are becoming more common, there is a need to consider how traditional IT roles and responsibilities need to change. This paper proposes a framework for roles that are required for evolving and maintaining SOA-based systems. It builds on work on traditional IT roles, as well as insights emerging from current research on SOA. The paper also presents a questionnaire for collecting data from organizations on roles that they use for SOA-based systems maintenance and evolution. Results from a pilot use of the questionnaire with Scandinavian Airline Systems (SAS) are presented.

From Knowing Nothing to Knowing a Little: Experiences Gained from Process Improvement in a Start-Up Company

Some software organizations still practice ad hoc development, evolution and maintenance of their systems. Many of them are typical start-up companies. They wish to become immediately profitable without paying heed to rudimentary success factors such as for instance software processes. As a result, they have little insight into and control over their activities. This paper reports on our experiences gained from our process improvement effort at mobile navigation, a Swedish start-up company. This effort has aided mobile navigation to progress from the stage of knowing almost nothing to knowing at least a little about their processes.