Integrating non-functional requirements into data modeling

Cysneiros, Luiz Marcio; Leite, Julio César Sampaio do Prado

doi:10.1109/isre.1999.777996

Cited by 28 publications

(26 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This work extends a previous one [13] and presents a strategy for dealing with NFRs and how to integrate them into conceptual models. Part of our work was strongly influenced by Chung's work on this subject [3,5,6,14], resulting in a slight adaptation of his NFR graph to be used in earlier stages of software development.…”

Section: Introductionmentioning

confidence: 80%

See 1 more Smart Citation

A Framework for Integrating Non-Functional Requirements into Conceptual Models

Cysneiros

Leite

Neto

2001

Requirements Engineering

View full text Add to dashboard Cite

The development of complex information systems calls for conceptual models that describe aspects beyond entities and activities. In particular, recent research has pointed out that conceptual models need to model goals, in order to capture the intentions which underlie complex situations within an organisational context. This paper focuses on one class of goals, namely nonfunctional requirements (NFR), which need to be captured and analysed from the very early phases of the software development process. The paper presents a framework for integrating NFRs into the ER and OO models. This framework has been validated by two case studies, one of which is very large. The results of the case studies suggest that goal modelling during early phases can lead to a more productive and complete modelling activity.

show abstract

Section: Introductionmentioning

confidence: 80%

“…Both studies point in 3 This sentence is adapted from Mylopoulos ( [13], p. 36). The important aspect is that by making this knowledge to be brought up, we increase our chances of better understanding the problem.…”

Section: Resultsmentioning

confidence: 99%

A Framework for Integrating Non-Functional Requirements into Conceptual Models

Cysneiros

Leite

Neto

2001

Requirements Engineering

View full text Add to dashboard Cite

show abstract

“…Ineffectively dealing with NFRs has led to a series of failures in software development [2], [3], as happened in well-known case of the London Ambulance System [4], where the deactivation of the system right after its deployment was strongly influenced by NFRs noncompliance. Literature [5], [6], [7] has been pointing out the difficulties of dealing with these requirements and showing that errors due to NFRs are the most expensive and difficult to correct. Literature review also shows that, NFRs are often poorly understood and not considered adequately in software development due to the characteristics of NFRs, and difficulties.…”

Section: Introductionmentioning

confidence: 99%

NFRs Model for Nuclear Power Plants

Shafei¹,

Sallam²,

Aref³

2017

IJSEA

View full text Add to dashboard Cite

Requirements analysis phase plays a vital role in drawing the performance and characteristics of critical software systems. As the requirements were global, detailed and complementary as the system was successfully functioning, free of errors and flaws, and adapted to environment dynamicity. In critical systems, such as Nuclear Power Plants (NPPs), implementing software functional requirements (FRs) is not enough to ensure system safety. Non-functional requirements NFRs implementation beside FRs becomes crucial for ensuring such function. NFRs performs other functions that are essentials for system availability, reliability, and dependability. NFRs should be supportive, not precluding to FRs, and keep system complexity and cost as low as possible. To this end, this paper proposes a model for NFRs which have importance in nuclear field based on safety system classification, and graded approach which assign the quality attributes and constraints to a given system based on its importance to safety. This model helps in enhancing the system overall safety without increasing the system complexity and implementation cost without need.

show abstract

“…Literature [7], [15], [11] has been pointing out these requirements as the most expensive and difficult to deal with.…”

Section: Introductionmentioning

confidence: 99%

Nonfunctional requirements: from elicitation to conceptual models

Cysneiros

Leite

2004

IIEEE Trans. Software Eng.

Self Cite

202

102

View full text Add to dashboard Cite

Abstract-Nonfunctional Requirements (NFRs) have been frequently neglected or forgotten in software design. They have been presented as a second or even third class type of requirement, frequently hidden inside notes. We tackle this problem by treating NFRs as first class requirements. We present a process to elicit NFRs, analyze their interdependencies, and trace them to functional conceptual models. We focus our attention on conceptual models expressed using UML (Unified Modeling Language). Extensions to UML are proposed to allow NFRs to be expressed. We will show how to integrate NFRs into the Class, Sequence, and Collaboration Diagrams. We will also show how Use Cases and Scenarios can be adapted to deal with NFRs. This work was used in three case studies and their results suggest that by using our proposal we can improve the quality of the resulting conceptual models.

show abstract

Integrating non-functional requirements into data modeling

Cited by 28 publications

References 17 publications

A Framework for Integrating Non-Functional Requirements into Conceptual Models

A Framework for Integrating Non-Functional Requirements into Conceptual Models

NFRs Model for Nuclear Power Plants

Nonfunctional requirements: from elicitation to conceptual models

Contact Info

Product

Resources

About