SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Kajko Mattsson Mira) "

Sökning: WFRF:(Kajko Mattsson Mira)

  • Resultat 1-50 av 130
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Kajko-Mattsson, Mira, et al. (författare)
  • A framework for the evolution and maintenance of web services
  • 2005
  • Ingår i: IEEE Int. Conf. Softw. Maint. ICSM. ; , s. 665-668, s. 665-668
  • Konferensbidrag (refereegranskat)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. (författare)
  • A Survey of Documentation Practice within Corrective Maintenance
  • 2005
  • Ingår i: Empirical Software Engineering. - 1382-3256 .- 1573-7616. ; 10:1, s. 31-55
  • Tidskriftsartikel (refereegranskat)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. (författare)
  • Outlining Developers' Testing Process Model
  • 2007
  • Ingår i: Software Engineering and Advanced Applications, 2007. 33rd EUROMICRO Conference on 28-31 Aug. 2007. - : IEEE. - 9780769529776 ; , s. 263-270
  • Konferensbidrag (refereegranskat)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. (författare)
  • Data mining for validation in software engineering : An example
  • 2004
  • Ingår i: International journal of software engineering and knowledge engineering. - 0218-1940. ; 14:4, s. 407-427
  • Tidskriftsartikel (refereegranskat)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. (författare)
  • Eliciting CM3 : Emergency Problem Management at Scandinavian Airline Systems
  • 2006
  • Ingår i: Journal of Research and Practice in Information Technology. - 1443-458X. ; 38:4, s. 303-316
  • Tidskriftsartikel (refereegranskat)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. (författare)
  • Problems within front-end support
  • 2004
  • Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 16:04-5, s. 309-329
  • Tidskriftsartikel (refereegranskat)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. (författare)
  • Outlining a model of a release management process
  • 2005
  • Ingår i: Journal of Integrated Design and Process Science. - 1092-0617 .- 1875-8959. ; 9:4, s. 13-25
  • Tidskriftsartikel (refereegranskat)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. (författare)
  • SOA-zation framework (SF)
  • 2010
  • Ingår i: PESOS '10 Proceedings of the 2nd International Workshop on Principles of Engineering Service-Oriented Systems. - New York, NY, USA : ACM. - 9781605589633 ; , s. 29-35
  • Konferensbidrag (refereegranskat)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. (författare)
  • Taxonomy of Handover Activities
  • 2010
  • Ingår i: PROFES '10 Proceedings of the 11th International Conference on Product Focused Software. - New York, NY, USA : ACM Press. - 9781450302814 ; , s. 131-134
  • Konferensbidrag (refereegranskat)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.
  •  
11.
  • Avetisyan, A., et al. (författare)
  • Preface
  • 2019
  • Ingår i: APSSE 2019 Actual Problems of System and Software Engineering. - : CEUR-WS. ; , s. 1-2
  • Konferensbidrag (refereegranskat)
  •  
12.
  • Dini, P., et al. (författare)
  • Proceedings - 5th International Conference on Software Engineering Advances, ICSEA 2010 : Preface
  • 2010
  • Ingår i: International Conference on Software Engineering Advances (ICSEA). - : Institute of Electrical and Electronics Engineers (IEEE). ; , s. xii-xiii
  • Konferensbidrag (populärvet., debatt m.m.)abstract
    • Presents the introductory welcome message from the conference proceedings. May include the conference officers' congratulations to all involved with the conference event and publication of the proceedings record.
  •  
13.
  •  
14.
  • Jacobson, Ivar, et al. (författare)
  • Re-founding Software Engineering : SEMAT at the Age of Three (Keynote Abstract)
  • 2012
  • Ingår i: Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering. - New York, NY, USA : ACM. - 9781450312042 ; , s. 15-19
  • Konferensbidrag (refereegranskat)abstract
    • Software engineering is gravely hampered by immature practices. Specific problems include: The prevalence of fads more typical of the fashion industry than an engineering discipline; a huge number of methods and method variants, with differences little understood and artificially magnified; the lack of credible experimental evaluation and validation; and the split between industry practice and academic research.
  •  
