project mca iii sem

8/8/2019 Project Mca III Sem

1/39

A

PROJECT ON

AUTOMOBILE

SUBMITTED TO

THE M.C.A. DEPARTMENT,

S.R.G.P.G.P.I. INDORE,

PROJECT GUIDE: SUBMITTED BY:

Prof. Manish Sharma Akilesh Purohit

Prof. Rupesh Kabra Arjun Singh Faguda

Nitin GaikwadMCA III SEM


2/39

CERTIFICATE

This is to certify that Arjun Singh Faguda,Akilesh Purohit and

Nitin Giakwad student of Second year M.C.A in the year 2007 of

Master Of Computer Applications of Shri RaojiBhai Gokal

Bhai Patel Gujrati Professional Institute has completed the

project work entitled AUTOMOBILE based on syllabus and

have submitted a satisfactory account of their work in thisreport.

External Examiner Internal examiner


3/39

CERTIFICATE

This is to certify that Arjun Singh Faguda,Akilesh Purohit

and Nitin Giakwad student of final year M.C.A in the year 2006of Master Of Computer Applications of Shri RaojiBhai Gokal Bhai

Patel Gujrati Professional Institute has completed the project work

entitled AUTOMOBILE based on syllabus and have submitted asatisfactory account of their work in this report.

Prof.Sanjay Bansal Project Guide[ [H.O.D.]


4/39

To make efforts is better that to achieve success and to choose the capableperson for success is greater that to make efforts and succeed.

We are eminently obliged to our project guide Mr. Manish Sharma andRupesh kabra under whose directives we are able to achieve success.

His brine of enunciations, eruditions, experience and influence not only

showed us easiest and knowledgeable way to eventuate our project but

also encouraged, inspired and enlightened.

We are heartily grateful to Mr. Sanjay Bansal, head Of

department of Computer, who incessantly remained the source ofcourage & inspiration to us and strengthened our will to succeed.

We wish to express our profound sense of gratitude to the staff

members of Computer Science department of Shri RaojiBhai Gokal Bhai

Patel Gujrati Professional Institute who provided us constant motivation

and inspiration throughout the project. We are thankful to them for

providing us the best of the available studying environment and

facilities for the guidance. Lastly, our thanks go to our parentscolleagues and friends for their co-operation.


5/39

CONTENTSONTENTS

1.)1.) Identity of client/organizationIdentity of client/organization2.)2.) Problem investigationProblem investigation

Introduction to problemIntroduction to problem2.1 Solution suggested2.1 Solution suggested2.2 Goal2.2 Goal2.3 Objective2.3 Objective2.4 Need of project2.4 Need of project

3.)3.) Theory of systemTheory of systemConcept of projectConcept of projectVarious processes runningVarious processes running

4.)4.) System analysisSystem analysis4.1 Requirement gathering4.1 Requirement gathering4.2 Process model used4.2 Process model used

4.2.1 Selected model4.2.1 Selected model4.2.2 Advantages of selected model4.2.2 Advantages of selected model4.2.3 Reason for selecting the model used4.2.3 Reason for selecting the model used

4.3 Limitations to Current System4.3 Limitations to Current System4.4 Introduction to proposed system4.4 Introduction to proposed system4.5 Merits of proposed system4.5 Merits of proposed system4.6 Information flow representation4.6 Information flow representation4.7 Input function identification4.7 Input function identification

4.8 Output function identification4.8 Output function identification4.9 System requirement specification4.9 System requirement specification

4.9.1 Function requirement of system4.9.1 Function requirement of system4.9.2 Non function requirement of system4.9.2 Non function requirement of system4.9.3 Constraints4.9.3 Constraints

4.10 Project resources4.10 Project resources4.10.1 Required documents4.10.1 Required documents4.10.2 Hardware & software requirements4.10.2 Hardware & software requirements4.10.3 Time4.10.3 Time

4.11General requirement4.11General requirement4.11.14.11.1 FunctionalityFunctionality

4.11.24.11.2 DocumentsDocuments4.11.34.11.3 DataData4.11.44.11.4 SecuritySecurity4.11.54.11.5 User factUser fact

5.)5.) Project planningProject planning5.15.1ObjectiveObjective5.2 Need and importance5.2 Need and importance


6/39

5.3 Major functions5.3 Major functions5.4 Management and technical constraint5.4 Management and technical constraint5.5 Project resources5.5 Project resources5.6 Team organization5.6 Team organization5.7 Schedule5.7 Schedule

5.8 Work break down structure5.8 Work break down structure5.9 Estimation5.9 Estimation6.)6.) Feasibility studyFeasibility study7.)7.) System designSystem design

7.17.1Design phaseDesign phase7.2 Design principal7.2 Design principal7.3 DFD7.3 DFD7.4 ERD7.4 ERD7.5 Data base design7.5 Data base design7.6 Components and interfaces7.6 Components and interfaces

8.)8.) Tools used and descriptionsTools used and descriptions

8.18.1Front endFront end8.2 Back end8.2 Back end8.3 Reason for tools selected8.3 Reason for tools selected

9.)9.) ImplementationImplementation9.1Programming approach followed9.1Programming approach followed9.29.2Administrative functionAdministrative function9.39.3User functionUser function9.49.4Screen layoutsScreen layouts

10.)10.) TestingTesting10.110.1TestingTesting10.210.2Objectives of testing methodsObjectives of testing methods

10.310.3Principal of testingPrincipal of testing10.410.4Testing methodsTesting methods11.)11.) MaintenanceMaintenance12.)12.) ConclusionConclusion

12 .1Conclusion and discussion12 .1Conclusion and discussion12.2 Limitations12.2 Limitations12.3 Difficulties encountered during project12.3 Difficulties encountered during project12.4 Suggestion for future extension of work12.4 Suggestion for future extension of work

13.)13.) BibliographyBibliography


7/39

INTRODUCTION


8/39

ORGANISATION OVERVIEW

INTRODUCTION

All your need is a trading organization dealing with vast variety of items. It owns a

franchise (dealership) of company where all its items are sold. All its goods are

stocked in a warehouse and issued to the customer as and when required.

Purchase Department: Places order with supplier and makes decision about

purchase returns.

Receiving Department: Is responsible for receiving the goods and physically

verifying the quantity and quality of goods received against the order placed. Apart

from it also keeps a track of pending requisition and satisfies them as soon as

possible.

The overall structure can view as follows: -

Creating and maintaining information on suppliers, items and customers.

Print invoices/bills for goods sold.

Accept/receive goods into the store.

Maintain all details about his customers.

Maintain all details about his suppliers.

Provide monthly statements on amount outstanding.

Provide monthly statements on amount payable.

Provide statements on stock on hand.


9/39

CURRENT SYSTEM

The current system is a fully computerized system built in FoxPro. The

Automobile are stored in the warehouse and all the movement of Automobile in and

out of the warehouse is supported by appropriate documents. And the above-

mentioned activity is due to Automobile purchased, Automobile issued to the dealer,

Automobile returned to the supplier, Automobile issued returned by the dealer or sub-

dealer.

The goods send by the supplier first go to the receiving dept. Here theyphysically count the Automobile and check the quantity against the order placed. The

Automobile are send to the warehouse along with Automobile receipt note that

indicates details such as item received, order no., against which they are receiving

and the number of units or accessories of each item.

If there is some sort of mistake in the receiving condition of the Automobile then

such are returned to the supplier, the purchase dept. Sends a copy of the purchase

return note to indicate Automobile are to be returned, the goods receipt note the

number against which they were received and the number of units of Automobile that

to be returned.

The issue dept. takes into account the availability and accordingly prepares the

Automobile issue note. Apart from the above mentioned activities the account section

of the organization. Keeps a record of all the financial transactional activities that are

going within the organization.

The organization has also decided to maintain in the computerized system the details

of the purchase orders so that the system can keep a track of completed, pending and

dead orders.


10/39

PROPOSED SYSTEM

PURCHASE ORDER ENTRY:

The copy of the quotation send to the supplier and after receiving the Automobile as

per order placed are checked both quality and quantity wise and the details like model

name, cambered code, chesis no, engine No details are stored in the database and

are used to validate the item code, supplier code and order date at later stages.

