You are on page 1of 48

Jewellery shop Management System




UNDER RAJEEV GANDHI TECHNOLOGICAL UNIVERSITY, BHOPAL, M.P. BY 0807CA101075 0807CA101079 0807CA101087 Under Guidance of Professor Kamlesh Malpani Professor Gopal Phoolkar Session July-Dec 2011 Prem Kumar Patel Rajendra Kumar Yadav Ritu Malviya

ACKNOWLEDGEMENT The project entitled Jewelry shop Management System cannot be completed without a word of thanks to those people whose invaluable support & guidance led to its successful completion. I extend my sincere through & grateful to Prof. S. R. Gupta (HOD).

The project entitled Jewelry shop Management System cannot be completed without a word of thanks to those people whose invaluable support & guidance led to its successful completion. Prof. Kamlesh Malpani, Prof. Gopal Phoolkar and Computer center that have been continuous source of inspiration & guided the development of the whole project. His guidance not only helped us technically, but also kept our morale high during the development of the project.

I also avail this opportunity to express our heartiest thanks to all Professors of SVIM, Indore & my classmates for providing me invaluable support & inspiration all through MCA course.

Page 2




This is to certify that the work embodied in this dissertation entitled Jewelry shop Management System has been satisfactorily completed by Prem Kumar Patel (0807CA101075), Rajendra Kumar Yadav (0807CA101079), and Ritu Malviya (0807CA101087). It is a bonafide piece of work, carried out under my guidance in the Master of Computer Application, Shri Vaishnav of Institute Management, Indore for the partial fulfillment of the Master of Computer of Applications degree during the academic Session July-Dec, 2011.

Prof. Kamlesh Malpani (SVIM, Indore) Prof. Gopal Phoolkar (SVIM, Indore)

Approved By Prof. S. R. Gupta Head, MCA

Page 3




This is to certify that the work embodied in this dissertation entitled Jewelry shop Management System has been satisfactorily completed by Prem Kumar Patel (0807CA101075), Rajendra Kumar Yadav (0807CA101079), and Ritu Malviya (0807CA101087). It is a bonafide piece of work, carried out under the guidance of Project mentor in the Master of Computer Application, Shri Vaishnav of Institute Management, Indore for the partial fulfillment of the Master of Computer of Applications degree during the academic Session JulyDec, 2011.

External Examiner

. Internal Examiner

Page 4

1. Introduction of client/organization 2. Problem Investigation Introduction to Existing System Objective 12 Goal & Need of project Solution suggested 3. System analysis Information Gathering Online Observation Interviews Questionnaires Record Review Process model used 1.) Select model 2.) Advantage of select model Limitations to current system Introductions to proposed system Merits of proposed system 18 1.) Required documents 2.) Hardware & software requirements 3.) Time Team organization Specify the role in team. Schedule 5. Feasibility study 20 Project resources 07 08

4. Project Planning

Page 5

6. System Design DFD ERD Data base design


78. Tools used and descriptions Front end Back end Reason for tools selected


8. Implementation Programming approach followed Top Down Approach / Bottom Up Approach Screen layouts Forms Layouts Reports Layouts 9. Testing Testing Objectives of testing methods Testing methods (Test cases used) 10. Maintenance 11. Conclusion Conclusion and discussion Limitations Suggestion for future extension of work 12. Bibliography



46 47


Page 6

PUNJAB JWELLERS E-biller is a client based billing system. This system deals with shops, it provides a complete solution to all problems that arise in conventional client based billing software. E-biller is customizable software; this enables it to be used anywhere in the shopping system. E-biller has one Component; the windows form application for the branch. It can be easily used to any system where we want to put the billing system. It is an offline system so we dont need any internet facility to run the program. It can replace the manual billing entry of book keeping. The client uses MS Excel, and maintains their product list, customer list, and prints the invoice, however it is not possible them to share the data from multiple system in multi user environment, there is lot of duplicate work, and chance of mistake. When the product price are changed they need to update each and every excel file. There is no option to find and print previous saved invoice. There is no security; anybody can access any report and sensitive data, also no reports to find out the sales volume, stock list, and summary report. This e-billing and invoicing system is used to overcome the entire problem which they are facing currently, and making complete atomization of manual billing and invoicing system. It is far faster than the conventional billing system and saves so much of time to increase the efficiency of billing work for the shop. This is the system which will provide easy entry, viewing products and keeping the billing records safe in the database. The owner of shop can easily view all the transactions of billing from the system without any problem. He can keep the track of the billing of the shop without any error.