15.
  • Jacobson, Ivar, et al. (författare)
  • Semat-Three Year Vision
  • 2012
  • Ingår i: Programming and computer software. - : Springer. - 0361-7688 .- 1608-3261. ; 38:1, s. 1-12
  • Tidskriftsartikel (refereegranskat)abstract
    • The purpose of writing this Three Year Vision paper is threefold. Firstly, it briefly recaps theprogress Semat has made thus far; secondly, it lays out the future directions for people working actively withinthe Semat community; thirdly, it provides the background for seeking funding support from agencies, such asthe European Community and the like. Funding support is necessary to sustain the ongoing activities ofSemat and its growth into a broader community effort, as most people working within Semat are volunteers.As such, the paper may be both too much and too little for the wider supporter base. However, we intend tomake our work fully transparent, hence, we publish it widely. We seek feedback and comments from supporters and signatories in order to improve the vision. In this context, other companion papers are being writtento better address the specific needs for the practitioners, the industry and the academia.
  •  
16.
  • Jeppesen, Gudrun, et al. (författare)
  • Peeking into developers' testing process
  • 2009
  • Ingår i: Proceedings - 2009 International Conference on Computational Intelligence and Software Engineering, CiSE 2009. - 9781424445073 ; , s. 5366347-
  • Konferensbidrag (refereegranskat)abstract
    • Recently, developers' testing process has received more recognition. Despite this, we have still no insight into its status within the industry. In this paper, we study the status of developers' testing process at Nomadic Software AB. Our results show that the process is not uniformly executed. The company suffers from lack of control over the methods used, lack of formal requirements communication, lack of static testing practice and lack of testing process documentation.
  •  
17.
  • Johnson, Pontus, et al. (författare)
  • 2nd SEMAT workshop on a general theory of software engineering (GTSE 2013)
  • 2013
  • Ingår i: 2013 35th International Conference on Software Engineering (ICSE). - New York : IEEE. - 9781467330763 ; , s. 1525-1526
  • Konferensbidrag (refereegranskat)abstract
    • Most academic disciplines emphasize the importance of their general theories. Examples of well-known general theories include the Big Bang theory, Maxwell's equations, the theory of the cell, the theory of evolution, and the theory of demand and supply. Less known to the wider audience, but established within their respective fields, are theories with names such as the general theory of crime and the theory of marriage. Few general theories of software engineering have, however, been proposed, and none have achieved significant recognition. This workshop, organized by the SEMAT initiative, aims to provide a forum for discussing the concept of a general theory of software engineering. The topics considered include the benefits, the desired qualities, the core components and the form of a such a theory.
  •  
18.
  • Kajko-Mattsson, Mira, et al. (författare)
  • A framework for roles for development, evolution and maintenance of SOA-based systems
  • 2007
  • Ingår i: Proceedings - ICSE 2007 Workshops. - 0769529607 - 9780769529608 ; , s. 4273295-
  • Konferensbidrag (refereegranskat)abstract
    • Development, evolution and maintenance of SOAbased 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.
  •  
19.
  • Kajko-Mattsson, Mira (författare)
  • A Method for Designing Software Engineering Educational Programs
  • 2012
  • Ingår i: 2012 IEEE 25th Conference On Software Engineering Education And Training (CSEE&T). - : IEEE. - 9780769546933 ; , s. 139-143
  • Konferensbidrag (refereegranskat)abstract
    • The scope of software engineering has become enormous and impossible to teach it in its entirety. Hence, educational programs should focus on a subset of its body of knowledge. In this paper, we suggest Reuse and Progress Driven Software Engineering Educational Method (RaPSEEM). The method aids in organizing the software engineering body of knowledge when designing specific software engineering programs.
  •  
20.
  •  
21.
  • Kajko-Mattsson, Mira, et al. (författare)
  • A model of front-end pre-change corrective testing
  • 2006
  • Konferensbidrag (refereegranskat)abstract
    • Most of the testing process models deal with testing within development. To our knowledge, there are no process models exclusively dedicated to the testing of corrective changes. For this reason, we have outlined a process model covering the testing activities at the front-end support level and evaluated them within IS software organizations.
  •  
