PRI

Published on May 2016 | Categories: Documents | Downloads: 26 | Comments: 0 | Views: 811
of 36
Download PDF   Embed   Report

Comments

Content

1.

INTRODUCTION

“PRODUCTION AND ADMINISTRATION MANAGEMENT SYSTEM” has been developed for Arthi Traders, Coimbatore. The Arthi range of solar water heaters has helped thousands of home owners and businesses to enjoy the benefits of the Solar Water Heater. It has earned a reputation of high performance with durable design while assuring trouble free maintenance with maximum savings. The person who wants to buy a Arthi water heater can join as a member in his system through registration. After deciding the model, capacity and operating temperature user can order the desired model. Based on payment agreement one can buy a Arthi Water Heater. After sales the service will conduct through e-mail easily. This system will increase the number of customers all over the world in a short time.

1

1.1 ORGANIZATION PROFILE
Arthi Trades was started by a group of technocrats in the year 1992 executed the first commercially successful Solar Water Heating project during the year. Formerly known as M/s.Associated Engineers, later it was renamed as “Arthi Trades Pvt Ltd” lead by Mr.R.Ravi as the Managing Director. Several innovations and improvements have been made in the design & development of Solar Water Heaters so far and still, the R&D efforts are in full swing to bring in better changes towards improvement of overall performance of every unit. The company is emerging as a one-stop shop for complete hot water / Pre-heating solutions through solar energy. The motto is to create new ideas and techniques to improve the quality and performance of the product. The products manufactured by the company are as per BIS, ISO, CETL, norms. The Solar water heaters ranging from 100 liters to 1, 00,000 liters capacity per day. The company is capable of designing and executing models like non motorized heater exchanger models for hard water application without any pumps. This is a unique system and achievement by an Indian company.

2

Company is having various in-houses departments as per ISO procedures adapted as mentioned below. • • • • • • • • Personal Dept Accounts Dept Marketing Dept Service Dept Design Dept Production Dept Stores Dept Quality control Dept The company is having marketing operation throughout India with branches at Tamil Nadu, Kerala, Andhra and Karnataka. Apart from regional Business Associates in and around south India. The company is also planning to open branches at Delhi, Mumbai, Calcutta, pune, and Ahamedabad. The main aim of the organization is to offer world class products and service in Solar Water Heater system and aspires to become the prime source in India for solar water heaters.

3

1.2 SYSTEM ENVIRONMENT
The system has been developed in Visual Basic 6.0 as front end and Microsoft Access as back end. The Specifications are listed below. 1.2.1 HARDWARE SPECIFICATION: Processor Motherboard Speed Main memory Hard disk DVD drive Key board Mouse : : : : : : : : Intel core 2 duo processor Intel graphics media Accelerator 950 1.6GHz 512MB 160GB DVD-super multi double layer Multimedia Logitech Optical Logitech

1.2.2 SOFTWARE SPECIFICATION: Operating system Front end Back end : : : Windows-XP Visual Basic version 6.0 Microsoft Access

4

1.3. SOFTWARE FEATURES

VISUAL BASIC 6.0: Visual basic 6.0 is an integrated development in which user can develop, run, test and debug event driven applications. It is a window based environment for the clientserver application development. It allows connection to a wide range of backend database systems such as MS-Access, SQL Server, and Oracle etc. FEATURES:  Data access features allows to create database front end application and scalable server side components for more popular database formats.  Active-X technologies allow to use the functionally provided by their application such as MS-WORD, MS-Excel, and other window applications.  Graphical user interface have revolutionized effect on the Micro Computer Industry.  User Friendly.  Easier Comprehension and faster application development.  Client-server architecture benefits.  Provide simple debugging.  Built-in database support.

5

MICROSOFT ACCESS

Microsoft access allows us to manage all our information from a single database file. It is a relational data base management system. The data is a represented as two dimensional tables. An access data base includes various objects like tables, forms, queries, reports etc. Access is a multi-featured data base management system that can be used by both the beginners and those who have previous data base management system experience.

FEATURES

 Visual Basic integrated development features.  Shares Microsoft Office programmability.  Quick data base development and debugging process.  Importing, Exporting and linking external files.  Builts-in function.  Large data management capacity.  Context-sensitive help and answer wizards and builders