Page 7

CHAPTER-2 2. PROBLEM INVESTIGATION 2.1 The Future Digital Jewelry Shop

The digital Jewelry Shop of the future will provide electronic access to information in many different forms. Recent Technological advances make the storage and transmission of digital Jewelry information possible. This paper will describe the design of a Jewelry Shop Management System (DJSMS) suitable for storing, indexing, searching, and retrieving video and audio information and providing that information across the internet or the evolving National Information Infrastructure. To be an effective Jewelry Shop, users need to be able to find the Jewelry items they want. Realizing this goal will require ground breaking research into automatic content-based indexing of Jewelries that will significantly improve the users ability to access specific segments of interest with Jewelries. In our approach, Jewelries items and transcripts will be digitized, this will allow users to quickly search indices for multiple Jewelries to locate the segments of interest, and to view and manipulate these segments on their remote computer. While this technology would be applicable to any collection of Jewelries, we will target educational users, providing teachers with the ability to select segments of nature and/or current events videos which complement their lessons.

Page 8

2.2 Introduction to Existing System

Current system is the one that work either offline or online. The online system requires a fulltime internet facility. The offline system wont support multi shop managing. The online system needs separate software for head office and local shops. This made the controlling very tough since one should install software in a system to view the selling rate or even to send a simple text message to a local shop. The security features were normal routines. The non-availability of internet facility in a single shop may lead to complete shutdown of the system due to synchronization problem. Many of the multi branched shops were running independent software system for billing, this lead to the overhead problem in calculation of monthly sales. These systems were not able to compare the sales of two different shops. There are many drawbacks for the present system.

Drawbacks: Online billing systems wont support offline billing. Offline billing systems wont support Multi shops. Inter shop communication was not supported. Low speed of operation due to huge local database. Manual billing was difficult. Customizing of software was not possible.

Page 9

2.3 Goal & Need of Project

To design and develop a Information System for a Jewelry Shop Management System , so as to make the task of management more efficient , speedy and effective using the concepts of database design and following the steps of IT project management.

The current system makes the work of Jewelry Shop Management System easier. The project Jewelry Shop Management System can help to the activity performed in a Jewelry Shop Management System to reduce the complexity in different fields like Customer data, transaction data, and data about items, managing the bills actively, and what the customers want, what are the titles available etc.

2.4 Objectives
3 4 5 6 7 8 9 The objectives of this system are as follows: Scientifically manage the project development life cycle. Systematically study the working of Jewelry Shop. Develop Systems Requirement Specification for the Jewelry Shop. Design a suitable model, which can represent the Universe of Database. Give documentation on the user requirements. Design a suitable conceptual model, which can represent the Universe of Database.

10 Design a logical model suitable for Database implementation. 11 Perform Testing and closure activities.

Page 10

2.5 Solution Suggested

Following are the solutions suggested for Scenario: 1. Learn about the problems with the present system. 2. Implement strategies and solutions to pave away the identified problems. 3. Develop a plan to solve the problems through a software solution. 4. To integrate the informational needs of the various aspect of Jewelry Shop. 5. To result a systematic data storage system. 6. To produce logical information out of the variety of data.

Page 11


3.1 Information Gathering

Information gathering refers to requirements gathering for the System. It includes study of the Project scenario and searching for the data that needs to be stored and retrieved, and also how the system will interact with the users.

1. Online Observation
This technique refers to gathering requirements for the system by searching for the resources available online, so that facts about already existing similar systems could be studied. This forms the layout for the system that is to be built.

2. Interviews
This technique refers to gathering requirements for the system by interviewing the clients. Here, the clients show how they want the system to be and how will the system interact with the users, what data will be stored, what data will be retrieved and how.

3. Questionnaires
This technique refers to gathering requirements for the system by asking questions. These questions can be asked by team members themselves, or else Users of the already existing similar systems.

4. Record Review
After requirements gathering phase, the facts gathered about the system are reviewed, so that the overall layout and working of the system could be analyzed and studied.

Page 12

3.2 Process Model Used

A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.

1. Select Model
Water fall model

One such approach used in software development is the waterfall model ,waterfall model approach was first a process model to be introduced and fallowed widely in software engineering to ensure success of the project . In waterfall approach the whole process of software development is divided in to separate phases .these phases in waterfall model are A: Requirement specification phase B: software design C: implementation D: testing and maintenance

Page 13

Requirement gathering and analysis System design

Implementation testing Deployment of system Maintenance

a. Advantage Of Select Model

1: compartmentalization of work and control in the waterfall model 2: one phase is over then other phase is start 3 :it maintain quality of the project and easier to understand

Page 14

3.3 Limitations To Current Systems

The current system that is being used in the Jewellery Shop Management System is completely manual in nature. Information about various customers is maintained separately in registers. The entries made in each and every register name and year. These serial numbers are unique in nature for a particular register. The serial numbers are used for searching the records of various sites. There are total of 8-10 registers, which are used to maintain details about various works of the firm. These registers contain information like customer information, Items information and stock information, Customers transaction data, etc. The following points describe the problem domain faced by the current users: 1. Non-Integration of all the records of the Jewellery Shop Management System. 2. Most of the bills are written on a paper and are sent to accounts department for final billing, which gives scope of human error. 3. All the information in the system is also maintained on papers. This results in wastage of precious time and energy. 4. Customer attraction is absent as he has to wait for things like summary report, bills. 5. Customer is also not satisfied as most of the reports and bills are handwritten in MS Word. 6. Records may have to be edited or re-entered adding to the cost. 7. Using manual storage and retrieval methods increases the potential pf misplaced document and compromises clients confidentiality. These enclosures are enormous amount of time.

Page 15

3.4 Introductions to Proposed Systems

The following points will give an overview of the proposed system 1. The proposed system will be a completely automated system, which will manage the entire operability of the Jewellery Shop Management System. 2. The system will also generate appropriate reports for different records. 3. All limitations of the present system will be removed to make the system more efficient. 4. The proposed system will help the user to retrieve the information as quickly as possible. 5. The system will build in such a way that it avoids data redundancy. 6. The system will provide backup plans to avoid data loss that is high priority. 7. It will be scalable so that in near future the system can be expanded and customized to the firms needs. 8. The system will be reliable enough to perform in adverse conditions. 9. The system will provide a detailed help and user manual to assist the end user. 10. The system will fulfil all necessary requirements of the end user as much as possible. 11. The system will provide a user friendly interface with realistic view. 12. The system will provide an error free environment. 13. The system will be capable enough to reduce the number of registers i.e. system will update the data from one register to another by a single click. 14. The system will provide search facilities to find a specific entry from the database.

Page 16

3.5 Merits of Proposed System

The proposed system is developed in order to eliminate the limitations of the current system. The aim of the proposed system is to address the limitations of the current system. The requirements have been gathered from feedback obtained from owner of the Video Library. They are also based on the objectives of the proposed system: 1. Reduce data duplication by use of RDBMS. 2. Implement validation techniques and checks that will help reduce the margin of error in operations. 3. Provide adequate data backup facilities in order to ensure system restart even after a calamity. 4. Since the system will be a RDBMS, searching and cataloguing of data will not be a problem. 5. The system will ensure consistency. 6. Should arrive at and obtain a complete automation of all the registers as well as the registers, which are used for smooth working of the firm. 7. Should produce reusable and extensible model/code. 8. Should develop a foolproof system that simulates and replaces the present manual system.

Page 17

CHAPTER-4 4 PROJECT PLANNING 4.1 Project Resources 1. Required Documents


Project Report

Project report provides an introduction to current system and system to be built. It gives the brief knowledge of current system.


Project Documentation