22.
  • Kajko-Mattsson, Mira, et al. (författare)
  • An outline of CM(3) : Emergency problem management
  • 2005
  • Ingår i: EUROMICRO-SEAA 2005: 31ST EUROMICRO CONFERENCE ON SOFTWARE ENGINEERING AND ADVANCED APPLICATIONS, PROCEEDINGS. - 0769524311 ; , s. 292-300
  • Konferensbidrag (refereegranskat)abstract
    • Despite its importance, the process for emergency corrective maintenance has received very little attention. Today, we do not have any standard process models for handling emergency situations. The only models that have been defined can be found within the industry. In this paper, we outline an emergency corrective maintenance process model and evaluate its applicability to manage the new technology systems, the Web service systems. Our model has been elicited at Scandinavian Airline Systems (SAS). It provides a basis for developing a more detailed model of emergency corrective maintenance process - CM(3): Emergency Problem Management.
  •  
23.
  • Kajko-Mattsson, Mira (författare)
  • Applicability of IEEE 1219 within corrective maintenance
  • 2006
  • Konferensbidrag (refereegranskat)abstract
    • The IEEE 1219 standard is too general. It proposes one generic process model for all maintenance categories. However, maintenance categories differ too much. Hence, they cannot be reflected in one generic model. In this paper, we match Corrective Maintenance Maturity Model and parts of Evolution and Maintenance Maturity Model against the IEEE 1219 standard. Our results show that the IEEE 1219 standard must be revised to properly reflect the domain of corrective maintenance within industry.
  •  
24.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Classes of distributed Agile development problems
  • 2010
  • Ingår i: Proceedings - 2010 Agile Conference, AGILE 2010. - 9780769541259 ; , s. 51-58
  • Konferensbidrag (refereegranskat)abstract
    • Little is known about problems encountered in distributed Agile development environments. There have been some case studies reporting on them. However, these studies have been mainly limited to the scope and context of only one or a few companies. As a result, we do not possess an overall picture of what types of problems and challenges the companies may encounter in distributed Agile environments. In this paper, we analyze twelve case studies from the existing literature, identify thirteen problems reported in them and their solutions, and we group the problems into six classes: Culture, Time Zone, Communication, Customer Collaboration, Trust, Training and Technical Issues.
  •  
25.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Cloud outsourcing requires a proper handover process (position paper)
  • 2010
  • Ingår i: Proceedings - 6th Intl. Conference on Advanced Information Management and Service, IMS2010, with ICMIA2010 - 2nd International Conference on Data Mining and Intelligent Information Technology Applications. - 9788988678312 ; , s. 142-146
  • Konferensbidrag (refereegranskat)abstract
    • Cloud Outsourcing has shown to be a successful form of delegating tasks to individual programmers over the Internet in the context of small businesses. As a result, bigger companies are now strongly considering to practice it. Going over to Cloud Outsourcing, however, can be a very challenging task. It does no longer imply delegating some simple tasks to some outsourcees and acquiring their results. It implies a handover of complex system parts to be worked upon and a handover of knowledge and experience required for performing the tasks on the system parts. In this paper, we claim that the software community must define a proper handover process before embarking on Cloud Outsourcing. If we do not have such a process in place, we are likely to fail when delegating complex responsibilities to unknown parties over the Internet. In this paper, we also identify research questions that need to be answered before going over the Cloud Outsourcing mode.
  •  
26.
  • Kajko-Mattsson, Mira, et al. (författare)
  • CM 3 : Emergency problem management - A scenario-based evaluation
  • 2012
  • Ingår i: Proceedings - ICIDT 2012, 8th International Conference on Information Science and Digital Content Technology. - : IEEE Computer Society. - 9788988678695 ; , s. 379-386, s. 379-386
  • Konferensbidrag (refereegranskat)abstract
    • Competitiveness and survivability of many companies today does not only depend on their products and development processes. It also strongly depends on how effective the organizations are in managing emergency software problems. Despite this, there is only one process model dealing with software emergencies. It is CM 3: Emergency Problem Management. In this paper, we evaluate CM 3: Emergency Problem Management using three real-life emergency case scenarios. Our results show that the emergency processes strongly vary from case to case. Despite this, they could be easily mapped on the CM 3: Emergency Problem Management constituents.
  •  
