ty cs black book construction - dinesh48

Construction Materials Supplier

1 | P a g e

PROJECT REPORT ON

CONSTRUCTION MATERIALS SUPPLIER

SUBMITTEDBY

NILAM PANASKAR

BACHELOR OF SCIENCE IN

(COMPUTER SCIENCE)

- PROJECT GUIDE –

MRS. DEVI NAIR & MRS. NEHA SAMUEL

S.K. COLLEGE OF SCIENCE AND COMMERCE SEC-25, NERUL (E),NEAR SEAWOODS STATIONNAVI MUMBAI-400706

2011-2012


2 | P a g e

ACKNOWLEDGEMENT It’s a great pleasure to get this opportunity and sincerely thank all the people, who have

showed me the way to create a successful .net project and helped me a lot during the

completion of the project.

I am highly obliged to the teaching and non-teaching staff members of the Computer Science Department who spared efforts in making the project a successful one with their guidance, appropriate advice and encouragement and of course inspiration without which

the project would be ineffective difficult task.

It gives a great pleasure in presenting this project report. It justification will never sound good if I do not express my vote of thanks to our S.K COLLEGE OF SCIENCE AND

COMMERCE.

I sincerely thank and express my profound gratitude and indebtedness to our Project

Guides Mrs. Dhatri(HOD) and Mrs. Neha Samuel for their timely and prestigious guidance required for the project completion at each phase of the project development apart

from the inspiration and motivation.

I also to owe my Friends who have been a constant source of help to solve their problems that cropped up during the development of the project and for being an encouraging and guiding force towards the successful completion of the project.


3 | P a g e

1

PRELIMINARY

INVESTIGATION


4 | P a g e

DESCRIPTION OF THE SYSTEM. INTRODUCTION

Myself Ms.NILAM PANASKAR has developed Software for Construction Materials Supplier

Today’s world is heading towards global computerization And information savvy network. Information should be easily Accessible from anywhere under a secure

protocol with no interference with daily activity of the organization. Thus we can say that computerization eradicates necessary paperwork increase efficiency of workface. But it is fact that in hotel ling

Industry, all transactions are carried out manually.

I tried my level best to develop such software for keeping Records of hotel rooms, other related

information’s about reservations, check in and checkout. This software automates all front desk operations and generates reports. My projects involve database management and reservation, check in and check out procedure of customer.

In this project search criteria is used to search available rooms and customers currently staying in

hotel rooms and also to search other required details. When customer wants a room in hotel, the clerk provides the information about available Rooms by searching. Customer can book a room in Advance or Currently. If customer book a room in advance or currently he will have to pay some advance amount.

customer can book more than one room. So for a room booking he has to fill a form for particular details. If customer cancels the advance reservation then appropriate refund will be given to that customer . when

customer check out the bill will be generated to him according to the room rates, and other charges. customer can pay the bill amount by cash or by credit card.

ions are not included in this system.


5 | P a g e

ADVANTAGES:

1. Speed

2. Easier database & front end compatibility

3. data management

4. Increase in performance

5. Reducing the process time

DISADVANTAGES:

1) If the old customer i.e. who is coming frequently in hotel we cannot retrieve his/her details and

transfer it to the current data store. So we have to again enter customers detail record in the current data store.

2) If customer booking multiple rooms then total room bill is generated And laundry bill and restaurant bill of all rooms is manually entered.

3) Data backup and recovery which are important in power failure and in other such situations are not

included in this system.


6 | P a g e

PLATFORM BEING USED

HARDWARE SPECIFICATIONS

Our system requires: -

10 GB of Hard Disk

128 MB RAM (minimum)

Processor type Pentium-4/AMD photon or onwards

SOFTWARE SPECIFICATIONS

Our system requires: -

Operating System – Windows Xp (or onwards)

Front-end– Visual Studio 2008

Back-end– MS-Access–MS Office 03/07


7 | P a g e

FEASIBILITY STUDY

Technical Feasibility:

Considering the following aspects feasibility study of the system is carried out. The feasibility

study is the deciding factor which determines all technical resources are essential for designing and

developing the system.

Below are the technical resources required for the system development: Hardware Requirement: 1. The client system should have at least 64MB RAM.

2. 50MB of hard disc space should be free. 3. Printer.

Software Requirement: 1. The system will run on windows 2000/ME/XP.

2. Microsoft Office 2000 and later required.

Economic Feasibility:

Economic study is the study of actual cost and benefit of the system. The actual cost of the system is

calculated in the economical study so as to inform the user and management about the system and also about the benefits of the outputs.

So the actual cost of the system is important before designing the new system. One or more factor

regarding after how many years the proposed system would prove beneficial is taken into consideration while designing the system.

The required cost for the newly developed system is low therefore, the system is economically feasible.

Operational Feasibility:

1. Total working hours required will be less.

2. A manpower required for clerical work will be reduced. 3. Reports can be generated in real time.

The system is operationally feasible because of the above tested benefits.


8 | P a g e

STAKE HOLDERS A Corporate stake holder is a party that can affect or be affected by the actions of the

business as a whole.

TYPES OF STAKE HOLDERS:

Internal Stake Holder:

Internal stake holders-Market (or primary) Stake Holders are those that are engaged in economic

transactions with the business.

External Stake Holder:

External stake holders-Non market(or secondary) stake holders are those who although they do not

engaged in direct economic exchange with the business are affected by or can affect its actions


9 | P a g e

TOPIC

PRELIMINARY INVESTIGATION I. ORGANIZATIONAL OVERVIEW

II. DESCRIPTION OF SYSTEM III. LIMITATIONS OF PRESENT SYSTEM

IV. PROPOSED SYSTEM ( Adv. Limitations) V. FEASIBILITY STUDY

VI. GANTT CHART

SYSTEM ANALYSIS I. STAKEHOLDERS

II. FACT FINDING TECHNIQUES III. EVENT TABLE

IV. USE CASE DIAGRAM,SCENARIOUS&USE CASE DESCRIPTION

V. ERD DIAGRAM VI. ACTIVITY DIAGRAM

VII. CLASS DIAGRAM VIII. SEQUENCE DIAGRAM

IX. COLLABORATION DIAGRAM

SYSTEM DESIGN I. CONVERTING ERD TO TABLES

II. COMPONENT DIAGRAM

III. PACKAGE DIAGRAM

IV. DEPLOYMENT DIAGRAM

V. STRUCTURE CHART (PRG LEVEL AND SYSTEM LEVEL)

SYSTEM CODING

I. MENU TREE

II. LIST OF TABLES WITH ATTRIBUTES AND CONSTRAINTS

III. VALIDATION ( coding for validation)

IV. TEST CASES ,TEST DATA AND TEST RESULTS

V. SCREEN LAYOUT & REPORT LAYOUT

SYSTEM IMPLEMENTATION

FUTURE ENHANCEMENTS

CONCLUSION

REFERENCES AND BIBLIOGRAPHY


10 | P a g e

2 SYSTEM

ANALYSIS.


11 | P a g e

2. A) FACT FINDING TECHNIQUE

There are following Fact Finding Techniques

1. Onsite Observation: Observations were done during the first interview with the manager of hotel. It was very useful in

which it help us to understand how hotel system works.

2. Review the existing Document: Various types of documentation were collected. These documents include bill, room reservation form

etc.

3. Interviews: We mainly interviewed the manager or receptionist of hotel. The information provided by both

interviewees was very important because it help in the analysis of the current system and the construction

of the data flow diagrams. In the interview some objectives are considered such as, 1. Determining the areas to be discussed.

2. Listing the facts you want to gather.

4. Questionnaires: A series of questions to be asked is called as Questionnaires.

For Hotel Management System I used Questionnaires technique to gather the information of existing system, it’s a better way to gather the information.

I developed the questionnaires as follows: 1. How the system works or flows? 2. What are room types and their rates?

3. How do you keep a track of all transactions? 4. What parameters you take into consideration while Advance reservation or current reservation?

5. What type of information you take from customer? 6. What is the procedure after canceling advance reservation? According to these Questionnaires the system study is performed and the system is developed.


12 | P a g e

Event Table:-

Event

Trigger Source Action

Response Destination

1) User Login

Look up the

System

Admin

1)check the

username &

password

Login

successfully &

Enter the

system

System

2) Product details

Add,Update,

delete

Admin

1)Add,update,

delete the details

of product with

company name

Add,Update

, delete

completely

Admin

3) Client Details

Look up the

company

Client

1)check the

Client valid

details

Entry for

details

Admin

4) Orders details

Look up the

product

Client

1)client valid

with details

2)check

product details

Place order

Admin

5) Purchase Details

Look up the

product

Client 1)check

purchase details

2)purchase product

Payment for

product

Admin


13 | P a g e

6) Payment

details

Look up the

transaction

Admin

1)check valid

bill details

2)update

payment details

Add, update,

Delete payment

details

Admin

7) Transport details

Look up

delivery details

Driver

1) Deliver the

product

2)give the bill

Receipt

Client

8) Stock details

Look up the stock

details

Admin

1)add, update,

delete the stock

record

Add, update,

delete

successfully

System

9) Supplier details Supplying raw materials details

Supplier 1)check for valid supplier &

valid raw materials 2)supply raw

materials

2)Bill payment

Bill receipt Admin

10)Salary details Add, Update,

delete salary

details

Admin

1)add, update,

delete salary

details of

