Process
A typical functional requirement will contain a unique name and number, a brief summary, and a rationale. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.
The crux of the requirement is the description of the required behavior, which must be clear and readable. The described behavior may come from organizational or business rules, or it may be discovered through elicitation sessions with users, stakeholders, and other experts within the organization. Many requirements may be uncovered during the use case development. When this happens, the requirements analyst may create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known.
Read more about this topic: Functional Requirement
Famous quotes containing the word process:
“Rules and particular inferences alike are justified by being brought into agreement with each other. A rule is amended if it yields an inference we are unwilling to accept; an inference is rejected if it violates a rule we are unwilling to amend. The process of justification is the delicate one of making mutual adjustments between rules and accepted inferences; and in the agreement achieved lies the only justification needed for either.”
—Nelson Goodman (b. 1906)
“That which endures is not one or another association of living forms, but the process of which the cosmos is the product, and of which these are among the transitory expressions.”
—Thomas Henry Huxley (1825–95)
“By Modernism I mean the positive rejection of the past and the blind belief in the process of change, in novelty for its own sake, in the idea that progress through time equates with cultural progress; in the cult of individuality, originality and self-expression.”
—Dan Cruickshank (b. 1949)