| What To Do | How To Do It |
|---|
Are any proprietary database standards used? | - Applications need to be easily portable from one RDBMS to another.
- Proprietary SQL, stored procedures, triggers, null foreign keys, and other types of solutions should be discussed with and approved by the Architecture Team before use.
|
Are industry practices for relational data modeling adhered to? | - Please refer to Agile Data Modeling 101 for reference
- Does every table have a primary key that will not change over time and preferably has no meaning?
- Is the data model in 3rd normal form and does it adequately enforce relational integrity and data quality?
- Does the cardinality reflect the business correctly?
- Would a programmer be able to read the data model and understand the business rules of an application?
- Has the Functional Lead reviewed and verified that the logical data model accurately reflects the business?
|
Review existing Entity Relationship Data Models and Data Dictionaries for possibility of database reuse. | - A catalog of existing data entities and attributes can be viewed for many existing applications. Please see an OIT Software Development Director for guidance.
|
| Does your application store or access SB1386, PCI, HIPAA or other sensitive or restricted data? | Encryption is required of all regulated restricted data. Has data model been normalized and sensitive data consolidated for easier encryption and auditing? Please contact the OIT Security Team Manager for guidance.
|
| Data model and Data Dictionary completed? | - Has a data dictionary been created?
- Have Entity-Relationship (ER) data models been completed?
|
Database servers need to be setup and configured securely before any coding can begin. | Please see a an OIT DBA. If using MS SQL Server, has the Secured Setup Checklist been performed? |