Professional Documents
Culture Documents
Reliance Fresh Inventory Management System
Reliance Fresh Inventory Management System
Reliance Fresh Inventory Management System
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.
INDEX
1. Introduction
5. E-R Diagram
6. Coding
7. Execution
9. Appendix
10. Conclusion
11. Implementation
12. Maintenance
13. Bibliography
INTRODUCTION
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.
SOFTWARE REQUIREMENT SPECIFICATION
System Analysis
System Analysis refers to the process of examining a situation with the intent of
improving 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.
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.
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 :-
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.
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.
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
DFD Notations
CUSTOMER
Customer
Details
SS_PURCHASE
SS_SALES
Purhase
Details
Updated purchase
Details
Sales Details
for
Bill Generation
Stock Details
SS_STOCK
CUSTOMER
RELIANCE Stock Details
FRESH
BILL
Generating Bill
Customer Details
Updating Spare
Details
Customer Details
Item Details
SS_ITEM
SS_CUSTOMER
STRUCTURE TABLE
RELIANCE FRESH
DESIGN
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
ENTITY
W WEAK ENTITY
RELATIONSHIP
IDENTIFYING
RELATIONSHIP
ATTRIBUTE
KEY ATTRIBUTE
MULTIVALUED
COMPOSITE
ATTRIBUTE
DATA FLOW
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.
RELIANCE FRESH
Ha id
Name
s
id
Phone
Name Phone
Address By Has
Item Sales
Name
Discount
id Bill No
Price Date
Bill Amount
id Stock Customer Id
Select
Qoh
CODING
Private Sub cmdadd_Click()
Text1.Enabled = True
Text2.Enabled = True
Text3.Enabled = True
Text4.Enabled = True
Command1.Enabled = True
smddelete.Enabled = True
Cmdrefresh.Enabled = True
cmdedit.Enabled = True
Adodc1.Recordset.AddNew
End Sub
Mainform.Show
CUSTOMERINFORMATION.Hide
Text1.Enabled = False
Text2.Enabled = False
Text3.Enabled = False
Text4.Enabled = False
cmdadd.Enabled = True
Command1.Enabled = True
smddelete.Enabled = True
Cmdrefresh.Enabled = True
cmdedit.Enabled = True
End Sub
If UPDATERECORD = 1 Then
Text1.Enabled = True
Text2.Enabled = True
Text3.Enabled = True
Text4.Enabled = True
cmdedit.Enabled = False
smddelete.Enabled = False
cmdadd.Enabled = False
Cmdrefresh.Enabled = False
Command1.Enabled = True
End If
End If
End Sub
instatus = 0
Exit For
End If
End If
Next
If instatus = 1 Then
Adodc1.Recordset.Update
MsgBox "Record Save In The Database", vbOKOnly + vbInformation, "Dear User"
cmdedit.Enabled = True
Command1.Enabled = False
smddelete.Enabled = True
cmdadd.Enabled = True
Cmdrefresh.Enabled = True
End If
Adodc1.Recordset.MoveFirst
End Sub
End If
Adodc1.Recordset.MoveFirst
End Sub
Private Sub cmdadd_Click()
txtitemcode.Enabled = True
txtitemname.Enabled = True
Command1.Enabled = True
Adodc1.Recordset.AddNew
End Sub
End Sub
If UPDATERECORD = 1 Then
txtitemcode.Enabled = True
txtitemname.Enabled = True
cmdedit.Enabled = False
Command1.Enabled = False
smddelete.Enabled = False
cmdadd.Enabled = False
Cmdrefresh(0).Enabled = True
End If
End If
End Sub
instatus = 0
Exit For
End If
End If
Next
If instatus = 1 Then
Adodc1.Recordset.Update
MsgBox "Record Save In The Database", vbOKOnly + vbInformation, "Dear User"
cmdedit.Enabled = True
Command1.Enabled = True
smddelete.Enabled = True
cmdadd.Enabled = True
Cmdrefresh(0).Enabled = False
End If
Adodc1.Recordset.MoveFirst
End Sub
End If
End If
Next
If instatus = 1 Then
Adodc1.Recordset.Delete
MsgBox "Record Deleted In Database", vbOKOnly + vbInformation, "Dear User"
End If
Adodc1.Recordset.MoveFirst
End Sub
Private Sub CMDOK_Click()
If (txtusername.Text = Adodc1.Recordset.Fields(0)) And (txtpassword.Text =
Adodc1.Recordset.Fields(1)) Then
MDIForm1.Show
Else
nm = MsgBox("WRONG USER NAME OR PASSWORD", vbCritical, "DEAR
CUSTOMER")
End If
End Sub
End
End Sub
Private Sub clickAdministration_Click()
ADMINISTRATION.Show
End Sub
End Sub
Adodc1.Recordset.MoveFirst
End If
End Sub
Mainform.Show
PURCHASEINFORMATION.Hide
End Sub
c=c+1
Else
End If
Next
Text8.Text = total
End Sub
End Sub
INTRODUCTION:-
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.
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.
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
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:
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
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.
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.
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.
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.
CONCLUSION
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.
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.
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
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 user’s 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
BIBLIOGRAPHY