Database Design G (6672.5)
|Faculty:||Faculty of Science and Technology|
|Discipline:||Academic Program Area - Technology|
To view your Unit Outline, click View to log in to MyUC and access this information, or visit your unit's online teaching site.
- Semester 1, 2018, ON-CAMPUS, BRUCE (181402) - View
- Semester 2, 2017, ON-CAMPUS, BRUCE (167457) - View
- Semester 1, 2017, ON-CAMPUS, BRUCE (167080) - View
- Semester 2, 2016, ON-CAMPUS, BRUCE (151239) - View
- Semester 1, 2016, ON-CAMPUS, BRUCE (154804) - View
- Semester 2, 2015, ON-CAMPUS, BRUCE (139493) - View
- Semester 1, 2015, ON-CAMPUS, BRUCE (145604) - View
To locate a Unit Outline for a Unit prior to 2015 click here.
If a link to your Unit Outline is not displayed, please check back later. Unit Outlines are generally published by Week One of the relevant teaching period.
This unit introduces a practical approach to the development and design of database systems. The emphasis is placed on relational database management systems, their design and implementation in a modern organisational environment. The use of modern query languages for relational databases is discussed and experienced. Conceptual, logical and physical database design issues are also covered. Other topics include client server database computing and database administration issues.
Upon successful completion of this unit, students will be able to:
1. List, describe, and illustrate the steps in a database system development life cycle;
2. Illustrate the inputs and outputs in that process, with an emphasis on data modelling;
3. Acquire data analysis skills;
4. Develop an appropriate set of data models for relational database implementation and evaluate these data models;
5. Demonstrate an understanding of theoretical concepts; and
6. Demonstrate the use of the SQL language in a database server environment.
Up to 52 hours per semester.
Implemented the physical model from logical modelLogical model models information gathered from business requirements.Physical model represents the actual design blueprint of a relational database. It represents how data should be structured and related in a specific DBMS. This means that an accurate use of data type is needed for entity columns and the use of reserved words has to be avoided in naming entities and columns. Besides, database designers may also add primary keys, foreign keys and constraints to the design.Model Transitor enables you to transit a logical ERD to a physical ERD and with the transition relationship maintained. To transit, right click on the background of your conceptual/logical ERD, and then selectUtilities > Transit to Logical/Physical ERD...fromthe popup menu. This will form a new ERD with new entities there. You can make changes like to rename the entities and columns, or to add extra entities in the new ERD.