27.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Communicating Risk Information in Agile and Traditional Environments
  • 2007
  • Ingår i: SEAA 2007. - 9780769529776 ; , s. 401-408
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • Structured and disciplined communication is a prerequisite for the effective management of risks. In this paper, we investigate what risk management information is communicated in traditional and agile development environments. Our goal is to find out whether there is any difference in the way risks are communicated. We do this by studying the management of risk information within three Canadian organizations. Our results show that there are few differences between the information as communicated in traditional and agile environments.
  •  
28.
  • Kajko-Mattsson, Mira, 1955- (författare)
  • Corrective maintenance maturity model : problem management
  • 2001
  • Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
    • Maintenance has become one of the most complex, crucial and costly disciplines within software engineering. Despite this, very few maintenance process models have been suggested. The extant models are too general, covering all maintenance categories, i.e., corrective, adaptive, perfective, and preventive maintenance. They do not help in acquiring a deep objective understanding of any of the maintenance categories.One way to remedy this is to create process models specialised to each maintenance category. Corrective Maintenance Maturity Model (CM3) is such a model. It is entirely dedicated to corrective maintenance. It encompasses the most important processes utilised within this domain. They are CM3: Predelivery/Prerelease, CM3: Transition, CM3: Problem Management, CM3: Testing, CM3: Documentation, CM3: Upfront Maintenance, and CM3: Maintainers' Education and Training.In this thesis, we consider in detail one of the CM3 constituent process models, CM3: Problem Management. Problem management is the basis for conducting corrective maintenance. It not only handles software problems but also provides quantitative feedback important for assessing product quality, crucial for continuous process analysis and improvement, and essential for defect prevention.Just as other CM3 constituent processes, CM3: Problem Management is based on CM3 definitions of maintenance and of corrective maintenance, and it follows the CM3 process structure. It has seven components: (1) Taxonomy of Activities, which lists a set of activities relevant for the problem management process; (2) Conceptual Model, which defines concepts relating to information about the process; (3) Maintenance Elements, which explain and motivate the implementation of maintenance process activities; (4) Process Phases, which structure the CM3 constituent processes into process phases; (5) Maturity Levels, which structure the problem management process into three maturity levels (Initial, Defined and Optimal); (6) Roles, which define the responsibilities of individuals executing the process, and (7) Roadmaps, which aid in the navigation through the problem management process.Our primary goal with the CM3 model and its constituent processes is to create a fine-grained process model that allows maximal visibility into corrective maintenance. Some of our other goals are (1) to establish a common forum for communicating about corrective maintenance, (2) to suggest an evolutionary improvement path for software organisations from an ad hoc immature process to a mature and disciplined one, (3) to enable industrial organisations to examine their own practices and compare notes, (4) to provide a pedagogical tool for universities and industrial organisations in the process of educating their students and software engineers within the area of corrective maintenance.CM3: Problem Management was built primarily for ABB. It is the result of two research projects: Software Metrics Laboratory, and Software Maintenance Laboratory. Software Metrics Laboratory was established jointly by Ericsson and the Department of Computer and Systems Sciences (DSV) at the Royal Institute of Technology and Stockholm University in the years 1994-1996. During these years, we have developed a conceptual model of the basic concepts relating to the handling of software problems within corrective maintenance. This conceptual model evolved into CM3: Problem Management: Conceptual Model (Revisited) developed during the Software Maintenance Laboratory phase - a collaboration between ABB and DSV in the years 1998-2000. Although CM3: Problem Management has been primarily developed in the ABB context, it is targeted to all software organisations involved in building or improving their corrective maintenance processes.
  •  
29.
  • Kajko-Mattsson, Mira (författare)
  • Demarcating risk management responsibilities of a project manager
  • 2010
  • Ingår i: ITNG2010 - 7th International Conference on Information Technology. - 9780769539843 ; , s. 1227-1232
  • Konferensbidrag (refereegranskat)abstract
    • Most of the standards and process models are not explicit enough about demarcating risk management responsibilities of project managers. Usually, they place them entirely on a project level. In this paper, we study the risk management responsibilities of project managers within 53 software companies. Our goal is to find out what exactly project managers do within pre-project and project activities such as requirements, project and task planning and what risk management responsibilities they have within these activities. Our results show that the responsibility portfolio of project managers varies depending on the degree of their engagement within pre-project and project phases; the broader the project managers' responsibility portfolio, the broader their risk management responsibility portfolio.
  •  
