Database Structuring and Project Planning
A project is divided into different timelines and this timeline structure is same for companies as well as for individual developers. The first stage of the timeline is Project Structuring. Project Structuring consists of frame planning, task division, data categorization, database structure mapping.
Project Structure
Firstly you need to decide the different frames in which your project will be divided. The data will be taken as input from each frame. You need to decide the elements in each frame. The best way is to use wireframing. In wireframing, you can link different frames and make a reference UI for the app/website.
Wireframing article: https://www.geeksforgeeks.org/wireframe-in-ux-design-a-beginners-guide/
Credits: https://github.com/mydraft-cc/ui
Data Categorization
Now you need to figure out the data type of the input and output data in each frame. During development, you need to typecast the data based on what you are taking as input and storing in the database or what you are retrieving from the database and displaying on the screen.
Database Structure
In the next step, you need to structure your database, decide the entities and their data types. Structuring of databases can be done on https://dbdiagram.io/home. The structured mapping of databases is called a DB Diagram. You can link different tables, set columns as not null, unique, primary key.
Above is the DB Diagram of my project Financify.
It consists of 6 tables and each table consists of multiple entities. Different entities can be linked with each other.
This diagram can be created by simply writing column names in curly braces.
Here’s the code for this diagram.
You can use dbdocs.io to create database documentation, for instance, refer:
https://dbdocs.io/kanavarora1515/Financify?view=table_structure
Development
Now the development phase begins… Db Diagram will help you to give a broader picture of your project. This will give you an idea of the data type you are working with and the data type required for the database.
This DB Diagram can be added to the documentation of your project. So that people who are unaware of your project can get an overview of your backend workflow.
You can refer to this GitHub repository for project documentation:
