dido:public:ra:1.4_req:00_aboutreq:01_govreqmdl
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:00_aboutreq:01_govreqmdl [2021/03/05 23:53] nick created |
dido:public:ra:1.4_req:00_aboutreq:01_govreqmdl [2021/10/03 08:08] (current) 168.119.68.126 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== 4.1 Governance Requirements Model ===== | + | ====== 4.1.1 Governance Requirements Model ====== |
| - | [[dido:public:ra:1.4_req | Return to Top]] | + | [[dido:public:ra:1.4_req:00_aboutreq | Return to About Requirements]] |
| - | In addition to this definition, requirements can be applied to various aspects of a project from a governance perspective. There are three different aspects of governance: Regulation, Execution and Compliance (See [[dido:public:ra:xapend:xapend.j_gov_model]]. (( | + | In addition to this definition, [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirements]] can be applied to various aspects of a project from a governance perspective. There are three different aspects of governance: Regulation, Execution and Compliance (See [[dido:public:ra:xapend:xapend.j_gov_model:start]]. (( |
| Stavros, Robert W. and | Stavros, Robert W. and | ||
| Albrant, Jeremiah; | Albrant, Jeremiah; | ||
| Line 20: | Line 20: | ||
| Accessibility of State and Local Government Websites to People with Disabilities, U.S. Department of Justice, Civil Rights Division, Disability Rights Section https://www.ada.gov/websites2.htm | Accessibility of State and Local Government Websites to People with Disabilities, U.S. Department of Justice, Civil Rights Division, Disability Rights Section https://www.ada.gov/websites2.htm | ||
| )), or it can be project specific such as the contract or the technical specification of a contract or can be as detailed as the steps defined for a particular test plan. | )), or it can be project specific such as the contract or the technical specification of a contract or can be as detailed as the steps defined for a particular test plan. | ||
| - | * **Execution** covers the lifecycle of a product or service being governed (i.e., design, building, maintenance, etc). This covers the functional and non-functional requirements of the product or service and can be in terms of static or dynamic compliance points | + | * **Execution** covers the lifecycle of a product or service being governed (i.e., design, building, maintenance, etc). This covers the functional and [[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq|non-functional requirements]] of the product or service and can be in terms of static or dynamic compliance points |
| * **Compliance** covers the oversight of the product or service being governed. This covers the not only the product or service itself but also the process of Regulation and Execution. For example, is the contract or technical specification well written and maintained throughout the lifecycle of the product or service. | * **Compliance** covers the oversight of the product or service being governed. This covers the not only the product or service itself but also the process of Regulation and Execution. For example, is the contract or technical specification well written and maintained throughout the lifecycle of the product or service. | ||
| Understanding requirements is an important part of specifying, building, using and maintaining any product. And when the System is Distributed on multiple machines, supporting multiple stakeholders the need for the proper governance is essential. The requirements must cover all three aspects of governance. For example, there can be a requirement that is expressed in the regulatory aspect which requires reporting of information. The Compliance aspect will have a corresponding requirement that validate and verifies the reporting of the information. These are then also reflected in the Execution Aspect that has to have processes and systems designed to collect and report the proper data. | Understanding requirements is an important part of specifying, building, using and maintaining any product. And when the System is Distributed on multiple machines, supporting multiple stakeholders the need for the proper governance is essential. The requirements must cover all three aspects of governance. For example, there can be a requirement that is expressed in the regulatory aspect which requires reporting of information. The Compliance aspect will have a corresponding requirement that validate and verifies the reporting of the information. These are then also reflected in the Execution Aspect that has to have processes and systems designed to collect and report the proper data. | ||
| + | |||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/1.4_req/00_aboutreq/01_govreqmdl.1615006387.txt.gz · Last modified: 2021/03/05 23:53 by nick
