DHEN’Z Motorcycle Spare Parts Inventory Management System Database Design Project
This inventory management system is made to help the owner of the Dhen’z motorcycle spare parts to make their everyday transactions easily.
This inventory management system can also use to monitor the product quantity, the price entity, and the item to be ordered to the supplier of the motorcycle spare parts to have efficient stocks.
It can also monitor what part of items is fast-moving, and to know which part of the items is still available. Most of all it can help monitor and retrieves information especially in the terms of income.
This system will keep the operations running smoothly to the user up to the transaction to the customer. This system was built to prevent some problems in transaction to the customer and to monitor those products its availability, quantities, and amount.
Spare Parts Business Background
Since spare parts business is one of the most well-known businesses nowadays Mr. Jesus Naga Delagon plan to start a business since he like to customize motors thus their location is perfect for the planned business so he build spare parts business which is the Dhen’z Motorcycle Spare Parts.
On December 2017 at Crossing Tuguis , Pontevedra Negros Occidental he officially opens and starts operating manually.
Features of Inventory Management System Database Design Project
Manage user to Add, Update and Delete the transactions.
It helps to monitor the product quantity and product to be ordered to the supplier to have an efficient stock operation.
It can help to keep the security and information to the database.
To enhance sale productivity and easy to add, list, edit and organize the product.
It helps to monitor the product quantity and product to be ordered to the supplier to have an efficient stock operation.
Data Dictionaries of DHEN’Z Motorcycle Spare Parts Inventory Management System Database Design Project
These tables below provide the entire database tables detail such as Field Name, Descriptions, data type, character lengths.
Table1. tblcostumer
| Field Name | Description | Type | Length |
| Costumer_no(pk) | Costumer number | Int | 11 |
| Costumer_id | Costumer id | int | 11 |
| Firstname | First name | varchar | 50 |
| Lastname | Last name | varchar | 50 |
| Phone_number | Phone number | varchar | 50 |
| Email address | varchar | 50 | |
| Address | Address | varchar | 50 |
Table2. tblorder
| Field Name | Description | Type | Length |
| Oder_id(pk) | Order id | int | 11 |
| Product_id | Product id | int | 11 |
| Quantity | Quantity | int | 11 |
| Price | Price | int | 11 |
| Subtotal | Subtotal | int | 11 |
| Costumer_id | Costumer id | int | 11 |
Table3. tblproduct
| Field Name | Description | Type | Length |
| Product_id(pk) | Product id | int | 11 |
| Product_name | Product name | varchar | 50 |
| Brand | Product Brand | varchar | 50 |
| Quantity | Quantity | varchar | 11 |
| Price | Price | int | 11 |
| Subtotal | Subtotal | int | 11 |
Table4. tbltransaction
| Field Name | Description | Type | Length |
| Transaction_no(pk) | Transaction number | int | 11 |
| User_id | User id | int | 11 |
| Costumer_id | Costumer id | int | 11 |
| Date | Date | Date | 20 |
| Quantity | Quantity | varchar | 50 |
| Total amount | Total amount | int | 11 |
Table5. tbluseraccount
| Field Name | Description | Type | Length |
| User_id(pk) | User id | int | 11 |
| Username | User name | varchar | 50 |
| Password | User password | varchar | 50 |
Table6. tbluserdetail
| Field Name | Description | Type | Length |
| User_id(pk) | User id | int | 11 |
| First_name | First name | varchar | 50 |
| Last_name | Last name | varchar | 50 |
| Position | Position | varchar | 50 |
| Age | Age | int | 11 |
| Gender | Gender | varchar | 20 |
| Contact_number | Contact number | varchar | 11 |
| varchar | 50 | ||
| Add_id | Address id | int | 11 |
Entity Relationship Diagram
Dhen’z Motorcycle Spare parts Inventory System Entity Relationship Diagram shows the system relationship in each entity and their supposed function in each relationship.
Figure1. Dhen’z Motorcycle Spare parts Inventory System Entity Relationship Diagram
DHEN’Z Motorcycle Spare Parts Inventory Management System Database Design Project Entity Relationship Diagram(ERD) are the entity of the Dhen’z Motorcycle Spare parts Inventory System database which is presented by tables, the tables are made be need the required specification of the system and provide any specific details of the entities within the system.
If you have any questions about DHEN’Z Motorcycle Spare Parts Inventory Management System Database Design Project, please feel free to contact us at our contact page or simply leave a comment below.
Related Database Design project you may Like
- ER Diagram for Sales and Inventory System Database Design
- Ordering System Database Design with ERD
- ER Diagram for Water Refilling Station System Database Design
How to read an ER diagram
An entity-relationship (ER) diagram documents the database schema: entities (tables), attributes (columns), and relationships (foreign keys and cardinality).
- Entity. Rectangle representing a table.
- Attribute. Oval or field for each column.
- Primary key. Underlined attribute name.
- Foreign key. Attribute referencing another entity.
- Relationship. Diamond or line connecting related entities.
Common capstone mistakes to avoid
- Many-to-many without junction table.
- Missing primary key.
- Denormalized redundancy.
- Ambiguous naming.
Where this diagram fits in Chapter 3
- Section 3.3 (Database Design).
- Include the CREATE TABLE SQL script alongside.
- Reference from the class diagram.
- Include a legend to explain the notation for panel members.
Official documentation
Official documentation
Working source code for this system
Download the actual implementation of this system in your preferred language. Each project includes source code, database, and setup instructions for BSIT capstone use.
- PHP: Stock Management System in PHP with Source Code
- VB.NET: Sales and Inventory Management System Project in VB.Net Source Code
- Java: Stock Management System Project in Java with Source Code
- Python: Django Warehouse Management System with Source Code
- Django: Django Warehouse Management System with Source Code
- Laravel: Inventory Management System in Laravel With Source Code
Frequently asked questions
What is a ER diagram used for in BSIT capstone?
An ER diagram shows the database schema: entities (tables), attributes (columns), and relationships (foreign keys, cardinality). It goes in Chapter 3 alongside the class diagram to communicate the data storage design.
What tool should I use to draw the ER diagram?
Free options: draw.io, Lucidchart free tier, PlantUML, StarUML 30-day trial, Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.
How detailed does the ER diagram need to be for capstone defense?
Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification.
Should I use black-and-white or colored diagrams?
Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity. Ensure text is readable at printed size (10pt minimum for labels).
Where does this diagram go in the capstone documentation?
Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it.
Frequently asked questions
What is a ER diagram used for in BSIT capstone?
An ER diagram shows the database schema: entities (tables), attributes (columns), and relationships (foreign keys, cardinality). It goes in Chapter 3 alongside the class diagram to communicate the data storage design.
What tool should I use to draw the ER diagram?
Free options: draw.io (browser-based, saves to Google Drive), Lucidchart free tier, PlantUML (text-based, version-controllable), StarUML (30-day trial then reduced feature set), Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.
How detailed does the ER diagram need to be for capstone defense?
Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification. Aim for 1-2 diagrams that fully cover the system, not many partial ones.
Should I use black-and-white or colored diagrams?
Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity (e.g., grouping subsystems). Ensure text is readable at printed size (10pt minimum for labels).
Where does this diagram go in the capstone documentation?
Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it. Reference specific elements in the surrounding text so panel members can follow the design rationale.
Mary Grace G. Patulada
Programmer & Technical Writer at PIES IT Solution
Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.
Expertise: UML Diagrams, DFD, ER Diagrams, Use Case Diagrams, Activity Diagrams, Capstone Documentation, PHP · View all posts by Mary Grace G. Patulada →