The COSMIC-FFP is a standard method that has been proven effective for measuring the functional size of business applications and realtime software systems from their functional user requirements specification. Despite of this, the methods based on COSMIC-FFP usually require a mapping between the concepts in the requirements specification and their own terms and do not take into account non-fun...

In traditional software engineering research and practice, requirements are classified either as functional or non-functional. Functional requirements consist of all functions the system-to-be ought to support, and have been modeled in terms of box-and-arrow diagrams in the spirit of SADT. Non-functional requirements include desired software qualities for the system-to-be and have been describe...

[Context and motivation] The starting point for software development is usually the system requirements. The requirements, especially non-functional requirements specified in a document are often incomplete and inconsistent with the initial user needs and expectations. [Question/problem] Experience at Siemens showed us that programmers working on software development often have trouble interpre...

Self-Adaptive Systems modify their behavior at run-time in response to changing environmental conditions. For these systems, Non-Functional Requirements play an important role, and one has to identify as early as possible the requirements that are adaptable. We propose an integrated approach for modeling and verifying the requirements of Self-Adaptive Systems using Model Driven Engineering tech...

The objective of this paper is to present an environment for the management of functional and non-functional requirements in systems project, developed using the XML (Extensible Markup Language) standard. This environment receives as inputs two entry structures for software requirements modelling: the UML ́s Use Case diagram, which describes functional requirements; and the I* framework used by ...

This paper addresses the use of goals to extract non-functional requirements from policy statements. Goals are important precursors to software requirements, but the process of abstracting them from security and policy policies has not been thoroughly researched. We present a summary of a goal-based approach for extracting standard security and privacy requirements from policy statements and il...

Non-functional requirements are critical in web engineering applications, but often ignored. Usually, these are articulated as statements of objectives, as opposed to prepositional assertions. A key challenge in dealing with objectives is that there is no obvious means of deciding when they are satisfied. In effect, these objectives are never fully satisfied, but satisficed to varying degrees. ...

Non-functional requirements significantly affect and determine the quality of software systems. In this paper it is shown how non-functional requirements are modelled in MIKE, an approach to the development of knowledge-based systems. A semi-formal hypermedia-based model is used to describe the results of the elicitation and interpretation of non-functional requirements and their relationships....

Due to constant pressure on software development team for development of workable software at a fast pace, the focus of the development team has always been on the functional requirements. As such, the identification and implementation of nonfunctional requirements, especially, security which otherwise is considered as a time consuming and quality providing process has always been neglected. Bu...

this paper describes the extension requirements in use of drip irrigation systems in tehran province. the study was functional (practical) in terms of goal, non-experimental in terms of control on variables, and causality-relational in terms of data collection. data collection method was based on the documentary-library and field study (questionnaire) and statistical population included 547 sam...