30.
  • Kajko-Mattsson, Mira, et al. (författare)
  • DRiMaP - A model of distributed risk management process
  • 2009
  • Ingår i: NCM 2009 - 5th International Joint Conference on INC, IMS, and IDC. - 9780769537696 ; , s. 994-1000
  • Konferensbidrag (refereegranskat)abstract
    • Distributed software development creates many challenges to the primary contractors having the responsibility of delivering high quality products to their customers. To tackle these challenges, organizations must have an efficient distributed development process in place. They must also effectively manage risks within this distributed environment. In this paper, we suggest DRiMaP - a model of distributed risk management. This model has been designed at IBM Sweden.
  •  
31.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Eliciting an enhancive maintenance model in three organisations in Ghana
  • 2006
  • Ingår i: Proc. IEEE/ACIS Int. Conf. Comput. Info. Sci.. - 0769526136 - 9780769526133 ; , s. 244-251
  • Konferensbidrag (refereegranskat)abstract
    • To continuously meet the changing needs of the customers, organisations follow their own enhancive maintenance process models. Unfortunately, these models are not easily available to the academic world. In this paper, we study enhancive maintenance in three organisations in Ghana. Our goal is to explore information about the initial phases of the enhancive maintenance process and put them into a process model Our model makes provision for process phases, their activities, roles, and data needed for managing enhancements. Although the primary goal of this paper is to elicit an enhancive maintenance model, we will not deny that it also provides the information on the state of enhancive maintenance practice in one developing country - Ghana.
  •  
32.
  •  
33.
  •  
34.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Essential components of e-maintenance
  • 2011
  • Ingår i: International Journal of Performability Engineering. - 0973-1318. ; 7:6, s. 555-571
  • Tidskriftsartikel (refereegranskat)abstract
    • Many intellectual, societal, business and technological forces are continuously pushing forward the frontiers of science. When combined, they provide an umbrella for generating new fields and exploring new grounds. One such a new field is e-Maintenance. e-Maintenance addresses new needs and provides various benefits in form of increased availability, reduced lifecycle cost and increased customer value. However, it suffers from lack of a commonly defined basis supporting the existence of e-Maintenance and determining the essential components inherent in the e-Maintenance domain. In this paper, we suggest an initial set of components that serve as the groundwork of the e-Maintenance universe. The set outlines ten initial components. These are definition, business,organization, product,service,methodology,technology,information,customer,and education and training. The paper also suggests a definition of e-Maintenance, places eMaintenance in the context of other e-Domains, and elicits e-Maintenance intellectual opportunities and challenges to be met by both the academia and industry.
  •  
35.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Evaluating A Taxonomy of Handover Activities in One Swedish Company
  • 2010
  • Ingår i: 36th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), 2010. - : IEEE Computer Society. - 9780769541709 - 9781424479016 ; , s. 324-349
  • Konferensbidrag (refereegranskat)abstract
    • Handing over a software system from development to maintenance is still an under-researched domain. The software community has a hazy insight into its constellation and inherent activities. In this paper, we have evaluated a preliminary version of a taxonomy of handover activities within one Swedish software company. The evaluation is conducted in an in-house handover context only. Despite this, our results provide evidence of its enormous complexity, variability and strong dependency on many other software engineering processes.
  •  
36.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Evaluating SLA management process model within four companies
  • 2008
  • Ingår i: Proc. - Int. Conf. Softw. Eng. Adv., ICSEA, Inlucdes ENTISY: Int. Workshop Enterp. Inf. Sys.. - 9780769533728 ; , s. 158-165
  • Konferensbidrag (refereegranskat)abstract
    • The ability to deliver support according to predetermined Service Level Agreements (SLAs) has become an important success factor. To be able to do it, organizations need a sound SLA management process model. Presently, they base their SLA management strategy on standardized frameworks, such as ITIL or COBIT. However, due to the complexity of these frameworks, organizations need simpler models that can be easily implemented. In this paper, we outline an SLA Management process model and evaluate it within four organisations.
  •  
