| 1. |
- Erol, Selim, et al.
(författare)
-
Combining BPM and social software : contradiction or chance?
- 2010
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 22:6-7, s. 449-476
-
Tidskriftsartikel (refereegranskat)abstract
- Social software has received much attention in the academia and industry due to many success stories. However, although social software is used widely for business support, its relationship with Business Process Management has not been analysed. The results of the workshop on Business Process Management and Social Software (BPMS2'08), as part of the International Conference on Business Process Management in Milano, show the manifold possibilities of combining concepts from Business Process Management and social software. Social software provides a better integration of all stakeholders into the business process life cycle and offers new possibilities for a more effective and flexible design of business processes. The modelling of business processes may profit particularly from using social software techniques by alleviating the integration of process knowledge from all stakeholders. In addition, the implementation and deployment phase of the business process life cycle may profit from social software by collecting valuable information for continuous process improvement from a larger set of sources than before. Furthermore, social software environments may be used to provide workflow support. Moreover, the use of social software also requires new considerations about the digital identity and reputation in business processes.
|
|
| 2. |
- Gorschek, Tony, et al.
(författare)
-
Introduction of a Process Maturity Model for Market-driven Product Management and Requirements engineering
- 2012
-
Ingår i: Journal of Software Maintenance and Evolution. - : John Wiley and Sons. - 1532-060X .- 1532-0618. ; 24:1, s. 83-113
-
Tidskriftsartikel (refereegranskat)abstract
- The area of software product development of software intensive products has received much attention, especially in the area of requirements engineering and product management. Many companies are faced with new challenges when operating in an environment where potential requirements number in thousands or even tens of thousands, and where a product does not have a customer, but any number of customers or markets. The development organization carries not only all the costs of development, but also takes all the risks. In this environment traditional bespoke requirements engineering, together with traditional process assessment and improvement models fall short as they do not address the unique challenges of a market-driven environment. This paper introduces the Market-driven Requirements Engineering Process Model, aimed at enabling process improvement and process assurance for organizations faced with these new challenges. The model is also validated in the industry through three case studies where the model is used for process assessment and improvement suggestion. Initial results show that the model is appropriate for process improvement for organizations operating in a market-driven environment. In addition, the model was designed to be light weight in terms of low cost and thus adapted not only for large organizations but suitable for small and medium enterprises as well.
|
|
| 3. |
- Jalali, Samireh, et al.
(författare)
-
Global software engineering and agile practices : a systematic review
- 2012
-
Ingår i: Journal of Software Maintenance and Evolution. - : John Wiley & Sons, Ltd.. - 1532-060X .- 1532-0618. ; 24:6
-
Tidskriftsartikel (refereegranskat)abstract
- Agile practices have received attention from industry as an alternative to plan-driven software development approaches. Agile encourages, for example, small self-organized collocated teams, whereas global software engineering (GSE) implies distribution across cultural, temporal, and geographical boundaries. Hence, combining them is a challenge. A systematic review was conducted to capture the status of combining agility with GSE. The results were limited to peer-reviewed conference papers or journal articles, published between 1999 and 2009. The synthesis was made through classifying the papers into different categories (e.g. publication year, contribution type, research method). At the end, 81 papers were judged as primary for further analysis. The distribution of papers over the years indicated that GSE and Agile in combination has received more attention in the last 5 years. However, the majority of the existing research is industrial experience reports in which Agile practices were modified with respect to the context and situational requirements. The emergent need in this research area is suggested to be developing a framework that considers various factors from different perspectives when incorporating Agile in GSE. Practitioners may use it as a decision-making basis in early phases of software development.
|
|
| 4. |
- Kajko-Mattsson, Mira Miroslawa
(författare)
-
Problem management maturity within corrective maintenance
- 2002
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 14:3, s. 197-227
-
Tidskriftsartikel (refereegranskat)abstract
- CM3: Problem Management is a first detailed descriptive problem management process model to be utilized within corrective maintenance. It is the result of a long-term empirical study of industrial corrective maintenance processes. It has been developed at ABB and evaluated for its industrial relevance within 17 non-ABB organizations. Playing the role of a descriptive model, CM3: Problem Management specifies what a problem management process should look like. It also structures it into three maturity levels, Initial, Defined, and Optimal, where each level offers a different grainedness of process visibility. In this paper, we present the CM3 levels of problem management process maturity within corrective maintenance and match them against the industrial state of practice. Our goal is to establish the current status of problem management maturity using CM3: Problem Management as an evaluation model. Our evaluation results show that the industrial processes today suffice to attend to software problems within corrective maintenance. Very few of them, however, do learn from the past in order to prevent future problems and to improve development or maintenance processes.
|
|
| 5. |
- 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.
|
|
| 6. |
- Khurum, Mahvish, et al.
(författare)
-
A method for alignment evaluation of product strategies among stakeholders (MASS) in software intensive product development
- 2011
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 23:7, s. 494-516
-
Tidskriftsartikel (refereegranskat)abstract
- Current practices in the industry are moving towards the market-driven development of software intensive products compared to customer-specific system development. Consequently, product management is faced with several challenges that have to be addressed as a part of the market-driven requirements engineering process. One of the important challenges is how to select the right mix of requirements, balancing short-term and long-term gains. One way to address this challenge is to utilize product strategies for selecting requirements. However, in order to do this the internal success-critical stakeholders (SCS) involved in strategies creation and requirements selection need to be aligned with respect to a product's strategic goals and objectives. This paper presents a method to enable the evaluation of degree of alignment between SCS with respect to the understanding and interpretation of a product's strategy. Further, the method not only enables the evaluation of alignment, but also specifically shows misalignment, and enables the identification of leading causes. The method has been developed in collaboration with the industry and its application is shown through a case study at Ericsson AB
|
|
| 7. |
- Khurum, Mahvish, et al.
(författare)
-
The software value map—an exhaustive collection of value aspects for the development of software intensive products
- 2013
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 25:7, s. 711-741
-
Tidskriftsartikel (refereegranskat)abstract
- In software intensive products such as cars or telecom systems, software has traditionally been associated with cost, and there has been no real perception of its value in relation to the entire product offering. However, because software is becoming a larger part of the main competitive advantage, driving innovation and product differentiation, hardware is becoming more standardized, thus the valuation of software is becoming critical. In existing literature, several value constructs and corresponding valuation/measurement solutions needed for making decisions about software product development are presented. However, the contributions are often isolated with respect to a certain perspective such as focusing on product's internal or external quality aspects only. Consequently, a complete view of value constructs relevant from different perspectives required for making decisions about software product development is missing. This paper presents a consolidated view of the software value concept utilizing the major perspectives and introduces a software value map. The created value map was evaluated through an industry case study through the development of impact evaluation patterns, which were subsequently used by professionals in industry, and experiences gathered. During industry evaluation, practitioners found substantial benefits of having a consolidated, vastly improved, and extended value aspect's view of software. Copyright © 2012 John Wiley & Sons, Ltd.
|
|
| 8. |
- Lagerström, Robert, et al.
(författare)
-
Increasing software development efficiency and maintainability for complex industrial systems - A case study
- 2013
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 25:3, s. 285-301
-
Tidskriftsartikel (refereegranskat)abstract
- It is difficult to manage complex software systems. Thus, many research initiatives focus on how to improve software development efficiency and maintainability. However, the trend in the industry is still alarming, software development projects fail, and maintenance is becoming more and more expensive. One problem could be that research has been focusing on the wrong things. Most research publications address either process improvements or architectural improvements. There are few known approaches that consider how architectural changes affect processes and vice versa. One method proposed, called the BusinessArchitectureProcess method, takes these aspects into consideration. In 2007 the method was tested in one case study. Findings in the 2007 case study show that the method is useful, but in need of improvements and further validation. The present paper employs the method in a second case study. The contribution in this paper is thus a second test and validation of the proposed method, and useful method improvements for future use of the method.
|
|
| 9. |
- Magazinovic, Ana, 1979, et al.
(författare)
-
Software cost estimation inhibitors—a case study in automotive context
- 2010
-
Ingår i: Journal of Software Maintenance and Evolution. - : Wiley. - 1532-060X .- 1532-0618. ; 22:5, s. 407-427
-
Tidskriftsartikel (refereegranskat)abstract
- As cost estimation is an important yet problematic part of project planning there is a need of process improvement to decrease the estimation errors. This paper has two purposes. Based on a qualitative case study conducted at a Swedish automotive company it describes the process of cost estimation in a real-life setting focusing on inhibitors to accurate cost estimates. Second, the results of this study are compared with four other studies with a similar purpose of concluding that a company-specific investigation of cost estimation inhibitors might give more actionable input to the activity of cost estimation process improvement than a more general investigation.
|
|
| 10. |
- Ohlsson, MC, et al.
(författare)
-
Modelling fault-proneness statistically over a sequence of releases : a case study
- 2001
-
Ingår i: Journal of Software Maintenance and Evolution. - W SUSSEX : JOHN WILEY & SONS LTD. - 1532-060X .- 1532-0618. ; , s. 167-199
-
Tidskriftsartikel (refereegranskat)abstract
- Many of today's software systems evolve through a series of releases that add new functionality and features, in addition to the results of corrective maintenance. As the systems evolve over time it is necessary to keep track of and manage their problematic components. Our focus is to track system evolution and to react before the systems become difficult to maintain. To do the tracking, we use a method based on a selection of statistical techniques. In the case study we report here that had historical data available primarily on corrective maintenance, we apply the method to four releases of a system consisting of 130 components. In each release, components are classified as fault-prone if the number of defect reports written against them are above a certain threshold. The outcome from the case study shows stabilizing principal components over the releases, and classification trees with lower thresholds in their decision nodes. Also, the variables used in the classification trees' decision nodes are related to changes in the same files. The discriminant functions use more variables than the classification trees and are more difficult to interpret. Box plots highlight the findings from the other analyses. The results show that for a context of corrective maintenance, principal components analysis together with classification trees are good descriptors for tracking software evolution, Copyright (C) 2001 John Wiley gr Sons, Ltd.
|
|