A complete documentation will be given in the form of SRS. Software requirement specification (SRS) will provide an introduction an introduction of current system and the system to be built. This overview includes the purpose of SRS and a brief knowledge of current system. The overview also provides an introduction of the proposed system.

1.3 Pre- Installation

The installation of prior softwares like visual studio 6.0 and MS Office. This software is essential for the smooth and proper running project.

4.2 Hardware & Software requirements

2.1Hardware RequiredMinimum 40 GB hard disk 128/256 MB RAM Celeron 1.70 GHZ/Pentium 4

Page 18

2.2 Software RequiredWindows 98/2000/XP/NT/2003 Microsoft Office 2000/or later Microsoft visual studio 6.0

4.3 Time
Successful information system projects are those that have been successfully managed. Poorly planned systems project to meet the schedule and disappoint the enthusiastic users. Those projects that are developed on time have these characteristics in common1. A carefully formulated estimation of time requirements. 2. A mean for management to monitor progress. 3. A mean of comparing actual against planned performance. 4. Sufficient information to deal with problems when they arise. One of the most aspects of project management is the formulation of estimates of the time required to develop a system. Estimates and time scheduling is an approximation of the hours, days, or months. The time includes collection requirements for the system from the current users of the similar system available, then actually implementing the system with the help of development tools like visual basic 6.0(for front end) and MS Access(for back end).

Page 19


One of the many stages in the system development life cycle is determining the feasibility of a project. A measure of how beneficial or practical the development of a software system will be to an organization. This analysis recurs, and how that technology can be of benefit. These studies can include policy recommendations for imaging systems, document management, and workflow applications for an interactive process of collecting and analyzing through the life cycle. Feasibility studies examine the organization data with the client and searching for cost-effective, viable technical and non technical solutions.

5.1 Economic Feasibility

The economic analysis of one project counts for the cost effectiveness of the project. The economic feasibility study (EFS) should demonstrate the net benefit of the proposed application in light of the benefits and costs to the agency, other state agencies and the general public as a whole. Economic feasibility is generally the bottom-line consideration for most of the systems. Economic justifications includes a broad range on concerns that include cost-benefit analysis, long term corporate incomes strategies, impact on other profit centres or products, cost of resources needed for the development etc. Economic feasibility is measured under the following heads: 1. The project fits in the proposed budget. 2. The project satisfies the economic constraints. 3. Weather the existing hardware will meet the budget proposed. 4. Weather new software is required for its working.

Page 20

5.2 Technical Feasibility

The technical feasibility of the system counts for the technical acceptance of the system. It refers to the ability of the process to take advantage of the current state of the technology in pursing farther improvement. The technical available technology should be considered. The criteria for technical feasibility is 1. Easy to use: the users were assumed to be normal ordinary people having knowledge of simple computer operation, so ease of use is a very essential factor if we want to get the job actually done quickly.

2. Reliable: we assume that the device will receive a lot of shock, from mishandling, vibrations, etc.

3. Easy maintenance of information Since the records of all the activities performed by the various sites are stored digitally and with the use of software it becomes east to retrieve and maintain data. It is also easy to backup the data.

4. Save time and effort Since the entire data management task is done by the system, it saves lot of time, effort and energy of the user to get the work done.

5. Various processes running The various processes that will be running through the project execution time can be summarized as follows:

1. User login 2. Changing password 3. Adding new item 4. Adding new copies of existing item

Page 21

5. View an item 6. Searching an item 7. Entry of transaction detail(rent/purchase) 8. Return of items, if rented 9. Searching a customer 10. Looking at transactions and incomes 6. Secure: the system should be secure enough to provide access to only authorized users. In our project the technical feasibility is considered up to a greater extent. The software is build using visual basic 6.0. Thus the problem of non availability of software is eradicated. The backend of the system is MS access, which is freeware database application. Proposed system can be expanded in future if required. Proposed system also provides data security by password protecting.

Page 22

CHAPTER-6 6. SYSTEM DESIGN 6.1 DFD (Data Flow Diagram)




System use

6.2 ERD

User valid ation

Service to user

System responsible

Page 23

System flow diagram




Check database

