0% found this document useful (0 votes)
100 views9 pages

Invotery Mangement

The document provides requirements for a stock maintenance system for a bookstore. It outlines objectives to define system requirements and replace an existing inefficient system. It describes functional requirements including allowing employees to enter book information, generate sales reports, and view stock. Non-functional requirements around reliability, usability, and performance are also specified. Use cases, actors, and design documentation with flows are defined for key functions like login, maintaining books, purchase orders, viewing stock, and reports.

Uploaded by

Seshu naidu
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)
100 views9 pages

Invotery Mangement

The document provides requirements for a stock maintenance system for a bookstore. It outlines objectives to define system requirements and replace an existing inefficient system. It describes functional requirements including allowing employees to enter book information, generate sales reports, and view stock. Non-functional requirements around reliability, usability, and performance are also specified. Use cases, actors, and design documentation with flows are defined for key functions like login, maintaining books, purchase orders, viewing stock, and reports.

Uploaded by

Seshu naidu
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/ 9

STOCK MAINTENANCE SYSTEM

Aim:To do requirement analysis and prepare SRS for stock maintenance system and also to
draw ER diagrams ,DFD,CFD and structured charts for stock maintenance system.

Software Requirements Specification(SRS) for stock maitanance system:


1. Problem analysis and project planning
1.1 Introduction
The stock maintenance system is basically for the customers who access the information
about the stock (here it is books in the book store) and retrieves the information .
1.2 Objectives
The purpose of the document is to define the requirements of the stock maintenance
system. This supplementary specification lists the requirements that are not readily
captured in the use cases of the use case model. The supplementary specification & the
use case model together capture a complete set of requirement on the system.
1.3 Scope
This supplementary specification applies to the stock maintenance system. This
specification defines the non-functional requirements of the system, such as reliability,
usability, performance and supportability as well as functional requirements that are
common across a number of use cases.
1.4 Problem Statement
A new stock maintenance system for a book store is to replace the existing maintenance
system which is in efficient. The new stock maintenance system will allow the employee
to record information of the nooks available in the book store and generate report
based on the total amount of sales.

The new system will has a windows based desktop interface to allow employee to enter
the information of sale, purchase orders, change employee preferences and create
reports. Employee can only access the information and purchase orders for security
purpose. The system retains information on all the books in the shop.

The system retains the records of the cost, edition, author, publication of the books. The
employee maintains the information of the sale of books. He can add the books at right
time and update the database.

The customer can view the availability of the required books and the price of the books.
The customer can just view them but cannot make any changes.
2. Problem statement (Use case) analysis
2.1 Identified use cases
i Login:
It is a transaction performed by the user when he wishes to the stock maintenance
system.

ii Maintain Books:
It is a transaction performed by the employee when he wishes to add, change and/or
delete books information from the system.

iii Purchase orders:


It is a transaction performed by the manager when he wishes to create, change or
delete purchase orders.

iv View Stock:
It is a transaction performed by the manager when he wishes to view the books
available in the stock maintenance system.

v View report:
It is a transaction performed by the administrator when he wishes to view the report
generated after all the stock update.

2.2 Identified Actors


i Employee:
The employee can add, change and/or delete the information from the system.

ii Customer:
The customer can just view the books available in the system.

iii Manager:
The manager can create, change or delete purchase orders.
iv Administrator:
The administrator maintains all the database and reports. He is responsible for
changing the information of database and takes care of the payment and administrative
reports.

v Database:
The database is the collection of data where the data is stored and form where the
data can be retrieved.

3. Design of Stock Maintenance System


3.1 Design Documentation
1. Login
1.1 Brief description:
This use case describes how a user logs into the stock maintenance system.

1.2 Flow of events:


1.2.1 Basic flow:
This use case starts when the actor wishes to login to the stock maintenance
system.
1. The system requests that the actor enter the name and password.
2. The actor enters their name and password.
3. The system validates the entire name and password and logs the actor into the
system

1.2.2 Alternative flow:


1. If in the basic flow, the actor enters an invalid name and password the system
display an error message.
2. The actor can choose to either return to the beginning of the basic flow or cancel
the login at which point the use case ends.

1.3 Pre Conditions:


None
1.4 Post Conditions:
If the use case successful the actor is now logged in the system, if not the system
state is unchanged.

2. Maintain Books
2.1 Brief description:
The use case describes how employees maintains book in the system.

2.2 Flow of events:


2.2.1 Basic flow:
1. The system requests that the employee specify the function he/she would like
to perform (add, update or delete). Once the employee provides requested information,
one of the sub-flow is executed.
2. If the employee selected ‘add book’ then add book sub-flow is executed.
3. If the employee selected ‘update book’ then update book subflow is executed.
4. If the employee selected ‘delete book’ then delete book subflow is executed.
2.2.1.1 Add Books
1. The system requests the employee to enter the books information. This include
its edition, author name, publication.
2. Once the information is provided the system generates and assigns a unique
book-id number.

2.2.1.2 Update Books


1. The system requires entering id.
2. The employee enters the id, the system retrieves and displays book information.
3. The employee makes desired changes to the book information.
4. Once the employee updates information the system updates the book
information.

2.2.1.3 Delete Books


1. The system specifies to enter id of the book.
2. The employee enters the id, the system retrieves and displays book information.
3. The system provides employee to confirm deletion of the books.

4. The employee verifies deletion.


5. The system deletes the books specified.

2.2.2 Alternative flow:


i. Book not found:
1. If in update books or delete books sub flow the books with specified id number
does not exist, the system displays an error message.
2. The employee can then enter different id number or cancel the operation at
which point the use case ends.

ii Delete Cancelled:
If information the delete books sub-flow the employee decides not to delete the
book, the delete is cancelled and the basic flow is restarted at the beginning.

2.3 Pre Condition:


The employee logs in to the system.

2.4 Post Condition:


If the use case is successful, the employee maintains books successfully else the system is
unchanged.

3. Purchase Orders
3.1 Brief description:
This use case describes how the manager provides orders for new stock in the stock in the
stock maintenance system.

3.2 Flow of events:


3.2.1 Basic flow:
This use case starts when the manager wishes to record and maintain purchase orders. This
includes adding, changing, and deleting purchase orders.
1. The system requests that the manager specify the function he/she would like to
perform (add, change or delete).
2. Once the manager provides the required information; one of the sub flow is
executed.
3. If the manager selected creates purchase order, it is executed.
4. If the manager selected change purchase order, the sub flow is executed.
5. If the manager selected delete purchase order then that sub flow is executed.
3.2.1.1 Create Purchase Orders
1. The system requests the manager to enter the purchase order information; this includes
the name of the book, quantity, and edition.
2. Once the information is provided, the system generates and assigns an order number.

3.2.1.2 Change Purchase Orders


1. The system requests to enter the order number.
2. The manager enters the id number; the system retrieves and displays the information.
3. The manager makes the desired changes to the orders.

4. The system updates the information.

3.2.1.3 Delete Purchase Orders


1. The system requests the manager to enter the id number.
2. The manager enters the number; the system retrieves and displays information.
3. The system provides manager to confirm deletion of orders.
4. The manager verifies deletion.
5. The system deletes the orders specified.

3.2.2 Alternative flow:


i. Purchase Order not found:
If in the change order or delete purchase order sub-flows, the purchase order with specified
id number does not exist, the system displays an error message the manager can then enter
a different number or cancel the operation at which point the use case ends.

ii. Cancel Deleted: If in the delete purchase order sub-flow the manager decides not to
delete the purchase order, the delete is cancelled and basic flow is started at the beginning.

3.3 Pre Condition:


The manager logs on the system.

3.4 Post Condition:


If the use case is successful the manager makes the purchase orders else the system is
unchanged.
4. View stock
4.1 Brief description:
This use case describes how the customer views the stock maintenance system.

4.2 Flow of events:


4.2.1 Basic flow:
This use case starts when the customer wishes to view the books available in the system.
1. The system requests to customer to enter the details (author, name, publication, and
edition) of the book required.
2. Once the information is provided the system displays the book information.

4.2.2 Alternative flow:


1. If in the basic flow the book specified is not found the system displays an error message.
2. The customer can enter the different book detail or cancel the operation at which point
the use case ends.

4.3 Pre Condition:


None

4.4 Post Condition:


If the use case was successful the customer is provided with the information if not the
system state is unchanged.

5. View Report
5.1 Brief description:
This use case describes how the administrator views the reports in the stock maintenance
system.

5.2 Flow of events:


5.2.1 Basic flow:
This use case starts when the administrator wishes to view the report generated after tall
the stock update.
1. The system specifies the administrator to enter his id.

2. Once the administrator is provided, the system retrieves and displays the report.
3. The administrator is provided; the system retrieves and displays the report.

5.2.2 Alternative flow:


1. If the id is incorrect the system displays an error message.
2. The administrator can either re-enter the correct id or else he can cancel the operation at
which point the use case ends.

5.3 Pre condition:


The administrator logs on the system.

5.4 Post condition:


If the use case is successful, the administrator views the report, if not, the system report is
unchanged.

Data Flow Diagram(DFD):


Use Case Diagram:

ER Diagram:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy