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:
“... the history of the race, from infancy through its stages of barbarism, heathenism, civilization, and Christianity, is a process of suffering, as the lower principles of humanity are gradually subjected to the higher.”
—Catherine E. Beecher (1800–1878)
“At the heart of the educational process lies the child. No advances in policy, no acquisition of new equipment have their desired effect unless they are in harmony with the child, unless they are fundamentally acceptable to him.”
—Central Advisory Council for Education. Children and Their Primary Schools (Plowden Report)
“Thinking is seeing.... Every human science is based on deduction, which is a slow process of seeing by which we work up from the effect to the cause; or, in a wider sense, all poetry like every work of art proceeds from a swift vision of things.”
—Honoré De Balzac (1799–1850)