LG SERVICES

A

REPORTON

“LG SERVICES”SUBMITTED TO PUNJAB TECHNICAL UNIVERSITY

JALANDHAR

In partial fulfillment of the requirement for the award of degree ofBachelor of Computer Applications

SESSION (2010-11)Under the Guidance of Submitted by:Mrs. Amandeep kaur Aman preet singh Miss. Vasudha 81401219003Lect.in(Computer Application)

APEEJAY INSTITUTE OF MANAGEMENTHOSHIARPUR ROAD, RAMA MANDI,

JALANDHAR

Economical Feasibility:Economical Feasibility:

The cost of acquiring the proposed system is not too high. The agency already has the suitable hardware with them. Even the software is already available with them. So it creates no extra burden on agency. System is developed in Visual Basic and in MS Access which are both advances in feature.

Operational feasibility:Operational feasibility:

The main objective here is to determine whether the system will work after it is developed and installed. A proper investigation was done in this regard and as a result, the following conclusions were derived:

* There was sufficient support from the management and the personnel involved.* As it automates the automobile agency system completely, so the system becomes more efficient.* The persons involved in the current working of the system were met and discussions were held with them to evolve a system with which they had good support and participation.* The repetitive work of the currently manual system is eliminated.

Technical feasibility:Technical feasibility:

The necessary technologies that are required to implement the proposed system are available easily in the software market. The main hardware equipments such as computers, printers, etc. are easily available. The software of VB is easily available in the market. VB is a tool that allows us to develop Windows based applications. So user feels very comfortable with it. Microsoft Access is a powerful program to create and manage our databases. It has many built in features to assist us in constructing and viewing our information. Access is much more involved and is a more genuine database application than other programs such as Microsoft Works.

Since visual basic is an event driven programming we used this tool to optimize our project.

We used the toolbox containing the object and controls, which we will add to the form to create the user interface for your project. Controls like command buttons, text boxes, radio buttons, check boxes, Adodc controls, data combo, data grid, frames, labels, image control, drive list box are present on the toolbox, also known as OCX files. He Form Designer window contains the form on which the controls and objects are going to be placed. Your application can have more than one form.

We used Access as backend to build our simple Payroll System. All tables are designed in Access for our project.

The database needs to be designed in an appropriate manner. This includes

The use of "Primary Keys" in each table Making sure that you use "Auto Numbers" where appropriate and normal numbers where you what to enter the information

manually Using the correct field type.

‘0’ LEVEL DFD

BILL PAYMENT SERVICE COMPLAINT INQUIRY FOR PRODUCT PAYMENT DETAILS OF PRODUCTS REQUEST FOR STOCK REQUEST FOR PRODUCT SUPPLY PRODUCTS RECEIVE PRODUCT BILL GENARATION BILL CHECK GENERATION STOCK REQUEST FOR PRODUCTS BILL ACCEPT RECEIVE ORDER RECEIVE PRODUCTS PAYMENTS DETAILS

LG SERVICES

CUSTOMER

SUPPLIER

OWNER

‘1’ LEVEL DFD SUPPLIER PURCHASE DATABASE DATABASE SUPPLIERS RECEIVE SUPPLIERS CODE DETAILS SUPPLIERS & DETAILS DETAIL PRODUCT DETAIL CUSTOMER CUSTOMER ID DETAIL DATABASE CUSTOMER DETAILS REQUEST FOR STOCK REQUEST FOR PRODUCT ACCEPT ORDER ENQUIRY ENQUIRY RECEIVE DETAILS PRODUCT DETAILS REQUEST FOR STOCK RECEIVE PRODUCTS GIVE PAYMENTS RECEIPT DETAI- SUPPLY L PRODUCTS RECEIVED RECEI- RECEIPT VED PROVIDE PRODUCTS PAYMENT RECEIVED RECEIVE PRODUCTS CHECK FOR STOCK CUSTOMER & PRODUCT DETAILS SALES DATABASE REQUEST RECEIVED DETAILS DETAILS RECEIVE DETAIL PAYMENTS TO SUPPLIERS PAYMENTS FROM CUSTOMER STOCK DATABAE RECEIVED RECEIPT GIVE RECEIPT

PURCHASE 1.0

OWNER SUPPLIER CUSTOMER

MODE OF PAYMENTS 2.0

SALES 2.0

STOCK PROCESSING 2.0

‘2’ LEVEL DFD (PURCHASE 1.0) ACCEPT ORDER ORDER FOR PRODUCTS ACCEPT ACKNOWLED- ACKNOWLEDGEMENT GEMENT

SUPPLY BILL PRODUCTS DETAILS ACCEPT RECEI- PAYMENT VE PRODUCTS STOCK DETAILS GIVE PAYMENTS RECEIPT DETAILS CHECK FOR STOCK PAYMENT DETAILS MODE OF PAYMENT DATABASE RECEIVE PAYMENT DETAILS SUPPLIER ID SUPPLIER DETAILS SUPPLIER DATABASE REQUEST FOR STOCK DETAILS RECEIVE STOCK DETAILS STOCK DATABASE

OWNER

SUPPLIER

ORDER PROCESSING 1.1

MODE OF PAYMENT 1.3

STOCK PROCESSING 1.2

‘2’ LEVEL DFD (SALES PROCESS 2.0)

