Specification of the context in which the system will operate, the purposes of the system, what operations the system must perform, and what quality of service the system must provide in achieving those purposes and rendering those services. A statement of properties that a system shall exhibit or shall not exhibit when completed. Note: requirements are derived from requirements in a many-to-ma...

Requirements Engineering (RE) is getting more attention as it has been recognized as a crucial phase in the development of the software system life cycle. Recent works have made a distinction between early-phase RE and later-phase RE. Early-phases RE activities are typically informal and addresses non-functional requirements. The later-phase RE usually focuses on completeness, consistency, and ...

Requirements engineering (RE) is concerned with the identification of stakeholders' needs concerning a future system, the specification of services and constraints that satisfy these needs, and the assignment of the resulting requirements to agents such as humans, hardware devices, and software components. Functional requirements describe what functions must be provided to satisfy the stakehold...

Distributed database design is a complex process that involves a set of distinct aspects for the accomplishment of an adequate data distribution (Buretta 1997). Many of these aspects correspond to non functional requirements (quality properties or systems restrictions), for example, availability, costs and performance, that are abstract questions. Non functional requirements are normally not ex...