WWW.VIDYARTHIPLUS.

COM

Ex no:
STOCK MAINTENANCE
Date:

AIM:

To create a system to perform the Stock maintenance

(I) PROBLEM STATEMENT
The stock maintenance system must take care of sales information of the company and
must analyze the potential of the trade. It maintains the number of items that are added or
removed. The sales person initiates this Use case. The sales person is allowed to update
information and view the database.
(II) SOFTWARE REQUIREMENT SPECIFICATION
1.0 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 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
 Market Data provider: One who analyze the product and distribute the news.
 Customer: One who takes order of product
 Sales person: One who maintains the stock details
1.4 REFERENCES
IEEE Software Requirement Specification format

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

1.5 TECHNOLOGIES TO BE USED

 Visual Studio
 VB Script

1.6 TOOLS TO BE USED

• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

1.7 OVERVIEW
SRS includes two sections overall description and specific requirements
Overall Description will describe major role of the system components and inter-
Connections
Specific Requirements will describe roles & functions of the actors.
2.0 OVERALL DESCRIPTION
2.1 PRODUCT 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 FUNCTIONS

• Secure order of information by the customer
• Schedule the customer an appointment for manual delivery of the product.

2.3 USER CHARACTERISTICS

1. Customer: The person who orders for the item.
2. Validate customer: The items ordered by the customer are validated.
3. Sales Detail: Maintains the stock details after delivering the items to the customer.
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.

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

(III) USE CASE DIAGRAM

The functionality of a system can be described in a number of different use-cases, each of
which represents a specific flow of events in a system. It is a graph of actors, a set of use-cases
enclosed in a boundary, communication, associations between the actors and the use-cases, and
generalization among the use-cases.
The use cases used in this system are
1. Product details: Used for placing an order.
2. Purchase details: Used for tracking items that have been ordered.
3. sales details: Used for give the sales particulars about a item.
4. stock details: Used for give the stock detail in a shop.
5. Purchase the product: Used to provide bills for the customer.
6. supply the product: Used to give the order product to customer.
ACTORS
The actors used in this system are
1. Customer: The person who orders for the item.
2. Shopkeeper: The items ordered by the customer are validated.
3. Company: Maintains the stock details after delivering the items to the customer.

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

product details

purchase details

shopkeeper customer
sales details

stock details

purchase the product

company

supply the product

Fig.3. USE CASE DIAGRAM

(IV) ACTIVITY DIAGRAM

It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior that has
a lot of parallel processing. An activity is a state of doing something: either a real-world process,
or the execution of a software routine.

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

login

order product check availability

product stock details

if availableif not available

do payment

cancle order

get payment

recive the stock

logout

Fig.4. ACTIVITY DIAGRAM

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

(V) CLASS DIAGRAM

Description:
 A class diagram describes the type of objects in system and various kinds of
relationships that exists among them.
 Class diagrams and collaboration diagrams are alternate representations of object
models.
The Stock maintenance system class diagram consists of seven classes:
1. PurchaseDetails: One who takes orders for the product?
2. SalesDetails: The customer make an order for the required products.
3. Product Details: The items that are stored as stock.

Fig.5. CLASS DIAGRAM

(VI) UML INTERACTION DIAGRAMS

It is the combination of sequence and collaboration diagram. It is used to depict the flow
of events in the system over a timeline. The interaction diagram is a dynamic model which
shows how the system behaves during dynamic execution.
1. SEQUENCE DIAGRAM
 A sequence diagram represents the sequence and interactions of a given USE-
CASE or scenario. Sequence diagrams can capture most of the information
about the system. Most object to object interactions and operations are

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

considered events and events include signals, inputs, decisions,

interrupts, transitions and actions to or from users or external devices.
o An event also is considered to be any action by an object that sends information.
The event line represents a message from one object to another, in which the
“from” object is requesting an operation be performed by the “to” object. The “to”
object performs the operation using a method that the class contains.
o It is also represented by the order in which things occur and how the objects in the
system send message to one another.
custom shopekeep dea databa

customer
1. request for item shopekeeper dealer database

2. enter the details

3.send for item

4.check for product availability

5.update product details

. 6. product available

7. send for quation

8.request for delivery

9.order item

10. update delivery details

11.product delivery

Fig.6.1 SEQUENCE DIAGRAM

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

2. COLLABORATION DIAGRAM
Collaboration diagram and sequence diagrams are alternate representations of an
interaction. A collaboration diagram is an interaction diagram that shows the order of messages
that implement an operation or a transaction. Collaboration diagram is an interaction diagram
that shows the order of messages that implement an operation or a transaction. Collaboration
diagram shows object s, their links and their messages. They can also contain simple class
instances and class utility instances.
During, analysis indicates the semantics of the primary and secondary interactions.
Design, shows the semantics of mechanisms in the logical design of system.

1: request for item

8: request for delivery
shopeke
custome eper
r
enter the details
11: product delivery
2:

7: send for quation update delivery details

9:
10: recording sales

send for item

order item
3:
5: update product details

4: check for availability

dealer databas
e
6: product available

Fig.6.2 COLLABORATION DIAGRAM

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

(VII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Fig.7.1.DEPLOYMENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

(VIII) IMPLEMENTATION OF DOMAIN OBJECTS LAYER AND TECHNICAL

SERVICE LAYER

//Source file: E:\\10764\\productDetails.java

public class productDetails

{
private integer prodCode;
private string prodName;
private integer prodQty;
private float prodPrice;

/**
@roseuid 5167CD420232
*/
public productDetails()
{

/**
@roseuid 512702DE0128

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

*/
public void prodAdd()
{

/**
@roseuid 512702E4003E
*/
public void prodDelete()
{

/**
@roseuid 512702EF003E
*/
public void prodUpdate()
{

}
/**
@roseuid 512B3FAC007F
*/
public void prodDetails()
{

}
}//Source file: E:\\10764\\purchaseDetails.java

public class purchaseDetails

{
private integer purcCode;
private date purcDate;
private integer subid;
private string subname;
private integer purcQty;
private float purcPrice;

/**
@roseuid 5167CD4201D4
*/
public purchaseDetails()
{

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

/**
@roseuid 5127049302DE
*/
public void save()
{

/**
@roseuid 512704970232
*/
public void delete()
{

/**
@roseuid 5127049F00FA
*/
public void purchasedit()
{

/**
@roseuid 512B3FC102C1
*/
public void purchaseDetials()
{

}
}
//Source file: E:\\10764\\salesDetails.java

public class salesDetails

{
private integer salId;
private date salDate;
private integer custCode;
private string custName;
private integer prodCode;
private integer price;
private integer qty;

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

/**
@roseuid 512840E5009C
*/
public salesDetails()
{

/**
@roseuid 512705AD030D
*/
public void sale()
{

}
}

(IX) IMPLEMENTATION OF USER INTERFACE LAYER

WWW.VIDYARTHIPLUS.CO V+TEA
 WWW.VIDYARTHIPLUS.COM

RESULT:
Thus the mini project for stock maintenance system has been successfully executed and
codes are generated.

WWW.VIDYARTHIPLUS.CO V+TEA