employees &

drivers

Add, update,

delete,

Successfully

System


14 | P a g e

E-R DIAGRAM

The file system structure is the database structure of the system. It represents the storage system

structure. An ER-Diagram (Entity Relationship Diagram) is a graphical model of the data needed by the

system. This includes the entities about which information is stored and relationships among them. It is

provided in structured analysis methods.


15 | P a g e

E-R Diagram:-

Company

Client

cid cid

address

cname

phno

mobile

email

Comp_name

has

order

Ord_id Pr

o_id

cid

cname

dri_id

quant

rate

Totalamt

place

Product

has Pro

_id

Sup_id

Pro_name

quantity

rate

Pro_size

delivers

supplier

has

Sup_id

Sup_name add

ress

Comp_name p

hno

mobile

email

supplies

driver

has

Dri_id

License_no

email

salary

mobile

Truck_no

doj

dob

Dri_name

address

address

designation

department

Stock

Stock_id

Pro_id

quantity

rate

Pro_name

Stock_date

has

transport

do

Dri_id

Truck_no

Challan_no Pro

_id Or

d_id qu

ant

Comp_name

Comp_add

No_of_trips


16 | P a g e

a

Company

Staff

Driver_details

Works in

ename

eid

phno

mobile

salary

email

doj

dob

Gen_status

Dri_id

Dri_name

salary

email

dob

address

phno

mobile

doj

License_no

Truck_no

salary

Time_period

eid

E_salary

Dri_id

Dri_sal

has


17 | P a g e

ACTIVITY DIAGRAM

Activity diagram-1

Admin

Login

Successfull login

yes

check login details

back to loginno


18 | P a g e

Activity-diagram-2

Customer

Place order

Admin

confirm order

arrange product

dispatch product

payment

bill receipt

check product availability

yes

No


19 | P a g e

Activity-diagram-3

Admin

order raw materials

supplier

confirm order

dispatch materials

payment

check details

yes


20 | P a g e

Use Case Diagrams:-

Use-case diagram-1

Use-case diagram-2

System

Admin

Login

checking login details

<<uses>>

System

client

admin

check order details

accept order

bill payment

dispatch product

place an order

receipt


21 | P a g e

Use-case diagram-3

System

Admin Supplier

Order for raw material

Accept the order

Check availability

Supplies raw material

Payment


22 | P a g e

Use-case diagram-4

Use-case diagram-5

System

Admin Driver

Products

Transport details

Driver Daily payment

System

Driver

Client

give Products

Check product details

Accept Products

Challan receipt


23 | P a g e

Use-case diagram-6

System

Admin

Employee details

Client details

Driver details

Supplier details

product details


24 | P a g e

2. F) CLASS DIAGRAM A class diagram is an illustration of the relationship & source code dependencies among class

in the unified modeling language. Class diagram are useful in all forms of object-oriented programming.


25 | P a g e

a. Sequence Diagram:-

Sequence-diagram-1

ClientAdmin

1 : Place order()

2 : Check & accept order details()

3 : sell product with bill details()

4 : Check & accept product()

5 : Bill payment()

6 : Check & accept bill details()

7 : Dispatch product()


26 | P a g e

Sequence-diagram-2

Admin Supplier

1 : Order for raw materials()

2 : Check availabilty & accept order()

3 : Supply raw materials with bill()

4 : Check & accept materials details()

5 : Bill Payment()

6 : Dispatch materials()


27 | P a g e

Sequence diagram-3

driveradmin client

1 : give product()

2 : deliver product()

3 : check & accept product()

4 : challan receipt()

5 : challan receipt()

6 : driver payment()

7 : bill payment()

8 : receipt()


28 | P a g e

Collaboration Diagram:-

8) Delivers the product(crushed stones)

1) Place an order

7)Crushed stones 6)supplies raw material

Crush the stones

If not available,

5)ask the supplier for raw materials if available 2) Check for product availability 9) manages employees details,salaries

Company

Client

Driver

Product Employees

Supplier


29 | P a g e

3

SYSTEM

DESIGN.


30 | P a g e

a) Converting ERD to Tables:-

1) Table name- Login

Column name Data type Constraint

username varchar(20) Not null

password varchar(20) Not null

2)Table name- Product_details


pro_id Int Primary key

pro_name varchar(10) Not null

pro_size Int Not null

rate Money Not null

quantity Int Not null

sup_id Int Foreign key

3)Table name- Client_details


client_id Int Primary key

client_name varchar(20) Not null

comp_name varchar(20) Not null

address varchar(70) Not null

ph_no varchar(8) Not null

mobile varchar(10) Not null

email varchar(30) Not null


31 | P a g e

4)Table name- order_details Column name Data type Constraint

ord_id Int Primary key

pro_id Int Foreign key