37.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Evaluating SLA Management Process Model within Four Companies
  • 2008
  • Ingår i: International Conference on Software Engineering and Applications.
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • The ability to deliver support according to pre-determined Service Level Agreements (SLAs) has become an important success factor. To be able to do it, organizations need a sound SLA management process model. Presently, they base their SLA Management strategy on standardized and widely accepted SLA management frameworks, such as ITIL or COBIT. However, due to the complexity of these frameworks, organizations need simpler SLA management process models that can be easily implemented. In this paper, we outline an SLA Management process model and evaluate it within four organisations.
  •  
38.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Evaluation of the Applicability of CM3 : Emergency Problem Management within the Industry
  • 2014
  • Ingår i: ICSEA 2014, The Ninth International Conference on Software Engineering Advances. - : International Academy, Research and Industry Association (IARIA). - 9781612083674 ; , s. 485-494
  • Konferensbidrag (refereegranskat)abstract
    • Software has become one of the main villains of many organizational problems, emergencies and crises. Despite this, there is only one process model defining how to manage emergency software problems. It is CM3: Emergency Problem Management. In this paper, we evaluate the applicability of the CM3: Emergency Problem Management model within five companies. Our results show that the model correctly manages the real-life emergency and crisis situations that are dependent on malfunctioning software. This evaluation shows that all the five companies have emergency processes that reflect CM3 model’s architecture, however, to different degrees. Additionally all the five companies have also designated roles that act as focal points of information and decision making during emergencies. Finally, only one company has identified the organizations and systems, which should be affected by the emergency process.
  •  
39.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Everything is possible to structure-even the software engineering body of knowledge
  • 2017
  • Ingår i: Proceedings - 2017 IEEE/ACM 1st International Workshop on Software Engineering Curricula for Millennials, SECM 2017. - : Institute of Electrical and Electronics Engineers (IEEE). - 9781538627952 ; , s. 61-67
  • Konferensbidrag (refereegranskat)abstract
    • Everything is possible to structure, even the software engineering body of knowledge. In this paper, we suggest a conceptual model of the software engineering body of knowledge. The model is a restructured version of SWEBOK and ACM/IEEE Curriculum Guidelines. It constitutes the first attempt to create an underlying structure that is common to most of the software engineering bodies of knowledge.
  •  
40.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Evolution and maintenance of SOA-based systems at SAS
  • 2008
  • Ingår i: Proc. Annu. Hawaii Int. Conf. Syst. Sci.. - 0769530753 - 9780769530758
  • Konferensbidrag (refereegranskat)abstract
    • 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.
  •  
41.
  • Kajko-Mattsson, Mira (författare)
  • Evolution and maintenance of web service applications
  • 2004
  • Ingår i: 20th IEEE International Conference on Software Maintenance,  proceedings. - 0769522130 ; , s. 492-493
  • Konferensbidrag (refereegranskat)abstract
    • In this paper, we suggest a panel debate on evolution and maintenance of web services. The panel will discuss the evolution and maintenance of web service applications.
  •  
42.
  • Kajko-Mattsson, Mira, et al. (författare)
  • From knowing nothing to knowing a little : Experiences gained from process improvement in a start-up company
  • 2008
  • Ingår i: Proceedings - International Conference on Computer Science and Software Engineering, CSSE 2008. - 9780769533360 ; , s. 617-621
  • Konferensbidrag (refereegranskat)abstract
    • 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.
  •  
43.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Fundamentals of the eMaintenance Concept
  • 2010
  • Ingår i: <em>Proceedings of the 1st International Congress on eMaintenance</em>. - Luleå, Sweden : Luleå University of Technology. - 9789174391206 ; , s. 147-154
  • Konferensbidrag (refereegranskat)abstract
    • Many intellectual, societal, business and technological forces are continuously pushing forward the frontiers of science. When being effectively combined, they may provide an umbrella for generating new fields and exploring new grounds.  One such emerging field is eMaintenance. It is based on the fields from operation & maintenance engineering, software engineering, information systems, business management, and many other strongly varying fields related to the application domains of eMaintenance. As a novel field, eMaintenance addresses new needs and provides various benefits in form of increased availability, reduced lifecycle cost and increased customer-value. On the other hand, being in a continuous flux, it suffers from many infant illnesses in form of lack of or fuzzy definitions and theoretical foundations. This paper constitutes the first call to the eMaintenance community to gather their forces and commonly define the eMaintenance concept. As an initial step, it outlines its ten essential components. These are (1) Definition, (2) Business, (3) Organization, (4) Product, (5) Service, (6) Methodology, (7) Technology, (8) Information, (9) Customer, and (10) Education and Training.  The paper also suggests a timeless definition of eMaintenance, it places eMaintenance in the context of other eDomains, and it elicits eMaintenance intellectual opportunities and challenges to be met by both the academia and industry when researching on or transitioning to the eMaintenance mode.
  •  
