22539345 Reliance Fresh Inventory Management System

7/29/2019 22539345 Reliance Fresh Inventory Management System

1/64

ACKNOWLEDGEMENT

Nothing concrete can be achieved without an optimal combination of inspiration andperspiration. No work can be accomplished without taking the guidance of the experts. It

is only the views and advice from ingenious intellectual that help in the transformation of

a product into a quality product.

We owe my sincere gratitude to Mr. Amit Yadav, our honorable project guide.

Last but not the least, no acknowledgement will be complete without mentioning our

parents. They have also supported us throughout the development project.


2/64

INDEX

1. Introduction

2. Software Requirement Specification

3. Software / Hardware Requirement

4. Data Flow Diagram

5. E-R Diagram

6. Coding

7. Execution

8. Testing & Debugging

9. Appendix

10. Conclusion

11. Implementation

12. Maintenance

13. Bibliography


3/64

INTRODUCTION

Management of any departmental store is a very difficult task. Departmental store is an

attempt to computerize the day to day activities of store. It is designed to help the store to

perform daily duties and transaction with ease. Members satisfaction is the foremost

priority of the system.

After a detailed study of the existing system, it is evident that it does not fulfil the

objectives of the organization. It is require to have a computerized information system

with the help of which all tasks can be processed more accurately & quickly. To achieve

this it is necessary to design & develop a new system which will have benefits, over

existing system

The generation of reports in the proposed system will take minimum time & they are

electronically prepared. As a result, it is highly accurate. It will be easy for the users of

the system to compile information at a very high pace, measure the performance over a

period & draw conclusion from the information retrieved by using the proposed system.

As new information are being added to & released from other respective courses every

year. It will be highly used friendly to track & maintaining presentation of all the

students. The system is such that is stand up to the user expectation like easy and faster

retrieval f information. The system is very easy to learn & understand. A native user will

be able to use the system effectively. Information being prepare of electronically can be

said as accurate which is first and foremost condition for taking a crucial decision by the

management. Work carried out by a staff at various stages will be loss time consuming.

Besides this, the proposed system will have the following capabilities.


4/64

SOFTWARE REQUIREMENT SPECIFICATION

System Analysis

System Analysis refers to the process of examining a situation with the intent ofimproving it through better process and methods. System analysis is, therefore, the

process of gathering and interpreting facts, diagnosing problem and using the information

to recommend information in system or in other words, it means a detailed explanation or

description. Before computerizing a system under consideration, it has to be analyzed.

We need to study how it function currently, what are problems and what are requirements

that proposed should meet.

The main components of making software are :

1. System and software requirements analysis.

2. Design and implementation of software.

3. Ensuring verifying and maintaining software integrity.

Information Gathering

The team paid a visit at the site to have a smell of existing system. All relevant

personal were consulted and no information was over-looked. The strategy consisted of:

1. Identify information sources.

2. Revolving a method of obtaining a information from identified source.

3. Using an information from module of organization.

Information Sources

The main sources of information were:

1. Users of the system

2. Presentations an documents using organization

3. Prospectus, manuals and the rulebooks, which specify how various activities are

carried out in the organization.

4. Computer Presentation of existing system.


5/64

UNDERSTANDING THE EXISTING SYSTEM

Existing system here is manual i.e. all the transaction or the information is recorded in

the registers and as simple text files on the computers. The person needy of particular

information has to go through the registers and the text files and then prepare the

information needed by him manually. Besides this, there are many other drawbacks with

the existing system which are listed as under :-

Flexibility in generation of information : The generation of information in the

proposed system takes long time and they are manually prepared.

Long time taken to draw conclusions : As individual files are maintained for

each information, it is very difficult to compile information, measure performance

over a period and draw conclusions from the information stored in two different

files.

User Friendliness : The system is not easy to learn and understand. A native

user cannot use the system effectively.

User Satisfaction : The system is such that it does not stand up to the user

expectations like easy and faster retrieval of information.

Response Time : Being manually driven, the response of all the operations is

very slow.

Error Handling : In case there arise some error in recovering or computation of

information, it is very cumbersome to trace it.

Safety and Robustness : The informative media is accessible by everyone. As

information being the most crucial for the organization, there are no safety measures

for the security of information. Furthermore, information is lying in the organization

in an unorganized manner and does not resemble the real world model.

Lack of Accuracy : Information being prepared manually cannot be said as

accurate which is the first and the foremost condition for taking a crucial decision by

the management.

More Time Consuming : Work carried out by the staff at various stages is

highly time consuming.


6/64

Error Prone Resources : Resources being used by the informative media were

provided by the organization long ago. Due to wear and tear with the resources, they

are highly error prone.

PROPOSED SYSTEM

After a detailed study of the existing system, it is evident that is does not fulfill the

objectives of the organization. To make the objective possible for the organization, it is

required to have a computerized information system with the help of which all tasks can

be processed more accurately and quickly. To achieve this, it is necessary to design and

develop a new system which will have the following benefits over existing system :

Flexibility in generation of information : The generation of reports in the

proposed system will take minimal time and they are electronically prepared. As a

result, it is highly accurate.

Less time is taken to draw conclusions : It will be easy for the user(s) of the

system to compile information at a very high pace, measure the performance over a

period and draw conclusion form the information retrieved by using the proposed

system.

Ease in maintaining information : As new information are being added to and

released from their respective courses every year, it will be highly user friendly to

track and maintain the presentation of all the students.

User satisfaction : The system is much that is stands up to the user expectations

like easy and faster retrieval of information.

Safety and Robustness : The system will be accessible by only the authorized

users. As information being the most crucial for the organization, there are safety

measures for the security of information.

Furthermore, data is stored by the system in an organized manner and resembles the

real world model.

Highly accurate : Information being prepared electronically, can be said as

accurate which is the first and the foremost condition for taking a crucial decision by

the management.


7/64

Less time consuming : Work carried out by the staff at various stages will be less

time consuming.

Error free resources : Resources being used by the system will be compatible

with the latest technologies available in the market. As proposed system uses highly

technically compatible resources, there will be very-very less wear and tear. So the

resources are error free.

Besides this, the proposed system will have the following capabilities :-

Multiple viewer facility : Proposed system is being designed in such a way that

many users can have a view with the system simultaneously. It makes effective and

perfect utilization of man power and resources.

User-friendly interfacing : Since main interaction of the system will be with the

user, the user interface will be interactive and meaningful.

Formatted output : The information generated by the proposed system us highly

formatted and help the users to reach the conclusion quickly.

Better organization of information : Proposed system has the capability to

express the information in a better and more meaningful way. Proposed system uses

modern techniques for storage and retrieval of information.

Accurate round the clock : Proposed system is capable of giving accurate

information round the clock.

Exception Handling : To ensure that the system does not halt in case undesired

situation or events, the system capable enough to handle these unpleasing

circumstances. Proposed system will be capable of taking necessary decisions so

that there is no loss information.

Minimum efforts : Proposed system ensures that very less efforts will be

required to start the presentation.

Capable of adapting to the changes in the outside environment : The system

will have scope to foresee modification and enhancement i.e. it is able to cope up

with the business changes in-order to be compatible with the latest changes in the

industry. Any enhancement to the information can be done without much effort and

is available instantly.


8/64


9/64

SYSTEM REQUIREMENTS

HARDWARE REQUIREMENTS

1. 40 GB Hard Disk

2. 256 MB Ram

3. Floppy Drive 1.44MB

4. Monitor

5. Keyboard

6. Processor PIV

SOFTWARE REQUIREMENTS

1. Visual Basic 6.0

2. Windows 2000

3. MS Access


10/64

DATA FLOW DIAGRAM (DFD)

A DFD is a graphical representation that depicts information flow and the

transforms that are applied as data move from input to output. The basic form of a

DFD is also known as a data flow graph or a bubble chart.

DFD may be used to represent a system or software at any level of abstraction.

DFDs can be partitioned into levels that represent increasing information flow and

functional detail.

A level 0 DFD, also called a fundamental system model or a context model,

represents the entire software element or a single bubble with input and output

data indicated by incoming and outgoing arrows, respectively.

A level 1 DFD may contain five or six bubbles with interconnection arrows. Each

of the processes represented at level 1 is a sub function of the overall system

depicted in the context model.

DFD Notations

It represents a process or transform that is applied to data.

It represents data store-stored information that is used

by software.

It represents one or more data items.

It represents external entities.


11/64

DFD

RELIANCEFRESH

SS_SALES

SS_PURCHASE

SS_STOCK

SS_ITEM

SS_CUSTOMER

CUSTOMER

BILL

CUSTOMER

CustomerDetails

PurhaseDetails

Updated purchaseDetails

Sales DetailsforBill Generation

Stock Details

Stock Details

Generating Bill

Updating SpareDetails

Item Details

Customer Details

Customer Details


12/64

RELIANCE FRESH

USTOMER ITEM PURCHASE SALES SUPPLIER BILL EXIT

STRUCTURE TABLE

DESIGN

ERD (ENTITY RELATIONSHIP DIAGRAM)

ERD are used to represent the object/relationship pair. It was originally purposed for the

design of relational database system. A set of primary components is identified for the

ERD: data object, attributes, relationship and various type indicators. The primary

purpose of ERD is to represent data object and their relationships. Data objects are real

world entities represented by a labeled rectangle. A labeled diamond represents

relationships. Connections between data objects and relationships are established using a

variety of special symbols that indicates cardinality and modality.

ERD Notations


13/64

ENTITY

W WEAK ENTITY

RELATIONSHIP

IDENTIFYING

RELATIONSHIP

ATTRIBUTE

KEY ATTRIBUTE

MULTIVALUED


14/64

COMPOSITEATTRIBUTE

DATA FLOW


15/64

Entity Relationship Diagrams are a major data modeling tool and will help organize the

data in your project into entities and define the relationships between the entities. This

process has proved to enable the analyst to produce a good database structure so that the

data can be stored and retrieved in a most efficient manner.

Stockid

Qoh

RELIANCE FRESH

Ha

s

Customer

id

Address

Name Phone

Has Supplier

idName

Phone

Address

By

Item

Name

Select

Price

id

Has

Sales

Discou

Bill Amount

Date

Customer Id

Bill No


16/64

CODING

Private Sub cmdadd_Click()Text1.Enabled = True

Text2.Enabled = True

Text3.Enabled = TrueText4.Enabled = TrueCommand1.Enabled = True

smddelete.Enabled = True

Cmdrefresh.Enabled = Truecmdedit.Enabled = True

Adodc1.Recordset.AddNew

End Sub

Private Sub cmdclose_Click()

Mainform.ShowCUSTOMERINFORMATION.Hide

Text1.Enabled = False

Text2.Enabled = FalseText3.Enabled = False


cmdadd.Enabled = TrueCommand1.Enabled = True


Cmdrefresh.Enabled = Truecmdedit.Enabled = True

End Sub

Private Sub cmdedit_Click()Dim checksave As Integer

checksave = 1

For Each Control In CUSTOMERINFORMATIONIf TypeOf Control Is TextBox Then

If Control.Enabled = False Then

MsgBox "Please Fill All The Required Data ", vbCritical, "Dear User"checksave = 0

Exit For

End IfEnd IfNext

If checksave = 1 Then

Adodc1.Recordset.UpdateMsgBox "Record Save In Database", vbOKOnly + vbInformation, "Dear User"

End If

cmdedit.Enabled = False


17/64

Adodc1.Recordset.MoveFirst

End Sub

Private Sub Cmdrefresh_Click()

Dim UPDATERECORD As Integer

Dim checkdata As Integercheckdata = 1

