ER model and its role in data modeling
Develop an ER model to characterize the information requirements of business case (Price, et.al, 2009). ER diagrams are powerful data modelling tools which describe the relationships between entities making up a system.
Entities: Activities Output
IO office Enrolment notices
Students Collecting information documents
Volunteers Organizing roster
Managers print a list of contacts
Faculty Washing windows
IO lounge Vacuuming floors
Games Mopping
Victoria University. Mentoring
Business rules are protocols which defines some aspects of the business and at all times resolves to either false or true. They are majorly intended to affirm business structure. The business rules in my case for the database for Victoria University include;
1 Applicant can submit one or more applications (one application per year for multiple years).
The applications by the prospectus students are not restricted to one application.
2.Each application is submitted by only one applicant.
The application can only be submitted by one applicant.
- Each course is associated with one or more applications. Each application is associated
with one faculty or school.The applications are specific to one school or faculty.
- Each application must include contact details.
- The lounge is associated with more than one category of students i.e full time and part time students. (Von Halle, B,(2001).
University school . one to many relationship
University faculty .one to many relationship
IO offices Director .one to one relationship
Faculty courses one to many relationship.
School courses one to many relationship.
Faculty students one to many relationship.
School students one to many relationship.
Students lounge many to one relationship.
1.3Map the ERD into a 3NF.
In this conversion, I am basing on the fact that entities sometimes have keys and dependant relationships between groups of non-key attributes.
- Identify the dependancies among the non-key attributes in the table.
- Remove the dependancies so that we form a new table.
- Promote one of the attributes which is the foreign key to be the primary key of the new table.
Normalization. (Kolahi, S.,et.al,2006, June).
|
Unormalised |
1NF |
2NF |
3NF |
Entity name |
|
Student_name) Registration_number) Course) Acivity) Year of study) Faculty) DOB) Gender) Phone) |
Registration_number Student_name Course Activity Year of study Faculty DOB Gender |
Registration_number Student_name Course Activity Year of study Faculty DOB Gender |
Registration_number Course Activity Year of study Faculty DOB Gender |
Students |
|
Course) Course_code |
Course_code corse |
Course_code corse |
Course_code |
Course |
|
Director_name) Director_number) |
Director_name Director_number |
Director_name Director_number |
Director_name |
Director |
|
Volunteer) Volunteer_phone |
Volunteer Volunteer_phone |
Volunteer Volunteer_phone |
Volunteer_phone |
volunteer |
|
Faculty_name) |
Faculty_name |
Faculty_name |
Faculty_name |
Faculty |
Data dictionary:
|
Attribute |
Meaning |
Data type |
other |
|
Student_name |
An attribute by which a student is identified with |
Text |
Might not be unique due to namesake issues |
|
Registration_number |
The primary identifier of students unique in all tables of the database |
String(VARCHAR) |
Example:IN3/20431/15 |
|
phone |
An identify which is foreign key in another table |
String(VARCHAR) |
Example:+1314223645 |
|
Roster |
Systematic schedule of activities |
Text |
Activity/person/day/time |
|
Facility |
A type of a service |
Text |
Example: coffee and tea |
|
position |
Title one holds |
Text |
Example: manager |
|
Enrolment |
Admission to a new place |
Text |
Admitted to the school of law |
Database implementation:
Create the database in phpMyAdmin:
My database is named Victoria;
Populating the database with sample data;
First create table(s) in my case I have a table named students;
Sample data:
c.Design forms; student information entry form:
Director and the jobs:
Report by Slimstat analytics:
Reports for the sites(Patel, et.al,2011).
References
Patel, S. K., Rathod, V. R., & Prajapati, J. B. (2011). Performance analysis of content management systems-joomla, drupal and wordpress. International Journal of Computer Applications, 21(4), 39-43.
Leone, S., de Spindler, A., & Norrie, M. C. (2012, November). A meta-plugin for bespoke data management in wordpress. In International Conference on Web Information Systems Engineering (pp. 580-593). Springer, Berlin, Heidelberg.
Kiefer, T., Schlegel, B., & Lehner, W. (2013). Experimental Evaluation of NUMA Effects on Database Management Systems. In BTW (Vol. 13, pp. 185-204).
Makinouchi, A. (1977, October). A consideration on normal form of not-necessarily-normalized relation in the relational data model. In VLDB (Vol. 1977, pp. 447-453).
Kung, H. J., & Tung, H. L. (2006, March). A web-based tool to enhance teaching/learning database normalization. In Proceedings of the 2006 Southern Association for Information Systems Conference (pp. 251-258).
Kolahi, S., & Libkin, L. (2006, June). On redundancy vs dependency preservation in normalization: an information-theoretic study of 3NF. In Proceedings of the twenty-fifth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems (pp. 114-123). ACM.
Von Halle, B. (2001). Business rules applied: building better systems using the business rules approach. Wiley Publishing.
Price, O. R., Munday, D. K., Whelan, M. J., Holt, M. S., Fox, K. K., Morris, G., & Young, A. R. (2009). Data requirements of GREAT-ER: Modelling and validation using LAS in four UK catchments. Environmental pollution, 157(10), 2610-2616.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