44.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Fundamentals of the eMaintenance concept
  • 2010
  • Ingår i: Proceedings of the 1st international workshop and congress on eMaintenance. - : Luleå tekniska universitet. - 9789174391206 ; , s. 147-154
  • Konferensbidrag (refereegranskat)abstract
    • Many intellectual, societal, business and technological forces are continuously pushing forward the frontiers of science. When being combined effectively, they may provide an umbrella for generating new fields and exploring new grounds. One such emerging field is eMaintenance. It is based on the fields from operation & maintenance engineering, software engineering, information systems, business management, and a myriad of strongly varying fields related to the application domains of eMaintenance. As a novel field, eMaintenance addresses new needs and provides various benefits in form of increased availability, reduced lifecycle cost and increased customer-value. On the other hand, being in a continuous flux, it suffers from many infant illnesses in form of lack of or fuzzy definitions and theoretical foundations. This paper explores the domain of eMaintenance. In striving toward that end, it defines the eMaintenance concept by identifying its essential constituents and characteristics, mapping out its application domains and by eliciting its intellectual opportunities and challenges. Finally, the paper reasons about the future of eMaintenance as an emerging field and identifies research questions that may serve as the impetus for defining future research strategies. Last but not least, it lists challenges to be met by the organizations transferring to eMainteannce and advocates to the eMaintenance community to further elaborate and improve the eMaintenance concept.
  •  
45.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Insight into risk management in five software organizations
  • 2009
  • Ingår i: SEAA '09. 35th Euromicro Conference on Software Engineering and Advanced Applications, 2009. - 9780769537849 ; , s. 321-326
  • Konferensbidrag (refereegranskat)abstract
    • Many software development and evolution projects use risk management process for tackling various uncertainties, unexpected events and unclear project prerequisites. Despite this, little is known about their effectiveness. In this paper, we report on the status of risk management practice within five organizations. The report encompasses issues such as (1) industrial understanding of risk, (2) project uncertainty, (3) risk management within projects, and (4) use of risk management process.
  •  
46.
  • Kajko-Mattsson, Mira, et al. (författare)
  • International workshop on processes for software evolution and maintenance (WoPSEM 2010)
  • 2010
  • Ingår i: 2010 17th Working Conference on Reverse Engineering (WCRE). - 9780769541235 ; , s. 281-282
  • Konferensbidrag (refereegranskat)abstract
    • Software evolution and maintenance processes have been and continue to be an unexplored domain. Current process models and standards do not cover the whole evolution and maintenance domain. As a result, the software community still possesses a blurred understanding of its scope, an unclear picture of how various processes are interrelated, how they impact each other and the product. The software community is also insecure about how to adapt evolution and maintenance processes to new methods and technologies. This workshop aims at discussing the challenges, problems and evolution and maintenance process models according to the latest findings.
  •  
47.
  • Kajko-Mattsson, Mira (författare)
  • Intra-Organizational Model of Communicaton on Serious Risks
  • 2010
  • Ingår i: INTERNATIONAL MULTICONFERENCE OF ENGINEERS AND COMPUTER SCIENTISTS (IMECS 2010), VOLS I-III. - 9789881701282 ; , s. 716-723
  • Konferensbidrag (refereegranskat)abstract
    • Organizations must be more forthright in their communication about risks. This is however not easy on an organization-wide basis where many different processes and roles are involved. In this paper, we evaluate a model of an intra-organizational risk management communication within 57 software organizations. Our results show that our model is mainly applicable within large companies.
  •  