'UPDATE THE DATA IN DATABASE

'*****************************************************'check blank text box in form

For Each Control In CUSTOMERINFORMATION

If TypeOf Control Is TextBox Then

If Control.Enabled = False ThenMsgBox "Data is Not Present ", vbCritical, "Dear User"

Cmdrefresh.Enabled = False

checkdata = 0

Exit ForEnd If

End IfNext

If checkdata = 0 Then

MsgBox "You Don't Have Permission To Update This Record ", vbCritical, "Dear User"Else

MsgBox "You Have Permission To Update This Record ", vbInformation, "Dear User"

UPDATERECORD = MsgBox("Are You Want To Update This Record",vbOKCancel, "Dear User")

If UPDATERECORD = 1 ThenText1.Enabled = True


Text3.Enabled = TrueText4.Enabled = True


smddelete.Enabled = False

cmdadd.Enabled = FalseCmdrefresh.Enabled = False

Command1.Enabled = True

End IfEnd If

End Sub

Private Sub Command1_Click()

Dim instatus As Integer

instatus = 1



18/64


If Control.Text = "" Then

MsgBox "Please Fill All The Required Data ", vbCritical, "Dear User"

instatus = 0

Exit For

End If

End IfNext

If instatus = 1 Then

Adodc1.Recordset.Update

MsgBox "Record Save In The Database", vbOKOnly + vbInformation, "Dear User"cmdedit.Enabled = True

Command1.Enabled = False


cmdadd.Enabled = TrueCmdrefresh.Enabled = True

End IfAdodc1.Recordset.MoveFirst

End Sub

Private Sub smddelete_Click()


instatus = 1

confirmdel = MsgBox("Are You Want To Delete This Record", vbOKCancel, "DearUser")


If TypeOf Control Is TextBox ThenIf Control.Enabled = False Then

MsgBox "Textboxes Are Disabled ", vbCritical, "Dear User"

smddelete.Enabled = Falseinstatus = 0

Exit For

End If

End IfNext


Adodc1.Recordset.DeleteMsgBox "Record Deleted In Database", vbOKOnly + vbInformation, "Dear User"


End Sub


19/64

Private Sub cmdadd_Click()

txtitemcode.Enabled = True

txtitemname.Enabled = TrueCommand1.Enabled = True

Adodc1.Recordset.AddNew

End Sub


Mainform.Showiteminformation.Hide

txtitemcode.Enabled = False

txtitemname.Enabled = False

cmdedit.Enabled = TrueCommand1.Enabled = True


cmdadd.Enabled = True

Cmdrefresh(0).Enabled = True

End Sub

Private Sub cmdedit_Click()

Dim UPDATERECORD As IntegerDim checkdata As Integer

checkdata = 1



For Each Control In iteminformation


MsgBox "Data is Not Present ", vbCritical, "Dear User"

cmdedit.Enabled = Falsecheckdata = 0

Exit For

End If

End IfNext


MsgBox "You Don't Have Permission To Update This Record ", vbCritical, "Dear User"Else

MsgBox "You Have Permission To Update This Record ", vbInformation, "Dear User"

UPDATERECORD = MsgBox("Are You Want To Update This Record",

vbOKCancel, "Dear User")

If UPDATERECORD = 1 Then


20/64

txtitemcode.Enabled = True

txtitemname.Enabled = True

cmdedit.Enabled = FalseCommand1.Enabled = False

smddelete.Enabled = False

cmdadd.Enabled = FalseCmdrefresh(0).Enabled = True

End If

End IfEnd Sub

Private Sub Cmdrefresh_Click(Index As Integer)

Dim instatus As Integerinstatus = 1

For Each Control In iteminformation


If Control.Text = "" ThenMsgBox "Please Fill All The Required Data ", vbCritical, "Dear User"

instatus = 0

Exit For

End If

End If

Next

If instatus = 1 ThenAdodc1.Recordset.Update

