UML DIAGRAM FOR

NEEDO LOCATOR
Project Guide
Prof.Rahul Navle Sir

Pratik Rodi
22352
ER Diagram
Class Diagram
Use case for system
Needolocator
Use case for Admin
Admin
Use case for Customer
Customer
Use case for serviceman
serviceman
Activity diagram for system
Activity diagram for customer
Activity diagram for serviceman
Activity diagram for Admin
Sequence diagram for system
Component diagram for System
Admin table

Field Name Datatype Size Constraints

A_Id int 4 Primary key

A_Password Varchar 8 Unique key

A_Name Varchar 20 Not null

Serviceman table

Field Name Datatype Size Constraints

S_Id int 4 Primary key

S_Password Varchar 8 Unique key

S_Name Varchar 20 Not null

S_Email Varchar 20 Unique key

S_Mno Int 10 Unique key

S_Type varchar 25 Not null

customer table
Field Name Datatype Size Constraints
C_Id int 4 Primary key
C_Password Varchar 8 Unique key
C_Name Varchar 20 Not null
C_Email Varchar 20 Unique key
C_Mno Int 10 Unique key
C_Adress varchar 25 Not null

Service table
Field Name Datatype Size Constraints
Se_Id int 4 Primary key
Se_Name Varchar 20 Not null
Se_Category Varchar 20 Unique key
Se_Details Varchar 30 Not null
Se_Amount float 20 Not null
Service Report table
Field Name Datatype Size Constraints
Se_Id int 4 foreign key

Se_Name Varchar 20 Not null

Se_Category Varchar 20 Unique key

Se_Details Varchar 30 Not null

Se_Amount float 20 Not null

C_Id int 4 foreign key

C_Name Varchar 20 Not null

S_Id Int 4 foreign key

S_Name Varchar 20 Not null

P_Date varchar 10 Not null

Payment table
Field Name Datatype Size Constraints

P_Id Int 10 Primary key

P_Date Varchar 10 Not null

C_Id Int 10 Foreign key

Se_Id int 10 Foreign key

Se_Amount float 10 Not null

Thank You