client_id Int Foreign key



rate Money Not null

dri_id Int Foreign key

5)Table name- supplier_details Column name Data type Constraint

sup_id Int Primary key

sup_name varchar(20) Not null







32 | P a g e

6)Table name- transport_details


challan_no Int Primary key

truck_no varchar(10) Not null

no_of_trip Int Not null

trans_cost Money Not null

petrol Int Not null



ord_id Int Foreign key

dri_id Int Foreign key


comp_add varchar(70) Not null

7)Table name- driver_details

Column name Data type constraint

dri_id Int Primary key

dri_name varchar(20) Not null


doj Datetime Not null

dob Datetime Not null

license_no varchar(20) Not null


salary Money Not null





33 | P a g e

8)Table name- stock_details


stock_id Int Primary key




rate Money Not null

stock_date datetime Not null

9)Table name- bill details


bill_id Int Primary key

bill_date datetime Not null



ord_id Int Foreign key

ord_date datetime Not null

client_id Int Foreign key



rate Money Not null

trans_cost Money Not null


challan_no Int Foreign key


no_of_trip Int Not null

pay_details varchar(10) Not null

tot_amt Money Not null

chq_no varchar(10) Not null

branch varchar(10) Not null

advance Money

balance Money


34 | P a g e

10)Table name- employee_details


emp_id Int Primary key

emp_name varchar(20) Not null


designation varchar(10) Not null

dept_name varchar(10) Not null

ph_no varchar(8)

mobile varchar(10)

email varchar(30)

dob datetime Not null

doj datetime Not null

gender char(6) Not null

salary Money Not null

11)Table name- salary details


emp_id Int Foreign key

emp_name varchar(10) Not null

no_of_days Int Not null

daily wage Money Not null

total days Int Not null

days_absent Int

tot_sal Money Not null

gross pay Money

advance Money

net pay Money

doj datetime Not null

extra days Int

overtime payment Money


35 | P a g e

b) Component diagram:-

Admin

Client

Supplier

Order Driver Company


36 | P a g e

c) Package diagram:-

company

Products

Person

Purchase raw

materials

Sell the product(crushed

stones) Client Supplier

Employee

Driver


37 | P a g e

d)Deployment diagram:-

Databa

se server

Process server

Printer

Client-

order

process


38 | P a g e

E) System Flow Chart:-

Company

Client

Product

Supplier

Bill

Maintaining

client details

Maintaining

product details

Maintaining

supplier details Maintaining

bill details

Client

report

Product report

Supplier

report

Bill

report


39 | P a g e

f) Structure Chart:-

Company

Admin

Add

product

Search

product

Purchase of raw

material

Sale

of product

Stock

details

Add

client

Add

employee Add

supplier

Generate Report

details


40 | P a g e

4

SYSTEM

CODING.


41 | P a g e

V

Screen Layout & Reports


42 | P a g e

Login Form


43 | P a g e

Home Page


44 | P a g e

Stock Details


45 | P a g e

Product Detail


46 | P a g e

Sales Details


47 | P a g e

Purchase Details


48 | P a g e

Payment Details


49 | P a g e

Customer Details


50 | P a g e

Supplier Details


51 | P a g e

Purchase Detail Report


52 | P a g e

Supplier Detail Report


53 | P a g e

Bill Detail Report


54 | P a g e

Bill Detail Report


55 | P a g e

SYSTEM IMPLEMENTATION

1. Operating system should be Windows XP or above

2. Install Visual Studio 2008.

3. Attach database to Access 2008. 4. Copy the project files on the Machine.


56 | P a g e

Future Enhancements

For any system that is developing, there is always room for more development.

Following are some of the feature that can be enhanced or include in future version of system.

1) Data backup and recovery options.

2) There will be facility of transferring the master record of the customer to the current data store if he visits again.

3) bills which are manually entered that will be system generated in next Version.


57 | P a g e

7

CONCLUSION


58 | P a g e

Conclusion

CONSTRUCTION MATERIALS SUPPLIER was made such that the problems faced by the consultancy with its meeting the requirements would be over. The burden of the manually done activities was made easy with the development of the system. The user can view the data and performance analysis

can be done.

The main aim of the project was to provide required amount of reporting tools with a back end that can

handle ample amount of data.

The developed system:

1. Maintains a record of employees, customers, services, and events which are organized.

2. Tracks data about reports & orders sent & received.

3. Generates bills, receipts, reports.

Thus the “CONSTRUCTION MATERIALS SUPPLIER” is an effective and efficient system fulfilling the needs required by an organization.


59 | P a g e

BIBILIOGRAPHY REFRENCES:

ty cs black book construction - dinesh48

Software

project completion

project development

project guides

successful net project

project search criteria

procedure of customer

room rates

college of science