Database Project Specs
Purpose: To gain exposure to relational database by creating a logical design (documentation of planning the design) and a physical design (actual implementation into MS Access) of an approved topic for a database.
Grading: project grading sheet can be found in the “content” area in Blackboard.
Framework: A framework for how your project should be submitted is attached.
Part A: Database Topic Selection
Submit via Blackboard -> Assignments -> Database Topic Submission.
You may not choose any of the database topics shown in the examples from the reference section or used in class.
Part B: Logical Design
Submit one Word document via Blackboard -> Assignments -> Logical Database Submission.
Questions to ask yourself to get started:
- What is the purpose of your db?
- What are the unique categories/tables/entities in your db?
- What fields/attributes does each table have?
- What are your key fields (primary & foreign)?
Create a Relational Database Logical Design to include:
Normalization (Justification as to how duplication was avoided),
Use any tool that you want for the ERD, but insert a .jpg (or equivalent file type) into your final document. One tool you might choose to use can be found in the “ER Diagram Templates” section at: http://creately.com/blog/diagrams/er-diagrams-tutorial/ . Another option that provides the ability to save your file as a jpg/gif and to use the Crow’s Foot Notation is: http://www.edrawsoft.com/entity-relationship-diagrams.php. In the reference section at the bottom of this document, other ERD tools and references are provided.
In your ERD, show entities, attributes, foreign key/primary key, relationships and cardinality. If any item needs further clarification, do this below the ERD.
Entities: Show entities in a rectangle. You must show >=3 entities.
Cardinality: use Crow’s Foot notation: http://www2.cs.uregina.ca/~bernatja/crowsfoot.html
Attributes: the cs.uregina site shows the attributes inside the entities. You can use this method, or show attributes in ovals as the creately.com site shows. You must have at least 3 attributes per entity
Foreign Key/Primary Key: below your ERD, provide a key to explain how you are notating foreign and primary keys.
Relationships: again, the two references show relationships differently. You may use either method. You must create >=2 relationships
Other: Remember, if any item in your ERD needs further clarification, do this below your diagram. Please provide a brief summary of what your ERD topic is and explain it to me like you did in class.
For each table provide table name, attribute name, contents, data type (use either notation: auto number/number/date/text or char/varchar/date/number), required (Y/N), Primary Key/Foreign Key, Foreign Key Referenced Table, specifics about the data
Write at least two paragraphs to justify how duplication was avoided.
Part C: Physical Design
Submit one Microsoft Access document via Blackboard -> Assignments -> Physical Database Submission. Also, please resubmit the same (or revised) ERD document that you submitted for your logical design. (two files should be submitted total) In your submission notes, indicate if you created any extra credit reports or forms and what they are named.
Implement the graded logical design (with improvements) into a physical design in MS Access. Before implementing in Access, any issues from grading of the logical DB must be addressed, either through further contact with the professor (if this was stated in your grading document) or in your Access database.
- For each implemented table:
- ensure that you have defined the Field Name, Data Type and provide a good description. If an input mask is applicable, make sure to put this in.
- you must have several data rows created (aim for >=10 rows per table, unless this doesn’t make sense for one of your tables)
- designate a primary key. In your description, indicate if a field will be a foreign key (FK)
- Make sure you have defined the database relationship(s) in Access. Make sure that you have specified the correct join type (hint: you don’t want redundant data. Join is most likely the default join unless you are doing something more advanced.)
- Create at least one query
- Create at least one lookup column
- Forms or report can be created for extra credit points if desired (max of 5 points possible).