48.
  • Kajko-Mattsson, Mira, et al. (författare)
  • Long-Term Perspective of Agile Methods
  • 2009
  • Ingår i: 2009 FOURTH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING ADVANCES (ICSEA 2009). - NEW YORK : IEEE. ; , s. 1-2
  • Konferensbidrag (refereegranskat)abstract
    • Even if we have recognized many short-term benefits of agile methods, we still know very little about their long-term effects. In this panel, we discuss the long-term perspective of the agile methods. The panelists are either industrial or academic representatives. They will discuss problems and benefits related to the long-term lifecycle system management in agile projects. Ideally, the panel's outcome will provide ideas for future research.
  •  
49.
  • Kajko-Mattsson, Mira Miroslawa, et al. (författare)
  • A model of predelivery problem management
  • 2008
  • Ingår i: IMECS 2008. - HONG KONG : INT ASSOC ENGINEERS-IAENG. - 9789889867188 ; , s. 976-981
  • Konferensbidrag (refereegranskat)abstract
    • Often, one connotes problem management with a postdelivery process for resolving problems within corrective maintenance. Very seldom, however, one relates it to the testing process within development, evolution and maintenance. In this paper, we propose a model of predelivery problem management. Using the model, we study the industrial status within eight companies situated in Greece. Our results show that all the organizations studied conduct a predelivery problem management process within system testing. However, only three out of eight companies perform it within central integration testing.
  •  
50.
  • Kajko-Mattsson, Mira Miroslawa, et al. (författare)
  • A template for communicating information about requirements and their realization
  • 2008
  • Ingår i: IMECS 2008. - HONG KONG : INT ASSOC ENGINEERS-IAENG. - 9789889867188 ; , s. 1020-1025
  • Konferensbidrag (refereegranskat)abstract
    • Structured and disciplined communication is a prerequisite for effective management of requirements. In this paper, we investigate what requirement management information is communicated within a software development cycle. We do this by studying the management of requirements information within one Canadian organization. Our results show that most of the information as designated in our template is recorded by the organization studied.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-50 av 130
Typ av publikation
konferensbidrag (99)
tidskriftsartikel (17)
bokkapitel (7)
doktorsavhandling (4)
annan publikation (2)
proceedings (redaktörskap) (1)
visa fler...
visa färre...
Typ av innehåll
refereegranskat (103)
övrigt vetenskapligt/konstnärligt (25)
populärvet., debatt m.m. (2)
Författare/redaktör
Nyfjord, Jaana (18)
Kajko-Mattsson, Miro ... (10)
Karim, Ramin (5)
Johnson, Pontus (3)
Kajko-Mattsson, Mira ... (3)
Petersen, A. (2)
visa fler...
Söderholm, Peter (2)
Liang, Z. (1)
Hartmann, H. (1)
Andersson, G (1)
Nelson, T. (1)
Huang, S. (1)
Johansson, Jan (1)
Zakharov, V (1)
Avetisyan, A. (1)
Sjögren, Anders (1)
Pooley, Rob (1)
Nordin, Maria (1)
Wilczek, Lukas (1)
Tyrberg, Tommy (1)
Ivar, J. (1)
Pozin, B. A. (1)
Petrenko, A. K. (1)
Cavalli, A. R. (1)
Arlazarov, V. (1)
Avdoshin, S. (1)
Batovrin, V. K. (1)
Bershadsky, A. M. (1)
Boichenko, A. (1)
Juris, B. (1)
Vasenin, V. A. (1)
Schlingloff, H. (1)
Kalyanov, G. (1)
Kantorovich, G. G. (1)
Korolev, A. (1)
Kosolapov, M. S. (1)
Kostogryzov, A. I. (1)
Koznov, D. V. (1)
Kuznetsov, S. (1)
Prokhorov, S. (1)
Soyfer, V. A. (1)
Starykh, V. A. (1)
Stolyarov, G. K. (1)
Stupnikov, S. A. (1)
Telnov, Y.Ph. (1)
Shmid, A. (1)
Wentzl, W. (1)
Mayer, W. H. (1)
Yevtushenko, N. (1)
Zmeev, O. (1)
visa färre...
Lärosäte
Kungliga Tekniska Högskolan (105)
Stockholms universitet (45)
Luleå tekniska universitet (4)
Linnéuniversitetet (2)
Språk
Engelska (117)
Odefinierat språk (13)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (93)
Teknik (14)
Samhällsvetenskap (5)

År

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy