Representing NFRs and FRs: A Goal-Oriented and Use Case Driven Approach

Chung, Lawrence; Supakkul, Sam

doi:10.1007/11668855_3

Cited by 28 publications

(12 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some authors have used NFRs in conjunction with a more structured requirements representation notation, e.g., the combination of NFRs with use cases or misuse cases (for example, see [23], [24], [25], [26] and [27]). …”

Section: Representations Of Non-functional Requirementsmentioning

confidence: 99%

On Non-Functional Requirements in Software Engineering

Chung

Leite

2009

Conceptual Modeling: Foundations and Applications

Self Cite

931

578

View full text Add to dashboard Cite

Abstract. Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.

show abstract

Section: Representations Of Non-functional Requirementsmentioning

confidence: 99%

On Non-Functional Requirements in Software Engineering

Chung

Leite

2009

Conceptual Modeling: Foundations and Applications

Self Cite

931

578

View full text Add to dashboard Cite

show abstract

“…To determine satisficeability, design alternatives or decisions (called operationalizing softgoals) are considered; design tradeoffs are analyzed, design rationale is recorded and design choices are made. The entire process is recorded in a "Softgoal Interdependency Graph" (SIG) and then the selected design decisions (operationalizing softgoals) can be used as a framework for architecture and design [8]. Figure 4 depicts a SIG for the Student Friendliness softgoal in the context of our example.…”

Section: Softgoal Interdependency Graphsmentioning

confidence: 99%

“…Softgoal Interdependency Graphs (SIGs) have been intensively used in software engineering for modeling non-functional requirements as "softgoals" to be "satisfied" [7,8]. To determine satisficeability, design alternatives or decisions (called operationalizing softgoals) are considered; design tradeoffs are analyzed, design rationale is recorded and design choices are made.…”

Section: Softgoal Interdependency Graphsmentioning

confidence: 99%

Engineering Accessible Web Applications. An Aspect-Oriented Approach

et al. 2010

View full text Add to dashboard Cite

The development of accessible Web software is complicated for several reasons. Though some of them are technological, the majority are related with the need to compose different and, many times, unrelated design concerns which may be functional as in the case of most of the specific application's requirements, or non-functional such as Accessibility itself. In this paper, we present a novel approach to conceive, design and develop Accessible Web applications in an aspect-oriented manner. In order to reach our goal, we provide some modeling techniques that we specifically developed for handling the nonfunctional, generic and crosscutting characteristics of the Accessibility concerns. Specifically, we have enriched User Interaction Diagrams with integration points, which are used to reason and document Accessibility for activity modeling during user interface design. Then by instantiating a Softgoal Interdependency Graph template with association tables, we work on an abstract interface model (composed by ontology widgets) to obtain a concrete and accessible interface model for the Web application being developed. We use a real application example to illustrate our ideas and point out the advantages of a clear separation of concerns throughout the development life-cycle.

show abstract

“…Aspect-oriented Pattern-based • NFR Representation multi-model [57] • Ontology based Quality modelling [58,59] • NFR use-case Model [60,61] • NFR integration Framework [62] • NFR use cases and scenarios models [8] • NFR Framework [63][64][65][66][67][68][69] • Activity-based quality model [70] • Efficiency use-cases [30] • Ontology-based NFR conceptualization [71] • NFR Traceability model [72] • QRA Framework [73,74] • NFR integration Framework [75,76] • ProcessNFL language [77] • UML Profile [78] • Quality requirements BP framework [79][80][81][82][83][84] • NoFun language [85] Several goal-oriented modelling approaches are proposed to represent the interrelations of different system development viewpoints [57], domain ontology and NFRs [58,59], functional and non-functional requirements [60][61][62], soft-goal interdependencies of NFRs [8,[63][64][65][66][67][68]…”

Section: Goal-orientedmentioning

confidence: 99%

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Hasan

Loucopoulos

Νικολαϊδου

2014

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

LNBIP reports state-of-the-art results in areas related to business information systems and industrial application software development -timely, at a high level, and in both printed and electronic form. The type of material published includes• Proceedings (published in time for the respective event)• Postproceedings (consisting of thoroughly revised and/or extended final papers) • Other edited monographs (such as, for example, project reports or invited volumes) • Tutorials (coherently integrated collections of lectures given at advanced courses, seminars, schools, etc.) • Award-winning or exceptional theses LNBIP is abstracted/indexed in DBLP, EI and Scopus. LNBIP volumes are also submitted for the inclusion in ISI Proceedings.

show abstract

Representing NFRs and FRs: A Goal-Oriented and Use Case Driven Approach

Cited by 28 publications

References 6 publications

On Non-Functional Requirements in Software Engineering

On Non-Functional Requirements in Software Engineering

Engineering Accessible Web Applications. An Aspect-Oriented Approach

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Contact Info

Product

Resources

About