You are on page 1of 45

SYNOPSIS

This project “MOBILE SALES AND SERVICE SYSTEM” maintains the sales and service activities of the company. The task of this organization is to communicate with make the customers to provide them a very much user interface to get their needs. The project allows the administrator to take easy reports and the sales and service details of the company are maintained very well and easy at any time. The main advantage of the system is to make available everything on the just clicking way.

The numbers of products are maintained to satisfy timely. The details are also made available even for the customer to take advantage over explain about the products to the enquiring persons. So when the Customers entered they are very much satisfied for their Time saving activity in the fast moving world.

INTRODUCTION

1.1About the Project
“Mobile Sales & Service System” is used to store the details of the purchase and sales and their orders. The quotation details can be created here to make the users easily verify the details of the task.

The project is suitable for all types of users because its interface is natural and it can be helpful for those people that have not got great skills in interacting with a computer. Here we maintain the details of the employee work allotment for further reference.

Most wearable computers today derive their interfaces from concepts in desktop computing such as keyboards, pointing devices, and graphical user interfaces. If wearable computers are expected to become as natural as clothing, we must re-examine the interface with different standards of usability.

The reports on the modules can be derived for the users to take a hard copy with them. The project minimizes the problem of forgetting important appointments and also gives perfect scheduling.

1.2Need for the System
The system is a manual one, which consumes lot of time as well as manpower. In order to elicit the requirements of the system and to identify the elements, inputs,

outputs and the procedures. The system had to be examined and analyzed in detail. This constituted the system study. Records, slips, procedures, rules, etc. were examined thoroughly. The system was studied involving a complete co-operation from the employees who run the system at present.

The system is to manage all the works like billing, service application acceptance etc. The updation of the system is needed to do the following process.  Maintain the Customer information  Maintains Sales details  Maintains Order details

 Maintains Service Details

1.3 SYSTEM REQUIREMENTS 1.3.1. Hardware Requirements:
Micro Processor used : Pentium IV

Clock Speed

:

3.0 Ghz.

Hard Disk Drive

:

160 GB 17‟‟ Samsung Color Monitor

Display Drive

:

Keyboard

:

Multimedia Keyboard

Mouse

:

Logitech Mouse (optical)

RAM

:

1 GB

DVD Writer

:

Samsung 52x

1.3.2 Software Requirements:
Operating System Front end used Back end used : : : Windows XP Visual Basic MS-Access

ADO presents a single.4. MULTIPLE DOCUMENT INTERFACE (MDI) MDI is used to opening multiple windows at the same time.0 is a window based programming language. by Microsoft. All documents windows are contained in the parent window which provides a workspace in application can have only MDI form at runtime. command buttons etc. The stock maintenance system involves the calculative part of the quantity to be purchased and the current asset value on the hand as stock are relatively very much ideal and visibility for the users of the system when these are created in visual basic. The first version of VB was released in the year 1991. As the successor to DAO and RDO. interface for the developer simplified .1. ACTIVE X DATA OBJECTS (ADO) ADO is an application level interface used to access the data from a variety of data sources. . Visual Basic programs used commands that are similar to Basic Programming Language. All the controls are interacted with the form and the user can easily observe the project for using it. VB like any other windows based language provide items like check boxes. FRONT END & BACK END: VISUAL BASIC Visual Basic 6.The above statements shows the options and advantages of visual basic as the programming language uses the graphical user interface environment.

The backend is created using MS-Access because it is user friendly and the database management system is very much familiar by all the users and the capability to create the tables as much we need and the data retrieval id very good. Import or Export of table from one database to another database. In a relational database. Relational Database Although there are different ways to organize data in a database. MS Access is a very powerful RDBMS available in the computing environment. Relational database systems are an application of mathematical set theory to the problem of effectively organizing data. the user runs an application that accesses data from the database and presents it to the user in an understandable format. relational databases are one of the most effective. Database A database is similar to a data file in that it is a storage place for data. This is the Back end database engine for Visual Basic. It is also possible to write queries. . data is collected into tables (called relations in relational theory). a database does not present information directly to a user. Like a data file.BACK END: ABOUT MS ACCESS The Back end that has been used in this project is MS access . It comprises of all the features from basic data storage to high level data representation techniques in the form of reports. It also provides security to data in the database in a way that data can be stored in an encrypted form. It also comprises of VB module programming. which allows embedding VB functions into MS Access. The idea behind this is easy to maintain the table.

SYSTEM ANALYSIS 2.  Only manual checking is done  Searching is very much difficult for the customers  Timely reports are not generated perfectly  Unavailability of quick references  Stocks are very difficult to maintain . Drawback of the Existing System  The main drawback of the existing system is manual and involves lots of inputs.CHAPTER II 2.1 Existing System The existing system in the company was maintaining the activities manually. All the activities are very much difficult to prepare reports for monthly and yearly. The information‟s provided by the existing system require a lot of manual interventions at the time of preparing the system. Hence there is a need for updating of the system.

 User friendly.2.  Faster date retrieval. which overcomes all the inconvenience and trouble of the present system.  Centralized database.  Built-in security features.  Unique paper work. The proposed system is to be developed using Visual Basic 6. It reports generated is accurate. ADVANTAGE OF THE PROPOSED SYSTEM: The report can be prepared in very short notices and in every short time. The proposed system package is menu driven. . After keying in the input.  Eliminating of redundancy of data. it is just a question of few minutes. This new software application has been developed with menu driven approach.0.  Easy to access.2 PROPOSED SYSTEM The purposed of the proposed system is to computerize the exiting system. after which we get a report. It is short for the top management to know the result in a glance.

SYSTEM DESIGN 3. Data store at rest. . data in motion Represents a process that transforms incoming data flow into out going dataflow. pertinence etc. DFD is a structural analysis and design. There includes DFD’s. Identifies data flow.1 DATA FLOW DIAGRAM This is concerned with the transformation of requirements into data &software architecture various notation are used in this stage. The most frequently used category of architectural design notation is directed graphs.CHAPTER III 3. The Data Flow Diagram is used as graphical notation to depict information flow. It describes the flow of data through out a system. The objective of this method is the derivation to program structure analysis and design. temporary repository of data. DFD SYMBOLS: Defines a Source or destination of a system.

It is a logical development. A set of generic design guidelines governs general interaction. Various input forms are designed categorically according to the need of the particular division.3. Design issues such as response time. The objective is to make information access easy and quick. Input design encompasses internal and external program interfaces and the design of user interfaces. error handling and help facilities are considered and a design model for the system is defined. A database is collections of inter related data stored with a minimum redundancy to serve many users quickly and efficiently. the authorized persons share data across applications with database software managing the data as an entity. Instead of each program managing its own data. which fulfills the every need the user. . inexpensive and flexible to the User. information display and data entry. It allows the user to access the source of information according to the security level assigned to the user. in the methods used by the computers to access and manipulates data stored in the various parts of computer system. comma structure. It is information from several files is coordinated accessed and operated upon as though it is a single file. This defines user tasks and actions either an elaborative or object oriented approach. Internal and external interface designs are guided by information obtained from the analysis model.2 DATABASE DESIGN The most important aspect of building candidate system is “database design”.

Tables Table Name: Product Master SNO 1 Field Name Prodcode (Primary Key) Data type Text Size 20 Description Product Code 2 3 4 ProdName Model Price Text Text Number 25 25 5 Product Name Model name Price of the product Table Name: Order SNO 1 Field Name OrderNo (Primary Key) Data type Text Size 20 Description Order Number 2 3 4 5 Date Name Address ProdCode (Foreign Key) Text Text Text Text 25 25 25 25 Date of Order Name Address Product Code 6 7 8 9 10 Prodname Model Qty Rate Total Text Text Number Number Number 25 25 20 20 20 Product Name Model Description Quantity Amount Total Amount .

Table Name: Purchase SNO 1 Field Name Invoice No (Primary Key) Data type Text Size 20 Description Invoice Number 2 3 Date OrderNo (Foreign Key) Text Text 25 25 Date of Sales Order Number 4 5 6 Supplier Code Sname ProdCode (Foreign Key) Text Text Text 25 25 25 Supplier Code Supplier Name Product Code 7 8 9 10 11 Prodname Model Qty Rate Amount Text Text Number Number Number 25 25 10 10 10 Product Name Model Description Quantity Amount Sub Total Amount Table Name: Payment SNO 1 2 3 4 5 6 7 Field Name BillNo Date Name Address Amount Advance Balance Data type Text Text Text Text Number Number Number Size 20 20 25 25 10 10 10 Description Bill Number Date Name Address Bill amount Advance amount Balance Amount .

Table Name: Sales SNO 1 Field Name Billno (Primary Key) Data type Text Size 20 Description Bill Number 2 3 Date OrderNo (Foreign Key) Text Text 25 25 Date of Sales Order Number 4 5 6 Name Address ProdCode (Foreign Key) Text Text Text 25 25 25 Name Address Product Code 7 8 9 10 11 12 13 Prodname Model Qty Rate Subtotal Discount GrandTot Text Text Number Number Number Number Number 25 25 10 10 10 10 10 Product Name Model Description Quantity Amount Sub Total Amount Discount Amount Payable Amount Table Name: Stock SNO 1 2 3 4 5 6 7 Field Name Prodcode ProdName Model OpenSt Purchase Sales Closest Data type Text Text Text Number Number Number Number Size 20 20 20 10 10 10 10 Description Product Code Product Name Model name Opening Stock Purchase Qty Sales Qty Closing Qty .

Table Name: Service SNO 1 2 3 4 5 6 7 8 9 Field Name ServiceID Date Bill No Date ProdCode ProdName Model Problem Amount Data type Text Text Text Text Text Text Text Text Number Size 20 20 25 25 25 25 25 50 10 Description Service ID Date Bill Number Name Product Code Product Name Model Description Nature of Problem Service Amount .

3. It allows the user to access the source of information according to the security level assigned to the user.3 Input Design Input design encompasses internal and external program interfaces and the design of user interfaces. comma structure. error handling and help facilities are considered and a design model for the system is defined. Internal and external interface designs are guided by information obtained from the analysis model. . Various input forms are designed categorically according to the need of the particular division. which fulfills the every need the user. This defines user tasks and actions either an elaborative or object oriented approach. A set of generic design guidelines governs general interaction. information display and data entry. Design issues such as response time.

The service system is created to make service facilities for the customer. Stock Module 1: Purchase This module deals with the details of purchase details such as ordering for the purpose of purchasing from the supplier for the needed mobiles.3. then the Purchase billing and the items purchased and the value of the purchased items. . All the details of the order received for sales have been maintained to takes how many items sold and the values of the sales are calculated here. Sales & Service 3. Order 2. Module 2: Sales & Service This module is used to maintain sales orders received and the billing activities takes place here. Module 3: Stock This module is for maintaining stock details and for the purpose to find the value of current stock.4 Module Design The System Consists of Three modules 1. The stock details are maintained till date to easy retrievement of the closing stock of the Current Item.

5 OUTPUT DESIGN The output design minimizes the intellectual distance between the software and the problem.3. Output design builds coherent. The output generated is clear and optimized. Outputs are created precisely to match the expectations of the users and presented with careful verifications with the works manager. as it exists in the real world. well planned representation of programs that concentrate on the inter relationships of parts at the higher level and logical operations involved at the lower level. The design is uniform and integrated. Every report are outputs presented with all attribute regarding every subject in a single report .

1 SYSTEM TESTING Testing is an important stage in system development life cycle (SDLC). . There are three ways to test a program 1. Tests for implementation efficiency attempt to find ways to make a correct program run faster and use less storage. Testing begins at the module level and work towards the integration of entire computer based system. Software testing is a critical element of software quality assurance and represents the ultimate view of specification. Nothing is complete without testing. This is much more difficult than it may first appear. For Correctness 2. especially for large programs. which re-examines the implementation phase of algorithm development. It is a code refining process.CHAPTER IV SYSTEM TESTING AND IMPLEMENTATION 4. For Implementation efficiency 3. Tests for computational complexity amount to an exceptional analysis of complexity of an algorithm or an experimental comparison of two or more algorithms. For Computational Complexity Tests for correctness are supposed to verify that a program does exactly what it was supposed to do. which solve the same problem. design and coding. as it is a vital success of the system.

Front end Validation Unit testing focuses verification efforts on the smallest unit of software design module. Unit Testing Integrated Testing Final/System Testing The code modules were tested individually one after another. The following were tested in each module. Finally the error handling paths were tested. Boundary conditions are tested to ensure that modules operate at boundaries and restrict processing when gone beyond the set boundary. Field Length 3. Boundary value analysis Control paths are tested to ensure the information properly flows into and out of the program unit. All independent paths through the control structure ensure that the statements have been executed at least once. the following were tested in this phase. Loop testing 2.4. Each module was found to be working properly. .1 TESTING METHODOLOGIES The entire testing process can be divided into 3 phases    Unit Testing As the system was totally GUI based. 1.1. 1. Menu Testing 4. In our testing the test data was given to each and every module in all respects and got the desired results. Tab Order 2. To check whether each module in the software works properly so that it gives desired output to the given input.

Integration Testing Integration testing is a systematic technique for constructing the program structure. while conducting test to discover error associated with interfacing. Test Data Test data should be prepared carefully since data only determines the efficiency and accuracy. Final/System Testing This is the final step of testing. This form of testing is known as Black Box Testing. All the above testing was successfully carried out for the month of March 2003. The output given by the system agreed with test data output created manually. The different modules of the system were combined together to form an integrated working application. . Integration test has been carried out successfully. Crosschecking has also been done with the existing System for accuracy. In this testing the entire system was tested as a whole. Black Box testing enables us to derive sets of input condition that will fully exercise all functional requirements for a program. Black Box testing has been successfully carried out with test data and got the desired output.

Conversion is one aspect of implementation.    Creating Computer-Compatible Files Training the operating staff Installing terminals an Hardware 4. Depending upon the nature of the system. The objective is to put the tested system into operation while holding costs. The initial parameters of the MIS should be modified as the result of programming efforts. extensive user training may be required. Implementation is used here to mean the process of converting a new revised system design into an operational one. Operational document includes the information of how the program has to be operated. extensive user training may be required. Conversion Conversion means changing from one system to another.4. Implementation phase is less creative than system design.2. Once the programs available. The system testing checks the readiness and accuracy of the system to access update and retrieve data from new files. in which one has to be cautious. it is essential that the user of the system is made familiar and comfortable with the environment. It is primarily concerned with User-Training. .2 SYSTEM IMPLEMENTATION 4. Depending on the nature of the system. the test data are read into the computer and process. Implementation is the phase. programming provides a reality test for the assumption made by the analyst. Site preparation and File Conversion.1 IMPLEMENTATION PROCEDURES Implementation is one of the most important tasks in the project. risks and personal irritation to a minimum involves the following.2 Operational Documentation Once the implementation plan is described.2. because all efforts undertaken during the project will be fruitful only if the software is properly implemented according to plans made.

Much of the process is automated and hence the chance of human errors is limited. Closing other programs and freeing up the memory would improve the systems performance. The system was tested with sample data and the performance of the system was found to be efficient. a little training would make the user understand the system much better. More security could have been given to the system by the way authorization and further features could have been added to make the system more robust. Through the system has been built with ease of use in mind. Due to time constraint are being a notice to the subject of „Mobile Sales and Service System”. The system requires users to take regular backups using backup feature in Access.CHAPTER V CONCLUSION The system development titled „Mobile Sales & Service System” was designed keeping in mind to provide maximum flexibility to the users. The system‟s performance is little slow due to the use Data Environment feature in programming. All efforts have been made to understand the system wholly and understand all the details. Almost all aspects regarding simple billing have been take into consideration when developing the system and are included into the system. . Also further internal documentation could be added to make the maintenance quick and easy. there have been certain limitations the system would be better off without. However.

PRESSMAN ”Software Engineering” Tata McGraw-Hill Publishing company. “Systems Programming and Operating Systems”.BIBILIOGRAPHY 1. Tata McGraw-Hill Publishing Company. M. 5. 2002. II Edition. . Prentice-Hall of India 1998 Edition 3. Galgotia Publications 1997 Edition. Vth Edition. D M DHAMDHERE. AWAD. 2001. BPB publications 1999 Edition 2. “Murach’s Visual Basic 6”. JOEL MURACH. 4. BRIAN SILER. “Special Edition: Using Visual Basic 6”. “System Analysis and Design”. ROGER S. ANNE PRINCE. ED KOOP. ELIAS.

Appendix Systems Flow Chart Start User Login If Password correct Yes Main Menu No Orders Purchase Stock Relogin Sales Service Payment .

E-R Diagram Customer O No Order Date Amount Checks Provides Sales Bill No Date Inv No Stock Request Purchase Date Amount Date Item Code No of Items Date Payment Generates Bill No Amount .

DATA FLOW DIAGRAM LEVEL 0 Customer REQUEST Order RESPONSE GENERAL REPORTS LEVEL 1 Order Ordering Processing Customer Processing Completing Sales Processing .

LEVEL 2 Customer Product Order Processing Product Order Product Details Order Order Details Sales Bill Verification Product Delivery Stock Update Stock Stock Stock Details Service Paying Details Sales Invoice Payment Payment Pay receipt Paying Details Service Service Details .

Sample Screens .

.

.

.

.

.

.

.

Reports .

.

.

.

.

Text) & "'. adLockOptimistic If Text1. vbYesNo + vbQuestion.'" & Trim(Text9.Text = "" Then msg = MsgBox("cannot insert NULL values".Text) & "'. "dd/MM/yyyy") Text6.'" & Trim(Text10. vbExclamation.Text) & "')") Call updatestk msg = MsgBox("Records are saved".'" & Trim(Text5.Text = "" Text7.Text) & "'.'" & Trim(Text7.Text = "" Text4.Text) & "'. "NOTE") Else msg = MsgBox("Do you want to save ?".Recordset Dim rs1 As New ADODB. "SAVE") End If End If .'" & Trim(Text4.'" & Trim(Text2.Text = "" Text8.MoveLast End Sub Private Sub Command2_Click() Set rs = New ADODB.'" & Trim(Text3.Recordset Dim msg As String Private Sub Command1_Click() Set rs = New ADODB.Text = "" Text2.Text = "" Text3.Sample Codings Dim strq As String Dim cn As New ADODB.Text) & "'.Text = "" Text9.Connection Dim rs As New ADODB.Text = Format(Date. cn. adOpenDynamic.Text = "" Text1.Text = "" Text5.Execute ("insert into SalesInvoice values('" & Trim(Text1.Recordset rs. adLockOptimistic Text1. "OPTION") If msg = vbYes Then cn.Text) & "'.'" & Trim(Text6.Open "select * from SalesInvoice".Text) & "'.Text) & "'. vbInformation.Recordset Dim rs2 As New ADODB.Text) & "'.SetFocus rs.Recordset rs.Open "select * from SalesInvoice".'" & Trim(Text8. cn.Text = "" Text10. adOpenDynamic.Text = "" And Text2.

cn. adLockOptimistic msg = MsgBox("Are yuo sure to delete the record?". adOpenDynemic.Text = "" Text5.Open "select * from SalesInvoice".Close Set rs = New ADODB.Open "select*from SalesInvoice".Recordset rs.Recordset rs.Text = "" Text2.Show End Sub .Hide MDIForm1. vbYesNo + vbQuestion.Text = "" Text8. cn. adLockOptimistic End Sub Private Sub Command3_Click() Set rs = New ADODB.Text) & "'") Text1.Recordset rs.Text = "" Text4. cn.Execute ("delete from SalesInvoice where InvoiceNo='" & Trim(Text1. adOpenDynamic.Text = "" Text7.Text = "" Text10.Text = "" msg = MsgBox("Records are deleted". "OPTION") If msg = vbYes Then cn.Text = "" Text9.rs. adLockOptimistic End Sub Private Sub Command4_Click() Me.Open "select*from SalesInvoice".Text = "" Text3.Close Setrs = New ADODB. "DELETE") End If rs. adOpenDynamic.Text = "" Text6. vbExclamation.

Text = rs(3) Text5.Text = rs(9) End Sub Private Sub Command6_Click() rs.Text = rs(1) Text3.BOF = False Then Text1.Text = rs(5) Text7.Text = rs(7) Text9.EOF = False Then Text1.Text = rs(9) Else MsgBox "This is your first record" rs.Text = rs(8) Text10.Text = rs(6) Text8.Text = rs(2) Text4.Text = rs(5) Text7.Text = rs(0) Text2.Text = rs(4) Text6.Text = rs(2) Text4.Text = rs(7) Text9.Text = rs(2) Text4.MoveNext If rs.Text = rs(6) Text8.Private Sub Command5_Click() rs.Text = rs(8) Text10.MoveFirst Text1.Text = rs(4) Text6.MovePrevious If rs.Text = rs(3) .Text = rs(1) Text3.Text = rs(0) Text2.Text = rs(3) Text5.Text = rs(0) Text2.Text = rs(1) Text3.MoveNext End If End Sub Private Sub Command7_Click() rs.

Text = rs(6) Text8.Text = "" Text3.Jet.Text = Format(Date.Text = rs(8) Text10.Text = rs(9) End Sub Private Sub Form_Load() cn.Text = rs(6) Text8.Text = "" rs.Path & "\data.Text = "" Text4.4.MoveLast Text1.0. adOpenDynamic.Text = "" Text8.Text = rs(7) Text9.Text = rs(0) Text2.Open strq. adLockOptimistic Text1.Text = rs(2) Text4.Text = "" Text10.data source=" & App.Text5.Text = "" Text9.Open "provider=Microsoft.OLEDB.Text = rs(9) Else MsgBox "This is your last record" rs.mdb.MoveLast .MovePrevious End If End Sub Private Sub Command8_Click() rs.Text = rs(5) Text7.Text = rs(8) Text10." strq = "select * from SalesInvoice" rs.Text = rs(1) Text3.Text = rs(4) Text6.Text = rs(4) Text6. cn.Text = rs(5) Text7.Text = rs(3) Text5.Text = "" Text5.Text = "" Text7. "dd/MM/yyyy") Text6.Text = rs(7) Text9.Text = "" Text2.

EOF If Trim(Text2.Text) = Trim(rs3. adOpenDynamic.Close End If End Sub .Text) .Text) End Sub Private Sub Text2_KeyPress(KeyAscii As Integer) If KeyAscii = 13 Then Set rs3 = New ADODB.Fields(0)) Then Text3.Text) .Val(Text14.MoveNext Loop rs3.Text = Val(Text13.Hide Unload Me cn.Text) End Sub Private Sub Text14_Change() Text10.MoveFirst Do While Not rs3.Text = rs3(1) Exit Sub End If rs3. cn. adLockOptimistic rs3.Text = Val(Text13.End Sub Private Sub Form_Unload(Cancel As Integer) Me.Val(Text14.Recordset rs3.Open "select * from Customer".Close End Sub Private Sub Text13_Change() Text10.