6

2. SYSTEM SYUDY AND DESIGN
2.1 EXISTING SYSTEM:
The Exiting system processing is going on with manual entries and maintenance which all paper modes and that can’t be well sophisticated to avoid this we can go upon the proposed system. The existing system has its own inefficiencies as it makes use of manpower. Customer are said to be the kings of any concern according to the entrepreneurs view. The main aim of the business is making the profits and this can only be done when the organizations gain the customer satisfaction.

DRAWBACKS OF EXISTING SYSTEM • • • • • • Manual work. Security of information is low. A lot of time is consumed. Needs a lot of man power. Frequent occurrence of errors. Calculations are difficult.

7

LIMITATIONS OF EXISITING SYSTEM • • • • • It is not computerized and hence not systematic. Lack of database security. Same data are stored in more than one location. Access speed is less for searching and modifying data. It cannot have efficient management.

8

2.2 SYSTEM DESIGN
2.2.1 LOGICAL DESIGN The Logical Design reviews the present physical system, prepares Input Output specification. The tools used are: 1. Context Analysis Diagram. 2. Data Flow Diagram. 3. Entity Relationship Diagram

9

2.2.1.1 CONTEXT ANALYSIS DIAGRAM

The context analysis diagram has entity, data flows and the process. It depicts the processing of every data through the entity for the delivery of the output. Context Analysis Diagram for “PRODUCTION AND ADMINISTRATION MANAGEMENT SYSTEM.

Party PARTY PRODUCT PURCHASE SUPPLIER Details Product Details Purchase Details Supplier Details Sales Details Production Details Report Administration Details

PRODUCTION AND ADMINISTRATION

SALES

PRODUCTION

Fig 2.2.1.1 CAD for Administration and Production Management
10

2.2.1.2 DATA FLOW DIAGRAM Data flow diagram is a way of expressing system requirements in a graphical form which leads to a modular design. They have purpose of clarifying system requirements and identifying major transformations .They functionally decomposes the requirements specification down to the lowest level of details. They are independent of hardware, software, data structure or file organization. Data flow Diagram for “PRODUCTION AND ADMINISTRATION MANAGEMENT SYSTEM”is shown in the figure 2.2.1.2(a), 2.2.1.2(b), 2.2.1.2(c), 2.2.1.2(d), 2.2.1.2(e), 2.2.1.2(f).

Retrieves PARTY Party Details

1.0 Party details process

Stores Party Details Party Data

Fig 2.2.1.2 (a) Data Flow diagram for Party details

11

Retrieves ITEM Item Details TDetails

2.0 Item details process

Stores Item details Item data

Fig 2.2.1.2 (b) Data Flow diagram for item details

Retrieves SUPPLIER Supplier details

3.0 Supplier details process

Stores Supplier details Supplier data

Fig 2.2.1.2 (c) Data Flow diagram for Supplier details

12

Retrieves
PRODUCTION

Production details

4.0 Productio n process

stores Production details Production Data

Fig 2.2.1.2 (d) Data Flow diagram for Production details

Retrieve SALES Sales details

5.0 Sales details process

Store Sales Data Sales details

Fig 2.2.1.2 (e) Data Flow diagram for Sales details

13

Retrieve

Purchase
Purchase details

6.0 Purchase details process

Store Purchase Data Purchase details

Fig 2.2.1.2 (f) Data Flow diagram for Purchase details

14

2.2.1.3 ENTITY RELATIONSHIP DIAGRAM Entity Relationship Diagram is a way of representing the relationship among the entities defined by a data structure. Relations may vary from one to one. Many to one, one to many, many to many. The Entity Relationship Diagram for “ADMINISTRATION AND PRODUCTION MANAGEMENT SYSTEM”

Fig 2.2.1.3. ENTITY RELATIONSHIP DIAGRAM

Ph..No Addres s Cust.n o
Cust Name
Cust

Order no no Plac e 1 Order 1 1.1 = One to One 1-M = One to Many M-1 = Many

Customer 1

1

Receivin g

produ ct

M Bill
Cust

1 Supplier Bill no

1
Supplier s

M Item

M

name Price

