EX.

NO:1 STOCK MAINTENANCE SYSTEM

PROBLEM DOMAIN:
Inventory system is a real time application used in the merchant’s day to day system. This is a

database to store the transaction that takes places between the Manufacturer, Dealer and the
Shop
Keeper that includes stock inward and stock outward with reference to the dealer.
Here we assume our self as the Dealer and proceed with the transaction as follows:
1. The Manufacturer is the producer of the items and it contains the necessary information of

the item such as price per item, Date of manufacture, best before use, Number of Item
available and their Company Address.

2. The Dealer is the secondary source of an Item and he purchases Item from the manufacturer

by requesting the required Item with its corresponding Company Name and the Number of
Items required. The Dealer is only responsible for distribution of the Item to the Retailers in
the Town
or City.
3. The Shop Keeper or Retailer is the one who is prime source for selling items in the market.
The
customers get Item from the Shop Keeper and not directly from the Manufacturer or the
Dealer.
4. The Stock is the database used in our System which records all transactions that takes place

between the Manufacturer and the Dealer and the Dealer and the Retailer.

1. INTRODUCTION:

1.1 Purpose :
This project is about developing a stock maintenance system within budget and should be
delivered on time. The system should be able to provide the customers to search the required
items

and receive the bill upon buying the item. The administrator should update the item details,
add or delete the required items. All the customer and administrator performed activities
should be updated in the database.
1.2 Document Conventions:

The headings have been written using “normal” style with “Times New Roman” font and font size
of “12”. with bold type. The contents under each heading uses “normal” style with “times” font
and font size of “12”. The subheadings under each headings also use “normal” style with
“times” font and size “12”. Every requirement statement has its own priority and each
requirement
is to be had a detailed study.
1.3 Intended Audience and Reading Suggestions:
The different types of reader that the document is intended for are developers, project
managers,

users, testers, and documentation writers. This SRS contains keenly analyzed and well
organized requirements specification which the system is supposed to contain when being
delivered to its customer.
1.4 Project Scope:
An online course reservation system is a software that allows the students to view the list of
courses available and make reservations. The system allows the students to enter their
personal details
needed for applying to a course. The administrator verifies the details and maintains course
details as well as the student information.

2. OVERALL DESCRIPTION:
2.1 Product Perspective:
The system is a new, self-contained product with its own requirements and functionalities

2.2 Product Features:

The significant functions that this product performs as well as lets the user to perform are as
follows:
1. Entering details of new items added to stock.
2. Deleting the items which are not in stock.
3. Update the item details.

4. Database updates all the details.

5. Search the items by customer.
6. Confirmation of purchase.

7. Bill receipt generation.

8. Purchase details to be stored in database.
2.3 User Classes and Characteristics:
The various user classes that are being anticipated will this product is administrator and
students.
ADMINISTRATOR:The administrator has the privilege to maintain the stock details, entering the
available item details, deleting records of unavailable items, updating any purchase.
CUSTOMERS:
The customer can browse through the available items in stock and make purchases. The
customer
receives a bill receipt after the purchase details are updated in database.

2.4 Operating Environment:

Hardware: 64 MB RAM, DB Server 128 MB RAM

Operating system: windows 98 and upwards
2.5 Design and Implementation Constraints:
A server with high end processor is required. The website must be registered in a domain to
post to on the internet. Time and funding are the major constraints. Delivering on time with
all the specification implied to the software is a major factor. To use and apply new
technology to the software in order to cope with time, funds play a vital role.

3. SYSTEM FEATURES:
LOGIN:
3.1. Description and Priority:
This use case allows the administrator and customer to access the website and perform
required
activities.

3.2. Stimulus/Response Sequences:

BASIC FLOW:

1. The customer can view the item list and details.

2. The customer can make purchases and get a payment receipt.
3. The administrator can make updating, addition and deletion of stock records from the
database.
4. The administrator has the access to the database to check for the purchase detail

3.3 Functional Requirements:

ALTERNATIVE FLOW:
If any of the database transactions; updating, deletion or addition fails it should not affect the
already existing record.
SPECIAL REQUIREMENTS: None.
PRE-CONDITIONS :
The administrator only has privilege to maintain record of all items in a stock .
POST-CONDITIONS:
Payment transaction should be updated

4. EXTERNAL INTERFACE REQUIREMENTS:

4.1 User Interfaces
:The interface allows the customer to browse the available item details and make payment
online. The administrator interface allows entering the item code, name and maintaining
the transaction ids.
4.2 Hardware Interfaces:
Disk is used for data storage. Keyboard is used for getting the input details and the monitor
displays the output generated for the given input. Printer is used for printing the generated
reports if necessary.
4.3 Software Interfaces:
Software: Java and Oracle10g
Windows XP,7

Tools: Eclipse IDE, Rational Rose-2 /Agro UML

5. OTHER NONFUNCTIONAL REQUIREMENTS:

5.1 Performance Requirements:
The updations in database should be persistent.
5.2 Security Requirements
The database access privilege is only provided to the authorized administrator. Purchase
transactions and all item details to be updated without error.
5.3 Software Quality Attributes

The expected key attributes out of this product are adaptability, availability, correctness,
flexibility,

interoperability, maintainability, portability, reliability, reusability, robustness, testability, and

usability.

PROBLEM ANALYSIS AND PROJECT PLANNING

The Stock Maintenance System, initial requirement to develop the project about the
mechanism of the Stock Maintenance System is caught from the customer. The requirement
are analyzed and refined which enables the end users to efficiently use Stock Maintenance
System. The complete project is developed after the whole project analysis explaining about the
scope and the project statement is prepared.

PROBLEM STATEMENT

The process of stock maintenance system is that the customer login to the particular site to
place the order for the customer product. The stock maintenance system are described
sequentially through steps:

• The customer login to the particular site.

• They fill the customer details.

 • They place the orders for their product.

• The vendor login and views the customer details and orders.

SOFTWARE REQUIREMENT SPECIFICATION

S.NO CONTENT

1 INTRODUCTION

2 OBJECTIVE

3 OVERVIEW

4 GLOSSARY

5 PURPOSE

6 SCOPE

7 FUNCTIONALITY

8 USABILITY

9 PERFORMANCE

10 RELIABILITY

11 FUNCTIONAL REQUIRMENTS

1. INTRODUCTION

This software specification documents full set of features and function for online stock
maintenance system that is performed in company website. In this we give specification about
the customer orders. It tells the usability, reliability defined in use case specification.

2. OBJECTIVE

The main objective of the stock maintenance system is to maintain the stock. It provides the
vendor to maintain the stock in an precise manner.

3. OVERVIEW

The overview of the project is to design an online tool for the recruitment process which eases
the work for the customer as well as the companies. Companies can create theircompany forms
according to their wish in which the applicant can register.
4. GLOSSARY
TERMS DESCRIPTION

CUSTOMER The customer can have the username and

password after login to the system. After
login they directed to fill the customer
details. And the customer places their
order. After placing orders they lead to
verify all the details in a single form. Then
they places the order successfully.

VENDOR Vendor has the login id. After login vendor

verify the customer details and orders. And
maintain the stocks.

DATABASE Database is used to verify the customer

details and orders.

SOFTWARE REQUIREMENT This software specification documents full

set of features and function for stock
SPECIFICATION
maintenance system that is performed in
company website.

5. PURPOSE

The purpose of stock maintenance system is to maintain the stock in an precise manner.

6. SCOPE

The scope of this stock maintenance system is to maintain the stock.

7. FUNCTIONALITY

The main functionality of the stock maintenance system is to maintain the stock.

8. USABILITY

User interface makes the stock maintenance system to be efficient. That is the system will help
the customer to place the details and orders easily and helps the vendor to maintain the stock
accurate. The system should be user friendly.
9. PERFORMANCE

It describes the capability of the system to maintain the stock without any loss of stock

and performing it efficiently.

10. RELIABILITY

The stock maintenance system should be able to maintain the stock with correct updates from
day to day placement of new orders from customer.

11. FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system. That is the services
that are provided to the customer who places the orders.

UML DIAGRAMS

The following UML diagrams describe the process involved in the online recruitmentsystem

• Use case diagram

• Class diagram

• Sequence diagram

• Collaboration diagram

• State chart diagram

• Activity diagram

• Component diagram

• Deployment diagram

• Package diagram

USE CASE DIAGRAM

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. It is represented
using ellipse. Actor is any external entity thatmakes use of the system being modeled. It is
represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are customer, vendor and database. The use cases are the
activities performed by actors.

CUSTOMER:

• Customer logins to the particular system and fills the customer details and places the orders.

DATABASE:

• All the details and orders given by customer are updated in the database.

VENDOR:

• Vendor logins and verify the customer orders and the stock details.

CLASS DIAGRAM

A class diagram in the unified modeling language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is represented using a rectangle with three compartments.
Top compartment have the class name, middle compartment the attributes and the bottom
compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM

This class diagram has three classes’ customer, vendor and database.

• Customer – is the class name. Its attributes are username, password,name, phone no and
address. The operations performed in the customer class are login and places the orders.

• Vendor – is the class name. Its attributes are views the database.

• Database – is the class name. The operations performed are storing customer details, and
their orders.

SEQUENCE DIAGRAM

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that
shows how processes operate with one another and in what order. It is aconstruct of a Message
Sequence Chart. There are two dimensions.

1. Veritcal dimension-represent time.

2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show •

The customer login in to the system and fills the customer details.

• Then the customer places the order. It updated to the database.

• The vendor login to the system and views the customer orders and the stockdetails.

COLLABRATION DIAGRAM :

A collaboration diagram, also called a communication diagram interactiondiagram,. A

