Professional Documents
Culture Documents
Stock Management System
Stock Management System
No:
STOCK MAINTENANCE SYSTEM
Date:
1.1 Introduction
1.2 Objectives
1.3 Scope
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
i Login:
ii Maintain Books:
iv View Stock:
v View report:
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:
iv Administrator:
v Database
The database is the collection of data where the data is stored and
form where the data can be retrieved.
2.3 Use Case Diagram:
Maintain books
Employee
Login
Manager Database
Purchase order
View report
Administrator
View stock
Customer
1. Login
1.1 Brief description:
This use case describes how a user logs into the stock maintenance
system.
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.
None
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.
ii Delete Cancelled:
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.
This use case starts when the manager wishes to record and maintain
purchase orders. This includes adding, changing, and deleting purchase
orders.
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.
This use case starts when the customer wishes to view the books
available in the system.
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.
None
If the use case was successful the customer is provided with the
information if not the system state is unchanged.
5. View Report
This use case describes how the administrator views the reports in the
stock maintenance system.
5.2 Flow of events:
This use case starts when the administrator wishes to view the report
generated after tall the stock update.
If the use case is successful, the administrator views the report, if not,
the system report is unchanged.
SEQUENCE DIAGRAM:
1.Login
Main form Login form Login Welcome Error message : Database
: Customer controller screen
login( )
Verification( )
Valid( )
Invalid( )
re-login( )
2.View Reports
main form controller error message
: Administrator : Database
request ID( )
Enter ID( )
Verification( )
Valid( )
Generate report( )
Invalid( )
re-enter ID( )
3. View Stock
Controller Error message
: Customer : Administrator : Database
Verify( )
Verified( )
Generate report( )
error message( )
4. Maintain Stock
to avail options( )
add books( )
Sequence
diagram...
update books( )
Sequence
delete books( ) diagram...
Sequence
diagram-...
4.1 Add
Selection modification Error message
: Employee : Database
form form
Request for new books( )
Verification( )
filled properly( )
Generate ID( )
Error message( )
4.2 Modify
Selecting books( )
intimate database( )
Retrieve datas( )
modify( )
Verification( )
improper modification( )
4.3 Delete
Selection Deletion form
: Manager : Database
form
Select order( )
retrieving datas( )
Deleting( )
update( )
5. Purchase Orders
create orders( )
Sequence
diagram-...
change orders( )
Sequence
diagram...
delete orders( )
Sequence
diagram-...
Verification( )
filled properly( )
Generate ID( )
Error message ( )
Selecting order( )
intimate database( )
retrieve datas ()
modifying( )
Verification ( )
Improper modification ( )
Error message( )
Selecting order( )
retrieving datas( )
Deleting( )
Update ( )
COLLABORATION DIAGRAM:
1. Login
Main
form
1: login( )
8: re-login( )
2: Enter username and password( )
Login
form
: Customer
5: Valid( )
Error Login Welcome
message controller screen
6: Invalid( )
4: Retrieve from database( )
: Database
2. View Reports
2: Enter ID( )
8: re-enter ID( ) 3: Verification( )
main controller
form
1: request ID( )
: Administrator
: Database
error
message
6: Invalid( )
3. View Stock
Error
message
2: Enter book details( ) 7: error message( )
: Customer
3: Verify( )
: Administrator
Controll
er
4: Verified( )
: Database
4. Maintain Stock
2: add books( )
3: update books( )
1: to avail options( ) 4: delete books( )
option book profile
form form
: Employee
4.1 Add
2: add new books( )
Selection
form
1: Request for new books( )
: Employee
5: Generate ID( )
7: Error message( ) 3: Verification( )
: Database
4: filled properly( )
Error modificatio
message n form
6: Not filled properly( )
4.2 Modify
3: intimate database( )
Selection
form
: Database
1: Request to select books( )
4: Retrieve datas( )
2: Selecting books( )
5: modify( )
Modification
form
: Employee
8: Displays error message( ) 6: Verification( )
Error Modification
message controller
7: improper modification( )
4.3 Delete
1: Select the book( )
Selection
form
: Manager
4: update( )
Deletion
form
: Database
5. Purchasing Orders
2: create orders( )
3: change orders( )
1: avail options( ) 4: delete orders( )
option order profile
form form
: Manager
: Database
Error 4: filled properly( ) controll
message er
6: not filled properly( )
: Database
1: Request to select order( )
4: retrieve datas ()
: Manager
8: Error message( ) 6: Verification ( )
error modification
message controller
7: Improper modification ( )
: Manager
3: Deleting( ) 2: retrieving datas( )
4: Update ( )
Deletion
form
: Database
CLASS DIAGRAM:
1. Login
Main form +1
login ()
+1
Welcome
Error Login
screen
Message Controller +1 +1
correct()
incorrect() verification() enter()
Login form
username()
password()
re-login()
2. Maintain Books
Delete books
retrieve details
confirm()
verify()
delete specified()
3. Purchase Orders
Create purchase
orders
assign order
Delete purchase
Change purchase order
order
request()
Identify ID() confirm()
desired changes() deletion()
updates() displays()
view stock
verification()
Login
SOURCE CODE
1.Login
Option Explicit
End Sub
2.Maintain Books
Option Explicit
End Sub
End Sub
End Sub
3.Purchase Orders
Option Explicit
End Sub
End Sub
End Sub
4.View stock
Option Explicit
End Sub
End Sub
End Sub