Results 271 to 280 of about 2,062,977 (296)

Extending UML with Non-functional Requirements Modelling

2011
Non-Functional Requirements (NFR) have been for too long overlooked during the development of software systems, leading in numerous cases to failure, an over budget or even cancellation of projects. In this paper, we propose a solution to integrate the modelling of NFRs into the UML diagrams.
Krishna, Aneesh, Gregoriades, Andreas
openaire   +2 more sources

Automated testing of non-functional requirements

Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications, 2008
We present an open-source toolkit that enables automated testing of non-functional requirements. Our toolkit offers an alternative to current approaches (e.g. testing suites) by being lightweight, flexible, free and by reusing libraries and executables found on common operating systems and platforms. The toolkit provides developers and project managers
Kristoffer Dyrkorn, Frank Wathne
openaire   +1 more source

Explainability as a Non-Functional Requirement

2019 IEEE 27th International Requirements Engineering Conference (RE), 2019
Recent research efforts strive to aid in designing explainable systems. Nevertheless, a systematic and overarching approach to ensure explainability by design is still missing. Often it is not even clear what precisely is meant when demanding explainability.
Kohl, Maximilian A., Baum, Kevin, Langer, Markus, Oster, Daniel, Speith, Timo, Bohlender, Dimitri   +5 more
openaire   +1 more source

On non-functional requirements: A survey

2012 IEEE Students' Conference on Electrical, Electronics and Computer Science, 2012
In this paper we give the details on Non-Functional Requirements and its importance in various fields. We also investigate the effect of working out for the Non-functional Requirements which leads to the discovery of new Functional Requirements. After the coding phase in the Software Development Life Cycle (SDLC), during the process of articulating the
Vikas Bajpai, Ravi Prakash Gorthi
openaire   +1 more source

Introduction to Non-functional Requirements

2015
One of the most easily understood tasks during any systems design endeavor is to define the systems functional requirements. The functional requirements are a direct extension of the stakeholder’s purpose for the systems and the goals and objectives that satisfy them.
openaire   +1 more source

Non-Functional Requirements and UML Stereotypes

2005
In Nuseibeh and Easterbrook (2000), an overview of the field of software and systems requirements engineering is presented. Therein is highlighted some key open-research issues for the future of the Requirements Engineering (RE). Some of the major challenges mentioned there, are related with the necessity of richer models for capturing and analyzing ...
Guadalupe Salazar-Zarate, Pere Botella
openaire   +1 more source

Introducing Non-functional Requirements in UML

2011
This chapter introduces an approach concerned with the non-functional features of software systems. The specific objectives of the research focus on the possibility of developing mechanisms to capture non-functional information in the development of software systems in a similar manner to its counterpart, the functional information.
Guadalupe Salazar-Zarate, Pere Botella, Ajantha Dahanayake   +2 more
openaire   +1 more source

Automatically classifying non-functional requirements using deep neural network

Pattern Recognition, 2022
bing li
exaly  

Automatic clustering of non-functional requirements

2004
Achieving requirement quality is a crucial factor for the quality of the final product. Requirements quality depends also on the way functional and non-functional requirements are organized in the requirement documents. In fact, it is very important to distinguish these two types of requirements in order to guarantee traceability, completeness and lack
Fabbrini F, Fusani M, Gnesi S, Lami G
openaire   +2 more sources

Functional Versus Non-Functional Requirements Analysis

1994
Specification languages are usually intended to serve as the foundation for a streamlined software development process in which only one complete formal description of the system is written [13]. Other representations (e.g. implementation code) consistent and correct with respect to the requirements specifications should be generated automatically from
openaire   +1 more source