0% found this document useful (0 votes)
24 views7 pages

Stock Maintenance: 1 Problem Statement

software engineering lab manual

Uploaded by

vaddijeevankanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views7 pages

Stock Maintenance: 1 Problem Statement

software engineering lab manual

Uploaded by

vaddijeevankanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

WEEK:4

STOCK MAINTENANCE
1 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.

2. SRS Document

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
If the entire process of 'Issue of Hall ticket' is done in a manual manner then it would takes several days for
the hall ticket to reach the student. Considering the fact that the number of students for hall ticket is increasing every
year, an Automated System becomes essential to meet the demand. So this system uses several programming and
database techniques to elucidate the work involved in this process. As this is a matter of National Security, the system
has been carefully verified and validated in order to satisfy it.

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.

1.5 TECHNOLOGIES TO BE USED


• Visual Studio
• VB Script

1.6 TOOLS TO BE USED


• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool/ STAR UML(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 custome.
• Schedule the customer an appointment for manual delivery of the product.

2.3 USER CHARACTERISTICS


Customer: The person who orders for the item.
Validate customer: The items ordered by the customer are validated.
Sales Detail: Maintains the stock details after delivering the items to the customer.

2.4 CONSTRAINTS
• The customer should wait until the trade contractor and other to analyze the product.
• After the distribution of the news about the product. The customer can take order andrequest of sales
person to fill it.
• Finally the sales person delivers the order.

3. Data Flow Diagrams


4. CLASS DIAGRAM

5. COMPONENT AND DEPLOYMENT DIAGRAM

Component Diagram

Deployment Diagram
6. USE CASE DIAGRAM

7. SEQUENCE DIAGRAM
8. COLLABORATION DIAGRAM

9. ACTIVITY DIAGRAM
10. STATE CHART DIAGRAM

You might also like