functional requirements

Also found in: Dictionary, Wikipedia.

functional requirements

What a system should be able to do, the functions it should perform.

This term is used at both the user requirements analysis and software requirements specifications phases in the software life-cycle.

An example of a non-functional requirement is an initialisation sequence incorporated into the software that is specific to a given customer.
This article is provided by FOLDOC - Free Online Dictionary of Computing (

functional specification

The blueprint for the design of a system. With regard to a business information system, the specification provides the documentation for the database structure, the human and machine procedures, and all the input, processing and output detail for each data entry, query, update and report program. See information requirements.

information requirements

The information needed to support a business or other activity. Systems analysts turn information requirements (the what and when) into functional specifications (the how) of an information system.

Details and Summaries
Requirements are typically defined as lists of detailed transactions, such as orders and purchases, as well as summarized data from master records, such as customers, vendors and employees. How frequently this information is made available is also part of the requirement.

A Group of Data Elements
The actual information is a collection of data elements that are obtained by running query and report programs against a particular database or group of databases. The data and information that are stored in the databases in the first place are also derived from the information requirements. See functional specification and desirement.

Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
A review of business requirements-engineering literature highlights three general requirements-engineering processes used in the software development process: functional requirement statements (Institute for Electrical and Electronics Engineers [IEEE], 1998, p.
Functional requirements and implicit constraints are gathered in raw form.
Non Functional Requirements specify how a system should be rather than what a system should do.
They also claimed that a clinical domain library could help them to elicit accurate functional requirements. The domain library should also have e several functions that can be used to facilitate the elicitation of accurate functional requirements.
Although these methods have contributed a lot to software development process and can be used with both kinds of requirements separately (these methods have mostly been adopted just with functional requirements [14, 21]), there is a need for proposing an approach in which prioritization of functional and nonfunctional requirements could be integrated.
Considering the link between customer needs and product quality characteristics, the FRs for product are classified into basic functional requirements, expectable functional requirements and adjunctive functional requirements based on the model of customer satisfaction presented by Kano, as shown in figure 1.
(6.) IFLA Study Group on the Functional Requirements for Bibliographic Records.
Sixteen functional requirements were discussed in five categories: philosophy, human behavior, rule base social system, strategy system and hardware, with the reference to the sixteen consumer requirements identified: info access limitation, data authenticity, data and backup recovery, device and system configuration information, personal key exchange, trusted network, interoperability and security, gap analysis, reliable data storage system, cyber security guidelines, law enforcement, improved wireless technology, controlled power consumption, protect secret, cryptographic protocols and encryption policies, as in Table III.
Submarines in order to satisfy the functional requirements for acoustic intercept capability in the Va., Class SSN.
Ann Arbor, Mich.-based Health Level Seven (HL7) announced it has passed the healthcare industry's first ANSI-approved standard that specifies the basic functional requirements for child healthcare in an electronic health record (EHR) system.

Full browser ?