| 1. |
- Borg, Andreas, 1976-
(author)
-
Processes and Models for Capacity Requirements in Telecommunication Systems
- 2009
-
Doctoral thesis (other academic/artistic)abstract
- Capacity is an essential quality factor in telecommunication systems. The ability to develop systems with the lowest cost per subscriber and transaction, that also meet the highest availability requirements and at the same time allow for scalability, is a true challenge for a telecommunication systems provider. This thesis describes a research collaboration between Linköping University and Ericsson AB aimed at improving the management, representation, and implementation of capacity requirements in large-scale software engineering.An industrial case study on non-functional requirements in general was conducted to provide the explorative research background, and a richer understanding of identified difficulties was gained by dedicating subsequent investigations to capacity. A best practice inventory within Ericsson regarding the management of capacity requirements and their refinement into design and implementation was carried out. It revealed that capacity requirements crosscut most of the development process and the system lifecycle, thus widening the research context considerably. The interview series resulted in the specification of 19 capacity sub-processes; these were represented as a method plug-in to the OpenUP software development process in order to construct a coherent package of knowledge as well as to communicate the results. They also provide the basis of an empirically grounded anatomy which has been validated in a focus group. The anatomy enables the assessment and stepwise improvement of an organization’s ability to develop for capacity, thus keeping the initial cost low. Moreover, the notion of capacity is discussed and a pragmatic approach for how to support model-based, function-oriented development with capacity information by its annotation in UML models is presented. The results combine into a method for how to improve the treatment of capacity requirements in large-scale software systems.
|
|
| 2. |
- Franch, Xavier, et al.
(author)
-
A Study about the Knowledge and Use of Requirements Engineering Standards in Industry
- 2022
-
In: IEEE Transactions on Software Engineering. - : Institute of Electrical and Electronics Engineers Inc.. - 0098-5589 .- 1939-3520. ; 48:9, s. 3310-3325
-
Journal article (peer-reviewed)abstract
- The use of standards is considered a vital part of any engineering discipline. So one could expect that standards play an important role in Requirements Engineering (RE) as well. However, little is known about the actual knowledge and use of RE-related standards in industry. <i>Objective</i>. In this article, we investigate to which ex-tent standards and related artifacts such as templates or guidelines are known and used by RE practitioners. <i>Method</i>. To this end, we have conducted an online survey. We could analyze the replies from 90 RE practitioners using a combination of closed and open-text questions. <i>Results</i>. Our results indicate that the knowledge and use of standards and related artifacts in RE may be less widespread than one might expect from an engineering perspective. For example, about 45% of the respondents working as requirements engineers or business analysts do not know at least one of the two core standards in RE. Participants in our study mostly use standards rather by personal decision than imposed by their company, customer, or regulator. Beyond insufficient knowledge, we also found cultural and organizational factors impeding the widespread adoption of standards in RE. <i>Conclusions</i>. Overall, our results provide empirically informed insights into the actual use of standards and related artifacts in RE practice and indirectly about the value that the current standards create for RE practitioners. IEEE
|
|
| 3. |
- Fricker, Samuel, et al.
(author)
-
Goal-Oriented Requirements Communication in New Product Development
- 2008
-
Conference paper (peer-reviewed)abstract
- Product development organizations often distribute the responsibilities for requirements engineering over several roles. The collaboration of product management, concerned with market needs, and product development, concerned with the technological aspects of a product, is well established. Such shared responsibility provides advantages in the utilization of specific knowledge, skills, and resources. However, the collaboration leads to increased demands on coordination. Novel concepts and models need to be investigated to support such collaborative requirements engineering. In this paper we focus on requirements communication from product management to a development team by proposing and evaluating the model of goaloriented requirements communication. The model explains how efficiency and effectiveness of requirements communication can be increased and allows the utilization of established requirements engineering knowledge in a new way to address the task of requirements communication.
|
|
| 4. |
- Glinz, Martin, et al.
(author)
-
On Shared Understanding in Software Engineering
- 2013
-
Conference paper (other academic/artistic)abstract
- Shared understanding is essential for efficient communication in software development and evolution projects when the risk of unsatisfactory outcome and rework of project results shall be low. Today, however, shared understanding is used mostly in an unreflected, intuitive way. This is particularly true for implicit shared understanding. In this paper, we investigate the role, value and usage of shared understanding in Software Engineering. We contribute a reflected analysis of the problem, in particular of how to rely on implicit shared understanding. We discuss enablers and obstacles, compile existing practices for dealing with shared understanding, and present a roadmap for improving knowledge and practice in this area.
|
|
| 5. |
- Glinz, Martin, et al.
(author)
-
On Shared Understanding in Software Engineering : an Essay
- 2015
-
In: Computer Science - Research and Development. - : Springer. - 1865-2034 .- 1865-2042. ; 30:3, s. 363-376
-
Journal article (peer-reviewed)abstract
- Shared understanding is essential for efficient software engineering when the risk of unsatisfactory outcome and rework of project results shall be low. Today, however, shared understanding is used mostly in an unreflected, ad-hoc way. This affects the quality of the engineered software solutions and generates re-work once the quality problems are discovered. In this article, we investigate the role, value, and usage of shared understanding in software engineering. We contribute a reflected analysis of the problem, in particular of how to rely on shared understanding that is implicit, rather than explicit. After an overview of the state of the art we discuss forms and value of shared understanding in software engineering, survey enablers and obstacles, compile existing practices for dealing with shared understanding, and present a roadmap for improving knowledge and practice in this area.
|
|
| 6. |
|
|
| 7. |
- Seyff, Norbert, et al.
(author)
-
End-user driven feedback prioritization
- 2017
-
In: CEUR Workshop Proceedings. - : CEUR-WS.
-
Conference paper (peer-reviewed)abstract
- End-user feedback is becoming more important for the evolution of software systems. There exist various communication channels for end-users (app stores, social networks) which allow them to express their experiences and requirements regarding a software application. End-users communicate a large amount of feedback via these channels which leads to open issues regarding the use of end-user feedback for software development, maintenance and evolution. This includes investigating how to identify relevant feedback scattered across different feedback channels and how to determine the priority of the feedback issues communicated. In this research preview paper, we discuss ideas for enduser driven feedback prioritization. © Copyright 2017 for this paper by its authors.
|
|
