Independent Projects Overview
Project prompts will be available on Epicenter at 8:00 am Friday for full-time students and 8:00 am on Thursday for part-time students. Before you begin your project, make sure to take a moment to review the Independent Projects and Code Reviews lesson.
Database Basics Project Objectives
Your code will be reviewed for the following objectives:
- Do the database table and column names follow proper naming conventions?
- Do the project folder and exported database follow the specific naming requirements for this project?
- Are the instructions for re-creating your database thorough and clear?
- Is there a one-to-many relationship set up correctly in the database?
- Is CREATE functionality included for one class and is CREATE and VIEW functionality included for the other class?
- Build files and sensitive information are included in
.gitignore file and is not to be tracked by Git, and includes instructions on how to create the
appsettings.json and set up the project.
- Project is in a polished, portfolio-quality state.
- The prompt’s required functionality and baseline project requirements are in place by the deadline.
What is a polished, portfolio-quality state?
When a project is both polished and in a portfolio-quality state, this means:
- You've reviewed your project and your README prior to submitting it to make sure there are no errors or missing information and you are consistent in your indentation, spacing, and code structure.
- You are following the best practices and coding conventions we teach.
What are the baseline project requirements?
All independent coding projects at Epicodus have these baseline requirements:
- A complete and informative README
- The project's commit history demonstrates that the project’s required work schedule and hours have been met:
- 8 hours completed on Friday is required for full-time students
- 4 hours completed over the weekend is required for part-time students
- Completion of the project based on the prompt and objectives. The prompt contains details on the project's theme and features that are not always detailed in the objective. Carefully read through the prompt towards the end of your work session to make sure that you are not missing anything.
For reference, here are the previous sections' objectives:
- Do MVC routes follow RESTful convention?
- Classes are encapsulated and getter methods are used to access properties.
- Logic is easy to understand.
- Code and Git documentation follows best practices (descriptive variables names, proper indentation and spacing, separation between front and back-end logic, detailed commit messages in the correct tense, and a well-formatted README).
Submit your code for review to the Database Basics code review on Epicenter.
Visit Independent Projects and Code Reviews for details on how to submit your code, how feedback works and course completion requirements.