Suppl no Item name Suppl add

Item no Item name

Rate

15

2.2.2 PHYSICAL DESIGN
Physical Design enables to determine input function format, Content, Frequency of reports including the terminal specification. 2.2.2.1 DATABASE DESIGN A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective is to make information access easy, quick, inexpensive, and flexible for the user. The database contains tables, where each table corresponds to one particular type of information. Each piece of information in table is called a field or column. A table also contains records, which is a set of fields. All records in a table are having the same set of fields with different information. There are primary key fields that uniquely identify a record in a table. There are also fields that contain primary key from another table is called foreign.

16

TABLE STRUCTURE Table Name Purpose : CUSTOMER : This table maintains the Customer details

Primary Key : Cus_code

FIELD Cus_code P.No Cus_name Cus_Address Dot Gen Mid

DATATYPE Int Text Text Text Int Text Text

DESCRIPTION Customer Code Phone Number Customer Name Communication Address Land Line Phone Number Gender Member Id

Table Name Purpose

: SUPPLIER : This table maintains the Supplier details

Primary Key : sup_no FIELD DATA TYPE DESCRIPTION

17

Sup_no Sup _name Sup_address Sup_phone

Int Text Text Int

Supplier Number Supplier Name Supplier Address Phone Number

Table Name Purpose FIELD PCode MoCode PName

: PRODUCT : This table maintains the product details. DATATYPE Text Text Text DESCRIPTION Product Code Model Code Product Name

Table Name Purpose

: PURCHASE : This table maintains the purchase details

FIELD PInvno Rcsno Cmcode PQty Prate Pamt Siid

DATATYPE Int Int Text Int Decimal Decimal Int

DESCRIPTION Invoice Number Serial Number Component Code Purchase Quantity Purchase Rate Purchase Amount Stock Inward Id

18

Table Name Purpose Primary Key FIELD Modcode Modname

: MODEL : This table maintains the model details. : Modcode DATATYPE Text Text DESCRIPTION Model Code Model Name

Table Name : SALES Purpose : This table maintains the Supplier details

19

FIELD SBno SSno Pcode SQty Sprice SAmt

DATATYPE Int Int Text Int Decimal Decimal

DESCRIPTION Sales Bill Number Sales Serial Number Product Code Sales Quantity Sales Price Sales Amount

Table Name : STOCK Purpose FIELD Siid Sidate Rccid StkQty : This table maintains the Stock detail DATATYPE Int Date Int Int DESCRIPTION Stock Inward Id Stock Inward Date Product Id Stock Quantity

20

Strans

Text

Stock Transaction

Table Name : CAPACITY Purpose FIELD CapCode CapDesc : This table maintains the capacity details. DATATYPE Text Text DESCRIPTION Capacity Code Capacity Description

Table Name : PRODUCT Purpose : This table maintains the product details.

21

FIELD PCode ModeCode PName

DATATYPE Text Text Text

DESCRIPTION Product Code Model Code Product Name

22

2.2.2.2 INPUT DESIGN Input design is the process of converting user-originated inputs to a computerbased format. After input data are identified, appropriate input media are selected for processing. In the system design phases, the expanded data flow diagram identifies logical data flows, data stores, source and destinations. Input data are collected and similar data. In this project the input is through text boxes, combo boxes, and text area. So in the input design the following things are considered.  What data should be given as input?  How the data should be arranged or coded?  The dialogue to guide the operating personnel in providing input.  Methods for preparing input validations and steps to follow when error occur. The samples of screen inputs are given in the appendix.

23

Form Name: Company Details Description: It maintains the Company Master

Fig 2.2.2.2 (a)

24

Form Name: Capacity Details Description: It maintains the Capacity Master

Fig 2.2.2.2 (b)

25

Form Name: Customer Details Description: It maintains the Customer Master

Fig 2.2.2.2 (c)

26

Form Name: Purchase Details Description: It maintains the Purchase Master

Fig 2.2.2.2 (d)

27

Form Name: Sales Details Description: It maintains the Sales Master

Fig 2.2.2.2 (e)

28

Form Name: Supplier Details Description: It maintains the Supplier Master

29

Fig 2.2.2.2 (f)