TRANSACTIONS:

The transactions like issue, receipts, delivery challan, received and due payments are

debited and credited accordingly. Apart from records of both customer and Automobile

are also taken into considerations.

RECEIPTS:

The receiving dept. checks goods received from supplier and sends the goods to thewarehouse along with a goods receipt note. The quantity hand and rate in the stock

file and the total receipts in the bal file are updated. Apart from it receipts given to the

customer in favor of the payment given by them for booking or as a down payment. All

the entries are stored in the database to reduce redundancy in the later stages.

PURCHASE RETURN:

The purchase dept. prepares a purchase return note to indicate Chocolates to be

returned to the supplier, and thereby updating the stock level and automatically

deleting the record of the returned Automobile.


11/39

ISSUES:

The issue dept. sends an Automobile issue note to the warehouse-indicating

Automobile to be dispatched to the customer. The quantity in the database and the

total issues in the balance record are updated.

ADJUSTMENTS:

There are some entries in which accurate information is not stored due to some

damage or any other technical fault, therefore such types of records are stored in the

temporarily database file temporarily so that on proper feedback it can be updated

accordingly.

REPORT GENERATION:

Daily generation of reports are taken regularly, facilities provided like date wise, month

wise and year wise reports. If the user wants to see the no of Automobile that are

financed and see the amt due report can be generated accordingly. Apart from it

reports like delivery challan, invoice, sales transaction, quotation and issue arefacilitated in the software.

DAILY BACKUPS:

Backups are taken of records marked for deletions are physically deleted from the

files.


12/39

INTRODUCTION TO VISUAL-BASIC

Microsoft Visual Basic, the fastest and easiest way to create applications for

Microsoft Windows. Whether you are an experienced professional or brand new to

Windows programming, Visual Basic provides you with a complete set of tools to

simplify rapid application development. The "Visual" part refers to the method used to

create the graphical user interface (GUI). Rather than writing numerous lines of code

to describe the appearance and location of interface elements, you simply add rebuiltobjects into place on screen. If you've ever used a drawing program such as Paint,

you already have most of the skills necessary to create an effective user interface.

The "Basic" part refers to the BASIC (Beginners All-Purpose Symbolic

Instruction Code) language, a language used by more programmers than any other

language in the history of computing. Visual Basic has evolved from the original

BASIC language and now contains several hundred statements, functions, and

keywords, many of which relate directly to the Windows GUI. Beginners can create

useful applications by learning just a few of the keywords, yet the power of the

language allows professionals to accomplish anything that can be accomplished using

any other Windows programming language.

The Visual Basic programming language is not unique to Visual Basic. The

Visual Basic programming system, Applications Edition included in Microsoft Excel,

Microsoft Access, and many other Windows applications uses the same language.

The investment you make in learning Visual Basic will carry over to these other areas.

Data access features allow you to create databases, front-end applications, and

scalable server-side components for most popular database formats, including

Microsoft SQL Server and other enterprise-level databases.


13/39

Introduction and characteristics ofMS-Access2000

Databases

A database is a collection of information related to a particular subject or purpose,

such as tracking customer orders or maintaining a music collection. if out database is

not stored on a computer , or only parts of it are, we may be tracking information from

a variety of sources that we have to coordinate and organize ourselves.

Using Microsoft Access, we can manage all our information from a single

database file. Within the file, divide our data into separate storage containers called

tables; add, and update table data using online forms; find and retrieve just the data

we want using queries; and analyze or print data in a specific layout using reports. To

store our data, create one table for each type of information we track to bring the data

from multiple tables together in a query form. Or report, we can define relationship

between the tables.

To find and retrieve just the data that meets conditions we specify, including

data from multiple tables, create a query. a query can also update or delete multiple

records at the same time and perform built-in or custom calculations on our data. To

easily view, enter, and change data in a table, we have created forms in Microsoft

Visual Basic 6.0. When we open a form, Microsoft Visual Basic retrieves the data

directly from one or more tables and displays it on screen using the form and Reports.

Table

In table data sheet view, we can add, edit or view the data in a table. We can also

check the spelling and print our tables data, filter or sort records, change the data

sheets appearance, or change the tables structure by adding or deleting columns.


14/39

INTRODUCTION TO REPORT

Every business system depends on a more or less abstract called

an information system. This system is the means by which data flow

from one person or department to another. Information systems serves

all the system of a business linking the different component in such a

way that they efficiently work towards the same purpose. Now the

question arises how such complex information does system came into

existence? First of all it is important to understand that, what the system

is?

In the broadest sense, a system is simply a set of components

that interact to accomplish same purpose. In other words, the system is

an organized or complex whole; an assemblage or combination of thing

or part forming a complete of unitary whole.

In business, system analysis and design refers to the process ofexamining a business situation with the intent of improving it through

better procedures and methods. As computers are used more and more

by the persons who are not computers professionals, the phase of

system development is taking on an additional dimension. User the

selves are undertaking development of some of the system they use.

These different situations are represented by 3 distinct approaches to

the development of system:

1. System Development Life Cycle Method.

2. Structured Analysis Development Method.

3. System Prototype Method.


15/39

The Project report in on the analysis of Housing Finance system.

For the development of this system, we are using the most widely used

system development life cycle method. In most business situation the

activity are closely related, usually inseparable and even the order of the

steps in these activities may be difficult to determine.

The system development life cycle method consists of the

following activities:

1. Preliminary Investigation.

2. Determination of system requirements

3. Design of system

4. Development of system

5. System testing

6. Implementation and testing

In this project report of Housing Finance system, we elaborate on

each of these activities as they have occurs in the development of the

system. By systematically adopting various methodologies, we have

ensured thereby improving the case with which it can be understood,

rebuilt, widespread or amended.


16/39

SYSTEM ANALYSIS


17/39

SYSTEM DEVELOPMENT LIFE CYCLE

System development is set of activities performed by analysts,

designers and users to develop and implement a system. The systems

development life cycle consists of the following activities:

Problem Definition

Fact Finding / Data Collection / Information Gathering

Alternatives, Feasibility and Proposal

System Design

Systems Testing

Implementation, Evaluation and Maintenance

Problem Definition

One of the most difficult tasks of system analysis is developing a

clear under-standing of the problem being analysed, without which it

becomes impossible to specify the requirements for a new project with

any accuracy. Several questions should be consider for this.


18/39

Some of those may be.

1. What is the problem?

2. How complex is it?

3. What are its likely causes?

4. Why is it important that the problem be solved?

5. What are possible solutions to the problem?

6. What types of benefits can be expected once the problem is

solved?

Beside the problems of reliability, validity, accuracy, economy and

timeliness, the problems of capacity and throughput are also common.

Capacity problems occur when a component of a system is not large

enough. Two people attempting to do the work of six is a capacityproblem. Throughput problems deal with the efficiency of a component

of a system. Six people doing the work of two represents a problem of

throughput. Lets consider each of these seven problems in more detail.

The Problem of Reliability: A system suffer from the problem of

reliability when procedures work some time but not all time, or when use

of the same procedure gives to different results. Analysts must work

continually to improve the reliability of systems.

The Problem of Validity: Systems that produce invalid results are often

most difficult to users and systems managers. Maintaining validity in

computer software is a difficult design problem. Validity problems result


19/39

when the environment changes and these changes are not included into

the software.

The Problem of Accuracy: The problem of accuracy is similar to the

problems of reliability and validity. A system may produce inaccurate

results.

The Problem of Economy: A system suffers from the problem of

economy when existing methods of processing, are very costly. An

organization might found that the cost of handling the paperwork

associated with each purchase order is Rs. 25. This cost is determined

to be problem of economy. After the installation of a new method of

processing, the cost per purchases is reduced from Rs 25 per order to

Rs 8 per order.

The Problem of Timeliness: A system suffers from the problem of

timeliness if information is available but cannot be retrieved when and

where it is needed.

The Problem of Capacity: The problem of capacity occurs when a

system component is not large enough. Capacity problems re specially

common in organizations.

The Problem of Throughput: The problem of throughput may be

viewed as the reverse of the problem of capacity. Throughput deals withthe efficiency of a system. If system capacity is high and production low,

a problem of throughput occurs. Consider the following example.


20/39

Five programmers are assigned to a fairly straightforward

programming assignment consisting of 10,000 lines of computer code.

After thirty days of coding, the programming team is evaluated. It is

discovered that they have completed 6000 usable lines of code. Now, if

each programmer worked eight hours a day, a total of 1200 hours would

have been expended on the project Calculated differently, the average

production rate for each programmer would be 5 lines of code per hour

(6000 lines divided by 1200 hours).

Fact-finding

This phase consists of gathering, examining and evaluating of all

the relevant data to the problem. Answering collects data:

What is being done? (Results),

Why it is being done? (Need),

How it is done? (Process),

Various different types of data may have to be collected

depending on the complexity of the problem. The different types of data

may be History data, Data on policies, Data about Govt. rules and

regulations, Process data, Data about file and records.

It should be noted that all problems do not require collection of allcategories of data. A proper limit should be defined for analysis.


21/39

Fact finding techniques

Methods, which are used, for fact-finding or data collection are

called fact-finding techniques. The following techniques may be used for

data collection

1. Interview

2. Questionnaire

3. Record Inspection

4. Observation

Alternative, Feasibility and proposal

The alternatives arise naturally in planning a new system and a

particular alternative may be implemented in many ways. The

alternatives will differ in their costs and benefits. The analyst should not

propose one solution but propose many alternatives, and leave final

decision to the management and actual users of the system.

The analyst should clearly specify feasibility of each alternative bytesting its costs and benefits. The analyst should make a formal proposal

to the management, regarding the problem, findings, alternatives and

feasibility.

System Design

System design process begins by identifying reports and other

outputs of system. The system design also describes the data to be

input, calculated or stored. Individual Data items and calculation

procedures are written in detail. Designers select file structure and

storage devices, such as magnetic disk, magnetic tape or even paper


22/39

files. Procedure the output. The detailed design information is passed on

to the programming staff the purpose of software development.

The design of a new system includes the design of following items

Input Design

Output Design

Process Design

File Design

System Testing

During system testing, the system is used experimentally to

ensure that the software does not fail. Special test data are input for

processing, and the results examined. It is required to identified any

errors and bug before the implementation of the system.

Implementation, Evaluation and Maintenance

Implementation is the processes to put new equipment into use,

train users, install the new application and construct programs and data

files. Sometimes, they will rum both old and new system in parallel way

to compare the results.

Evaluation of the system is performed to identify its strengths

and weaknesses. The actual evaluation can occur along any of the

following dimensions:


23/39

1. Operational Evaluation: Assessment of the manner in which the

system function, including case of use, response time, overall reliability and

level of utilization.

2. Organizational impact: Identification and measurement of benefits tothe organization in such areas as financial concerns, operational efficiency and

competitive impact.

3. User Manager Assessment evaluation of the attitudes of senior and

user manager within the organization, as well as end-users.

4. Development performance: Evaluation of the development process in

accordance with such yardsticks as overall development time and efforts,

conformance to budgets and standards and other project management criteria.

Maintenance is necessary to eliminate errors in the working

system during its working life and to tune the system to any variations in

its working environment often small system deficiencies are found as a

system is brought into operation and changes are made to remove them.

Feasibility Study

In the conduct of the feasibility study, the we have consider seven

distinct, but inter-related types of feasibility. They are:

1. Technical feasibility

2. Operational feasibility

3. Economic feasibility

4. Social feasibility

5. Management feasibility

6. Legal feasibility

7. Time feasibility


24/39

Technical Feasibility

This is concerned with specifying and software that will successful

satisfy the user requirement the technical needs of the system may vary

considerably, but might include:

The facility to produce outputs in a given time.

Response time under certain conditions.

Ability to process a certain volume of transaction at a particular

speed.

Facility to communicate data to distant location.

In examining technical feasibility, configuration of the system is

given more importance than the actual make of hardware. The

configuration should give the complete picture about the systems

requirements:

How many workstations are required, how these units are

interconnected smoothly? What speeds of input and out-put should be

achieved at particular quality of printing. This can be used as a basis for

the tender document against which dealers and manufactures can later

make their equipment bids. Specific hardware and software products can

then be evaluated keeping in view with the logical needs.

At the feasibility stages, it is desirable that two or three different

configuration will be pursued that satisfy the key technical requirement

but which represent different levels of ambition and cost. Investigation of


25/39

these technical alternatives can be aided by approaching a range of

suppliers for preliminary discussions out of all types of feasibility.

Technical feasibility generally is the most difficult to determine.

Operational Feasibility

It is mainly related to human organizational and political aspects.

The points to be considered are:

what changes will be brought with the system?

What organizational structures are disturbed?

What new skills will be required? Do the existing staff members

have these skills?

If not, can they be trained in due course of time?

Generally project will not be rejected simply because of

operational infeasibility but such considerations are likely to critically

affect the nature and scope of the eventual recommendation. This

feasibility study is carried out by a small group of people who are familiar

with in-formation system techniques, who understand the parts of the

business that are relevant to the project and are skilled in system

analysis and design process.

Economic Feasibility

Economic analysis is the most frequently used technique for

evaluating the effectiveness of a proposed system. More commonly

known as cost / benefits analysis; the procedure is to determine the

benefits and savings that are expected from a proposed system and

compare them with costs. If benefits outweigh costs, a decision is taken

to design and implement the system. Otherwise, further justification or


26/39

alternative in the proposed system will have to be made if it is to have a

chance of being approved. This is an ongoing effort that improves in

accuracy at each of the system life cycle.

Social feasibility

Social feasibility is a determination of whether a proposed project

will be acceptable to the people or not. This determination typically

examines the probability of the project being accepted by the group

directly affected by the proposed system change.

Management feasibility

It is determination of whether a proposed project will be

acceptable to management. If management does not accept a project or

gives a negligible support to it, the analyst will tend to view the project as

a non-feasible one.

Legal feasibility

Legal feasibility is determination of whether a proposed project

infringes on known Acts. Statutes, as well as any pending legislation.

Although in some instances the project might appear sound, on closer

investigation it may be found to infringe on several legal areas.

Time feasibility

Time feasibility is a determination of whether a proposed

project can be implemented fully within a stipulated time frame. If a

project takes too much time it is likely to be rejected.


27/39

DATA FLOW DIAGRAM


28/39

DATA FLOW DIAGRAM (DFD)

DFD is a tool by which we can identify the flow of data I a system

without specifying the media or hardware. So, DFD can be defined as a

Graphical tool which represents the flow of systems data and how the

process performs on the data.

To construct data flow diagrams, we use:

1. Arrows

2. Circles

3. Open-ended boxes

4. Squares

An arrow identifies data flow data in motion. It is a pipeline

through which information flows. Like the rectangle in flowcharts, circles

stand for a process that converts data/into in-formation. An open-ended


29/39

box represents a data store (file or database). A Square defines a

source or destination of system data.

The following seven rules govern construction of data flow

diagrams (DFD) :

1. Arrows should not cross each other.

2. Squares, Circles and files must bear names.

