dido:public:ra:1.4_req:1_func
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.4_req:1_func [2022/05/08 14:14] nick |
dido:public:ra:1.4_req:1_func [2022/08/31 15:32] (current) nick |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq]] define the basic system behavior. Essentially, they are requirements stating what the system must do or must not do, and can be thought of in terms of how the system responds to inputs. Functional requirements usually define if/then behaviors and include calculations, data input, and business processes. | [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq]] define the basic system behavior. Essentially, they are requirements stating what the system must do or must not do, and can be thought of in terms of how the system responds to inputs. Functional requirements usually define if/then behaviors and include calculations, data input, and business processes. | ||
| - | Functional Requirements are features that allow the system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements. Functional Requirements can be used during all phases of a project [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle| Lifecycle]] independent of the development model (i.e., [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]] or [[dido:public:ra:xapend:xapend.a_glossary:a:agile]]). In the Waterfall method, these requirements are generally specified early on in the process. In the Agile method, they can be applied derived during each [[dido:public:ra:xapend:xapend.a_glossary:s:sprint]] or applied during specific Sprints. | + | Functional Requirements are features that allow the system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements. Functional Requirements can be used during all phases of a project [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle| Lifecycle]] independent of the [[dido:public:ra:xapend:xapend.a_glossary:s:software_development_model]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]] or [[dido:public:ra:xapend:xapend.a_glossary:a:agile]], etc.). In the Waterfall method, these requirements are generally specified early on in the process. In the Agile method, they can be applied derived during each [[dido:public:ra:xapend:xapend.a_glossary:s:sprint]] or applied during specific Sprints. |
| The DIDO RA views functional requirements from the following perspectives: | The DIDO RA views functional requirements from the following perspectives: | ||
dido/public/ra/1.4_req/1_func.txt · Last modified: 2022/08/31 15:32 by nick
