Create a Database Design

[KarthikElumalai]

This below document and the diagram is solely for QUEUE MANAGEMENT

Flow Of E-Token Process by Different Diagrams

Putting the above , will help us to identify the entities

We need to add User Interaction to this

DataBase Design for ETOKEN

Hi Friends,

We will use this task, to share the things about our database design . While doing our pages , whenever we get an entities ideas, we will add in this task so that finally we will get the full design.

Brief info of Database Design:

1. Determine the purpose of the database - This helps prepare for the remaining steps.
2. Find and organize the information required - Gather all of the types of information to record in the database, such as product name and order number.
3. Divide the information into tables - Divide information items into major entities or subjects, such as Products or Orders. Each subject then becomes a table.
4. Turn information items into columns - Decide what information needs to be stored in each table. Each item becomes a field, and is displayed as a column in the table. For example, an Employees table might include fields such as Last Name and Hire Date.
5. Specify primary keys - Choose each table’s primary key. The primary key is a column, or a set of columns, that is used to uniquely identify each row. An example might be Product ID or Order ID.
6. Set up the table relationships - Look at each table and decide how the data in one table is related to the data in other tables. Add fields to tables or create new tables to clarify the relationships, as necessary.
7. Refine the design - Analyse the design for errors. Create tables and add a few records of sample data. Check if results come from the tables as expected. Make adjustments to the design, as needed.
8. Apply the normalization rules - Apply the data normalization rules to see if tables are structured correctly. Make adjustments to the tables, as needed

Etoken:

Based on the VerbandNoun analysis i have identified the entities

Entities identified so far: Business Consumers Queue Token Rating

Entities with Properties:

Business – id ,name ,type/category,location/address ,phone,ismultibranch,branchno Branch – Businessid ,branch id , branch name ,address,etc Consumers – id,name,phone Queue Token – ID,No,Consumerid, businessid,token status Rating

Relationships: Business table has one to many relationship with Branch table Consumer has one to many relationship with token table

Thanks

[KarthikElumalai]

Hi Friends,

As of now, I found that the below video is so useful to learn about database design and usecase analysis.

https://www.youtube.com/watch?v=KeMgPqLCkuo

We will use this task to add our ideas and find outs regarding database design in the future

Thanks Karthik

[KarthikElumalai]

Hi Team,

Here is a data model that appears to be suitable for most of the scenarios in our e-token project.

ER diagram of that modal is below:

Verified this, using code first approach of entity framework in our E-Token Project.

Here is the Source code commit link.

https://github.com/KarthikElumalai/ETokenSln/commit/346e4931b8097409409339ace72e83fc1b8827d8

For the above tables, I have put some sample data in excel, to get the full idea of how our data will look like from start to end. Here is the Link for that.

E-Token Tables with Sample Data:

https://docs.google.com/spreadsheets/d/14zbv8H4fnbW_UWa0OQvH3yYlBsrGVDVFNTSHssC_OzU/edit?usp=sharing

Hope it will help us, kindly take a look at it and share your valuable thoughts or feedbacks

Thanks Karthik