Modeling Web Services by Iterative Reformulation of Functional and Non-Functional Requirements [PDF]
. We propose an approach for incremental modeling of composite Web services. The technique takes into consideration both the functional and nonfunctional requirements of the composition.
B. Benatallah +10 more
core +2 more sources
Non-Functional Requirements Elicitation
Non-Functional requirements elicitation is one of the most important activity in requirements engineering. Non-functional requirements define the quality attributes of software system. If this analysis is not done properly, it may cause for problems in further phases that in turn may lead to failure of the software.
openaire +1 more source
Designing with Non-Functional Requirements [PDF]
A major class of software and systems engineering projects are critically dependent upon the attributes of the final system as much upon its functionality. These attributes reflect the quality of the design and implementation of the product, yet in most circumstances, they are treated in a very loose and haphazard fashion during the system development.
Colin J. Theaker, Jenny Whitworth
openaire +1 more source
Exploiting a Goal-Decomposition Technique to Prioritize Non-functional Requirements [PDF]
Business stakeholders need to have clear and realistic goals if they want to meet commitments in application development. As a consequence, at early stages they prioritize requirements. However, requirements do change.
Daneva, M. +4 more
core +1 more source
A MDE-based process for the design, implementation and validation of safety critical systems [PDF]
Distributed Real-Time Embedded (DRE) systems have critical requirements that need to be verified. They are either related to functional (e.g. stability of a furnace controller) or non-functional (e.g. meeting deadlines) aspects. Model-Driven Engineering (
De Niz, Diosisio +3 more
core +1 more source
Non-functional Requirements in Architectural Decision Making
Software architects often must work with incomplete or ill-specified non-functional requirements (NFRs) and use them to make decisions. Through this process, existing NFRs are refined or modified and new ones emerge. Although much research has centered on how software architects treat NFRs, no empirical studies have investigated the state of the ...
Ameller, David +3 more
openaire +4 more sources
What Works Better? A Study of Classifying Requirements
Classifying requirements into functional requirements (FR) and non-functional ones (NFR) is an important task in requirements engineering. However, automated classification of requirements written in natural language is not straightforward, due to the ...
Abad, Zahra Shakeri Hossein +5 more
core +1 more source
Model2Roo: A Model Driven Approach for Web Application Development based on the Eclipse Modeling Framework and Spring Roo [PDF]
International audienceInherent complexity in web application development is continually increasing due to changes in both functional and non-functional requirements, as well as to technological changes like new programming languages, tools, frameworks ...
Castrejon-Castillo, Juan-Carlos +2 more
core +3 more sources
Embracing Localization Inaccuracy: A Case Study [PDF]
In recent years, indoor localization has become a hot research topic with some sophisticated solutions reaching accuracy on the order of ten centimeters.
Murphy, Amy L. +2 more
core +1 more source
How Architects See Non-Functional Requirements: Beware of Modifiability [PDF]
This paper presents the analysis and key findings of a survey about dealing with non-functional requirements (NFRs) among architects. We find that, as long as the architect is aware of the importance of NFRs, they do not adversely affect project success, with one exception: highly business critical modifiability tends to be detrimental to project ...
Poort, Eltjo R. +3 more
openaire +2 more sources