MsgBox "Record Save In The Database", vbOKOnly + vbInformation, "Dear User"

cmdedit.Enabled = TrueCommand1.Enabled = True


cmdadd.Enabled = TrueCmdrefresh(0).Enabled = False

End If


End Sub

Private Sub Command1_Click()Dim checksave As Integer

checksave = 1

For Each Control In iteminformationIf TypeOf Control Is TextBox Then



checksave = 0


21/64

Exit For

End If

End IfNext

If checksave = 1 Then

Adodc1.Recordset.SaveMsgBox "Record Save In Database", vbOKOnly + vbInformation, "Dear User"

End If

Command1.Enabled = FalseAdodc1.Recordset.MoveFirst

End Sub



instatus = 1

confirmdel = MsgBox("Are You Want To Delete This Record", vbOKCancel, "DearUser")

For Each Control In iteminformationIf TypeOf Control Is TextBox Then


MsgBox "Textboxes Are Disabled ", vbCritical, "Dear User"smddelete.Enabled = False

instatus = 0

Exit For

End If

End IfNext


Adodc1.Recordset.Delete

MsgBox "Record Deleted In Database", vbOKOnly + vbInformation, "Dear User"

End If

Adodc1.Recordset.MoveFirstEnd Sub


22/64

Private Sub CMDOK_Click()If (txtusername.Text = Adodc1.Recordset.Fields(0)) And (txtpassword.Text =

Adodc1.Recordset.Fields(1)) Then

MDIForm1.ShowElse

nm = MsgBox("WRONG USER NAME OR PASSWORD", vbCritical, "DEAR

CUSTOMER")

End IfEnd Sub


End

End Sub


23/64

Private Sub clickAdministration_Click()

ADMINISTRATION.Show

End Sub

Private Sub clickCustomertotal_Click()

CUSTOMERINFORMATION.ShowEnd Sub

Private Sub clickexit_Click()End

End Sub

Private Sub ClickItemInformation_Click()iteminformation.Show

End Sub

Private Sub clickPurchaseForm_Click()PURCHASEFORM.Show

End Sub

Private Sub clickPurchaseInformation_Click()

PURCHASEINFORMATION.ShowEnd Sub

Private Sub clickraisebill_Click()

PRINTBILL.ShowEnd Sub

Private Sub clicksalebill_Click()

End Sub

Private Sub clicksaledetail_Click()

SALEDETAIL.Show

End Sub

Private Sub clicksaleform_Click()

SALEFORM.Show

End Sub

Private Sub clickSupplierInformation_Click()

SUPPLIERINFORMATION.ShowEnd Sub


24/64

Private Sub Timer3_Timer()

Static i As Integer

i = i + 1If i >= 101 Then

Picture1.Visible = False

Timer3.Enabled = FalseMDIForm1.Hide

Mainform.Show

ElseProgressBar1.Value = i

End If

End Sub


25/64


PRINTBILL.Hide

End Sub

Private Sub Command2_Click()CommonDialog1.ShowPrinter

End Sub


26/64





Text6.Enabled = TrueAdodc1.Recordset.AddNew

End Sub

Private Sub cmdedit_Click()Dim checksave As Integer

checksave = 1

For Each Control In PURCHASEFORM




checksave = 0Exit For

End IfEnd If

Next

If checksave = 1 ThenAdodc1.Recordset.Save

MsgBox "Record Save In Database", vbOKOnly + vbInformation, "Dear User"

End If


Private Sub Cmdrefresh_Click()Mainform.Show

PURCHASEFORM.Hide

cmdedit.Enabled = TrueEnd Sub



Private Sub Command2_Click()If (Adodc1.Recordset.BOF = False) Then

Adodc1.Recordset.MovePrevious

ElseMsgBox "Record are Finished ", vbCritical, "Dear User"


End If


27/64

End Sub

Private Sub Command3_Click()If (Adodc1.Recordset.EOF = False) Then

Adodc1.Recordset.MoveNext

ElseMsgBox "Record are Finished ", vbCritical, "Dear User"


End IfEnd Sub


Adodc1.Recordset.MoveLastEnd Sub


28/64


Mainform.ShowPURCHASEINFORMATION.Hide

End Sub



End Sub


Adodc1.Recordset.Delete



29/64

Dim u As Integer

Private Sub cmdclose_Click()Mainform.Show

SALEFORM.Hide

End Sub


Dim i, j As Integer

j = 0i = 0

For i = i To 9

If (t1(j) "") Then

t3(j) = t1(j) * t2(j)j = j + 1

ElseEnd If

Next

End Sub


Dim c, total As Integer

Dim i As Integertotal = 0

c = 0

i = 0For i = i To 9

If t3(c) "" Then

total = total + t3(c)

c = c + 1

Else

End IfNext

Text8.Text = total

End Sub

Private Sub Form_Load()

Text5.Text = DateDim a As String

Do While (Adodc1.Recordset.EOF = False)

a = Adodc1.Recordset.Fields("itemname")

List1.AddItem (a)


30/64

Adodc1.Recordset.MoveNext

Loop

End Sub

Private Sub Text19_Change()

End Sub

Private Sub Text2_LostFocus()

Text1.Text = (Text2.Text * Text3.Text)End Sub

Private Sub List1_DblClick()

If (Text1(u).Index < 9) ThenText1(u) = List1.Text

u = u + 1Else

hs = MsgBox("NO MORE ARE INSERTED", vbCritical, "DEAR CUSTOMER")

End IfEnd Sub


PRINTBILL.txtbdate.Text = Text5.TextPRINTBILL.txtbno.Text = Text6.Text

PRINTBILL.txtdis.Text = Text7.Text

PRINTBILL.txtbamount.Text = Val(Text8.Text) - (Val(Text8.Text) * (Val(Text7.Text) /100))

PRINTBILL.txtcname.Text = Text10.Text

PRINTBILL.txtcaddress.Text = Text9.TextSALEFORM.Hide

PRINTBILL.Show

End Sub


31/64





cmdedit.Enabled = TrueAdodc1.Recordset.AddNew

End Sub


Mainform.Show

SUPPLIERINFORMATION.Hide

Text1.Enabled = FalseText2.Enabled = False



cmdadd.Enabled = TrueCommand1.Enabled = True

smddelete.Enabled = TrueCmdrefresh.Enabled = True

cmdedit.Enabled = True

End Sub

Private Sub cmdedit_Click()

Dim checksave As Integer

checksave = 1For Each Control In SUPPLIERINFORMATION


If Control.Enabled = False ThenMsgBox "Please Fill All The Required Data ", vbCritical, "Dear User"

checksave = 0

Exit ForEnd If

End If

Next

If checksave = 1 ThenAdodc1.Recordset.Update

MsgBox "Record Save In Database", vbOKOnly + vbInformation, "Dear User"

End Ifcmdedit.Enabled = False


End Sub


Dim UPDATERECORD As Integer

Dim checkdata As Integer


32/64

checkdata = 1



For Each Control In SUPPLIERINFORMATION


MsgBox "Data is Not Present ", vbCritical, "Dear User"

Cmdrefresh.Enabled = Falsecheckdata = 0

Exit For

End If

End IfNext


MsgBox "You Don't Have Permission To Update This Record ", vbCritical, "Dear User"

ElseMsgBox "You Have Permission To Update This Record ", vbInformation, "Dear User"

UPDATERECORD = MsgBox("Are You Want To Update This Record", vbOKCancel,"Dear User")

If UPDATERECORD = 1 Then




cmdedit.Enabled = Falsesmddelete.Enabled = False

cmdadd.Enabled = False

Cmdrefresh.Enabled = FalseCommand1.Enabled = True

End If

End IfEnd Sub


Dim instatus As Integerinstatus = 1

For Each Control In SUPPLIERINFORMATION

If TypeOf Control Is TextBox ThenIf Control.Text = "" Then


instatus = 0Exit For

End If

End If

Next


33/64


Adodc1.Recordset.Update

MsgBox "Record Save In The Database", vbOKOnly + vbInformation, "Dear User"cmdedit.Enabled = True

Command1.Enabled = True

smddelete.Enabled = Truecmdadd.Enabled = True

Cmdrefresh.Enabled = False


End Sub

Private Sub smddelete_Click()Dim instatus As Integer

instatus = 1

confirmdel = MsgBox("Are You Want To Delete This Record", vbOKCancel, "Dear

User")For Each Control In SUPPLIERINFORMATION


MsgBox "Textboxes Are Disabled ", vbCritical, "Dear User"

smddelete.Enabled = Falseinstatus = 0

Exit For

End If

End IfNext


Adodc1.Recordset.DeleteMsgBox "Record Deleted In Database", vbOKOnly + vbInformation, "Dear User"

End If



34/64

OUTPUT


35/64


36/64


37/64


38/64


39/64


40/64


41/64


42/64


43/64


44/64


45/64


46/64


47/64


48/64


49/64


50/64


51/64


52/64


53/64


54/64

TESTING AND DEBUGGING

INTRODUCTION:-

The implementation phase of software development is concerned with translating design

specification into source code. The preliminary goal of implementation is to write source

code and internal documentation so that conformance of the code to its specifications can

be easily verified, and so that debugging, testing and modifications are eased. This goal

can be achieved by making the source code as clear and straightforword as possible.

Simplicity, clarity and elegance are the hallmark of good programs, obscurity, cleverness,

and complexity are indications of inadequate design and misdirected thinking.

Source code clarity is enhanced by structured coding techniques, by good coding style,

by, appropriate supporting documents, by good internal comments, and by feature

provided in modern programming languages.

The implementation team should be provided with a well-defined set of software

requirement, an architectural design specification, and a detailed design description. Eachteam member must understand the objectives of implementation.

SOME SPECIAL TERMS IN TESTING FUNDAMENTAL

1. Error

The term error is used in two ways. It refers to the difference between the actual output of

software and the correct output, in this interpretation, error is essential a measure of the

difference between actual and ideal. Error is also to used to refer to human action that

result in software containing a defect or fault.


55/64

2. Fault

Fault is a condition that causes to fail in performing its required function. A fault is a

basic reason for software malfunction and is synonymous with the commonly used term

Bug.

3. Failure

Failure is the inability of a system or component to perform a required function according

to its specifications. A software failure occurs if the behavior of the software is the

different from the specified behavior. Failure may be caused due to functional or

performance reasons.

SOME OF THE COMMON USED STRATEGIES FOR TESTING ARE AS

FOLLOWS:-

a. Unit Testing

The term unit testing comprises the sets of tests performed by an individual programmer

prior to integration of the unit into a larger system. The situation is illustrated as follows:

Coding & debugging ------- Unit testing ------- Integration testing

A program unit is usually small enough that the programmer who developed it

can test it in great detail, and certainly in greater detail than will be possible when the unit


56/64

is integrated into an evolving software product. In the unit testing the programs are tested

separately, independent of each other. Since the check is done at the program level, it is

also called program teasing.

b. Module Testing

A module and encapsulates related component. So can be tested without other system

module.

c. Subsystem Testing

Subsystem testing may be independently design and implemented common problems are

sub-system interface mistake in this checking we concentrate on it.

There are four categories of tests that a programmer will typically perform on a program

unit.

1) Functional test

2) Performance test