3. Decomposed data flows must be balance (all data flows on the

decomposed diagram must reflect flows in the original diagram.

4. No two data flows squares. Or circles can have the same name.

5. Dram all data flows around the out side of the diagram,

6. Choose meaningful names for data flows, processes, and data

stores. Use strong verbs followed by nouns.

7. Control information such as record counts, passwords and

validation requirements are not pertinent to a data-flow diagram.


30/39

SYSTEM REQUIREMENTS


31/39

HARDWARE REQUIREMENTS

1. IBM COMPATIBLE PC-AT.

2. THE CPU SHOULD BE P-I OR HIGHER FOR BETTERPERFORMANCE.

3. 108 KEYS KEYBOARD.

4. 32 MB OR MORE RAM.

5. HARD DISK AND FLOPPY DISK DRIVE.


32/39

SOFTWARE REQUIREMENT

1. WINDOW-98

2. 9X/NT/2000/XP

3. MICRO-SOFT VISUAL BASIC

4. MICRO-SOFT ACCSES


33/39

TESTING

Objectives of testing: Testing is vital to the success of any systemtesting is done at different stages within the development phase.System testing males a logical assumption that if all parts of thesystem are correct, the goals will be achieved successfully.Inadequate testing or no testing leads to errors that may come upafter a long time when correction would be extremely difficult.Another objective of testing is its utility as a user oriented vehiclebefore implementation. The testing of the system was done on bothartificial and live data. The following types of tests are performed.

Unit Testing: This testing focuses verification on the module. Using Proceduraldesign description as a guide, important control paths are tested to

uncover errors within the boundaries of the module. The relativecomplexity of tests and uncovered errors is limited by the constrains

scope established for unit testing. The unit testing can be conducted inparallel for several modules.

Integration Testing: Generally a combined approach known as sandwich testing

using features of top down testing strategy for upper levels of the program

structure, coupled with the bottom up strategy for subordinate modules

Functional Testing: This is done for each module/sub-module of the system.

Functional testing serves as a means of validating whether the functionality of the

system confers the original user requirement i.e. does the module do what it is

supposed to do? Separate schedules were made for functional testing .it involves

preparation of test data, writing of test cases, testing for conformance to test cases

and preparation of bugs listing for non conformities.

System Testing: System testing is done when the entire system has been fully

integrated. The purpose of the system testing is to test how the different modulesinteract with each other and whether the system provides the functionality that

was expected. It consists of the following steps.

Program testing

String Testing


34/39

System testing

System documentation

User Acceptance Testing

Various Levels of Testingarious Levels of TestingLevel I Testing (Alpha Testing)At this level a test data is prepared for testing .Project leaders test thesystem on the test data keeping the following points into consideration.

Proper Error Handling

Exit points in code

Exception handling

Input/output format

Black Box testing 29

Before the screens (forms/Reports) are submitted to the project leader orconsidered to be complete the following checklist should be applied bythe programmer (who has made the screen) to minimize the small GUIbased mistakesThe list is as follows:

Standard Check List

1. Is the tab order set appropriately?2. Can the window be resized, moved or scrolled?3. Are all functions that relate to the window operational?4. Are text typeface, size and format correct and uniform?5. Is invalid data properly recognized?6. Are data input messages intelligible?7. Is the code commented?8. Are coding standards followed?9. Is error handling taken care of?10. Is data validation checked?11. Is business logic validation checked?12. Have you checked the data at backend?13. Have you used any SQL queries except the UCs

and entities? If any, writeThe locations in code. Ex: a) Data change event of

master data element.14. Have you tested and verified your object with

somebody in your team?15. Have you made the known bug list?16. Any issues?


35/39

17. Have you incorporated the ADF list screen?18. Have you added the custom search screen?19. Have you tested the list screen for search?20. Have you added column header text for search and

lookup(s) on the Screens?21. Have you added all the lookups?22. Have you implemented data change for all auto

retrieval fields?

Level II testing (Beta testing)

Here the testing is done on the live database. If errors are detected then it

is sent back to Level I for modification otherwise it is passed onto Level II

Level IIIHere the Error free and properly tested system is implemented

Quality AssuranceProper documentation is a must for maintenance of any software. Thespecification documentation required for each screen was preparedbefore any coding could be started.This gave the programmer a clear and concise view of the screen and listof validations, which, needed to be performed on the screen.

30


36/39

CONCLUSION

The Project has been a good experience for us

regarding development of a compressive software which

would handle all aspects (Chock lets) Persistent efforts &

dedication that have gone into this project have led us to solve

many intricate problems that any Chock-lets Company faces

in day to day transactions, though there is still enough room

for improvement being amateur software developers, this

project has given is not only an opportunity to express ourtalents but also to gain knowledge.

At last we welcome all suggestion, which could make our

project more efficient & more beneficial to a larger interest of

the corporate sector as well as the society in general.


37/39

BIBLOGRAPHY


38/39

BIBLOGRAPHY

1. MASTERING VISUAL BASIC 6.0

EVANCGELOS PETEROUTSOS.

2. VISUAL BASIC IN 21 DAYS

TECHMEDIA PUBLICATION

3. MICROSOFT DEVELOPER NETWORK (MSDN)

MICROSOFT

4. DATABASE CONCEPT

ELAM SARI.

5. SYSTEAM ANALYSIS AND DESING

AWAD


39/39