Dealing with NFRs for Smart-Phone Applications: A Goal-Oriented Approach

Mehta, R. Vasanth Kumar; Wang, Hongyuan; Chung, Lawrence

doi:10.1007/978-3-642-30460-6_8

Cited by 5 publications

(4 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…First, similar to NFR [5], [24] and other works e.g [13], we acknowledge that committing to a design decision too early may result in some stakeholders' solutions being discarded, making their views irrelevant. However, a key contribution of this work compared with other work is that it further encourages stakeholder involvement by facilitating the inclusion of all key stakeholders in the modelling and analysis of the system, not just the elicitation.…”

Section: Requirements Elicitation and Analysismentioning

confidence: 66%

Requirements Elicitation and Specification Using the Agent Paradigm: The Case Study of an Aircraft Turnaround Simulator

Miller

Sterling

et al. 2014

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

In this paper, we describe research results arising from a technology transfer exercise on agent-oriented requirements engineering with an industry partner. We introduce two improvements to the state-of-the-art in agent-oriented requirements engineering, designed to mitigate two problems experienced by ourselves and our industry partner: (1) the lack of systematic methods for agent-oriented requirements elicitation and modelling; and (2) the lack of prescribed deliverables in agent-oriented requirements engineering. We discuss the application of our new approach to an aircraft turnaround simulator built in conjunction with our industry partner, and show how agent-oriented models can be derived and used to construct a complete requirements package. We evaluate this by having three independent people design and implement prototypes of the aircraft turnaround simulator, and comparing the three prototypes. Our evaluation indicates that our approach is effective at delivering correct, complete, and consistent requirements that satisfy the stakeholders, and can be used in a repeatable manner to produce designs and implementations. We discuss lessons learnt from applying this approach.

show abstract

Section: Requirements Elicitation and Analysismentioning

confidence: 66%

Requirements Elicitation and Specification Using the Agent Paradigm: The Case Study of an Aircraft Turnaround Simulator

Miller

Sterling

et al. 2014

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…They introduced the concept of "softgoal" to denote an ill-defined goal, and introduced the Softgoal Interdependency Graph (SIG) to represent whether a design decision contributed positively or negatively to satisfying a particular goal or requirement, under the architect or developer's perspective. Other authors have adapted and discovered new uses for the NFR Framework [17,18,16,13].…”

Section: Related Workmentioning

confidence: 99%

“…Finally, Mehta et al applied the NFR Framework to analyze smartphone applications. They proposed a goal-oriented approach to explore and select alternatives to satisfy NFRs specially for the particular characteristics of smartphones [13].…”

Section: Related Workmentioning

confidence: 99%

Tailoring the NFR Framework for Measuring Software Ecosystems Health

Amorim

Andrade²,

McGregor

et al. 2018

Anais Do WER18 - Workshop Em Engenharia De Requisitos

View full text Add to dashboard Cite

A healthy software ecosystem is capable of maintaining productivity and attractiveness, even in the face of problems and disruptions. Some studies have used software metrics to measure the health of a software ecosystem; however, there is little agreement on how to measure those aspects related to software architecture nor how to weigh their influence on the health state of the ecosystem. This paper introduces an approach to measuring and assessing the state of a software ecosystem's health that is aware of the architectural practices used. The approach uses a variation of the softgoal interdependence graph belonging to NFR (Non-Functional Requirements) framework on goal modeling. The key idea is to model and estimate influences of architectural practices on the health indicators. This research carried out an exploratory case study in the KDE ecosystem. KDE architectural practices were identified and analyzed with the support of our proposed practice-aware approach. The findings present the measurable influences that can be used to support decision-making processes related to architectural practices.

show abstract

“…The Reference Model emphasizes that the requirements are satisfied by the collaboration between the user and the events in its environment, hence the term collaborative system. A previous study describes the importance of comprehensively identifying the key NFRs (Non-Functional Requirements) and appropriately handling them [10]. For example, with apps such as Theia, a smartphone app for helping blind people navigate indoors, there is always chance for the user (blind person) getting hurt, if risks, which are related to user goals, e.g., safety, reliability, timeliness, etc.…”

Section: Introductionmentioning

confidence: 99%

Identifying Risks and Risk Mitigation Strategies for Collaborative Systems during Requirements Engineering: A Goal-Oriented Approach (S)

Kolluri,

Hill,

Chung

2023

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

If risks are not identified, they are unlikely to be addressed, possibly resulting in undesirable consequences, such as fatal accidents or even loss of human lives. Furthermore, risks should be considered not only in terms of system behavior but also events occurring in the system environment -i.e., in a collaborative setting in which the system and its environment work together towards certain goals the system is intended to help achieve. In this paper, we present a goal-oriented risk analysis framework, Murphy+G, in which non-functional requirements (hereafter, NFRs) are treated as softgoals to be achieved and systematically addressed in terms of both the system and its environment during requirements engineering, by adopting what is called the Reference Model. A study of a smartphone app, Theia, which is intended to help blind people navigate indoors, is used for the purpose of both illustration and experimentation. In this study, NFRs (e.g., safety, reliability, timeliness, etc.) are treated as softgoals, and risks (e.g., fall down, injury, etc.) are identified, along with risk-mitigation strategies for both the system and its environment, with the help of an activity-oriented ontology. To see both the strengths and weaknesses of Murphy+G, a systematic methodology for risk analysis for collaborative systems, a controlled experiment has been carried out, in terms of three different versions of Theia implementations. Feedback from students show improvements on the accuracy of the risk analysis and the risk mitigation strategies devised, as well as enhanced users' experience with respect to increased confidence in navigating indoors, in a safe, timely, and reliable manner.

show abstract

Dealing with NFRs for Smart-Phone Applications: A Goal-Oriented Approach

Cited by 5 publications

References 10 publications

Requirements Elicitation and Specification Using the Agent Paradigm: The Case Study of an Aircraft Turnaround Simulator

Requirements Elicitation and Specification Using the Agent Paradigm: The Case Study of an Aircraft Turnaround Simulator

Tailoring the NFR Framework for Measuring Software Ecosystems Health

Identifying Risks and Risk Mitigation Strategies for Collaborative Systems during Requirements Engineering: A Goal-Oriented Approach (S)

Contact Info

Product

Resources

About