Tracing the Implementation of Non-Functional Requirements

Bode, Stephan; Riebisch, Matthias

doi:10.4018/978-1-60566-794-2.ch001

Cited by 2 publications

(2 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As the previous studies show, the challenge of converting soft goals into design choices remains generally unsolved. The current techniques cannot be used to analyse people's emotional goals and incorporate them into design parameters Bode and Riebisch (2011); Xu et al (2006).…”

Section: Emotional Goals In Software Engineering Domainmentioning

confidence: 99%

Emotionalism Within People-Oriented Software Design

Sherkat

Miller

Mendoza

et al. 2021

Front. Comput. Sci.

View full text Add to dashboard Cite

In designing most software applications, much effort is placed upon the functional goals, making a software system useful. However, the failure to consider emotional goals, which make a software system pleasurable to use, can result in disappointment and system rejection even if utilitarian goals are well implemented. Although several studies have emphasised the importance of people’s emotional goals in developing software, there is little advice on how to address these goals in the software system development process. This paper bridges the gap between emotional goals elicitation and the software system design process by proposing a novel technique entitled the Emotional Goal Systematic Analysis Technique (EG-SAT) to systematically analyse people’s emotional goals in cooperation with functional and quality goals. EG-SAT allows in-depth analysis of emotional goals to build a software system and provides a visual notation for representing the analysis, facilitating communication and documentation. EG-SAT provides traceability of emotional goals in system design by connecting the emotional goals to functional and quality goals. To demonstrate the method in use, a two-part evaluation is conducted. First, EG-SAT is used to analyse the emotional goals of potential users of a mobile learning application that provides information about low carbon living for tradespeople and professionals in the building industry in Australia. The results of using EG-SAT in this case study are compared with a professionally developed baseline. Second, we ran a semi-controlled experiment in which 12 participants were asked to apply EG-SAT and another technique to our case study. The outcomes show that EG-SAT helped participants analyse emotional goals and gain valuable insights about the functional and non-functional goals for addressing people’s emotional goals. The key novelty of the EG-SAT is in proposing an easy to learn and easy to use technique that helps system analysts gain insights on how to address people’s emotional goals. Furthermore, the EG-SAT enables system analysts to convert emotional goals to traditional functional and non-functional goals that existing software engineering methodologies can analyse without demanding excessive effort.

show abstract

Section: Emotional Goals In Software Engineering Domainmentioning

confidence: 99%

Emotionalism Within People-Oriented Software Design

Sherkat

Miller

Mendoza

et al. 2021

Front. Comput. Sci.

View full text Add to dashboard Cite

show abstract

“…The mapping is implemented as a layered structure of a catalogue, which we call Goal Solution Scheme (GSS). It has been introduced and discussed with a forward engineering perspective and different quality goals in earlier works [4,7,36]. In the paper we extend the scheme by a reengineering perspective to widen its application for evolution.…”

Section: Introductionmentioning

confidence: 98%

Problem-solution mapping for forward and reengineering on architectural level

Riebisch

Bode

Brcina

2011

Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th Annual ERCIM Workshop on Softwar

Self Cite

View full text Add to dashboard Cite

Software architectures play a key role for the development and evolution of software systems because they have to enable their quality properties such as scalability, flexibility, and security. Software architectural decisions represent a transition from problem space with quality goals and requirements on one side to solution space with technical solutions on the other side. Technical solutions are reusable elements for the work of the architect as for example patterns, styles, frameworks and building blocks. For long-term evolution of the systems, an explicit mapping between goals and solutions is helpful for expressing design knowledge and fundamental decisions. Such a mapping has to bridge between the fields of requirements engineering, software architectural design, and software quality thus enabling reuse. In this paper the Goal Solution Scheme is discussed, which maps quality goals and goal refinements to architectural principles and solutions. The paper extends the approach from the previously discussed forward engineering to re-engineering activities thus covering evolutionary development processes. The evaluation of the approach has been performed in several case studies and projects including a large industrial one.

show abstract

Tracing the Implementation of Non-Functional Requirements

Cited by 2 publications

References 29 publications

Emotionalism Within People-Oriented Software Design

Emotionalism Within People-Oriented Software Design

Problem-solution mapping for forward and reengineering on architectural level

Contact Info

Product

Resources

About