Requirements for Bibliographic Records F unctional Requirements for Bibliographic Records (FRBR) [1], a report developed by the IFLA Study Group on the functional requirements for bibliographic records, has been discussed and explored for nearly a decade. FRBR offers a new perspective on how to create and relate records about information packages for more effective support of user information t...

A model of requirements determination as the process of establishing visions in context explains how both new ideas and existing habits influence diversity in a family of information systems applications. Visions are operationalized as non-functional requirements which are broken down according to constraints imposed by context, and traded off against other non-functional requirements. Context ...

Today’s companies are increasingly being challenged to develop platform-based product families to increase variety of products, while keeping production costs low. In order to provide effective platform-based method and systematically analyzing the customer needs on product design, the functional requirements are classified into basic functional requirements, expectable functional requirements ...

Non-Functional Requirements (NFR) are subjective, interactive and relative, thus realizing the need for particular NFR is by itself a challenge. Furthermore understanding what the software must implement in order to cope with these needs may prove to be an even more challenging task. One way of addressing the need for help on NFR elicitation is the use of catalogues. However, it is not clear ho...

Requirement analyses have a deep impact on software engineering. Requirement as the initial phase in the software development is a continuous client-centric process for the successful Agile software implementation. System Requirements for implementation are classified as Functional and Non-functional requirement. This paper represents different Function and Non-functional requirement elicitatio...

Background: Determining quality requirements and quality dimensions is one of the most reliable ways of providing high quality services. The objective of the present study was to investigate the association between quality requirements and quality dimensions according to the points of view of physicians, nurses, and patients. Materials and Methods: This descriptive study was carried out in h...

Although the System Requirement Specification, as a first formal and detailed document, is the base for the software project in classic software methodologies, there is a noticeable problem of assuring the completeness of this document. The lack of its completeness causes uncertainty of the project foundations. This was one of motivations for agile methodologies – if the SRS cannot be easily va...

Decision Support System (DSS) are interactive software systems that are built to assist the management of an organization in the decision making process when faced with nonroutine problems in a specific application domain. Non-functional requirements (NFRs) for a DSS deal with the desirable qualities and restrictions that the DSS functionalities must satisfy. Unlike the functional requirements,...

The elicitation of security requirements (SRs) is a crucial issue to develop secure information systems of high quality. Although we have several methods mainly for functional requirements such as goal-oriented methods and use case modeling, most of them do not provide sufficient supports to identify threats, security objectives and security functions. Security functions are closely related to ...

In the 52-page document, we describe our approach to the Software Requirements Specification of the IUfA's UUIS prototype. This includes the overall system description, functional requirements, non-functional requirements, use cases, the corresponding data dictionary for all entities involved, mock user interface (UI) design, and the overall projected cost estimate. The design specification of ...