sophisticated modeling tool can easily convert acollaboration diagram into sequence
diagram and the vice versa.
DOCUMENTATION OF COLLABRATION DIAGRAM

The collaboration diagram is to show how the customer login and places the orders in the

system. Here the sequence is numbered according to the flow of execution.

STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in performing a

method. It is also called as state diagram. A state is represented as a round box, which may

contain one or more compartments. An initial state is represented as small dot. An

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.

• First state is login where the customer login to the system.

• The next state is to fill the customer details.

• And the next state is to place the orders.

Update database with the orders and details of customer

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and actions

with support for choice, iteration and concurrency. In the Unified Modeling Language, activity

diagrams can be used to describe the business and operational step-by-step workflows of

components in a system. An activity diagram shows the overall flow of control.

An activity is shown as an rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in stock maintenance system.

First the customer login then fills the details.

• The customer places the order according to their needs.

• After placing the order the database is updated.

• Vendor login to the system and verifies the customer orders and stock details.

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the

components of a systems. It is represented by boxed figure. Dependencies arerepresented by

communication assosiation.
DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is stock maintenance systems. And customer

database details and update database then vendor views the database are the components

comes under the main component.

DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation
ofartifacts to nodes according to the Deployments defined between them. It is represented by
3dimentional box. Dependencies are represented by communication assosiation.
DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the stock maintenance system which is the

main part and the devices are the filling customer details and placing orders then vendor

views which are the some of the main activities performed in the system.

PACKAGE DIAGRAM

A package diagram in unified modeling language that depicts the dependencies between the

packages that make up a model. A Package Diagram (PD) shows a grouping ofelements in the

OO model, and is a Cradle extension to UML. PDs can be used to show groups of classes in Class

Diagrams (CDs), groups of components or processes in ComponentDiagrams (CPDs), or groups

of processors in Deployment Diagrams (DPDs).

There are three types of layer. They areUser interface layer

Software objects representing domain concepts that fulfill application reqirements, such as

calculation of a sale total.Domain layerLayer that contains domain objects to handle application

logic workTechnical services layer

General purpose object and sub system that provide supporting technical services,such as
interfacing with a database logging
DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are

• The User interface layer - consists of the web and login. This layer decribes

how the applicant logins to the website and places the order.

• The Domain layer – shows the activities that are performed by the customer

to place the orders.

• The Technical service layer - the vendor logins and verifies the customer

orders and stock details

CODING
import java.util.HashMap;
import java.util.Map;
import java.util.Scanner;

class Stock {
private String name;
private int quantity;
private double price;

public Stock(String name, int quantity, double price)

{ this.name = name;
this.quantity = quantity;
this.price = price;
}

// Getters and setters

public String getName() {
return name;
}

public void setName(String name)

{ this.name = name;
}

public int getQuantity()

{ return quantity;
}

public void setQuantity(int quantity)

{ this.quantity = quantity;
}

public double getPrice()

{ return price;
}

public void setPrice(double price)

{ this.price = price;
}

@Override
public String toString()
{ return "Stock{" +
"name='" + name + '\'' +
", quantity=" + quantity +
", price=" + price +
'}';
}
}

public class StockMaintenanceSystem

{ private Map<String, Stock> stocks;
public StockMaintenanceSystem()
{ this.stocks = new HashMap<>();
}

// Method to add new stock

public void addStock(String name, int quantity, double price) {
Stock stock = new Stock(name, quantity, price);
stocks.put(name, stock);
}

// Method to update stock quantity

public void updateStock(String name, int newQuantity)
{ if (stocks.containsKey(name)) {
Stock stock = stocks.get(name);
stock.setQuantity(newQuantity);
} else {
System.out.println("Stock not found.");
}
}

// Method to update stock price

public void updateStockPrice(String name, double newPrice)
{ if (stocks.containsKey(name)) {
Stock stock = stocks.get(name);
stock.setPrice(newPrice);
} else {
System.out.println("Stock not found.");
}
}

// Method to display all stocks

public void displayAllStocks() {
for (Stock stock : stocks.values()) {
System.out.println(stock);
}
}

public static void main(String[] args) {

Scanner scanner = new Scanner(System.in);
StockMaintenanceSystem system = new StockMaintenanceSystem();

// Example usage
system.addStock("Apple", 100, 150.0);
system.addStock("Banana", 200, 100.0);

// Display all stocks

system.displayAllStocks();

// Update stock quantity

System.out.print("Enter the name of the stock to update quantity: ");
String stockName = scanner.nextLine();
System.out.print("Enter the new quantity: ");
int newQuantity = scanner.nextInt();
scanner.nextLine(); // Consume newline character
 system.updateStock(stockName, newQuantity);

// Display all stocks after update

system.displayAllStocks();
}
}FORMS:

FORM 1

FORM 2
FORM 3

FORM 4
FORM5

FORM 6
FORM 7

FORM 8