Database Design Clause Samples
The Database Design clause outlines the requirements and standards for creating and structuring a database within a project or agreement. It typically specifies the responsibilities for designing the database schema, ensuring data integrity, and meeting performance or security standards. For example, it may require the use of specific database technologies, adherence to normalization rules, or compliance with data privacy regulations. The core function of this clause is to ensure that the resulting database is robust, efficient, and suitable for the intended application, thereby reducing the risk of future technical issues or misunderstandings about database expectations.
POPULAR SAMPLE Copied 1 times
Database Design. Figure 21 presents the Entity Relationship (ER) schema of the Physical Activity Motivation and the Physical Activity Guidance Services. This is included in the Guidance database schema is interacting with the KnowledgeBase. All the tables included in this schema are described in Table 7. For more details about the attributes included in each table as well as the type and the description of these attributes please refer to Appendix A.
Database Design. Figure 9 presents the Entity Relationship (ER) schema of the Medication service that is included in the Care and Wellness database schema. All the tables currently included in this database are described in Table 3. Similarly to the Agenda Service described earlier, in order to protect the structure and data of the base tables, we have implemented the VIEW_PERSON_MEDICATION and VIEW_MEDICINE view structures that provide all data required by the Care and Wellness methods. NAME FK1 ROUTE_ID DATE_END FK2 FREQUENCY_ID DOSE COMMENTS MEDICINE_FREQUENCY PERSON_MEDICATION MEDICINE MEDICINE_ROUTE
Database Design. Figure 18 illustrates the current database design of the Object Location Assistance Service. The database schema presents the Entity Relationship (ER) schema of the Object Location Assistance service included in the Guidance schema and its interaction with KnowledgeBase and Monitoring. All the tables currently included in this database are described in Table 7. However, for more details about the attributes included in each table as well as the type and the description of these attributes please refer to Appendix A.
Database Design. In this section, we provide the current database design of the Agenda Database Design. The database schema shown in Figure 6, presents the Entity Relationship (ER) schema of the Agenda service included in the care and wellness schema and its interaction with KnowledgeBase and Monitoring. All the tables currently included in this database are described in Table 1. However, for more details about the attributes included in each table as well as the type and the description of these attributes please refer to Appendix A.
Database Design. Database design involves the design of the table structures, views, etc., on the basis of the customization to be carried out MS SQL may be used to generate the database design. The structures thus created may have to be fine-tuned (normalized / de-normalized) to gear up for performance.
Database Design. Figure 29 presents the Entity Relationship (ER) schema of the Meal Assistance service that is included in the Education\Leisure database schema. All the tables currently included in this database are described in Table 14. RECIPE_TYPE DESCRIPTION RECIPE_TYPE_ID DIFFICULTY TIME_IN_MINUTES COOKING_TYPE_ID IS_LOW_CARB IS_HIGH_FIBER IS_LOW_FAT IS_KOSHER IS_VEGETARIAN IS_LOW_CAL IS_NO_SUGAR IS_GLUTEN_FREE VIDEO_LINK MEAL_RECIPES
Database Design. In this section, a formal description of the databases to be used by WP5’s WasteApp is presented. A top-to-down approach will be used to clarify the structure of the databases, presenting a coarse macro-description and finally a more in-depth definition. As it has been already presented, there will be a main database where all the authentication information of the users will be stored. In addition, each municipality will have a specific database, comprising all the information attaining containers, awards and sponsor companies. Hence, the global database scheme could be summarized as it was shown in Figure 4.1.
Database Design. Figure 13 illustrates the current database design of the Shopping List Assistance Service. The database schema shown in Figure 13 presents the Entity Relationship (ER) schema of the Shopping List Assistance service included in the Care and Wellness schema and its interaction with KnowledgeBase. Moreover, the table PRODUCTS indicates the names of possible items with their units of measurements that can be included in the shopping list. This is mainly for supporting the avatar. All the tables currently included in this database are described in Table 5. However, for more details about the attributes included in each table as well as the type and the description of these attributes please refer to Appendix A. PERSON_SHOPPING_LIST AGE PICTURE RESIDENCE_ID RESIDENCE_ROOM_ID EMAIL SKYPE_NAME SKYPE_USERNAME SKYPE_PASSWORD LANGUAGE_ID PRODUCTS
Database Design. The most critical component of the system is the database. It will not only be used to store the County’s current property record card data, but it must keep a historical record. BHA will design a property record card database that addresses the following requirements: ● Property Data Schema ○ BHA will take inventory of all data entry fields on the paper property record cards, identify use cases based on filled property record cards, and present the inventory and use case findings to Macoupin County. This inventory will include the recommended column datatypes, such as numeric or date. ○ Macoupin County will verify BHA’s inventory and use case findings of each data entry field on each of the paper property record cards. ○ Once the County has verified the datatypes of each field on the paper property record cards, BHA will organize the data fields into logical tables. ○ Primary / Foreign key relationships will be used to link one-to-many data to the main property table. ● Export ○ BHA will ensure that the property record card data that is stored is easily extracted to be used for third party systems such as CAMA, field appraisal, GIS, and property search websites. ● Import ○ Similar to the export process, BHA will define an external property record schema or API for the importing of data.
Database Design. 11.1. Database queries, reports and database design in support of the college is the primary responsibility of the Computer Database Specialist. All of work is completed in a manner secondary to this primary goal.
11.2. Other projects may be developed with the permission of the Director with the following understanding:
11.2.1. A letter of agreement is developed detailing the work that is to be completed and any deadlines that must be adhered to.
11.2.2. Grant- funded research that relies on database design, must include funding for SBSTech.
11.2.3. SBSTech will ensure that individuals working with data have completed any training or certification required by the university or granting agency. Any costs must be supported by the grant.
11.2.4. SBSTech will ensure that the data is protected in a fashion deemed appropriate by the university or granting agency.
11.2.5. Data entry is the responsibility of the department/individual.