information requirements

Also found in: Encyclopedia, Wikipedia.
(redirected from Functional requirements)

information requirements

Those items of information regarding the adversary and the environment that need to be collected and processed in order to meet the intelligence requirements of a commander. See also priority intelligence requirements.
Dictionary of Military and Associated Terms. US Department of Defense 2005.
Mentioned in
References in periodicals archive
"Kurz heat transfer foils are always developed with the customer's application processes, functional requirements, substrates and any other particular needs In mind."
Most of the functional requirements found in the Combined Arms Support Command's GCSS -Army requirements database originated from antiquated software end-user manuals of systems no longer in service.
Nonfunctional requirement (NFR) also known as nonfunctional-concerns [2] refer to global properties and usually to quality of functional requirements. It is generally recognized that NFR are an important and difficult part of the requirement engineering process.
For these domains, which are also called evolutionary domains, the data types and functional requirements are dynamic in nature.
In addition to Functional Requirements (FR), Non-Functional Requirements (NFR) should also be considered while creating a conceptual model.
Based on a survey conducted with 20 respondents it was found that eliciting clinical functional requirements is more difficult than the business requirements.
Functional requirements, which are more specific and come into play once the ECM platform has been chosen, state exactly how the system should be set up and what the system should do relative to all the processes that will be covered in the implementation.
The requirements engineering community has classified the requirements of a software system into two main categories: functional requirements and nonfunctional requirements [8].
of Ljubljana, Slovenia), Marcia Lei Zeng, and Athena Salaba (both Kent State U., Ohio) use the Functional Requirements for Subject Authority Data (FRSAD) model to provide an overview of modeling of aboutness in general and to compare the model with other models that have emerged recently, as well as to demonstrate its applicability for future implementations.
Different customer needs drive the difference of function-structure for product, and the variation of customer needs affect the customization degree of product, so the different product in product family should have the different functional requirements (FRs) which are expressed by corresponding characteristic attributes.
The needs or "User Tasks" were systematically defined in Functional Requirements for Bibliographic Records or, as this report has come to be known, FRBR.
Copyright © 2003-2025 Farlex, Inc Disclaimer
All content on this website, including dictionary, thesaurus, literature, geography, and other reference data is for informational purposes only. This information should not be considered complete, up to date, and is not intended to be used in place of a visit, consultation, or advice of a legal, medical, or any other professional.