| 1. |
- Bjarnason, Elizabeth, et al.
(författare)
-
Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map
- 2013
-
Ingår i: Lectur Notes in Computer Science/ Requirements Engineering: Foundation for Software Quality. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 9783642374210 ; 7830, s. 292-307
-
Konferensbidrag (refereegranskat)abstract
- [Context and Motivation] The main role of requirements engineering (RE) is to guide development projects towards implementing products that will appeal to customers. To effectively achieve this RE needs to be coordinated with and clearly communicated to the later software development activities. [Question/Problem] Communication gaps between RE and other development activities reduce coordination and alignment, and can lead to project delays and failure to meet customer needs. [Principle ideas/results] The main hypothesis is that coordination is enhanced by proximity to RE roles and artefacts, and that distances to later activities increase the effort needed to align requirements with other development work. Thirteen RE-related distances have been identified through a systematic map of existing research. [Contribution] Reported dis-tances are mapped according to research type, RE activity and later software development activities. The results provide an overview of RE distances and can be used a basis for defining a theoretical framework.
|
|
| 2. |
- Bjarnason, Elizabeth, et al.
(författare)
-
Reflecting on Evidence-Based Timelines
- 2014
-
Ingår i: IEEE Software. - 0740-7459 .- 1937-4194. ; 31:4, s. 37-43
-
Tidskriftsartikel (refereegranskat)abstract
- Project retrospectives can be powerful tools for project teams to collectively identify communication gaps and practices to improve for future projects. However, even if project members take the time for a retrospective, it can be hard to correctly remember and jointly discuss past events in a constructive way. Fact-based timelines that visualize a project's events offer a possible solution.
|
|
| 3. |
- Bjarnason, Elizabeth, et al.
(författare)
-
Variations on the Evidence-Based Timeline Retrospective Method A Comparison of Two Cases
- 2013
-
Ingår i: 39th Euromicro Conference Series on Software Engineering and Advanced Applications. ; 2013, s. 37-44
-
Konferensbidrag (refereegranskat)abstract
- Project retrospectives can be a powerful tool for process improvement through obtaining new insights. However pure experience-based reflections may lead to incorrect conclusions. Our method, evidence-based timeline retrospectives (EBTR), mitigates this risk by providing a pre-generated timeline that visualises project history based on evidence rather than relying on subjective opinions and biased memories. Through a comparative study of two cases, a set of variation points has been evaluated. The variation points enable configuring the EBTR method to different contexts and retrospective goals. The results indicate that by selecting certain variations the EBTR method can be configured to support either wide assessments (e.g. the overall impact of a new process) or assessments of a specific process area. For example, through using open or semi-structured discussions, or by varying the applied timeline technique.
|
|
| 4. |
- Callele, David, et al.
(författare)
-
Risk Identification on the Interface Between Business Case and Requirements
- 2013
-
Ingår i: Requirements Engineering: Foundation for Software Quality / Lecture Notes in Computer Science. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1611-3349 .- 0302-9743. - 9783642374210 ; 7830, s. 253-268
-
Konferensbidrag (refereegranskat)abstract
- Motivation: The requirements engineering (RE) research community is aware of the importance of performing feasibility studies before starting requirements elicitation. Unfortunately, projects still frequently fail to achieve commercial success, responsibility is often unknown, and requirements engineers may be deemed responsible for mistakes made by others. Problem: There is neither empirical evidence available from a post-mortem risk analysis for projects that performed adequate RE but commercially failed nor guidance for requirements engineers on validating a business case analysis to mitigate this risk. Principal idea: By performing a post-mortem analysis of software development projects that failed to achieve commercial success, we investigate the root causes for the failures and, in most cases, trace the causes back to business case issues. We identify risk areas and provide practical due diligence guidance to the practitioner. Contribution: This exploratory case study performs an in-depth review of a detailed post-mortem analysis of three software development projects performed over a 2.5 year period. Each of the analyzed projects failed to make the expected transition to commercialization despite using appropriate RE techniques and achieving satisfactory deliverables. The analysis identifies risk factors that the RE practitioner should consider and we provide a checklist for RE practitioners to use when checking for these risks in an antecedent business case as part of their due diligence. A low-cost commercial viability assessment technique, employing Fermi approximation, is provided to equip the RE practitioner with a risk mitigation tool in the absence of business analyst resources.
|
|
| 5. |
|
|
| 6. |
- Olsson, Thomas, et al.
(författare)
-
Non-functional requirements in industry : Three case studies adopting an experience-based NFR method
- 2005
-
Ingår i: Proceedings of the IEEE International Conference on Requirements Engineering 2005. - : IEEE Computer Society. ; , s. 373-382
-
Konferensbidrag (refereegranskat)abstract
- Non-functional characteristics of products can be essential for business success and are a key differentiator between a company and its competitors. This paper presents the application of a systematic, experience-based method to elicit, document, and analyze non-functional requirements. The objective of the method is to achieve a minimal and sufficient set of measurable and traceable non-functional requirements. The method gives clear guidance for the requirements elicitation, using workshops for capturing the important quality aspects and eliciting the non-functional requirements. This paper shows its application in three different settings, reporting the experience and lessons learned from industrial case studies that applied our NFR method. As the case studies were applied in different domains and performed with companies of various maturity, and since different quality attributes were considered, a set of interesting results has emerged. Therefore, each case study tells its own story about how the elicitation of NFR in industry can work. The paper discusses the different settings and gives a comparison of the different lessons we learned from the case studies.
|
|
| 7. |
|
|
| 8. |
- Regnell, Björn, et al.
(författare)
-
reqT.org – Towards a Semi-Formal, Open and Scalable Requirements Modeling Tool
- 2013
-
Ingår i: Lecture Notes in Computer Science. - 9783642374210 - 9783642374227 ; 7830, s. 112-118
-
Konferensbidrag (refereegranskat)abstract
- [Context and motivation] This research preview presents ongoing work on a free software requirements modeling tool called reqT that is developed in an educational context. [Question/problem] The work aims to engage computer science students in Requirements Engineering (RE) through a tool that captures essential RE concepts in executable code. [Principal ideas] Requirements are modeled using an internal DSL in the Scala programming language that blends natural language strings with a graph-oriented formalism. [Contribution] The metamodel of reqT and its main features are presented and modeling examples are provided together with a discussion on initial experiences from student projects, limitations and directions of further research.
|
|
