IT 204 Final Project Guidelines and Rubric
Database Proposal and Implementation Plan Report
Overview
The final project for this course is the creation of a database proposal and implementation plan report that will address the needs of a case scenario involving Southern New Hampshire Schools. The purpose of this project is to assess your understanding of data models, simple database structures and functions, and terminology from an information management perspective.
Outcomes
Apply the appropriate terminology of the realm of data and information management to real-world scenarios
Develop and address complete and valid data requirements for business cases
Prompt
You will design a relational database and develop a strategy for implementation, which you will fully document in a comprehensive written report. Current data requirements include the following:
Student data (full name, full address, phone, email, birthdate, enrollment date, graduation date, courses taken, courses currently enrolled)
Introduction: Based on the given scenario you were provided:
Summarize the data and information requirements of the business case and client needs using appropriate data and information management terminology.
Relational Database Model: Based on the scenario and the information from your introduction and your analysis:
Design a basic relational database visual diagram with entities, attributes, and relationships based on the requirements you have identified. Be sure to include proper relationship mapping.
Comparatively evaluate these technologies in terms of their applicability to the needs of Southern New Hampshire Schools.
Implementation of Relational Database Model: In outline format, recommend a step-by-step process for implementing the new database.
Milestones
|
|
||
|---|---|---|---|
|
|
||
|
|||
|
|||
|
|||
|
|
Final Project Rubric
|
Meets “Proficient” criteria, and the relational database visual diagram is simply and intuitively organized | Basic relational database visual diagram does not illustrate applicable entities, attributes, and relationships | |||
|---|---|---|---|---|---|
| Meets “Proficient” criteria, and the conceptual and logical visual diagrams are simply and intuitively organized |
|
|
Conceptual and logical visual diagrams do not illustrate applicable entities and attributes | ||
| Meets “Proficient” criteria, and the database selection reasoning evidences keen insight into the world of information technology | Database selection is not supported |
|
|||
|
Meets “Proficient” criteria, and the database selection explanation demonstrates keen insight into additional or alternative technologies | Does not explain additional or alternative technologies | |||
| Meets “Proficient” criteria, and the database selection evaluation demonstrates keen insight on additional or alternative technologies |
|
|
Does not comparative evaluate additional or alternative technologies | ||
| Meets “Proficient” criteria, and the information outline shows keen insight into the nuances of successful implementation | Does not include all key relevant information and steps necessary for implementing the new database |
|
