This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dido:public:ra:1.4_req:2_nonfunc:25_security:04_data_integrity [2021/06/08 23:57] char |
dido:public:ra:1.4_req:2_nonfunc:25_security:04_data_integrity [2021/06/11 14:43] (current) char |
||
---|---|---|---|
Line 31: | Line 31: | ||
* [[dido:public:ra:xapend:xapend.a_glossary:l:logicalintegrity]] keeps data unchanged as it is accessed. Logical integrity protects data from some of the same issues as Physical Integrity (i.e., human error and hackers as well) but in different ways. There are four types of logical integrity. \\ | * [[dido:public:ra:xapend:xapend.a_glossary:l:logicalintegrity]] keeps data unchanged as it is accessed. Logical integrity protects data from some of the same issues as Physical Integrity (i.e., human error and hackers as well) but in different ways. There are four types of logical integrity. \\ | ||
1 - [[dido:public:ra:xapend:xapend.a_glossary:e:entityintegrity]] - supports unique values that identify any particular data entry and that the [[dido:public:ra:xapend:xapend.a_glossary:k:key|key]] is not null. \\ | 1 - [[dido:public:ra:xapend:xapend.a_glossary:e:entityintegrity]] - supports unique values that identify any particular data entry and that the [[dido:public:ra:xapend:xapend.a_glossary:k:key|key]] is not null. \\ | ||
- | 2 - [[dido:public:ra:xapend:xapend.a_glossary:r:refintegrity]] - ensures that references to other data entries exists. \\ | + | 2 - [[dido:public:ra:xapend:xapend.a_glossary:r:refintegrity]] - ensures that references to other data entries exist. \\ |
3 - [[dido:public:ra:xapend:xapend.a_glossary:d:dataintegrity]] - ensures that domain rules (i.e., data restrictions) are enforced for the data within the [[dido:public:ra:xapend:xapend.a_glossary:d:datastructure]]. For example, minimum, maximum, number of decimals, nullable, etc. are enforced. \\ | 3 - [[dido:public:ra:xapend:xapend.a_glossary:d:dataintegrity]] - ensures that domain rules (i.e., data restrictions) are enforced for the data within the [[dido:public:ra:xapend:xapend.a_glossary:d:datastructure]]. For example, minimum, maximum, number of decimals, nullable, etc. are enforced. \\ | ||
- | 4 - [[dido:public:ra:xapend:xapend.a_glossary:u:userdefintegrity]] - ensures that business rules are enforced. For example, if a value is set, another value must also be set (unset); if a value exceeds a threshold, a notice must be sent. \\ | + | 4 - [[dido:public:ra:xapend:xapend.a_glossary:u:udefintegrity]] - ensures that business rules are enforced. For example, if a value is set, another value must also be set (unset); if a value exceeds a threshold, a notice must be sent. \\ |
**Note:** Data integrity is not [[dido:public:ra:xapend:xapend.a_glossary:d:datasecurity]] and not [[dido:public:ra:xapend:xapend.a_glossary:d:dataquality]]. | **Note:** Data integrity is not [[dido:public:ra:xapend:xapend.a_glossary:d:datasecurity]] and not [[dido:public:ra:xapend:xapend.a_glossary:d:dataquality]]. | ||
Line 42: | Line 42: | ||
[[dido:public:ra:1.4_req:2_nonfunc:25_security:04_data_integrity | Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:25_security:04_data_integrity | Return to Top]] | ||
- | //<color #FF0000><todo>TBD - to be added/expanded in future revisions of the DIDO RA (look at spec in DDSF)</todo></color>// | + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA (look at spec if DDSF) </color></wrap> |
/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |