Custom PC
Custom PC
Custom
PC
Build
TABLE OF CONTENTS
1. Introduction of Project
2. Objectives of Project
3. Project category
4. Tools/Platform of Project H/W and S/W
5. Design of Project
a. DFD
b. ER DIAGRAM
c. DATA STRUCTURE
d. Number of Modules & Their Description
e. Process Logic of Modules
6. Validation check
7. Types of Report Generation
8. Limitation Of the Projects
9. Future Scope of Project
10. Biblography
INTRODUCTION
The project is based on three tier architecture. The three tier architecture
where the application is divided into three logical constituents
» User Services — Provide services such as user interface. (VB.NET
application in this case).
» Business services — Implement business rules (ActiveX DLL in this case)
» Data Services — Provide handling and validation of data. (MS SQL Server
in this case) Disadvantages of the two tier architecture
» It puts extra load on the server
» It increases the network traffic.
» Difficult to implement incremental improvements.
» Applications are bound to the data source.
Technology to be used:
Hardware Requirement:-
• Processor: Pentium Processor ISA 32 Family
• Secondary Storage: 80 GB HDD
• ROM: 52X CD ROM Drive
• Floppy Drive: 1.44 FDD
• Memory: 1 GB RAM
• Network Adapter: Ethernet Adapter, Wifi
• Others: 17" Color Monitor, Printer, Scanner, Keyboard, Mouse.
Software Requirement:-
• Platform: Windows
• Operating System: Windows 10
• Framework: ASP.NET Framework 2019, Springboot
• Front-End Tool: HTML with BootStrap
• Back- End Tool: MY SQL 8.0, Java
• Editing Tool: Microsoft FrontPage 2016
• Scripting Tool: Java script, XML (style Sheet (.xsl))
• Server: Internet Information Server: (IIS Server), TomCat
DFD 0 level :-
Shiping
Management
Sales
Management
Customer
Management
Custom pc
build
System User
Management
Category
Management
Login
Management
1st LEVEL DFD
Item Code,
Quantity
UserId, User Price PC Parts
Password Validation Purchase
Item Code,Quantity
Price
Stock
Guaranty Management
Card Master
PC Code, Quantity,
BillNo,BillDate
Customer Name
Pc Set Code
Sales Bill
Master
ENTITY-RELATIONSHIP DIAGRAM
Product Code
Company
Address
Phone
Name
Guaranty Card
Bill No
has
Due Date
Has
PC Set
Address
has
Generatd
Customer for
Id
Bill
Customer
Name
amount
Payment amount
DATA STRUCTURE
Table Name: User_Master
Column Name Data Type Constraints Description
PV_No Numeric Primary key Purchase Voucher No
Item_Code Varchar(20) Not null Item Code
Price Varchar(50) Not Null Price
Quantity Datetime Quantity
Total_Price Varchar(15) Total Price
1. Secure Login
2. User Management
3. Item Management
4. Purchase Management
5. Stock Management
6. Sales Management
7. Billing
8. Guarabty Card Management
PROCESS LOGIC OF EACH MODULE
Administrator — He has the privilege of doing any thing with the system.
He and only he has the permission to add new Login Id’s (Employees) to the
system, change passwords, change connection settings and perform any other
function which the application provides.
Clerk — He is responsible for showing all the Details Related with the
Connection,bill Details and updating status of the Purchase, Sales. He/she also
handles Customers queries, which are complicated and are referred by
Customer support executive.
Secure Login
This is the very first module of this Project through which any of the
unauthorized user is checked to be logged in inside the system so that to
maintain only authorized login this module is required. This module helps in
maintaining the security.
User Management
This is an extra module added to the system which enable the
administrator to make the new user and delete the existing user along with the
changing of the password of the existing users.
Item Management
The Item management is the module which is responsible for managing
all the details of items like Item_Code, Item_Name, Purchase_Price, Sale_Price
etc. The new fresh Item can be added to the database, modified the existing
one and deleted not selling Items. This module is related with the master
database of Item not the stock.
Purchase Management
The Purchase Management module is used to manage all the purchasing details
of the items. it stores the details in two table Master & Details. Stores the
details like purchase voucher no, item code, quantity date of
purchase etc.
Stock Management
The stock management maintains the relation between purchase and sales
module. It automatically update the alvailability quantity status of the item
within the stock. When a purchase is done then it increment the purchase
quantity of the corresponding item in stock and decrement the same during
sales of the items.
Sales Management
This module is opposite of purchase module because the quantity of
the product is decreased through this module which gets increased in the
purchase module. One more difference here is that card holder participate in
this
module instead of the supplier which happens in the purchase module.
Billing
Billing is the module which can be said the part of selling moudule and
repairing module because it comes during the sale and repairing of the product.
Whenever the sale or repairing of any mobile set is done then the billing must
Be done and the details of billing is sent to the Sales master & details table of
the database and in case of repairing.
After selling or repaing of a set a guaranty card is issued to the customer for
the future reference during the guaranty period. When a customer comes with
any complain then the customer can only be recognized with the guaranty card.
Report Output:
1) Item purchase report
2) Sales report.
3) Monthly Income Details
4) Annual Income Details
5) Daily payment/income details
LIMITATION OF THE PROJECT
WEBSITE -
1. www.google.com
2. http://www.microsoft.com/en-in/download/
3. http://www.quackit.com/sql_server/sql_server_2005/tutorial/
4. https://www.wikipedia.org/
5. https://stackoverflow.com/