Process out Check out authority Database

Check status Enquiry authority Database

Search guest Enquiry Authority


Page 24

6.2 (Entity-Relationship Diagram)

Login Password


Login Name

Login Id

Item Id Item Jewelry Type

Item Name

Item Weight

Present Item Id

Purchase Have Price/Quantity Item Quantity Bill

C. Mobile No. Customer C. Phone No. C. Name C. Id C. Address

Bill No.

C. Id Item Id

Page 25

6.3 Database Design

user A Naresh PANJAB JWELERS a prem PANJAB JWELERS password

Item_Id Item_Name 1 RING 2 EARRING 3 PENDANT 4 NECKLACE 5 DIAMONDRING 6 BROOCH 7 BRACELET 8 BANGEL 9 GOLD RING 10 BELT 11 RING 12 CHAIN 13 CLIP Gold Gold Gold Gold Gold Gold Gold Gold Gold Silver Silver Gold Silver Item_Type Item_W 10 11 12 13 15 14 16 17 18 20 10 100 3

Page 26

S_Id 1 2 3 5 6 7 8 9 10 11 17 18 19 20 21 22 Item_Id 1 2 3 4 5 6 6 7 8 8 9 9 10 11 12 12 U_Q 4 2 6 2 2 1 0 1 1 0 2 0 5 4 9 0

C_Id 1 2 3 4 5 6 7 8 9 10 13 14 15 16 17 18 19 C_Name ABC a b cc dd nm mm abc ww q v nnnn gh asas vb q a C_P_No 0 0 C_M_No C_Add ABC a b cc dd nm mm abc ww q v nnnn gh asas vb q a



Page 27

B_Id 1 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 21 23 25 27 28 29 30 31 C_Id 1 2 3 3 3 4 4 5 5 6 7 8 9 10 11 14 15 16 17 18 18 18 19 19 Item_Id 1 2 1 4 6 1 2 1 2 1 1 1 1 1 2 10 2 2 1 3 6 8 1 2 S_POI $1,000.00 $3,000.00 $1,000.00 $5,000.00 $2,000.00 $2,000.00 $2,000.00 $3,000.00 $4,000.00 $2,000.00 $4,000.00 $1,500.00 $1,000.00 $1,800.00 $2,222.00 $1,111.00 $2,222.00 $3,333.00 $1,000.00 $444.00 $666.00 $88.00 $1,200.00 $6,000.00 T_POI $2,000.00 $6,000.00 $3,000.00 $10,000.00 $4,000.00 $4,000.00 $4,000.00 $6,000.00 $8,000.00 $2,000.00 $4,000.00 $1,500.00 $2,000.00 $3,600.00 $4,444.00 $1,111.00 $2,222.00 $3,333.00 $1,000.00 $444.00 $666.00 $88.00 $2,400.00 $6,000.00 P_AOI 2 2 3 2 2 2 2 2 2 1 1 1 2 2 2 1 1 1 1 1 1 1 2 1

Page 28


7.1 Front End

The Front end, i.e., the User Interfaces is implemented in: Microsoft Visual Basic 6.0

7.2 Back End

The Back end, i.e., the Database is implemented in: Microsoft Access 2003

7.3 Reasons for Tools Selected 1. Visual basic 6.0

Visual basic is not just a language. Its an integrated development environment in which you can run, test, and debug your programs. Visual basic comes in three flavours *the visual basic learning edition *the visual basic professional edition *the visual basic enterprise edition The visual basic learning edition is the introductory edition that nets you easily create windows applications. The visual basic professional edition is for computer professionals and includes advanced features such as active x and internet control. The visual basic enterprise edition is the most advanced edition and is aimed at programmers who built the applications in a team environment. It includes all the features of professional

Page 29

edition plus tools such as visual source safe (a version control system) and automation and component manager. Advantage- a standard language means that, no matter which program you use, you have to learn only on set of statements and techniques. VB is easier to use than most programming language. You can also create dialog box by simply drawing appropriate controls on to a document or on to separate user form by providing title codes as desired by user. VB is a full blown programming environment that includes high level programming constructors as well as every access to every future in the application it also include the powerful tools and the ability to create a help system .

Page 30

CHAPTER-8 8. Implementation 8.1 Programming approach followed

The programming approach followed while development of the system is Bottom-up approach. This approach is implemented by developing the sub-modules, then integrating those submodules into the wholly integrated, fully functional jewellery shop management system. A crucial phase in the system life cycle is the successful implementation of the new system design. Implementation simply means converting a new system design in to operation.

Bottom-up Approach
A bottomup approach is the piecing together of systems to give rise to grander systems, thus making the original systems sub-systems of the emergent system. Bottom-up processing is a type of information processing based on incoming data from the environment to form a perception. Information enters the eyes in one direction (input), and is then turned into an image by the brain that can be interpreted and recognized as a perception (output). In a bottomup approach the individual base elements of the system are first specified in great detail. These elements are then linked together to form larger subsystems, which then in turn are linked, sometimes in many levels, until a complete top-level system is formed. This strategy often resembles a "seed" model, whereby the beginnings are small but eventually grow in complexity and completeness. However, "organic strategies" may result in a tangle of elements and subsystems, developed in isolation and subject to local optimization as opposed to meeting a global purpose.


User and business awareness of the product. Benefits are realized in the early phases. You can replace many manual processes with early automation. You can implement password management for a large number of users. You do not have to develop custom adapters in the early phases.

Page 31

Your organization broadens identity management skills and understanding during the first phase.

Tivoli Identity Manager is introduced to your business with less intrusion to your operations.


The organizational structure you establish might have to be changed in a later roll-out phase.

Because of the immediate changes to repository owners and the user population, the rollout will have a higher impact earlier and require greater cooperation.

This strategy is driven by the existing infrastructure instead of the business processes.

Implementation of Computerized System To Replace Old One

This involves creating computer compatible files, training the operating staff and installing hardware, terminals, and telecommunication network before the system is up and running.

Conversion means changing from one system to another. The objective is to put the tested system into operation while holding costs, risks and personnel irritation to minimum. It involves: Creating computer-compatible files Training the operation staff and Installing terminals and hardware

Page 32

8.2 Screen layouts 1 Forms Layouts

Welcome Screen

Page 33

Login Screen

Page 34

Change Password

Page 35

Adding New Item

Page 36

Update Jewellery Stock

Page 37

Showing All Jewellery

Page 38


Page 39


Page 40

2 Reports Layouts


Page 41


Testing is an important step in software development life cycle. The process of testing takes place at various stages of development in programming. This is vital step in development life cycle because the process of testing helps to identify the mistakes and sends the program for correction.

Objectives Of Testing Methods

Testing is a process of executing a program with the intent of finding an error. A good test case is one that has high probability of finding an as-yet-undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error.

The objective is to design tests that systematically uncover different classes of errors and to do so with a minimum amount of time and effort.

Test Planning
Test planning is concerned with setting out standards for the testing process. The test plans are intended for both management and software developers. The preparation of test plans usually starts at the end of the requirements analysis stage and developed throughout the design stage. Plans should be made for both development testing (done by software developers) and independent testing (done by an independent team of testers). We will look at techniques for testing in the small (i.e. testing individual components) first. Later we will discuss techniques of testing in the large i.e. testing clusters of components and testing the complete system. We will discuss black box and white box techniques. In black box testing, the tester does not know the internal structure to design test cases. These techniques are applicable to both traditional and

Page 42

object oriented systems. In object oriented systems, test techniques would be applied to the operations within a class. It is impossible to test exhaustively (i.e. test every possible situation that might occur). The goal is to select a set of test cases, which provides good coverage and can be completed with a reasonable amount of effort.

Testing Methods (Test Cases Used)

Testing requires that the developer discard preconceived notions of the correctness of software just developed and overcome a conflict of interest that occurs when errors are uncovered.

Testing a software system usually involves 4 stages:

1. Unit Testing In unit testing, individual components are tested individually. This can
be done throughout the coding process, as each unit is completed. White box methods are typically used for unit testing.

2. Integration Testing It is a systematic technique for constructing the program

