1. |
- Kajko-Mattsson, Mira, et al.
(author)
-
A framework for the evolution and maintenance of web services
- 2005
-
In: IEEE Int. Conf. Softw. Maint. ICSM. ; , s. 665-668, s. 665-668
-
Conference paper (peer-reviewed)abstract
- In this paper, we propose SERVIAM Maintenance Framework - a framework for evolving and maintaining Web services. Our framework includes organisation, role, and process changes to accommodate Web service product and use characteristics.
|
|
2. |
- Kajko-Mattsson, Miroslawa E J, et al.
(author)
-
A Survey of Documentation Practice within Corrective Maintenance
- 2005
-
In: Empirical Software Engineering. - 1382-3256 .- 1573-7616. ; 10:1, s. 31-55
-
Journal article (peer-reviewed)abstract
- The purpose of documentation is to describe software systems and software processes. Consistent, correct and complete documentation of a software system is an important vehicle for the maintainer to gain its understanding, to ease its learning and/or relearning processes, and to make the system more maintainable. Poor system documentation, on the other hand, is the primary reason for quick software system quality degradation and ageing. Proper process documentation records the process, its stages and tasks, executing roles, their decisions and motivations, and the results of each individual process task. It is extremely important for achieving insight and visibility into the processes, important for their meaningful process measurement and thereby pivotal for achieving high process maturity. In this paper, we report on the results of an explorative study in which we have identified a number of rudimentary documentation requirements relevant within corrective maintenance, and found out how they were implemented within eighteen software organizations in Sweden. The goal was to examine the industrial documentation practice within corrective maintenance. Our results show that the documentation within corrective maintenance is still a very neglected issue within the organisations studied. None of our organisations has fully implemented all our documentation requirements.
|
|
3. |
- Kajko-Mattsson, Miroslawa E J, et al.
(author)
-
Outlining Developers' Testing Process Model
- 2007
-
In: Software Engineering and Advanced Applications, 2007. 33rd EUROMICRO Conference on 28-31 Aug. 2007. - : IEEE. - 9780769529776 ; , s. 263-270
-
Conference paper (peer-reviewed)abstract
- Most of the effort has been spent on formalizing processes for system testing. Little has been done regarding developers' unit and unit integration testing. In this paper, we study the routines of six developers when testing their software components. Our contribution is twofold. It first outlines a process model for unit and unit integration testing. It then provides feedback on the state of practice within six organizations.
|
|
4. |
- Kajko-Mattsson, Mira Miroslawa, et al.
(author)
-
Data mining for validation in software engineering : An example
- 2004
-
In: International journal of software engineering and knowledge engineering. - 0218-1940. ; 14:4, s. 407-427
-
Journal article (peer-reviewed)abstract
- Consider two independently done software engineering studies that used different approaches to cover some of the same subject area, such as software maintenance. Although done differently and for different purposes, to what extent can each study serve as a validation of the other? Within the scope of the subject area overlap, data mining can be applied to provide a quantitative assessment. This paper reports on the data mining that attempted to cross validate two independently done and published software engineering studies of software maintenance, one on a corrective maintenance maturity model, and the other on an objective classification of software maintenance activities. The data mining established that each of the two independently done studies effectively and very strongly validates the other.
|
|
5. |
- Kajko-Mattsson, Mira Miroslawa, et al.
(author)
-
Eliciting CM3 : Emergency Problem Management at Scandinavian Airline Systems
- 2006
-
In: Journal of Research and Practice in Information Technology. - 1443-458X. ; 38:4, s. 303-316
-
Journal article (peer-reviewed)abstract
- Emergency software problems may present an immediate danger to public health, safety, general welfare or business. Hence, the organisations must be well prepared to handle them with the greatest expediency. Unfortunately, the software community has paid little attention to the emergency corrective maintenance. Today, we do not have any standard process models for handling emergency situations. In this paper, we outline an emergency corrective maintenance process model. The model is called CM3: Emergency Problem Management. It is based on an industrial process model as defined at Scandinavian Airline Systems. In addition to the emergency process model, we present the status within the emergency process at Scandinavian Airline Systems, and describe the lessons learned.
|
|
6. |
|
|
7. |
- Kajko-Mattsson, Mira Miroslawa, et al.
(author)
-
Problems within front-end support
- 2004
-
In: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 16:04-5, s. 309-329
-
Journal article (peer-reviewed)abstract
- Within corrective maintenance, the front-end support mainly assists the customer- and back-end maintenance organizations in the communication of corrective maintenance demands. This implies receiving problem reports from customers, transferring them on to the back-end maintenance organization/vendor, and delivering problem solutions from the back-end maintenance organization/vendor to the customers. In this paper, we identify problems as experienced within 37 front-end support organizations in Sweden. Our results show a great variety of problems within the organizations studied. The dominating problems are the complexity of applications, customer knowledge, and complexity of support organizations.
|
|
8. |
- Kajko-Mattsson, Mira, et al.
(author)
-
Outlining a model of a release management process
- 2005
-
In: Journal of Integrated Design and Process Science. - 1092-0617 .- 1875-8959. ; 9:4, s. 13-25
-
Journal article (peer-reviewed)abstract
- One of the major concerns of any maintenance organization is to deliver software releases with maximal functionality and quality within the boundaries of the resource constraints. Hence, there is a great deal of merit in establishing a well thought-out end-to-end release management process. Unfortunately, there are no detailed models encompassing the overall activities involved in such a process. To remedy this, in this paper, we outline a preliminary release management process model integrating two sides: vendor and acceptor side.
|
|
9. |
- Kajko-Mattsson, Mira, et al.
(author)
-
SOA-zation framework (SF)
- 2010
-
In: PESOS '10 Proceedings of the 2nd International Workshop on Principles of Engineering Service-Oriented Systems. - New York, NY, USA : ACM. - 9781605589633 ; , s. 29-35
-
Conference paper (peer-reviewed)abstract
- Transitioning to SOA is a complex process. It affects and is affected by many organizational components such as strategies, processes, organizational infrastructures, and the like. These components strongly interact, keep changing, yet provide guidance for an organization's management in migrating to the use of SOA in its information systems. This paper suggests a SOA-zation Framework (SF). The framework is based on the industrial practices as observed by the authors of this paper.
|
|
10. |
- Khan, Ahmad Salman, 1979-, et al.
(author)
-
Taxonomy of Handover Activities
- 2010
-
In: PROFES '10 Proceedings of the 11th International Conference on Product Focused Software. - New York, NY, USA : ACM Press. - 9781450302814 ; , s. 131-134
-
Conference paper (peer-reviewed)abstract
- Handover of software systems is a critical stage in the system lifecycle. Despite this, it is still an under researched area. In this paper, we have developed an initial taxonomy of activities for software handover. Our taxonomy consists of seven process components where each component clusters logically coherent activities. The process components are Management and Administration, Maintenance Environment, Version and Configuration Management, Deployment, Training, Documentation and, Maintainability Management.
|
|