Ex No: 2

STOCK MAINTENANCE SYSTEM

Date:

Aim:
To identify the problem statement, formulate the SRS document and to develop design
solutions for the application “STOCK MAINTENANCE SYSTEM”.

Problem Statement:
A problem statement is a concise description of the issues that need to be addressed by a
problem solving team and should be presented to them (or created by them) before they try to
solve the problem. When bringing together a team to achieve a particular purpose provide them
with a problem statement. The main purpose of the stock maintenance system is to manage the
entire details of the stock system in an automated way. The stocks which are purchased from
the various dealers and suppliers are stored in the store keeper and their entries are recorded
into the database. The software system provides facilities for adding new item, removing an
item, updating the stock, calculating the turn over, sales amount, total number of stocks. It also
involves purchasing of stocks by the customers.

SRS Document:

1. Introduction:

Stock maintenance is an interface between the customer and the sales person. It aims at
improving the efficiency in maintaining the stocks.

1.1 Purpose :

The entire process of Stock maintenance is done in a manual manner Considering the fact that
the number of customers for purchase is increasing every year, a maintenance system is
essential to meet the demand. So this system uses several programming and database
techniques to elucidate the work involved in this process.

1.2 Scope :

• The System provides an interface to the customer where they can fill in orders for the item
needed.

• The sales person is concerned with the issue of items and can use this system.

• Provide a communication platform between the customer and the sales person.
1.3. Overview :

SRS includes two sections overall description and specific requirements Overall Description
will describe major role of the system components and interConnections Specific
Requirements will describe roles & functions of the actor.

1.4. References :

IEEE Software Requirement Specification format

Pressman, Roger S. Software Engineering: A Practitioner’s Approach. New York, NY:

McGraw-Hill, 2005.

2. Overall description

2.1 Project Perspective :

The Stock maintenance acts as an interface between the 'customer' and the 'sales person'. This
system tries to make the interface as simple as possible and at the same time not risking the
work of data stored in

2.2 System function :

• Automatic customer registrations

• Obtain the current stock rates and log the required information

• Provides friendly relationship with shopkeeper and customers

• Gives complete statistical data on particular stock

• Updates the stock values periodically and automatically

2.3 User Characteristics :

** Naive Users: Customers who require product for daily use, Such as common people, office
goers etc…

** Warehouse Manager: Manages items in the warehouse does packaging & delivery.

** Inventory Management: Re-ordering and ordering based on arrival of stocks.

** Shipping Vendor: Picks up the packages from the warehouses and delivers to the users,
gives facility for order tracking.

** Managing Administrator: Manages the whole process in a shop involving bill calculation,
resolves financial problems, approve refunding and order acceptance and cancellation.
2.4 Constraints :

1. The customer should wait until the trade contractor and other to analyze the product.

2. After the distribution of the news about the product. The customer can take order and request
of sales person to fill it.

3. Finally the sales person delivers the order.

2.5 User Documentation :

This product will include user manual. This will include product overview, complete
configuration of the software’s to be used and hence the description of the overall product<list
the user’s documentation components(such as user manuals,on -line help and tutorial)that will
be delivered along the software.identify any known user documentation delivery formats or
standards>

2.6 Assumptions and Dependencies :

Each user must be provided with id and password on his/her first appearance. Administrator is
responsible for all activities happening. He should hold the authority of permitting any
activities regarding stocks. Database system must be connected across the network for any time
and any where access. Customers alone are responsible for the safety of their products.

3. FUNCTIONAL REQUIREMENTS

3.1 External Interface Requirements:

The system uses the GUI – Graphical User Interface for easy interaction with the customer.
The system maintains a relationship with the Rational Rose Tool. According to the code
generated by the Rose tool, the system is developed. This gives more sequential access for the
functions and the functions can be coded easily.

3.2 User Interfaces:

The User Interface should be very attractive featuring importance of our system. The
introductory screen consists of a Welcome note and product advertisement. The next screen is
the user login screen. The next interface displays the product details under different categories
and the subsequent screens contain the details of each and every product and finally provided
with provision for getting card number for settling the cash by the customers. The final screen
displays salutations to the customer by displaying Thank You. At the same time the stock
details are updated.

3.3 Hardware Interfaces:

• Needed: Computers
• Hard Disk: 100-150 GB

• RAM: 512-1 GB required

• Internet Connection required.

• Cables, wires, Network adapters are required

3.4 Software Interfaces:

SYSTEM SOFTWARE REQUIRED: Windows XP or Windows 7 with 32 bit (recommended).

APPLICATION SOFTWARE REQUIRED: Stock Master v 1.0, Oracle 9i, MY SQL, Tally
5.0.

3.5 Source of input:

The input is given by the user who wishes to use the Stock Maintenance system. The user feels
it easy to give the inputs, as the system is more user-interactive. They find the option to perform
their work more easily rather than waiting for a long time to get the transactions to be completed
manually.

3.6 Destination of output:

The input given by the user is updated into the database where the account details
corresponding to the user are stored. With the help of the database the account details of the
customer can be administered and monthly statements can be generated.