structure while conducting tests to uncover errors associated with interfacing. An incremental approach to integration means that we build the program by increments and test after each piece is added on. Two incremental approaches are: Top Down Integration Top down integration is appropriate for testing systems built using the traditional view. The structure chart created during the design stage shows the control hierarchy of the program. We start with the main control module and add other modules in either a depth-first or breadth-first manner. Breadth-first integration allows us to test all the high-level modules before the low-level ones. Depth-first integration allows us to test certain major control paths of the structure early in the testing stage.

Page 43

Bottom-Up Integration It is opposite of top-down testing. We first test modules

at the lower levels of the control hierarchy and then we work towards the top. Test drivers are used to exercise the low-level components. Then the components are grouped into clusters sometimes called builds and these clusters are tested together with another driver. Drivers are removed and larger clusters are combined, as we move upward in the program structure.

Regression Testing It is the process of checking whether changes made to the

system has introduced unintended behavior or additional errors. It generally involves reexecuting a small subset of the test cases that have already been executed. There should also be additional tests that focus on the components that have changed and the components most likely to have been affected by the change.

3. Validation Testing It refers to the process of checking that all reasonable

expectations for the software are met. These expectations are usually defined in the requirements specifications developed during the analysis stage. Usually, black-box testing techniques are used for validation testing and tests are done by independent testers (customers or members of an independent test team from the developers organization). It includes acceptance testing done by the customer or potential customers. Acceptance testing involves both alpha testing and beta testing. A customer conducts alpha testing at the developers site. The testing is done in a controlled setting with the developer presence. Beta testing is conducted at one or more customer sites. The developer is usually not present during beta testing and thus cannot control the environment. The customer must report the errors to the developer as beta testing takes place.

4. SYSTEM TESTING When a software system is part of a larger system containing

many other elements as hardware, people, etc. additional tests are necessary once the whole system is put together. Tests should be designed so that it is possible to answer the questions listed below:

Page 44

Recovery: How well does the system recover from faults and how quickly does it resume processing?

Security: How secure is the system? How easy it is for unauthorized users to break into the system?

Stress: How well does the system stand up to abnormal situations in which there are unusual demands for resources? Performance: Does the system meet all performance requirements? Debugging It is the process of locating and fixing an error, after testing has determined that the error exists. Usually locating the error rather than fixing it, takes the majority of the effort required for debugging. After fixing an error, it is important to do regression testing to make sure that the correction did not introduce new errors into the program.

Page 45


Maintenance is the enigma of the system development. It holds the software industry captive, trying up programming resources. Maintenance can be classified as corrective, adaptive or perceptive

Corrective maintenance means repairing process or performance failures or making changes because of previously unconnected problem or false assumption.

Adaptive maintenance means changing the program function.

Perceptive maintenance means enhancing the performance or modifying the programs to respond to the users additional or changing needs.

For providing maintenance and security to databases the users have been classified in two types the administrator and general user. Administrator handles the maintenance part and other system design.

Documentation is as much a part of maintenance as it is of system development as system is well documented user can understand the system unambiguously, so modifications in the programs can be performed in the system with great case.

Page 46

CHAPTER-11 11. CONCLUSION 11.1 Conclusion and Discussion

Following are the conclusions and lessons learnt throughout the project lifecycle: 1. Coordination among team member. 2. Communication with end user. 3. Complete the task within the time span. 4. Document design. 5. Decide team members responsibility based on personnel interests and each team members strength.

11.2 Limitations
As we are also student according to our views we have tried our best of fulfill the Requirement about the project inspire other awareness may be left some important things. As we have realized later after discussion in our friends.

1. Visual Studio can make system slower. 2. Any Unexpected bug can be cause the data failure.

Page 47


1.Complete reference: Visual Basic 6.0, Tata McGraw-Hill Publication by jerky 2.Complete reference: Visual Basic 6.0, Tata McGraw-Hill Publication by Bradley 3.Mastering Visual Basic 6.0, Gupta Publishing by Petroutsos Davis 4.Mastering Visual Basic 6.0, Gupta Publishing by Evangelos Petroutsos

Page 48