| 1. |
- Alves, C. F., et al.
(author)
-
Welcome from the IWSECO-WEA chairs
- 2014
-
In: Proceedings - International Conference on Software Engineering. - New York, NY, USA : ACM. - 0270-5257.
-
Conference paper (peer-reviewed)abstract
- The creation and adoption of a software ecosystem is becoming increasingly pervasive, leading to new research and management challenges. Several companies are platformizing successful products and opening these products up for outside innovation where customers expect to be actively involved in the shaping of the technology they use. This also leads to new opportunities and challenges regarding new business models, open innovation, collaborative development, strategic planning, and coordination of multiple platforms. IWSECO and WEA aim to further increase the body of knowledge in software ecosystems by providing a forum to exchange ideas and discuss the most recent innovations, trends and experiences in the field. It aims to build and shape the community of leading practitioners and research experts by providing a forum for the exchange of research results and industrial practice in software ecosystems. By co-locating both, IWSECO and WEA we aim at attracting and involving interested participants from the larger European software engineering community in an early stage of shaping software ecosystem research and community building. The co-located workshops will be a venue for practitioners and researchers to share experience and lessons learned; with a particular focus on architecture, as the ecosystem architecture can actually determine the success or failure of software ecosystems as a whole.
|
|
| 2. |
- Andreo, Sebastien, et al.
(author)
-
API management challenges in ecosystems
- 2019
-
In: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 370, s. 86-93
-
Conference paper (peer-reviewed)abstract
- The API has become a cornerstone of software ecosystems, providing ways to drive innovation inside and outside the organization. Because of this criticality, we should manage APIs. The purpose of this study is to identify and classify the challenges that organizations evolving into internal ecosystems are facing as they have to deal with APIs. We performed a qualitative research study on three Siemens internal ecosystems with different sizes, technologies, and age. The results reveal that even if we are talking about the API economy, organizations are struggling with different aspects of API management related to Business, Architecture, Process, and Organization. The challenges identified in this paper provide a basis for future research.
|
|
| 3. |
- Andreo, Sebastien, et al.
(author)
-
OpEx driven software architecture a case study
- 2021
-
In: CEUR Workshop Proceedings. - 1613-0073. ; 2978
-
Conference paper (peer-reviewed)abstract
- In the last thirty years, the software industry has changed how systems are architected and how systems are distributed. Software is moving from a monolithic architecture and locally installed application to micro-services architecture and applications accessible through the internet. The accessibility over the internet is provided by the emergence of cloud providers like Amazon AWS, Microsoft Azure, or Google GCP. This transformation also impacts the financial structure of software projects, which is moving from capital expenditure (CapEx) to operational expenditure (OpEx). This paper highlights the implication of architecture decisions on a cloud application’s operating cost based on two industrial case studies.
|
|
| 4. |
- Backlund, Emil, 1988, et al.
(author)
-
Automated User Interaction Analysis for Workflow-Based Web Portals
- 2014
-
In: Software Business. - Cham : Springer. ; 182, s. 148-162
-
Conference paper (peer-reviewed)abstract
- Success in the software market requires constant improvement of the software. These improvements however have to directly align with the needs of the users of the software. A recent trend in software engineering is to collect post-deployment data about how users use a software system. We report in this paper about a case study with an industrial partner in which (1) we identified which data has to be collected for a web-based portal system, (2) implemented the data collection, and (3) performed an experiment comparing the collected data with answers of the test subjects in a survey.
|
|
| 5. |
- Begel, A., et al.
(author)
-
Bridging Software Communities through Social Networking
- 2013
-
In: IEEE Software. - 1937-4194 .- 0740-7459. ; 30:1, s. 26-28
-
Research review (peer-reviewed)abstract
- Over the past decade, the advent of social networking has fundamentally altered the landscape of how software is used, designed, and developed. It has expanded how communities of software stakeholders communicate, collaborate, learn from, and coordinate with one another. The guest editors of this special issue describe both the field and the articles they selected for it.
|
|
| 6. |
- Begel, A., et al.
(author)
-
Social networking meets software development: Perspectives from git hub, MSDN, stack exchange, and top coder
- 2013
-
In: IEEE Software. - 1937-4194 .- 0740-7459. ; 30:1, s. 52-66
-
Journal article (peer-reviewed)abstract
- Many successful software companies use social networking as a way to improve the services or products they provide. To gain an understanding of the role social networking plays in today's software development world, the guest editors of the January/February 2013 issue conducted semistructured interviews with leaders from four successful companies: Brian Doll, an engineer who manages GitHub's marketing; Doug Laundry, a principal group program manager at Microsoft; David Fullerton, vice president of engineering at Stack Exchange; and Robert Hughes, the president and chief operating officer of TopCoder. The first Web extra at http://try.github.com is a video of Joel Spolsky discussing the structure, software, technology, and culture of Stack Exchange. The second Web extra at http://blip.tv/play/gvUBgqLbRgI.html is a video of Matthew McCullough and Tim Berglund demonstrating how Git not only incorporates the best features of existing source control systems but also includes unique distributed capabilities that make version control commands available without connectivity, allowing you to choose when to interact with a network. The third Web extra at http://blip.tv/play/gvUBgqLbRgI.html is a video of Matthew McCullough and Tim Berglund demonstrating how to leverage Git's powerful yet underused advanced features. The last Web extra at http://youtu.be/SK6TBI1bNLI is a video of Thomas Baden, Chief Information Officer, State of Minnesota, Department of Human Services, describing the experience of working on the TopCoder Platform and with the members of the TopCoder Community.
|
|
| 7. |
- Besker, Terese, 1970, et al.
(author)
-
A systematic literature review and a unified model of ATD
- 2016
-
In: Proceedings of the EUROMICRO Conference. - 1089-6503. - 9781509028191 ; , s. 189-197
-
Conference paper (peer-reviewed)abstract
- Fast software deliveries are hindered by high maintenance efforts due to internal quality issues and Technical Debt (TD) and specifically, Architectural Technical Debt (ATD) has received increased attention in the last few years. ATD has a significant influence and impact on system success and, left unchecked, it can cause expensive repercussions; it is, therefore, of maintenance and evolutionary importance to understand the basic underlying factors of ATD. Thus, with this as background, there is a need for a descriptive model to illustrate and explain the different ATD issues. The aim of this study is to synthesize and compile research efforts with the goal of creating new knowledge with a specific interest in the ATD field. The contribution of this paper is the presentation of a novel descriptive model, providing a comprehensive interpretation of the ATD phenomenon. This model categorizes the main characteristics of ATD and reveals their corresponding relations. The model is based on a systematic literature review (SLR) of currently recognized knowledge concerning ATD.
|
|
| 8. |
- Besker, Terese, 1970, et al.
(author)
-
An investigation of Technical Debt in Automatic Production Systems
- 2017
-
In: ACM International Conference Proceeding Series. - New York, NY, USA : ACM. - 9781450352642
-
Conference paper (peer-reviewed)abstract
- Technical Debt is a recent concept, borrowed from the financial domain. It has been recently used in software development to describe technical sub-optimal solutions that have short-term benefits but long-term extra-costs. However, no body of literature investigates how Automatic Production Systems companies deal with Technical Debt. We investigated how Technical Debt is known, how much it hurts and how is managed in an automatic production systems company. Results from one in-depth investigation show that the automatic production systems company spend quite a lot of resources because of Technical Debt, both in the extra-costs (interest) and in its management. The company presents moderate awareness of what Technical Debt is and how much is present in its systems. However, the tracking level is quite low. We, therefore, claim that Technical Debt needs more research in this domain, as it is a source of substantial extra-costs and the current practices to manage it are not suitable.
|
|
| 9. |
- Besker, Terese, 1970, et al.
(author)
-
Carrot and Stick approaches when managing Technical Debt
- 2020
-
In: Proceedings - 2020 IEEE/ACM International Conference on Technical Debt, TechDebt 2020. - New York, NY, USA : ACM. ; , s. 21-30
-
Conference paper (peer-reviewed)abstract
- When developing software, it is vitally important to keep the level of technical debt down since it is well established from several studies that technical debt can, e.g., lower the development productivity, decrease the developers’ morale, and compromise the overall quality of the software. However, even if researchers and practitioners working in today's software development industry are quite familiar with the concept of technical debt and its related negative consequences, there has been no empirical research focusing specifically on how software managers actively communicate and manage the need to keep the level of technical debt as low as possible. This paper aims to explore how software companies encourage and reward practitioners for actively keeping the level of technical debt down and also whether the companies use any forcing or penalizing initiatives when managing technical debt. This paper reports the results of both an online web-survey provided quantitative data from 258 participants and follow-up interviews with 32 industrial software practitioners. The findings show that having a TD management strategy can significantly impact the amount of TD in the software. When surveying how commonly used different TD management strategies are, we found that only the encouraging strategy is, to some extent, adopted in today's’ software industry. This study also provides a model describing the four assessed strategies by presenting its strategies and tactics, together with recommendations on how they could be operationalized in today’s software companies.
|
|
| 10. |
- Besker, Terese, 1970, et al.
(author)
-
Embracing Technical Debt, from a Startup Company Perspective
- 2018
-
In: PROCEEDINGS 2018 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE AND EVOLUTION (ICSME). - 1063-6773. - 9781538678701 - 9781538678701 ; , s. 415-425
-
Conference paper (peer-reviewed)abstract
- Software startups are typically under extreme pressure to get to market quickly with limited resources and high uncertainty. This pressure and uncertainty is likely to cause startups to accumulate technical debt as they make decisions that are more focused on the short-term than the long-term health of the codebase. However, most research on technical debt has been focused on more mature software teams, who may have less pressure and, therefore, reason about technical debt very differently than software startups. In this study, we seek to understand the organizational factors that lead to and the benefits and challenges associated with the intentional accumulation of technical debt in software startups. We interviewed 16 professionals involved in seven different software startups. We find that the startup phase, the experience of the developers, software knowledge of the founders, and level of employee growth are some of the organizational factors that influence the intentional accumulation of technical debt. In addition, we find the software startups are typically driven to achieve a “good enough level,” and this guides the amount of technical debt that they intentionally accumulate to balance the benefits of speed to market and reduced resources with the challenges of later addressing technical debt.
|
|
