A Non-Functional Requirements Modeling Aided Method Based on Domain Knowledge

2014 ◽  
Vol 36 (1) ◽  
pp. 39-53
Author(s):  
Fei SHAO ◽  
Rong PENG
2016 ◽  
Vol 13 (1) ◽  
pp. 287-308 ◽  
Author(s):  
Zhang Tingting ◽  
Liu Xiaoming ◽  
Wang Zhixue ◽  
Dong Qingchao

A number of problems may arise from architectural requirements modeling, including alignment of it with business strategy, model integration and handling the uncertain and vague information. The paper introduces a method for modeling architectural requirements in a way of ontology-based and capability-oriented requirements elicitation. The requirements can be modeled within a three-layer framework. The Capability Meta-concept Framework is provided at the top level. The domain experts can capture the domain knowledge within the framework, forming the domain ontology at the second level. The domain concepts can be used for extending the UML to produce a domain-specific modeling language. A fuzzy UML is introduced to model the vague and uncertain features of the capability requirements. An algorithm is provided to transform the fuzzy UML models into the fuzzy Description Logics ontology for model verification. A case study is given to demonstrate the applicability of the method.


Author(s):  
Sarah Bouraga ◽  
Ivan Jureta ◽  
Stéphane Faulkner

Online social networks (OSNs) such as Facebook and LinkedIn are now widely used. They count users in the hundreds of millions. This chapter surveys popular social networks in order to present a pattern of recurring functional requirements as well as non-functional requirements, and a model of that pattern in the i* requirements modelling language. The pattern can serve as a starting point for requirements engineering of new OSNs. The authors test their model by applying it to a popular OSN, namely Twitter.


Author(s):  
Juan C. Muñoz-Fernández ◽  
Gabriel Tamura ◽  
Raúl Mazo ◽  
Camille Salinesi

The analysis of self-adaptive systems (SAS) requirements involves addressing uncertainty from several sources. Despite advances in requirements for SAS, uncertainty remains an extremely difficult challenge. In this paper, we propose REFAS, a framework to model the requirements of self-adaptive software systems. Our aim with REFAS is to address and reduce uncertainty and to provide a language with sufficient power of expression to specify the different aspects of self-adaptive systems, relative to functional and non-functional requirements. The REFAS modeling language includes concepts closely related to these kind of requirements and their fulfillment, such as context variables, claims, and soft dependencies. Specifically, the paper´s contribution is twofold. First, REFAS supports different viewpoints and concerns related to requirements modeling, with key associations between them. Moreover, the modeler can define additional models and views by exploiting the REFAS meta-modeling capability, in order to capture additional aspects contributing to reduce uncertainty. Second, REFAS promotes in-depth analysis of all of the modeled concerns with aggregation and association capabilities, especially with context variables. Furthermore, we also define a process that enforces modeling requirements, considering different aspects of uncertainty. We demonstrate the applicability of REFAS by using the VariaMos software tool, which implements the REFAS meta-model, views, and process.


2020 ◽  
Vol 31 (4) ◽  
pp. 449-469
Author(s):  
Prabhu Shankar ◽  
Beshoy Morkos ◽  
Darshan Yadav ◽  
Joshua D. Summers

Abstract This paper explores the formal roles of non-functional requirements’ (NFR) elicitation, definition, and verification in the early stages of an engineering design project. This is performed using a case study conducted at an automotive original equipment manufacturer (OEM) during the design and development of a rear bumper sub-system. The purpose of this exploration is to determine if NFRs should be formalized within requirements modeling scheme. This can capture conceptual design information to identify their impact on other requirements while conducting design changes. The modeling scheme in this paper consists of a sequence of following domains—requirements, functions, working principle, components, design parameters, test measures, and tests—that are mapped to each other using matrices. It is revealed through this case study that non-functional requirements drive much of the design decision-making process and constrain the manner in which the product functionality is realized. Hence, the inclusion of NFRs as a separate and distinct domain in the design process is critical to recognize their significance during design changes. Based on the observations made in the case study, the NFR domain is included in the requirements modeling scheme.


Sign in / Sign up

Export Citation Format

Share Document