ENQUIRY ENQUIRY DETAILS PROVIDED DETAILS RECEIVED ACCEPT ORDER GIVE ORDER GIVE PRODUCT RECEIVE PRODUCT PAYMENT RECEIVED PAYMENT CHECK STOCK RECEIVED GIVE RECEIPT RECEIPT PROVIDE DETAILS CUSTOMER ID DETAILS CUSTOMER RECEIVE CUSTOMER DATABASE DETAILS PAYMENT RECEIVE PAYMENT DETAILS DETAILS MODE OF PAYMENT DATABASE REQUEST FOR RECEIVED DETAILS STOCK DETAILS OF STOCK STOCK DATABASE

OWNER

CUSTOMER

ORDER 2.1

STOCK PROCESSING

MODE OF PAYMENT 2.3

‘2’LEVEL DFD (SERVICE PROCESS 3.0) ACCEPT COMPLAINT COMPLAINT PROVIDE SERVICE RECEIVE AUTOMOBILE PAYMENT PAYMENT CHECK DETAILS STOCK BILL GIVEN BILL RECEIVED GIVE

DETAILS DETAILS CUSTOMER DETAIL CUSTOMER ID DATABASE PAYMENTS RECEIVE PAYMENT DETAILS DETAILS MODE OF PAYMENT DATABASE REQUEST STOCK DETAILS RECEIVE STOCK DETAILS

STOCK DATABASE

COMPLAINT PROCESSING 3.1

MODE OF PAYMENT 3.3

CUSTOMER

STOCK PROCESSING 3.2

OWNER

E-R DIAGRAM FOR AUTOMOBILE AGENCY AUTOMATION

PRODUCT

SUPPLIER

CUSTOMER

SALES/ PURCHASE

PURCHASE SALES

P_PRICE

P_QUALITY

P_COLOR

P_MODEL

P_CHASIS NUMBER

C_NAME

C_CONTACT NUMBER

S_ID

S_NAME

S_ADDRESS

S_CONTACT NUMBER

C_ADDRESS

C_ID

1.LOGIN DATABASE

2. PURCHASE DATABASE

3. SALES DATABASE

4. SUPPLIER DATABASE

5.CUSTOMER DATABASE

6.PRODUCT DATABASE

1. LOGIN FORM

2. NEW USER FORM

4. MAIN FORM

5.CHANGING PASSWORD FORM

6.PURCHASE INFORMATION FORM

7.SALES INFORMATION FORM

8.Dynamic Form of Customer/Supplier

9.SUPPLIER INFORMATION FORM

10.CUSTOMER INFORMATION FORM

11.PRODUCT INFORMATION FORM

12.MDI FORM

13.MODELS FORM

13. MODELS FORM

14.PLEASURE FORM

LOADING OUT FORM

1.REPORT ON PURCHASE

2.REPORT ON SALES

3.REPORT ON SUPPLIERS

4.REPORT ON CUSTOMERS

5.DYNAMIC REPORT OF CUSTOMER

5.DYNAMIC REPORT OF SUPPLIER

TESTING

The testing of various modules is done at various stages of development process. The golden rule to be kept in mind while testing is that the testing should be done with a view to identifying the ways to in which system is likely to fail.

NEED FOR TESTING

Testing is vital to the success of the system. Testing has the logical assumption that all the part of the system is correct and the goal is successfully achieved.

LEVELS OF TESTING

1. Unit Testing2. Integration testing3. System testing4. System acceptances

USERS NEEDSACCEPTANCE TESTING

REQUIREMENT SYSTEM

DESIGNINTEGRATION TESTING

CODE UNIT

These different levels of testing attempt to detect types of faults. The relation of faults introduced in different phases and different levels of testing are shown here.

1. UNIT TESTING

For my project I performed this testing by running each form separately and encountered many errors. Most of which were type mismatch, data source not found, linking errors, end of file encountered, problem with loops etc.

2. INTEGRATION TESTING

The second level of testing is often called integration testing. In this, many testing modes are combined into sub system, which are tested .The goes here is to see if the modules can be integrated properly, the emphasis being on the testing interface between modules. During this also I encountered a number of problem ranging from the similar type of problems as above to new kind of problems mainly updating.

3. SYSTEM TESTING

The next level of testing is the system testing. Here the entire software system is tested. The reference and the goal are to see if the software meets its requirement. This is essentially a validation exercise.

This level of testing is performed with realistic data to demonstrate that software is working satisfactory. Testing is on external behavior of the system. The internal logic is not emphasized.

4.ACCEPTANCE TESTING

TEST CASES

Verification and validation of each field

1. Check for invalid data type of each field.2. Check for wrong id or name of the entity.3. Check for incomplete entry in case of storing data in the database.4. Check for entering numeric and characters where required.

Other checks:

1. Display message if record does not exist.2. Display message if the table s empty.3. Display message when an item is successfully issued.

SUPPLIER FORM

CUSTOMER FORM

CONCLUSION

This project is a computerized version of the existing lg services. Using MS-Access as back end and visual basic as front end developed this software. The project is software capable of conducting computerization of lg services viz includes information of the suppliers, generating data reports etc .The search modules of this project help the end users to easily search for suppliers and information etc. the data access using this project is very fast. The project also has a distinct feature of report generation. Various reports related to suppliers, customer, etc can be effectively generated. This project includes all the features needed for effective and accurate working of office staff.