Search results
Results from the WOW.Com Content Network
Functional Requirements for Bibliographic Records (FRBR / ˈ f ɜːr b ər /) is a conceptual entity–relationship model developed by the International Federation of Library Associations and Institutions (IFLA) that relates user tasks of retrieval and access in online library catalogues and bibliographic databases from a user’s perspective.
Generally, functional requirements are expressed in the form "system must do <requirement>," while non-functional requirements take the form "system shall be <requirement>." [3] The plan for implementing functional requirements is detailed in the system design, whereas non-functional requirements are detailed in the system architecture. [4] [5]
A software requirements specification (SRS) is a description of a software system to be developed.It is modeled after the business requirements specification.The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.
A functional specification is the more technical response to a matching requirements document, e.g. the Product Requirements Document "PRD" [citation needed]. Thus it picks up the results of the requirements analysis stage. On more complex systems multiple levels of functional specifications will typically nest to each other, e.g. on the system ...
It unifies the models of Functional Requirements for Bibliographic Records (FRBR), Functional Requirements for Authority Data (FRAD) and Functional Requirements for Subject Authority Data (FRSAD). [1] The IFLA LRM is intended to be used as the basis of cataloguing rules and implementing bibliographic information systems. [2]
The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down and detailed in a Functional Specification (sometimes also called Technical Requirements Document). The form of the PRD will vary from project to project and depends, for example, on the approach to project implementation.
Requirements Triage or prioritization of requirements is another activity which often follows analysis. [4] This relates to Agile software development in the planning phase, e.g. by Planning poker, however it might not be the same depending on the context and nature of the project and requirements or product/service that is being built.
Functional Requirements for Authority Data (FRAD), formerly known as Functional Requirements for Authority Records (FRAR), is a conceptual entity-relationship model developed by the International Federation of Library Associations and Institutions (IFLA) for relating the data that are recorded in library authority records to the needs of the users of those records and facilitate and sharing of ...