Abstract. The paper investigates a formal approach to the verification of non functional software requirements, e.g. portability, time and space efficiency, dependability/robustness. The key-idea is the notion of observable, i.e., an abstraction of the concrete semantics when focusing on a behavioral property of interest. By applying an abstract interpretationbased static analysis of the source program, and by a suitable choice of abstract domains, it is possible to design formal and effective tools for non-functional requirements validation.
An important aspect of the requirements engineering process is the specification of traceable, unamb...
Software impacts almost every aspects of modern society. Software development process is a coherent ...
In order to contribute to the software reliability problem, tools have beend esigned inord er to ana...
The paper investigates a formal approach to the verification of non functional software requirements...
This chapter investigates a formal approach to the verification of non-functional software requireme...
This paper presents the framework for the creation of various domain-specific languages for verifica...
Abstract: The norm ISO-26262 aims at ascertaining the functional safety of Automo-tive Electric/Elec...
Abstract Identification of non-functional requirements is important for successful development and d...
Abstract. Non-functional requirements (NFRs) have been the focus of research in Requirements Enginee...
Safety, reliability, reusability, and portability are among the most prominent nonfunctional require...
In model-based design verification, software models are checked against functional and nonfunctional...
Requirements engineering is the first activity in engineering a softwarebased product. Making mistak...
Although the term ‘non-functional requirement’ has been in use for more than 20 years, there is stil...
Abstract—We propose a modeling language for non-functional requirements (NFRs) that views NFRs as re...
Non-functional requirements (NFRs) are rarely taken in account in most software development processe...
An important aspect of the requirements engineering process is the specification of traceable, unamb...
Software impacts almost every aspects of modern society. Software development process is a coherent ...
In order to contribute to the software reliability problem, tools have beend esigned inord er to ana...
The paper investigates a formal approach to the verification of non functional software requirements...
This chapter investigates a formal approach to the verification of non-functional software requireme...
This paper presents the framework for the creation of various domain-specific languages for verifica...
Abstract: The norm ISO-26262 aims at ascertaining the functional safety of Automo-tive Electric/Elec...
Abstract Identification of non-functional requirements is important for successful development and d...
Abstract. Non-functional requirements (NFRs) have been the focus of research in Requirements Enginee...
Safety, reliability, reusability, and portability are among the most prominent nonfunctional require...
In model-based design verification, software models are checked against functional and nonfunctional...
Requirements engineering is the first activity in engineering a softwarebased product. Making mistak...
Although the term ‘non-functional requirement’ has been in use for more than 20 years, there is stil...
Abstract—We propose a modeling language for non-functional requirements (NFRs) that views NFRs as re...
Non-functional requirements (NFRs) are rarely taken in account in most software development processe...
An important aspect of the requirements engineering process is the specification of traceable, unamb...
Software impacts almost every aspects of modern society. Software development process is a coherent ...
In order to contribute to the software reliability problem, tools have beend esigned inord er to ana...