2.2.2.3 OUTPUT DESIGN Computer output is more important and direct source of information to the user. Efficient, intelligible output design should improve the system’s relationships with the user and help in decision making. A major from of output is hard copy from the printer. Printout should be designed around the output requirements of the user. The output devices to consider depend on factors such as compatibility of the device with the system, response time requirements, expand print quality and number of copies needed. In this project, the output is displayed on the screen as form and also stored in the proper database. The following things are to be considered.  Determine what information to be presented.  Arrange the presentation of information in an acceptable format.  Decided how to distribute the output to intended receipts.

30

REPORTS

Report name : Supplier Details Description : This form contains the bill details

SUPPLIER DETAILS

SCode R001 C001 U001 G001

Sname R.R ENGINEERS COIMBATORE TUBE CO., UNITED TOOLS CORPORATION GEETHA AGENCIES

Saddress1 10, 4th Street, Bharathi Nagar 290, Dr. Nanjappa Road, 81-A, Regal Complex, Park st. 128, Alagesan Road,

Scity Coimbatore Coimbatore Coimbatore Coimbatore

Sphone 251051 0 223548 3 223424 0 230104 4

Suppitem EPDM Products PIPES, FITTINGS PIPES, FITTINGS Packing Material PIPE PIPE Rubber

31

Fig 2.2.2.3. (a)

Report name :Customer Details Description : This form contains the customer details

CUSTOMER REPORT

ccode

cname

Company Name
PRIYA

Address

Dist

Total Payable

CUS1 CUS2 CUS3 CUS4 CUS5

Mr.MOHAN Mr.PALANISAMY Mr.S.RAJA Mr.SUNDHARAM Mr.NAGARAJAN

TEXTILES MOHAN TEX. RAJA TEX. KUMAR TEXTILES DEVI TEX.

R.N.ROAD P.N.ROAD VIDUDHALAI NAGAR PALLADAM INDUSTRIAL ESTATE

CBE TIRUPUR CHENNAI TIRUPUR CBE

17,000.00 25,489.00 45,000.00 17,756.00 17,500.00

32

Fig 2.2.2.3. (b)

Report name : Sales Details Description : This form contains the Sales details

SALES REPORT

Bill No 001 002 003

SDate 4.3.2008 12.3.2008 23.3.1008

Customer Name R.Sumi S.Kannan S.Mohan

Product Name Regular Regular Regular

Price

Quantity

Amount

43000 40000 55000

5 3 2

215000 120000 110000

Fig 2.2.2.3. (c)

33

CONCLUSION
The developed system is highly interactive and user friendly. Reports have been generated so that it statistics the user requirement to the maximum extent possible the system provides accurate results. The new system successfully overcomes most of the limitations of the manual system. Change over is the stage of moving over from the old manual system to the newcomputer based systems. This is very difficult task to achieve quickly and accurately. They are given user manual, which explains, how to use the systems and all the exceptions handling procedures. After this the newly developed system is run with the existing system. The system has been designed and developed according to the current requirements of the user, which may subject to the changes in the near future. The system can be upgraded and modifications can be incorporated in a flexible manner so as to reflect the new requirements. The modular approach and the programming technique incorporated during the development of the system will be of grant help for future enhancement. In Future it can be extended as a Dynamic website.

34

BIBLIOGRAPHY

1. David Jerry Jeff, “VISUAL BASIC 6.0”, Tata Megraw Hill Publication,Second Edition. 2. Gary Corner,”VISUAL BASIC 6.0”,Tata Mcgraw Hill Publication, First edition. 3. Ali 4. Peter 5. Rogers Behforooz, Rob, Carlos Fredrick.J.Hudson Cornel, “SOFTWARE SYSTEM ENGINEERING DESIGN AND FUNDAMENTALS”, Galgotia Publication Second Edition. “DATABASE IMPLEMENTATION SYSTEM”,First edition. S.Pressman, “SOFTWARE ENGINEERING”,Tata McGraw-Hill Publications,Fifth edition, 2007.

WEBSITES

1. 2.

WWW.schools//basic of visual basiconlineexamples//.com WWW.tutorial.com//tutorial/visualbasic/

35

3.

WWW.developerfusion.co.uk/vb

36

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close