| 1. |
- Asklund, Ulf, et al.
(författare)
-
Experiences from Monitoring Effect of Architectural Changes
- 2016
-
Ingår i: Software Quality.. - Cham : Springer International Publishing. - 9783319270333 ; 238, s. 97-108
-
Konferensbidrag (refereegranskat)abstract
- A common situation is that an initial architecture has been sufficient in the initial phases of a project, but when the size and complexity of the product increases the architecture must be changed. In this paper experiences are presented from changing an architecture into independent units, providing basic reuse of main functionality although giving higher priority to independence than reuse. An objective was also to introduce metrics in order to monitor the architectural changes. The change was studied in a case-study through weekly meetings with the team, collected metrics, and questionnaires. The new architecture was well received by the development team, who found it to be less fragile. Concerning the metrics for monitoring it was concluded that a high abstraction level was useful for the purpose.
|
|
| 2. |
- Badampudi, Deepika, 1984-, et al.
(författare)
-
A decision-making process-line for selection of software asset origins and components
- 2018
-
Ingår i: Journal of Systems and Software. - : Elsevier Inc.. - 0164-1212 .- 1873-1228. ; 135, s. 88-104
-
Tidskriftsartikel (refereegranskat)abstract
- Selecting sourcing options for software assets and components is an important process that helps companies to gain and keep their competitive advantage. The sourcing options include: in-house, COTS, open source and outsourcing. The objective of this paper is to further refine, extend and validate a solution presented in our previous work. The refinement includes a set of decision-making activities, which are described in the form of a process-line that can be used by decision-makers to build their specific decision-making process. We conducted five case studies in three companies to validate the coverage of the set of decision-making activities. The solution in our previous work was validated in two cases in the first two companies. In the validation, it was observed that no activity in the proposed set was perceived to be missing, although not all activities were conducted and the activities that were conducted were not executed in a specific order. Therefore, the refinement of the solution into a process-line approach increases the flexibility and hence it is better in capturing the differences in the decision-making processes observed in the case studies. The applicability of the process-line was then validated in three case studies in a third company. © 2017 Elsevier Inc.
|
|
| 3. |
- Borg, Markus, et al.
(författare)
-
Practitioners' Perspectives on Change Impact Analysis for Safety-Critical Software - A Preliminary Analysis
- 2016. - 11
-
Ingår i: Computer Safety, Reliability, and Security. - Cham : Springer International Publishing. - 9783319454795 - 9783319454801 ; , s. 346-358
-
Konferensbidrag (refereegranskat)abstract
- Safety standards prescribe change impact analysis (CIA) during evolution of safety-critical software systems. Although CIA is a fundamental activity, there is a lack of empirical studies about how it is performed in practice. We present a case study on CIA in the context of an evolving automation system, based on 14 interviews in Sweden and India. Our analysis suggests that engineers on average spend 50-100 hours on CIA per year, but the effort varies considerably with the phases of projects. Also, the respondents presented different connotations to CIA and perceived the importance of CIA differently. We report the most pressing CIA challenges, and several ideas on how to support future CIA. However, we show that measuring the effect of such improvement solutions is non-trivial, as CIA is intertwined with other development activities. While this paper only reports preliminary results, our work contributes empirical insights into practical CIA.
|
|
| 4. |
- Borg, Markus, et al.
(författare)
-
Safely Entering the Deep: A Review of Verification and Validation for Machine Learning and a Challenge Elicitation in the Automotive Industry
- 2019
-
Ingår i: Journal of Automotive Software Engineering. - Paris : Athena International Publishing B.V.. - 2589-2258. ; 1:1, s. 1-13
-
Tidskriftsartikel (refereegranskat)abstract
- Deep neural networks (DNNs) will emerge as a cornerstone in automotive software engineering. However, developing systems with DNNs introduces novel challenges for safety assessments. This paper reviews the state-of-the-art in verification and validation of safety-critical systems that rely on machine learning. Furthermore, we report from a workshop series on DNNs for perception with automotive experts in Sweden, confirming that ISO 26262 largely contravenes the nature of DNNs. We recommend aerospace-to-automotive knowledge transfer and systems-based safety approaches, for example, safety cage architectures and simulated system test cases.
|
|
| 5. |
- Borg, Markus, et al.
(författare)
-
Selecting component sourcing options : A survey of software engineering's broader make-or-buy decisions
- 2019
-
Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 112, s. 18-34
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them from external sources. In CBSE, several different sourcing options are available: (1) developing software in-house, (2) outsourcing development, (3) buying commercial-off-the-shelf software, and (4) integrating open source software components. Objective: Unfortunately, there is little available research on how organizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Results: Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. Conclusion: We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking.
|
|
| 6. |
- Borg, Markus, et al.
(författare)
-
Selecting Software Component Sourcing Options : Detailed Survey Description and Analysis
- 2018
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them fromexternal sources. In CBSE, several different sourcing options are available: 1) developing software in-house, 2) outsourcing development, 3) buying commercial-off-the-shelf software, and 4) integrating open source software components. Unfortunately, there is little available research on howorganizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking.
|
|
| 7. |
- Borg, Martin, et al.
(författare)
-
Supporting Change Impact Analysis Using a Recommendation System : An Industrial Case Study in a Safety-Critical Context
- 2017
-
Ingår i: IEEE Transactions on Software Engineering. - : IEEE. - 0098-5589 .- 1939-3520. ; 43:7, s. 675-700
-
Tidskriftsartikel (refereegranskat)abstract
- Change Impact Analysis (CIA) during software evolution of safety-critical systems is a labor-intensive task. Several authors have proposed tool support for CIA, but very few tools were evaluated in industry. We present a case study on ImpRec, a recommendation System for Software Engineering (RSSE), tailored for CIA at a process automation company. ImpRec builds on assisted tracing, using information retrieval solutions and mining software repositories to recommend development artifacts, potentially impacted when resolving incoming issue reports. In contrast to the majority of tools for automated CIA, ImpRec explicitly targets development artifacts that are not source code. We evaluate ImpRec in a two-phase study. First, we measure the correctness of ImpRec's recommendations by a simulation based on 12 years' worth of issue reports in the company. Second, we assess the utility of working with ImpRec by deploying the RSSE in two development teams on different continents. The results suggest that ImpRec presents about 40 percent of the true impact among the top-10 recommendations. Furthermore, user log analysis indicates that ImpRec can support CIA in industry, and developers acknowledge the value of ImpRec in interviews. In conclusion, our findings show the potential of reusing traceability associated with developers' past activities in an RSSE.
|
|
| 8. |
- Callele, David, et al.
(författare)
-
A Process for Product and Service Definition
- 2016
-
Ingår i: 9th International Workshop on Software Product Management (IWSPM 2016). - : IEEE. - 9781509036943 ; , s. 322-327
-
Konferensbidrag (refereegranskat)abstract
- This short paper presents an iterative and incrementalprocess to improve the probability that the product or service definition leading to requirements and implementation is both representative of the market needs and has a reasonable expecta-tion of a financially viable business model. Rather than a relative-ly linear process wherein marketing delivers a product definition to the development team, this process ensures that all assump-tions are validated during the definition stage and that all team members are engaged. The process balances the need to address current challenges against future opportunities, providing short-term customer satisfaction (and justification for purchasing or adoption) and a coherent vision for future development efforts (and maintaining and growing the customer base). The process is applied to a case in the agriculture commodities sector.
|
|
| 9. |
- Callele, David, et al.
(författare)
-
Experience requirements in video games definition and testability
- 2015
-
Ingår i: Requirements Engineering Conference (RE), 2015 IEEE 23rd International. - : IEEE. - 9781467369060
-
Konferensbidrag (refereegranskat)abstract
- A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance.
|
|
| 10. |
- Callele, David, et al.
(författare)
-
New Frontiers for Requirements Engineering
- 2017
-
Ingår i: 2017 IEEE 25th International Requirements Engineering Conference, RE 2017. - : Institute of Electrical and Electronics Engineers Inc.. - 9781538631911 ; , s. 184-193
-
Konferensbidrag (refereegranskat)abstract
- Requirements Engineering (RE) has grown from its humble beginnings to embrace a wide variety of techniques, drawn from many disciplines, and the diversity of tasks currently performed under the label of RE has grown beyond that encom-passed by software development. We briefly review how RE has evolved and observe that RE is now a collection of best practices for pragmatic, outcome-focused critical thinking-A pplicable to any domain. We discuss an alternative perspective on, and de-scription of, the discipline of RE and advocate for the evolution of RE toward a discipline that supports the application of RE prac-tice to any domain. We call upon RE practitioners to proactively engage in alternative domains and call upon researchers that adopt practices from other domains to actively engage with their inspiring domains. For both, we ask that they report upon their experience so that we can continue to expand RE frontiers. © 2017 IEEE.
|
|
| 11. |
- Callele, David, et al.
(författare)
-
Public policy challenges : An RE perspective
- 2018
-
Ingår i: CEUR Workshop Proceedings. - : CEUR-WS. ; , s. 24-33
-
Konferensbidrag (refereegranskat)abstract
- In this perspective paper, we investigate the parallels between public policy and IT projects from the perspective of traditional RE practice. Using the mainstream media as an information source (as would an average citizen), over a period of approximately one year we captured documents that presented analyses of public policy issues. The documents were categorized into eight topic areas, then analyzed to identify patterns that RE practitioners would recognize. We found evidence of policy failures that parallel project failures traceable to requirements engineering problems. Our analysis revealed evidence of bias across all stakeholder groups, similar to the rise of the “beliefs over facts” phenomenon often associated with “fake news”. We also found substantial evidence of unintended consequences due to inadequate problem scoping, terminology definition, domain knowledge, and stakeholder identification and engagement. Further, ideological motivations were found to affect constraint definitions resulting in solution spaces that may approach locally optimal but may not be globally optimal. Public policy addresses societal issues; our analysis supports our conclusion that RE techniques could be utilized to support policy creation and implementation. © 2018 SPIE. All rights reserved.
|
|
| 12. |
- Chatzipetrou, Panagiota, Assistant Professor, 1984-, et al.
(författare)
-
Component selection in software engineering - Which attributes are the most important in the decision process?
- 2018
-
Ingår i: Proceedings - 44th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2018. - : IEEE conference proceedings. - 9781538673829 ; , s. 198-205, s. 198-205
-
Konferensbidrag (refereegranskat)abstract
- Component-based software engineering is a common approach to develop and evolve contemporary software systems where different component sourcing options are available: 1)Software developed internally (in-house), 2)Software developed outsourced, 3)Commercial of the shelf software, and 4) Open Source Software. However, there is little available research on what attributes of a component are the most important ones when selecting new components. The object of the present study is to investigate what matters the most to industry practitioners during component selection. We conducted a cross-domain anonymous survey with industry practitioners involved in component selection. First, the practitioners selected the most important attributes from a list. Next, they prioritized their selection using the Hundred-Dollar ($100) test. We analyzed the results using Compositional Data Analysis. The descriptive results showed that Cost was clearly considered the most important attribute during the component selection. Other important attributes for the practitioners were: Support of the component, Longevity prediction, and Level of off-the-shelf fit to product. Next, an exploratory analysis was conducted based on the practitioners' inherent characteristics. Nonparametric tests and biplots were used. It seems that smaller organizations and more immature products focus on different attributes than bigger organizations and mature products which focus more on Cost. .
|
|
| 13. |
- Cicchetti, Antonio, et al.
(författare)
-
Towards Software Assets Origin Selection Supported by a Knowledge Repository
- 2016
-
Ingår i: Proceedings - 2016 1st International Workshop on Decision Making in Software ARCHitecture, MARCH 2016. - : IEEE Computer Society. - 9781509025732 ; , s. 22-29
-
Konferensbidrag (refereegranskat)abstract
- Software architecture is no more a mere system specification as resulting from the design phase, but it includes the process by which its specification was carried out. In this respect, design decisions in component-based software engineering play an important role: They are used to enhance the quality of the system, keep the current market level, keep partnership relationships, reduce costs, and so forth. For non trivial systems, a recurring situation is the selection of an asset origin, that is if going for in-house, outsourcing, open-source, or COTS, when in the need of a certain missing functionality. Usually, the decision making process follows a case-by-case approach, in which historical information is largely neglected: hence, it is avoided the overhead of keeping detailed documentation about past decisions, but it is hampered consistency among multiple, possibly related, decisions.The ORION project aims at developing a decision support framework in which historical decision information plays a pivotal role: it is used to analyse current decision scenarios, take well-founded decisions, and store the collected data for future exploitation. In this paper, we outline the potentials of such a knowledge repository, including the information it is intended to be stored in it, and when and how to retrieve it within a decision case.
|
|
| 14. |
- de la Vara, José Luis, et al.
(författare)
-
An Industrial Survey of Safety Evidence Change Impact Analysis Practice
- 2016. - 13
-
Ingår i: IEEE Transactions on Software Engineering. - : IEEE. - 0098-5589 .- 1939-3520. ; 42:12, s. 1095-1117
-
Tidskriftsartikel (refereegranskat)abstract
- In many application domains, critical systems must comply with safety standards. This involves gathering safety evidence in the form of artefacts such as safety analyses, system specifications, and testing results. These artefacts can evolve during a system's lifecycle, creating a need for impact analysis to guarantee that system safety and compliance are not jeopardised. Although extensive research has been conducted on change impact analysis and on safety evidence management, the knowledge about how safety evidence change impact analysis is addressed in practice is limited. This paper reports on a survey targeted at filling this gap by analysing the circumstances under which safety evidence change impact analysis is addressed, the tool support used, and the challenges faced. We obtained 97 valid responses representing 16 application domains, 28 countries, and 47 safety standards. The results suggest that most practitioners deal with safety evidence change impact analysis during system development and mainly from system specifications. Furthermore, the level of automation in the process is low and insufficient tool support is the most frequent challenge. Other notable findings include that the different artefact types used as safety evidence seem to co-evolve, the evolution of safety case should probably be better managed, and no commercial impact analysis tool has been reported as used for all artefact types. Finally, we identified over 20 areas where the state of the practice in safety evidence change impact analysis can be improved.
|
|
| 15. |
- Linåker, J., et al.
(författare)
-
Motivating the contributions : An Open Innovation perspective on what to share as Open Source Software
- 2018
-
Ingår i: Journal of Systems and Software. - : Elsevier Inc.. - 0164-1212 .- 1873-1228. ; 135, s. 17-36
-
Tidskriftsartikel (refereegranskat)abstract
- Open Source Software (OSS) ecosystems have reshaped the ways how software-intensive firms develop products and deliver value to customers. However, firms still need support for strategic product planning in terms of what to develop internally and what to share as OSS. Existing models accurately capture commoditization in software business, but lack operational support to decide what contribution strategy to employ in terms of what and when to contribute. This study proposes a Contribution Acceptance Process (CAP) model from which firms can adopt contribution strategies that align with product strategies and planning. In a design science influenced case study executed at Sony Mobile, the CAP model was iteratively developed in close collaboration with the firm's practitioners. The CAP model helps classify artifacts according to business impact and control complexity so firms may estimate and plan whether an artifact should be contributed or not. Further, an information meta-model is proposed that helps operationalize the CAP model at the organization. The CAP model provides an operational OI perspective on what firms involved in OSS ecosystems should share, by helping them motivate contributions through the creation of contribution strategies. The goal is to help maximize return on investment and sustain needed influence in OSS ecosystems. © 2017
|
|
| 16. |
- Linåker, Johan, et al.
(författare)
-
Requirements analysis and management for benefiting openness
- 2017
-
Ingår i: Proceedings - 2016 IEEE 24th International Requirements Engineering Conference Workshops, REW 2016. - : IEEE. - 9781509036943 ; , s. 344-349
-
Konferensbidrag (refereegranskat)abstract
- Requirements Engineering has recently been greatly influenced by the way how firms use Open Source Software (OSS) and Software Ecosystems (SECOs) as a part of their product development and business models. This is further emphasized by the paradigm of Open Innovation, which highlights how firms should strive to use both internal and external resources to advance their internal innovation and technology capabilities. The evolution from market-driven requirements engineering and management processes, has reshaped the understanding of what a requirement is, and how it is documented and used. In this work, we suggest a model for analyzing and managing requirements that is designed in the context of OSS and SECOs, including the advances and challenges that it brings. The model clarifies how the main stages of requirements engineering and management processes can be adjusted to benefit from the openness that the new context offers. We believe that the model is a first step towards the inevitable adaptation of requirements engineering to an open and informal arena, where processes and collaboration are decentralized, transparency and governance are the key success factors.
|
|
| 17. |
|
|
| 18. |
- Minhas, Nasir Mehmood, et al.
(författare)
-
Regression testing goals : View of practitioners and researchers
- 2017
-
Ingår i: 24th Asia-Pacific Software Engineering Conference Workshops (APSECW). - : IEEE. - 9781538626498 ; , s. 25-32
-
Konferensbidrag (refereegranskat)abstract
- Context: Regression testing is a well-researched area. However, the majority regression testing techniques proposed by the researchers are not getting the attention of the practitioners. Communication gaps between industry and academia and disparity in the regression testing goals are the main reasons. Close collaboration can help in bridging the communication gaps and resolving the disparities.Objective: The study aims at exploring the views of academics and practitioners about the goals of regression testing. The purpose is to investigate the commonalities and differences in their viewpoints and defining some common goals for the success of regression testing.Method: We conducted a focus group study, with 7 testing experts from industry and academia. 4 testing practitioners from 2companies and 3 researchers from 2 universities participated in the study. We followed GQM approach, to elicit the regression testing goals, information needs, and measures.Results: 43 regression testing goals were identified by the participants, which were reduced to 10 on the basis of similarity among the identified goals. Later during the priority assignment process, 5 goals were discarded, because the priority assigned to these goals was very low. Participants identified 47 information needs/questions required to evaluate the success of regression testing with reference to goal G5 (confidence). Which were then reduced to10 on the basis of similarity. Finally, we identified measures to gauge those information needs/questions, which were corresponding to the goal (G5).Conclusions: We observed that participation level of practitioners and researchers during the elicitation of goals and questions was same. We found a certain level of agreement between the participants regarding the regression testing definitions and goals.But there was some level of disagreement regarding the priorities of the goals. We also identified the need to implement a regression testing evaluation framework in the participating companies.
|
|
| 19. |
- Mols, Carl-Eric, et al.
(författare)
-
Charting the market disruptive nature of open source : Experiences from sony mobile
- 2017
-
Ingår i: PROCEEDINGS OF THE 2017 IEEE/ACM 39TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING COMPANION (ICSE-C 2017). - : Institute of Electrical and Electronics Engineers Inc.. - 9781538615898 ; , s. 175-176
-
Konferensbidrag (refereegranskat)abstract
- Open Source Software (OSS) has substantial impact on how software-intensive firms develop products and deliver value to the customers. These companies need both strategic and operational support on how to adapt OSS as a part of their products and how to adjust processes and organizations to increase the benefits from OSS participation. This work presents the key insights from the journey that Sony Mobile has made from a company developing proprietary software to a respected member of OSS communities. We framed the experiences into an Open Source Maturity Model that includes two scenarios: engineering-driven and business-driven open source. We outline the most important decisions, roles, processes and implications. © 2017 IEEE.
|
|
| 20. |
- Mols, Carl-Eric, et al.
(författare)
-
The open source officer role – experiences
- 2017
-
Ingår i: IFIP Advances in Information and Communication Technology. - Cham : Springer-Verlag New York. - 1868-4238. - 9783319577340 ; , s. 55-59
-
Konferensbidrag (refereegranskat)abstract
- This papers describe the Open Source Officer role and the experiences from introducing this role in several companies. We outline the role description, main responsibilities, and interfaces to other roles and organizations. We investigated the role in several organization and bring interesting discrepancies and overlaps of how companies operate with OSS. © The Author(s) 2017.
|
|
| 21. |
- Münch, Jürgen, et al.
(författare)
-
Workshops and tutorials
- 2018
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer Verlag. - 9783030036720 ; , s. 365-369
-
Konferensbidrag (refereegranskat)abstract
- The 19th International Conference on Product-Focused Software Process Improvement (PROFES 2018) hosted two workshops and three tutorials. The workshops and tutorials complemented and enhanced the main conference program, offering a wider knowledge perspective around the conference topics. The topics of the two workshops were Hybrid Development Approaches in Software Systems Development (HELENA) and Managing Quality in Agile & Rapid Software Development Processes (QUaSD). The topics of the tutorials were The human factor in agile transitions – Using the personas concept in agile coaching, Process Management 4.0 – Best Practices, and Domain-specific languages for specification, development, and testing of autonomous systems. The workshop organizers would like to thank all persons that organized the workshop or contributed to the workshops as well as the presenters of the tutorials. The workshops and tutorials provided interesting forums for discussing ideas, presenting novel work, learning and networking. In the following the workshop and tutorials are summarized based on the content of the respective workshop and tutorial web descriptions. © Springer Nature Switzerland AG 2018.
|
|
| 22. |
- Munir, Hussan, et al.
(författare)
-
A theory of openness for software engineering tools in software organizations
- 2018
-
Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849 .- 1873-6025. ; 97, s. 26-45
-
Tidskriftsartikel (refereegranskat)abstract
- Context: The increased use of Open Source Software (OSS) affects how software-intensive product development organizations (SIPDO) innovate and compete, moving them towards Open Innovation (OI). Specifically, software engineering tools have the potential for OI, but require better understanding regarding what to develop internally and what to acquire from outside the organization, and how to cooperate with potential competitors. Aim: This paper aims at synthesizing a theory of openness for software engineering tools in SIPDOs, that can be utilized by managers in defining more efficient strategies towards OSS communities. Method: We synthesize empirical evidence from a systematic mapping study, a case study, and a survey, using a narrative method. The synthesis method entails four steps: (1) Developing a preliminary synthesis, (2) Exploring the relationship between studies, (3) Assessing the validity of the synthesis, and (4) Theory formation. Result: We present a theory of openness for OSS tools in software engineering in relation to four constructs: (1) Strategy, (2) Triggers, (3) Outcomes, and (4) Level of openness. Conclusion: The theory reasons that openness provides opportunities to reduce the development cost and development time. Furthermore, OI positively impacts on the process and product innovation, but it requires investment by organizations in OSS communities. By betting on openness, organizations may be able to significantly increase their competitiveness.
|
|
| 23. |
- Munir, Hussan, Assistant Professor, et al.
(författare)
-
How Companies Use OSS Tools Ecosystems for Open Innovation
- 2019
-
Ingår i: IT Professional Magazine. - : IEEE Computer Society. - 1520-9202 .- 1941-045X. ; 21:6, s. 40-45
-
Tidskriftsartikel (refereegranskat)abstract
- Moving toward the open innovation (OI) model requires multifaceted transformations within companies. It often involves giving away the tools for product development or sharing future product directions with open tools ecosystems. Moving from the traditional closed innovation model toward an OI model for software development tools shows the potential to increase software development competence and efficiency of organizations. We report a case study in software-intensive company developing embedded devices (e.g., smartphones) followed by a survey in OSS communities such as Gerrit, Git, and Jenkins. The studied branch focuses on developing Android phones. This paper presents contribution strategies and triggers for openness. These strategies include avoid forking OSS tools, empower developers to participate in the ecosystem, steer ecosystems through contributions, create business through differentiation, and create new ecosystems. The triggers of openness are from 30 different companies with examples. Finally, openness requires a cultural change aligned with strategies and business models. © 1999-2012 IEEE.
|
|
| 24. |
- Munir, Hussan, et al.
(författare)
-
Open innovation in software engineering: a systematic mapping study
- 2016
-
Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1573-7616 .- 1382-3256. ; 21:2, s. 684-723
-
Tidskriftsartikel (refereegranskat)abstract
- Open innovation (OI) means that innovation is fostered by using both external and 5 internal influences in the innovation process. In software engineering (SE), OI has existed 6 for decades, while we currently see a faster and broader move towards OI in SE. We there- 7 fore survey research on how OI takes place and contributes to innovation in SE. This study 8 aims to synthesize the research knowledge on OI in the SE domain. We launched a system- 9 atic mapping study and conducted a thematic analysis of the results. Moreover, we analyzed 10 the strength of the evidence in the light of a rigor and relevance assessment of the research. 11 We identified 33 publications, divided into 9 themes related to OI. 17/33 studies fall in the 12 high–rigor/high–relevance category, suggesting the results are highly industry relevant. The 13 research indicates that start-ups have higher tendency to opt OI compared to incumbents. 14 The evidence also suggests that firms assimilating knowledge into their internal R&D activ- 15 ities, have higher likelihood of gaining financial advantages. We concluded that OI should 16 be adopted as a complementary approach to facilitate internal innovation and not to substi- 17 tute it. Further research is advised on situated OI strategies and the interplay between OI 18 and agile practices.
|
|
| 25. |
- Munir, Hussan, et al.
(författare)
-
Open Innovation through the Lens of Open Source Tools: A case study at Sony Mobile
- 2018
-
Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 23, s. 186-223
-
Tidskriftsartikel (refereegranskat)abstract
- Despite growing interest of Open Innovation (OI) in Software Engineering (SE), little is known about what triggers software organizations to adopt it and how this affects SE practices. OI can be realized in numerous of ways, including Open Source Software (OSS) involvement. Outcomes from OI are not restricted to product innovation but also include process innovation, e.g. improved SE practices and methods. This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI. It also highlights the innovative outcomes resulting from OI. An exploratory embedded case study investigates how Sony Mobile use and contribute to Jenkins and Gerrit; the two central OSS tools in their continuous integration tool chain. Quantitative analysis was performed on change log data from source code repositories in order to identify the top contributors and triangulated with the results from five semi-structured interviews to explore the nature of the commits. The findings of the case study include five major themes: i) The process of opening up towards the tool communities correlates in time with a general adoption of OSS in the organization. ii) Assets not seen as competitive advantage nor a source of revenue are made open to OSS communities, and gradually, the organization turns more open. iii) The requirements engineering process towards the community is informal and based on engagement. iv) The need for systematic and automated testing is still in its infancy, but the needs are identified. v) The innovation outcomes included free features and maintenance, and were believed to increase speed and quality in development. Adopting OI was a result of a paradigm shift of moving from Windows to Linux. This shift enabled Sony Mobile to utilize the Jenkins and Gerrit communities to make their internal development process better for its software developers and testers.
|
|
| 26. |
- Munir, Hussan, Assistant Professor, et al.
(författare)
-
Open innovation using open source tools : a case study at Sony Mobile
- 2018
-
Ingår i: Empirical Software Engineering. - : Springer New York LLC. - 1382-3256 .- 1573-7616. ; 23:1, s. 186-223
-
Tidskriftsartikel (refereegranskat)abstract
- Despite growing interest of Open Innovation (OI) in Software Engineering (SE), little is known about what triggers software organizations to adopt it and how this affects SE practices. OI can be realized in numerous of ways, including Open Source Software (OSS) involvement. Outcomes from OI are not restricted to product innovation but also include process innovation, e.g. improved SE practices and methods. This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI. It also highlights the innovative outcomes resulting from OI. An exploratory embedded case study investigates how Sony Mobile use and contribute to Jenkins and Gerrit; the two central OSS tools in their continuous integration tool chain. Quantitative analysis was performed on change log data from source code repositories in order to identify the top contributors and triangulated with the results from five semi-structured interviews to explore the nature of the commits. The findings of the case study include five major themes: i) The process of opening up towards the tool communities correlates in time with a general adoption of OSS in the organization. ii) Assets not seen as competitive advantage nor a source of revenue are made open to OSS communities, and gradually, the organization turns more open. iii) The requirements engineering process towards the community is informal and based on engagement. iv) The need for systematic and automated testing is still in its infancy, but the needs are identified. v) The innovation outcomes included free features and maintenance, and were believed to increase speed and quality in development. Adopting OI was a result of a paradigm shift of moving from Windows to Linux. This shift enabled Sony Mobile to utilize the Jenkins and Gerrit communities to make their internal development process better for its software developers and testers. © 2017 The Author(s)
|
|
| 27. |
- Munir, Hussan, Assistant Professor, et al.
(författare)
-
Open tools for software engineering : Validation of a theory of openness in the automotive industry
- 2019
-
Ingår i: PROCEEDINGS OF EASE 2019 - EVALUATION AND ASSESSMENT IN SOFTWARE ENGINEERING. - New York, NY, USA : Association for Computing Machinery. - 9781450371452 ; , s. 2-11, s. 2-11
-
Konferensbidrag (refereegranskat)abstract
- Context: Open tools (e.g., Jenkins, Gerrit and Git) offer a lucrative alternative to commercial tools. Many companies and developers from OSS communities make a collaborative effort to improve the tools. Prior to this study, we developed an empirically based theory for companies’ strategic choices on the development of these tools, based on empirical observations in the telecom domain. Aim: The aim of this study is to validate the theory of openness for tools in software engineering, in another domain, automotive. Specifically, we validated the theory propositions and mapped the case companies onto the model of openness. Method: We run focus groups in two automotive companies, collecting data in a survey and followup discussions. We used the repertory grid technique to analyze the survey responses, in combination with qualitative data from the focus group, to validate the propositions. Results: Openness of tools has the potential to reduce development costs and time, and may lead to process and product innovation. This study confirms three out of five theory propositions, on cost and time reduction, and the complementary role of open tools. One propositions was not possible to validate due to lack of investment in OSS tools communities by both companies. However, our findings extend the fifth proposition to require management being involved for both the proactive and reactive strategy. Further, we observe that the move towards open tools happen with a paradigm shift towards openness in the automotive domain, and lead to standardization of tools. Both companies confirm that they need legal procedures for the contribution, as well as an internal champion, driving the open tools strategy. Conclusion: We validated the theory, originating from the telecom domain, partially using two automotive companies. Both case companies are classified as laggards (reactive, cost saving) in the model of openness presented in the theory. Furthermore, we would like to have more validations studies to validate the remaining quadrants (e.g., leverage, lucrativeness and leaders). © 2019 Association for Computing Machinery.
|
|
| 28. |
- Ocieszak, Marcin, et al.
(författare)
-
On the use of Financial Valuation Techniques in Requirements Engineering
- 2018
-
Ingår i: 2018 1ST INTERNATIONAL WORKSHOP ON LEARNING FROM OTHER DISCIPLINES FOR REQUIREMENTS ENGINEERING (D4RE 2018). - : IEEE Communications Society. - 9781538684184 ; , s. 16-17
-
Konferensbidrag (refereegranskat)abstract
- This paper investigates methods and techniquesfrom finance for supporting value estimation for features orrequirements. We discuss the applicability and challenges as-sociated with applying financial techniques for feature valueestimation and for supporting requirements prioritization
|
|
| 29. |
- Ocieszak, Marcin, et al.
(författare)
-
Quo Vadis Mergers and Acquisitions in Software Business?
- 2019
-
Ingår i: VISION 2025. - : INT BUSINESS INFORMATION MANAGEMENT ASSOC-IBIMA. ; , s. 5502-5507
-
Konferensbidrag (refereegranskat)abstract
- This vision paper investigates the last three decades of mergers and acquisitions in the software industry and explores if the takeover strategy is still valid and promising and what implications could be drawn for software business. Our main findings highlight that the number of deals is decreasing but the average deal size is increasing. We also discover that the frequency of M&As is decreasing despite the growing capital market (S&P 500 index). We discuss the possible hypothesis and implications from these observations.
|
|
| 30. |
- Ocieszak, Marcin, et al.
(författare)
-
Using financial valuation techniques to minimize waste in requirements scoping
- 2019
-
Ingår i: Proceedings - 2019 IEEE 27th International Requirements Engineering Conference Workshops, REW 2019. - : Institute of Electrical and Electronics Engineers Inc.. - 9781728151656 ; , s. 3-6
-
Konferensbidrag (refereegranskat)abstract
- This paper presents our initial experiences with employing option theory and NPV techniques for optimizing waste reduction in requirements scoping. Inspired by financial market theories, we analyze a large requirements scoping decision making history from the mobile handset domain. We outline how we can optimize waste reduction in requirements scoping by modeling the neutral, positive and negative scenarios, giving each of the scenarios appropriate budget and development team commitment. © 2019 IEEE.
|
|
| 31. |
- Olsson, Thomas, et al.
(författare)
-
An empirical study on decision making for quality requirements
- 2019
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 149, s. 217-233
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Quality requirements are important for product success yet often handled poorly. The problems with scope decision lead to delayed handling and an unbalanced scope. Objective: This study characterizes the scope decision process to understand influencing factors and properties affecting the scope decision of quality requirements. Method: We studied one company's scope decision process over a period of five years. We analyzed the decisions artifacts and interviewed experienced engineers involved in the scope decision process. Results: Features addressing quality aspects explicitly are a minor part (4.41%) of all features handled. The phase of the product line seems to influence the prevalence and acceptance rate of quality features. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. Conclusions: There is a need to make quality mode explicit in the scope decision process. We propose a scope decision process at a strategic level and a tactical level. The former to address long-term planning and the latter to cater for a speedy process. Furthermore, we believe it is key to balance the stakeholder input with feedback from usage and market in a more direct way than through a long plan-driven process.
|
|
| 32. |
- Olsson, Thomas, et al.
(författare)
-
QREME – Quality requirements management model for supporting decision-making
- 2018
-
Ingår i: Part of the Lecture Notes in Computer Science book series (LNCS, volume 10753). - Cham : Springer International Publishing. - 9783319772424 ; , s. 173-188
-
Konferensbidrag (refereegranskat)abstract
- [Context and motivation] Quality requirements (QRs) are inherently difficult to manage as they are often subjective, context-dependent and hard to fully grasp by various stakeholders. Furthermore, there are many sources that can provide input on important QRs and suitable levels. Responding timely to customer needs and realizing them in product portfolio and product scope decisions remain the main challenge. [Question/problem] Data-driven methodologies based on product usage data analysis gain popularity and enable new (bottom-up, feedback-driven) ways of planning and evaluating QRs in product development. Can these be efficiently combined with established top-down, forward-driven management of QRs? [Principal idea/Results] We propose a model for how to handle decisions about QRs at a strategic and operational level, encompassing product decisions as well as business intelligence and usage data. We inferred the model from an extensive empirical investigation of five years of decision making history at a large B2C company. We illustrate the model by assessing two industrial case studies from different domains. [Contribution] We believe that utilizing the right approach in the right situation will be key for handling QRs, as both different groups of QRs and domains have their special characteristics.
|
|
| 33. |
- Ouriques, Raquel, et al.
(författare)
-
A Method to Evaluate Knowledge Resources in Agile Software Development
- 2019
-
Ingår i: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019. - : IEEE. - 9781728129686
-
Konferensbidrag (refereegranskat)abstract
- Background: Organizations adopting Agile Software Development (ASD) use different Knowledge Management (KM) practices to retain and share knowledge. However, it is often the case that knowledge retention is carried out in an ad-hoc way.Aims: In this study, we report our experience from proposing the Knowledge Critically Evaluation Method (KCEM) to evaluate knowledge items (KIT). Our main goal with KCEMs is to support companies to systematically retain knowledge in ASD contexts.Method: We conducted an improvement case study to develop and evaluate KCEM. This research follows the guidelines for technology transfer between industry and academia. The case and unit of analysis is Ericsson, a Swedish company that develops telecommunication solutions.Results: In this paper, we provide initial results of both lab and static validation, enriched by the lessons learned.Conclusions: The preliminary results show that KCEM is easy to understand and use, provides a different perspective on the KIT by visualizing in the criticality chart, and reduces the level of abstraction associated to a knowledge subject area.
|
|
| 34. |
- Ouriques, Raquel, et al.
(författare)
-
Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review
- 2019
-
Ingår i: International Journal of Software Engineering and Knowledge Engineering. - : World Scientific. - 0218-1940. ; 29:3
-
Tidskriftsartikel (refereegranskat)abstract
- Knowledge-intensive companies that adopt Agile Software Development (ASD) rely on efficient implementation of Knowledge Management (KM) strategies to promote different Knowledge Processes (KPs) to gain competitive advantage. This study aims to explore how companies that adopt ASD implement KM strategies utilizing practices that promote the KPs in the different organizational layers. Through a systematic literature review, we analyzed 32 primary studies, selected by automated search and snowballing in the extant literature. To analyze the data, we applied narrative synthesis. Most of the identified KM practices implement personalization strategies (81%), supported by codification (19%). Our review shows that the primary studies do not report KM practices in the strategic layer and two of them in the product portfolio layer; on the other hand, in the project layer, the studies report 33 practices that implement personalization strategy, and seven practices that implement codification. KM strategies in ASD promote mainly the knowledge transfer process with practices that stimulates social interaction to share tacit knowledge in the project layer. As a result of using informal communication, a significant amount of knowledge can be lost or not properly transferred to other individuals and, instead of propagating the knowledge, it remains inside a few individuals' minds.
|
|
| 35. |
- Ouriques, Raquel, et al.
(författare)
-
Thinking strategically about knowledge management in agile software development
- 2018
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer Verlag. - 0302-9743 .- 1611-3349. - 9783030036720 ; 11271 LNCS, s. 389-395
-
Konferensbidrag (refereegranskat)abstract
- Agile methodologies gave teams more autonomy regarding planning tasks and executing them. As a result, coordination gets more flexible, but much relevant knowledge remains undocumented and inside teams’ borders, due to informal communication and reduced development documentation. Since knowledge plays an essential role in software development, it is important to have effective knowledge management (KM) practices that contribute to a better knowledge resource allocation. Several KM practices have been reported in empirical studies in Agile Software Development (ASD). However, these practices are not evaluated regarding its effectiveness or how do they affect product quality. Besides, the studies do not demonstrate connections between the KM practices in the project level and the strategic level. The lack of connection between these levels can result in deviations from the company’s corporate strategy, wasted resources and irrelevant knowledge acquisition. This paper discusses how the strategic management can contribute to an integrated approach to KM in ASD; considering the organizational structure and the corporate strategy. Based on this discussion, we propose research areas that may help with planning KM strategies that can have their effectiveness measured and contribute to product quality. © Springer Nature Switzerland AG 2018.
|
|
| 36. |
- Ouriques, Raquel
(författare)
-
Understanding and Supporting Knowledge Management in Agile Software Development
- 2019
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Background. Agile Software Development (ASD) promises agility and flexibility in dealing with uncertainty by prioritizing interaction between people supported by informal communication and knowledge sharing. The lack of practices to manage the knowledge as a resource might jeopardize the application of knowledge in the production of goods and service. The utilization of Knowledge Management (KM) strategies can significantly support achieving and sustaining competitive advantage and brings several benefits to software development. However, how to manage knowledge in ASD is still not well understood or investigated. Objectives. The main objective of this thesis is to contribute to the software engineering field by providing a different perspective on directions that KM can take to improve knowledge-based resource (KBR) management in ASD. The detailed objectives are: (i) Understand the current ASD environment regarding KM; (ii) Identify KBRs in ASD and its implications for KM; and (iii) Provide an initial set of variables to evaluate knowledge criticality of knowledge items in ASD. Method. We used a mixed-methods approach to address the objective of this thesis. The methods selected to conduct the studies include systematic literature review, grounded theory, and improvement case study. The data collection comprised a literature review, semi-structured interviews, and practitioners’ feedback through static validation. Results. From our SLR we observed that that KM strategies in ASD promote mainly knowledge transfer through practices that stimulate social interaction to share tacit knowledge in the project layer, increasing the risk of losing knowledge by keeping the knowledge localized inside a few individual’s minds. When it comes to coordination, practitioners utilize KBRs in their routines, through social collaboration within teams’ environment/settings. However, this process is nonsystematic, which brings inefficiency to KBR utilization resulting in knowledge loss. It can generate negative implications to the course of the software development, including meaningless searches in databases, frustration because of recurrent problems, and unawareness of knowledge sources. To support decision making related to knowledge retention, we have developed an initial version of the method to evaluate the criticality (KCEM) of a knowledge item, which is divided into two categories, relevance, and scarcity. Conclusion. The current results of this thesis are of particular interest. However, we recognize that the work is unfinished. As a complement to this thesis, we have planned our long-term objective, which is to contribute to creating scalable KM solutions for companies adopting ASD.We divide this long-term objective into three studies: Carry out a complementary study to apply KCEM in different companies; explore efficient ways of storing codified knowledge in combination with the KCEM, and investigate how to define metrics to evaluate the outcomes of KM practices.
|
|
| 37. |
- Papatheocharous, Efi, et al.
(författare)
-
The GRADE taxonomy for supporting decision-making of asset selection in software-intensive system development
- 2018
-
Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849 .- 1873-6025. ; 100, s. 1-17
-
Tidskriftsartikel (refereegranskat)abstract
- Context: The development of software-intensive systems includes many decisions involving various stakeholders with often conflicting interests and viewpoints. Objective: Decisions are rarely systematically documented and sporadically explored. This limits the opportunity for learning and improving on important decisions made in the development of software-intensive systems. Method: In this work, we enable support for the systematic documentation of decisions, improve their traceability and contribute to potentially improved decision-making in strategic, tactical and operational contexts. Results: We constructed a taxonomy for documentation supporting decision-making, called GRADE. GRADE was developed in a research project that required composition of a common dedicated language to make feasible the identification of new opportunities for better decision support and evaluation of multiple decision alternatives. The use of the taxonomy has been validated through thirty three decision cases from industry. Conclusion: This paper occupies this important yet greatly unexplored research gap by developing the GRADE taxonomy that serves as a common vocabulary to describe and classify decision-making with respect to architectural assets.
|
|
| 38. |
|
|
| 39. |
- Petersen, Kai, et al.
(författare)
-
Choosing Component Origins for Software Intensive Systems: In-House, COTS, OSS or Outsourcing?-A Case Survey
- 2018
-
Ingår i: IEEE Transactions on Software Engineering. - : IEEE Computer Society. - 0098-5589 .- 1939-3520. ; 44:3, s. 237-261
-
Tidskriftsartikel (refereegranskat)abstract
- The choice of which software component to use influences the success of a software system. Only a few empirical studies investigate how the choice of components is conducted in industrial practice. This is important to understand to tailor research solutions to the needs of the industry. Existing studies focus on the choice for off-the-shelf (OTS) components. It is, however, also important to understand the implications of the choice of alternative component sourcing options (CSOs), such as outsourcing versus the use of OTS. Previous research has shown that the choice has major implications on the development process as well as on the ability to evolve the system. The objective of this study is to explore how decision making took place in industry to choose among CSOs. Overall, 22 industrial cases have been studied through a case survey. The results show that the solutions specifically for CSO decisions are deterministic and based on optimization approaches. The non-deterministic solutions proposed for architectural group decision making appear to suit the CSO decision making in industry better. Interestingly, the final decision was perceived negatively in nine cases and positively in seven cases, while in the remaining cases it was perceived as neither positive nor negative.
|
|
| 40. |
- Runeson, Per, et al.
(författare)
-
It is More Blessed to Give than to Receive – Open Software Tools Enable Open Innovation
- 2015
-
Ingår i: Tiny Transactions on Computer Science. ; 4
-
Tidskriftsartikel (refereegranskat)abstract
- Open Innovation (OI) has attracted scholarly interest from a wide range of disciplines since introduced by Chesbrough, i.e. ”a paradigm that assumes that firms can and should use external ideas as well as internal ideas, and internal and external paths to market, as they look to advance their technology”. However, OI remains unexplored for software engineering (SE), although widespread in practice through Open Source Software (OSS). We studied the relation between SE and OI and in particular how OSS tools impact on software-intensive organization’s innovation capability. We surveyed the literature on SE and OI and found that studies conclude that start-ups have higher tendency to opt for OI compared to established companies. The literature also suggests that firms assimilating external knowledge into their internal R&D activities, have higher likelihood of gaining financial advantages. In a case study, we observed how OSS tools Jenkins and Gerrit enabled open innovation. We mined software commits to identify major contributors, found them be affiliated to Sony Mobile, contacted five of them for interviews about their and their employer’s principles and practices with respect to OI and tools, which they gave a consistent view of. Our findings indicate that the company’s transition to OI was part of a major paradigm shift towards OSS, while the adoption of open tools was driven bottom up by engineers with support from management. By adopting OI, Sony Mobile achieved freed-up developers’ time, better quality assurance, inner source initiatives, flexible development environment, faster releases and upgrades. Particularly, the introduction of a test framework was proposed by Sony Mobile but implemented by other contributors. However, the benefits are gained through investing significant attention and resources to the OSS community in terms of technical contributions and leadership.
|
|
| 41. |
- Silva, Lakmal, et al.
(författare)
-
Monitoring and maintenance of telecommunication systems : Challenges and research perspectives
- 2019. - 830
-
Ingår i: ENGINEERING SOFTWARE SYSTEMS. - Cham : Springer. - 9783319996172 ; , s. 166-172
-
Konferensbidrag (refereegranskat)abstract
- In this paper, we present challenges associated with monitoring and maintaining a large telecom system at Ericsson that was developed with high degree of component reuse. The system constitutes of multiple services, composed of both legacy and modern systems that are constantly changing and need to be adapted to changing business needs. The paper is based on firsthand experience from architecting, developing and maintaining such a system, pointing out current challenges and potential avenues for future research that might contribute to addressing them. © Springer Nature Switzerland AG 2019.
|
|
| 42. |
- Silvander, Johan, 1965-, et al.
(författare)
-
Encouraging Business Flexibility by Improved Context Descriptions
- 2017
-
Ingår i: Proceedings of the Seventh International Symposium on Business Modeling and Software Design. - : SciTePress. - 9789897582387 ; , s. 225-228
-
Konferensbidrag (refereegranskat)abstract
- Business-driven software architectures are emerging and gaining importance for many industries. As softwareintensive solutions continue to be more complex and operate in rapidly changing environments, there is a pressure for increased business flexibility realized by more efficient software architecture mechanisms to keep up with the necessary speed of change. We investigate how improved context descriptions could be implemented in software components, and support important software development practices like business modeling and requirement engineering. This paper proposes context descriptions as an architectural support for improving the connection between business flexibility and software components. We provide initial results regarding software architectural mechanisms which can support context descriptions as well as the context description’s support for business-driven software architecture, and the business flexibility demanded by the business ecosystems.
|
|
| 43. |
- Silvander, Johan, 1965-, et al.
(författare)
-
Supporting Continuous Changes to Business Intents
- 2017
-
Ingår i: International journal of software engineering and knowledge engineering. - : World Scientific. - 0218-1940. ; 27:8, s. 1167-1198
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Software supporting an enterprise’s business, also known as a business support system, needs to support the correlation of activities between actors as well as influence the activities based on knowledge about the value networks in which the enterprise acts. This requires the use of policies and rules to guide or enforce the execution of strategies or tactics within an enterprise as well as in collaborations between enterprises. With the help of policies and rules, an enterprise is able to capture an actor’s intent in its business support system, and act according to this intent on behalf of the actor. Since the value networks an enterprise is part of will change over time the business intents’ life cycle states might change. Achieving the changes in an effective and efficient way requires knowledge about the affected intents and the correlation between intents.Objective: The aim of the study is to identify how a business support system can support continuous changes to business intents. The first step is to find a theoretical model which serves as a foundation for intent-driven systems.Method: We conducted a case study using a focus group approach with employees from Ericsson. This case study was influenced by the spiral case study process.Results: The study resulted in a model supporting continuous definition and execution of an enterprise. The model is divided into three layers; Define, Execute, and a com- mon governance view layer. This makes it possible to support continuous definition and execution of business intents and to identify the actors needed to support the business intents’ life cycles. This model is supported by a meta-model for capturing information into viewpoints.Conclusion: The research question is addressed by suggesting a solution supporting con- tinuous definition and execution of an enterprise as a model of value architecture compo- nents and business functions. The results will affect how Ericsson will build the business studio for their next generation business support systems.
|
|
| 44. |
- Sundelin, Anders, 1970-, et al.
(författare)
-
Test-Driving FinTech Product Development : An Experience Report
- 2018
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer. - 9783030036720 ; , s. 219-226
-
Konferensbidrag (refereegranskat)abstract
- In this paper, we present experiences from eight years of developing a financial transaction engine, using what can be described as an integration-test-centric software development process.We discuss the product and the relation between three different categories of its software and how the relative weight of these artifacts has varied over the years.In addition to the presentation, some challenges and future research directions are discussed.
|
|
| 45. |
- Wilson, Magnus, et al.
(författare)
-
A Literature Review on the Effectiveness and Efficiency of Business Modeling
- 2018
-
Ingår i: e-Informatica Software Engineering Journal. - : WROCLAW UNIV TECHNOLOGY. - 1897-7979 .- 2084-4840. ; 12:1, s. 265-302
-
Forskningsöversikt (refereegranskat)abstract
- Background: Achieving and maintaining a strategic competitive advantage through business and technology innovation via continually improving effectiveness and efficiency of the operations are the critical survival factors for software-intensive product development companies. These companies invest in business modeling and tool support for integrating business models into their product development, but remain uncertain, if such investments generate desired results. Aim: This study explores the effects of business modeling on effectiveness and efficiency for companies developing software-intensive products. Method: We conducted a systematic literature review using the snowballing methodology, followed by thematic and narrative analysis. 57 papers were selected for analysis and synthesis, after screening 16 320 papers from multiple research fields. Results: We analyzed the literature based on purpose, benefit, challenge, effectiveness, and efficiency with software and software-intensive products as the unit of analysis. The alignment between strategy and execution is the primary challenge, and we found no evidence that business modeling increases effectiveness and efficiency for a company. Any outcome variations may simply be a result of fluctuating contextual or environmental factors rather than the application of a specific business modeling method. Therefore, we argue that governance is the fundamental challenge needed for business modeling, as it must efficiently support simultaneous experimentation with products and business models while turning experiences into knowledge. Conclusion: We propose a conceptual governance model for exploring the effectiveness and efficiency of business modeling to occupy the missing link between business strategy, processes and software tools. We also recommend managers to introduce a systematic approach for experimentation and organizational learning, collaboration, and value co-creation.
|
|
| 46. |
- Wilson, Magnus, et al.
(författare)
-
Business Modeling and Flexibility in Software-Intensive Product Development - A Systematic Literature Review
- 2018
-
Ingår i: 17th IFIP WG 6.11 Conference on e-Business, e-Services, and e-Society, I3E 2018, Kuwait City, Kuwait, October 30 – November 1, 2018, Proceedings. - Cham : Springer. - 9783030021306 ; , s. 292-304
-
Konferensbidrag (refereegranskat)abstract
- Continuously achieving and maintaining competitive advantage is the critical survival factor for software-intensive product development companies undergoing digitalization transformation. These companies remain uncertain if investments in business modeling is sufficient to cope with rapidly changing business models, technology, and customer demands. We conducted a Systematic Literature Review using the snowballing methodology to explore the effects of business modeling on business flexibility and variability in the realization. Our results confirm a research gap regarding translating desired strategic flexibility into business options that can efficiently and effectively be implemented using software-based variability in the realization. We conclude that more research is needed consolidating business model innovation, experimentation, and operationalization. Building on theories for learning and knowledge creation, we propose a framework for describing change and analyzing strategic, tactical and operational choices in business model experimentation.
|
|
| 47. |
- Wilson, Magnus, 1965-
(författare)
-
Towards Effective and Efficient Business Model change : Opportunities and challenges for software-intensive product development companies
- 2019
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Digitalization initiates and drives significant changes to the process level, organization level, and business level of software-intensive product development (SIPD) companies and their customers. Digitalization creates new opportunities through digital transformation strategies of the business environment. Digitalization also significantly reduces the turnaround-time on a transaction, driving new challenges for the alignment of business and technology changes. For a successful business model realization, a company must understand what capabilities the organization has (in staff and products), what is required, and more importantly, how to turn these capabilities into good-enough abilities without disturbing the effectiveness and efficiency of the daily operations. Integrating the product and service development and the value delivery with a learning organization is critical for efficient business model change (BMCh).This thesis seeks to develop conceptual models for how BMCh is linked to value, learning organization design, and the transformation of capabilities into abilities derived from business model activities and actor interactions. Such conceptual models facilitate to investigate and identify critical mechanisms and capabilities needed to effectively and efficiently manage BMCh at full scale for SIPD companies, allowing them to exploit the on-going digitalization, may it be through (disruptive) business model innovation, technology innovation, or by continuously adapting and evolving the business operations. I use the SIPD company as the unit of analysis, with the dual-lens of value and knowledge, set in the context of a business model and how the value creation and capture are influenced by the interaction between two actors performing a business model activity. I build on the business model literature and infuse theories for knowledge creation, learning organizations, and contractual promises to create value. Conducting a cross-disciplinary literature review, followed by a synthesis of related literature, industry best-practices, and an associated design science study, my propositions were validated in a longitudinal case study exploring a service industrialization program in the telecommunication industry.I have produced five conceptual models and seven propositions as a start to be able to support the design of a governance mechanism, as the critical engine for both the learning organization and effective and efficient BMCh. The industry now explores the models found during the case study.My synthesis shows a need for further research into BMCh regarding early detection and measurements of gaps in value, gaps in knowledge, ambiguity, equivocality, and abilities. Flexible role-based governance views present the measurements, as part of the governance mechanisms for full-scale, effective, and efficient BMCh. Further, I also aim to implement such governance mechanisms in software, by using the associated research in intent-driven systems. In the meantime, I propose industry to build knowledge and experience related to the seven propositions.
|
|
| 48. |
- wilson, Magnus, et al.
(författare)
-
Towards Multi-context Goal Modeling and Analysis with the Help of Intents
- 2018
-
Ingår i: Proceedings - 2018 8th International Model-Driven Requirements Engineering Workshop, MoDRE 2018. - : IEEE Computer Society Digital Library. - 9781538684061 ; , s. 68-72
-
Konferensbidrag (refereegranskat)abstract
- This vision paper discusses the need for enriching goal modeling with intents and context frame to provide much richer contextual information over goals and realization strategies. Based on the extensive experience of business modeling at Ericsson and a review of current goal modeling approaches, we suggest possible research directions towards enriching goal modeling.
|
|
| 49. |
- Wnuk, Krzysztof, et al.
(författare)
-
A systematic mapping study on requirements scoping
- 2016
-
Ingår i: ACM International Conference Proceeding Series. - New York, NY, USA : ACM Press. - 9781450336918
-
Konferensbidrag (refereegranskat)abstract
- Context: Requirements scoping is one of the key activities in requirements management but also a major risk for project management. Continuously changing scope may create a congestion state in handling the requirements inflow which causes negative consequences, e.g. delays or scope creep. Objectives: In this paper, we look at requirements scoping literature outside Software Product Line (SPL) by exploring the current literature on the phenomenon, summarizing publication trends, performing thematic analysis and analyzing the strength of the evidence in the light of rigor and relevance assessment. Method: We run a Systematic Mapping Study (SMS) using snowballing procedure, supported by a database search for the start set identification, and identified 21 primary studies and 2 secondary studies. Results: The research interest in this area steadily increases and includes mainly case studies, validation or evaluation studies. The results were categorized into four themes: definitions, negative effects associated with scoping, challenges and identified methods/tools. The identified scope management techniques are also matched against the identified requirements scoping challenges.
|
|
| 50. |
- Wnuk, Krzysztof, 1982-, et al.
(författare)
-
Agile and lean metrics associated with requirements engineering
- 2017
-
Ingår i: ACM International Conference Proceeding Series. - New York, NY, USA : Association for Computing Machinery. - 9781450348539 ; , s. 33-40
-
Konferensbidrag (refereegranskat)abstract
- Despite the continuously increasing importance of Agile and Lean in software development, the number of studies that investigate Requirements Engineering (RE) related aspects remains low. In this paper, we report the results from a literature review about Agile and Lean requirements engineering. By performing a systematic mapping literature review, we identified 22 metrics in 18 publications. We analyzed the identified papers based on research methodology, rigor and relevance and other external attributes. We also map the identified metrics on the abstracted model for Agile and Lean development. We conclude that requirements-associated metrics are underrepresented in the literature and most of the metrics focuses on the time aspect rather than the quality aspect. © 2017 Copyright is held by the owner/author(s).
|
|