3) Stress test

4) Structure test

1) Functional Test

Functional test cases involve exercising the code with Nominal input values for which

expected results are known; as well as boundary values (minimum values, maximum

values and values on and just outside the functional boundaries) and special values.


57/64

2) Performance Test

Performance testing determines the amount of execution time spent in various parts of the

unit, program throughput, response time, and device utilization by the program unit. A

certain amount of avoid expending too much effort on fine-tuning of a program unit that

contributes little to the over all performance of the entire system. Performance testing is

most productive at the subsystem and system levels.

3) Stress Test

Stress test are those designed to intentionally break the unit. A great deal can be learned

about the strengths and limitations of a program by examining the manner in which a

program unit breaks.

4)Structure Test

Structure tests are concerned with exercising the internal logic of a program and

traversing particular execution paths. Some authors refer collectively to functional

performance and stress testing as black box testing. While structure testing is referred

to as white box or glass box testing. The major activities in structural testing are

deciding which path to exercise, deriving test date to exercise those paths, determining

the test coverage criterion to be used, executing the test, and measuring the test coverage

achieved when the test cases are exercised.


58/64

DEBUGGING

Defect testing is intended to find areas where the program does not confirm to its

specifications. Tests are designed to reveal the presence of defect in the system.

When defect have been found in the program. There must be discovered and removed.

