| 1. |
- Nedstam, Josef, et al.
(author)
-
Experiences from the Architectural Change Process
- 2003
-
In: Proceedings of the Second International Workshop “From Software Requirements to Architectures” (STRAW’03) at the International Conference on Software Engineering.
-
Conference paper (peer-reviewed)abstract
- A good software architecture is becoming recognized as a major factor for successful products. There has been much research on the technical aspects of software architecture and it is recognized that the driving requirements for architectures are "non-functional", but few have studied how organizations decide on architectural changes. In this paper we study the topic through several case studies. The changes to the architecture are in all cases changes to the "non-functional" requirements on the system. Issues that we want to evaluate are: when and how is the need for an architectural change discovered; what is the underlying non-functional requirement; who drives the change; how is it prepared and evaluated; and finally, who makes the decision and how is it implemented. Through interviews with people that have experience from architectural changes we compare the decision process for architectural changes to the ordinary functional requirement change process and the organizational change process. We find that architectural changes have aspects of both functional and organizational changes. An architectural change does not only need to be technically sound, it also needs to be anchored firmly in the organization. This report gives both architects and managers guidelines to balance short-term project goals and longterm organizational goals with respect to architecture.
|
|
| 2. |
- Nedstam, Josef, et al.
(author)
-
The architectural change process
- 2004
-
In: 2004 International Symposium on Empirical Software Engineering. - 0769521657 ; , s. 27-36
-
Conference paper (peer-reviewed)abstract
- Software architecture is recognized as a critical factor for successful products, but few have studied how organizations decide on architectural changes. In this paper we study the topic through several case studies. The changes are in all cases changes to the quality attributes of the system, and follow the same general process. We find that architectural changes have aspects of both functional and organizational changes. An architectural change does not only need to be technically sound, but it also needs to be anchored firmly in the organization. This paper describes the general architectural change process, and gives both architects and managers guidelines to balance short-term project goals and long-term organizational goals within this process
|
|
| 3. |
- Taxén, Lars, et al.
(author)
-
Incremental development for AXE 10
- 1995
-
Conference paper (peer-reviewed)abstract
- To become more reactive and flexible to the market needs, i.e. shorter lead-times and more flexibility in handling late and changing requirements, Ericsson’s AXE 10 development processes have been adapted to support incremental development. The basic principle is to develop each of the customer features in one executable and testable increment. In order to plan, coordinate and control projects executed in this way, an Incremental Development Method Package, IDMP, has been developed by UAB in close cooperation with support groups in development projects. In this paper, we define what we mean with incremental development and describe the main aspects of the package. We also report experiences from using the package in the CMS 30 phase 7 and HELIOS projects. A prototype tool which supports the package is described, together with the experiences from using the tool in the pilot project Combined Gateway. Even if the IDMP has been developed towards AXE 10, it has proven useful in non AXE 10 projects, as the principles are rather independent of development process.
|
|
| 4. |
- Wnuk, Krzysztof, et al.
(author)
-
Controlling Lost Opportunity Costs in Agile Development – the Basic Lost Opportunity Estimation Model for Requirements Scoping
- 2012
-
In: Software Business/Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 9783642307454 ; 114:2, s. 255-260
-
Conference paper (peer-reviewed)abstract
- We present a model for estimating the final keep/cancel decision point, on a per-feature basis, for scope inclusion in a future release. The Basic Lost Opportunity Estimation Model (BLOEM), based on data from a company that uses an agile-inspired software development model, supports feature selection when the time-dependent business value estimates change as the requirements analysis progresses. The initial BLOEM validation, conducted on a set of 166 features, suggests that the model can valuable input to the feature selection process for a given release, helping to control lost opportunity costs due to feature cancellation. Limitations of BLOEM are discussed and issues for further research are presented.
|
|
| 5. |
|
|
| 6. |
|
|
| 7. |
- Wnuk, Krzysztof, et al.
(author)
-
How can Open Source Software Development Help Requirements Management Gain the Potential of Open Innovation: An Exploratory Study
- 2012
-
In: Proceedings Of The ACM-IEEE International Symposium On Empirical Software Engineering And Measurement (ESEM'12). - 1938-6451. ; , s. 271-279
-
Conference paper (peer-reviewed)abstract
- A key component in successfully managing software products is to properly, and in a timely manner, identify and secure competitive advantage by innovation via feature differentiation. Although open source software (OSS) is not a new idea, several product development companies that operate in a market-driven context have started to use open source solutions as core software components in their products. Adopting open source core components implies a lower degree of control over software development and increased business risk associated with integrating differentiating contributions into the core release stream. Whether and how to adjust the current requirements management practices after the adoption of OSS components to fully benefit from the concept of open innovation has not yet been empirically explored. We outline experiences and challenges related to leveraging open innovation via engaging in OSS identified during 19 interviews with practitioners occupying different roles in the requirements management process at a large company followed by four validation interviews with other practitioners. We then propose a research agenda for requirements and decision management in the open innovation context and suggest which challenges in requirements engineering open innovation affects.
|
|
| 8. |
- Wnuk, Krzysztof, et al.
(author)
-
Supporting Scope Tracking and Visualization for Very Large-Scale Requirements Engineering-Utilizing FSC+, Decision Patterns, and Atomic Decision Visualizations
- 2016
-
In: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; 42:1, s. 47-74
-
Journal article (peer-reviewed)abstract
- Deciding the optimal project scope that fulfills the needs of the most important stakeholders is challenging due to a plethora of aspects that may impact decisions. Large companies that operate in rapidly changing environments experience frequently changing customer needs which force decision makers to continuously adjust the scope of their projects. Change intensity is further fueled by fierce market competition and hard time-to-market deadlines. Staying in control of the changes in thousands of features becomes a major issue as information overload hinders decision makers from rapidly extracting relevant information. This paper presents a visual technique, called Feature Survival Charts+ (FSC+), designed to give a quick and effective overview of the requirements scoping process for Very Large-Scale Requirements Engineering (VLSRE). FSC+ were applied at a large company with thousands of features in the database and supported the transition from plan-driven to a more dynamic and change-tolerant release scope management process. FSC+ provides multiple views, filtering, zooming, state-change intensity views, and support for variable time spans. Moreover, this paper introduces five decision archetypes deduced from the dataset and subsequently analyzed and the atomic decision visualization that shows the frequency of various decisions in the process. The capabilities and usefulness of FSC+, decision patterns (state changes that features undergo) and atomic decision visualizations are evaluated through interviews with practitioners who found utility in all techniques and indicated that their inherent flexibility was necessary to meet the varying needs of the stakeholders.
|
|