3.7 Information flows:

The data given by the user flows over stage by stage and reaches the database finally for making
insertion or updating for storing the details. This can be represented by the following Data Flow
Diagrams.

3.8 Communication Interfaces:

The local system must be connected to the server via Internet Connection. Email and file
transfer services are provided. E-Shopping is the key concept.

4 SYSTEM FEATURES

4.1 Automated Functioning:

This system provides automated functionalities like stock updating, product listing, calculating
the total stocks available etc.. This feature is of high priority only based on this feature other
aspects are designed. No risk, high expenses are involved in implementation of this system.
Risk rate is 2 (very low).
OTHER NON-FUNCTIONAL REQUIREMENTS

4.2 Performance Requirements:

The number of users is not confined to any specific value. Any number of users can use the
system. But the only constraint is that only one user can use this system at a time. The response
time is greater for the system. It gives the output quickly so that the user will feel easy to
proceed with the next transaction. The amount of information to be handled is enormous. The
database stores a large amount of data and it also helps in quick insertion and retrieval of data
from it. So, the system furnishes all the required information at the request of the user to view
the details.

4.3 Safety Requirements:

Avoid frequent usages of flash devices such as pen drive to prevent database collapse. System
must be installed with original version of Windows OS with perfect license to avoid duplication
problems. Take regular backup of data. Store the stocks in a closed place to avoid loss of stocks
by theft, misplacement etc...

4.4 Security Requirements:

There will be proper security mainly regarding data accessibility. Security to user can be
provided by login authentication. Data stored in database should be private that is it must be
known only to administrator who is authorized using a secured id. The whole system is
prevented from unauthorized access.

System Design

UML DIAGRAMS

USE CASE DIAGRAM :

A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary,
communication associations between actors and the use cases and generalization among use
cases. Use cases are text documents, not diagrams, and use-case modeling is primarily an act
of writing text, not drawing diagrams. The credit card processing system is used by the
customers to do crediting and payback.
 << extend>>

Login invalid login

Stock management
system view << include>>

add new
<< include>>

<< include>> << extend>>

Update edit and delete purchase order
<< include> >

purchase
<< include>>

search
<< extend>> << extend>> sold out check existing shade

pay id pay name

CLASS DIAGRAM
 Stock manager: Stock manager is responsible for developing, monitoring and maintaining
the system. He updates the stock and carries out transactions based on the quantity.

 supplier: Supplier is the dealer who provides Stock

 Customer: Based on the available quantity the stock is delivered.

SEQUENCE DIAGRAM
Sequence diagrams are an easy and intuitive way of describing the behavior of the system by
viewing the interaction between the system and its environment. A sequence diagram shows
the objects participating in a time sequence. It shows the objects participating in an interaction
by their lifelines and the messages they exchange, arranged in a time sequence. We can also
use terminologies like Opt, Alt, and Loop.

COLLABORATION DIAGRAM
A collaboration diagram represents a collaboration, which is a set of objects related in a
particular context, and interaction, which is a set of objects within the collaboration, to achieve
a desired outcome.
 3: view 18: subtract with available qty
6: enter the details
8: enter the productid to be added
11: enter the reqd quantity
14: enter the productid to be sold
17: enter the required quantity
Manager System

5: display details
10: display details
16: display details

4: pass details
9: pass details 2: update
15: pass details 7: update
13: update
19: update

Database

ACTIVITY DIAGRAM
An activity diagram is a variation or special case of state machine, in which the states are
activities representing the performance of operations and transitions are triggered by the
completion of the operations. It models the entire business process.
STATE CHART DIAGRAM
A state diagram is a type of diagram used in computer science and related fields to describe
the behavior of systems. State diagrams require that the system described is composed of a
finite number of states.

PACKAGE DIAGRAM
A package is a group of modeling elements. It may contain both subordinate packages and
ordinary model elements. The entire system can be thought of as a single high-level package,
with all the uml diagrams organized within it.
COMPONENT DIAGRAM
A component diagram depicts how components are wired together to form larger components
and or software systems. They are used to illustrate the structure of arbitrarily complex systems.
Components are wired together by using an assembly connector to connect the required
interface of one component with the provided interface of another component. This illustrates
the service consumer - service provider relationship between the two components.

DEPLOYMENT DIAGRAM
A deployment diagram in the Unified Modeling Language models the physical deployment of
artifacts on nodes. The nodes appear as boxes, and the artifacts allocated to each node appear
as rectangles within the boxes. Nodes may have sub nodes, which appear as nested boxes. A
single node in a deployment diagram may conceptually represent multiple physical nodes, such
as a cluster of database servers.
Summary:
The problem statement, formulation of SRS document and design solution of the " STOCK
MAINTENANCE SYSTEM " is completed successfully.
REPORT EVALUATION:

S.NO DESCRIPTION WEIGHTAGE MARK

AWARDED
1. Problem Statement and Analysis 10
2. UML Diagrams and Design Pattern 20
with creativity
3. Experimental Results 10
4. Viva-voce 10
TOTAL 50