This is called Debugging. Defect testing and debugging is quite different testing

establishes the existence of effects and debugging is concerned with locating and

correcting this defect.

Locate

Error

Design

ErrorReport

RepairError

Request

Theprogram


59/64

APPENDIX

Data Control :-

The data control gives you access to database without any programming.

Module :-

Modules are used to store procedure. Procedure stored in a module can be called from

any part of the application. This is one method by which forms and procedures in

different forms can exchange information.

Text Box:-

This control displays that the user can edit.

Frame:-

This control is used to draw boxes on the form and to group other elements.

Command Button :-

A common button represent an action that is carried out when the used click the button.


60/64

CONCLUSION

1. The RELIANCE FRESH is automated as hand written documentation is minimized to

a bare minimum once the S/w is fully implemented.

2. The data can be easily backed up onto a reliable media so that no or minimal data loss

is there in case of system crash.

This project has made us require a professional outlook towards a problem statement and

solving it to the best and maximum.


61/64

IMPLEMENTATION

This project is successfully implemented in Visual Basic and MS Access and was seen in

all respect of specification. Any number of record can be maintained according

to given schedule of store. Till now it is successfully working. As far as the

modification in the this Project is considered, this facility is build in this

project. You can add an customer information and also can delete his

information from the database in case of his exit from this organization.

It is granted that this project will work as it is at Present and also in future as all

specifications are along the time and frame of the department. Also this project can be

successfully implemented in any organization.


62/64

MAINTENANCE

Maintenance Phase:

Any change to any component of the product (including documentation) after it has

passed the acceptance test.

Types of maintenance:

1. Perfective maintenance

Client requests changes to improve product effectiveness

Add additional functionality

Make product run faster

Improve maintainability

2. Adaptive maintenance

Responses to changes in the environment in which the product operates

The product is ported to a new compiler, operating system, and/or hardware

3. Corrective Maintenance

Suppose that the maintenance programmer has located the fault/Problem

How to fix it without introducing a regression fault

Major skills required for corrective maintenance

Superb diagnostic skills

Superb testing skills

Superb documentation skills

Difficulty of Maintenance

About 67% of the total cost of a product accrues during the maintenance phase

Maintenance is a major income source

Nevertheless, even today many organizations assign maintenance to

Unsupervised beginners, and Less competent programmers

The Rewards of Maintenance


63/64

Maintenance is a thankless task in every way

Maintainers deal with dissatisfied users

If the user were happy, the product would not need maintenance

The users problems are often caused by the individuals who developed the product,

not the maintainer

The code itself may be badly written

Maintenance is despised by many software developers

Unless good maintenance service is provided, the client will take future

development business elsewhere

Maintenance is the most important phase of software production, the most difficult

and most thankless


64/64

BIBLIOGRAPHY

1. Complete Reference Visual Basic 6.0 - By Hebert Schild

2. Mastering Visual Basic 6.0 - By Evangelos Petroutsos

3. Visual Basic 6 from ground up - By Gary Cornell

Documents

22539345 Reliance Fresh Inventory Management System