STOCKMAINTENANCESYSTEM
STOCKMAINTENANCESYSTEM
net/publication/328382291
CITATIONS
READS
0
14,389
1 author:
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Suhaib Bin Younis on 19 October 2018.
1.2 Objectives
1.3 Scope
http://
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.
http://
2. Problem statement (Use case) analysis
i Login:
ii Maintain Books:
iv View Stock:
v View report:
http://
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:
iv Administrator:
v Database
The database is the collection of data where the data is stored and
form where the data can be retrieved.
http://
2.3 Use Case Diagram:
Maintain books
Employee
Login
Manager Database
Purchase order
View report
Administrator
View stock
Customer
http://
3. Design of Stock Maintenance System
3.1 Design Documentation
1. Login
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
http://
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
http://
2.2.1.2 Update Books
ii Delete Cancelled:
http://
2.4 Post Condition:
3. Purchase Orders
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.
http://
3.2.1.2 Change Purchase Orders
http://
3.4 Post Condition:
If the use case is successful the manager makes the purchase orders
else the system is unchanged.
4. View stock
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.
http://
5. View Report
This use case describes how the administrator views the reports in the
stock maintenance system.
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.
http://
SEQUENCE DIAGRAM:
1. Login
: Customer Main form Login form Login Welcome Error message : Database
controller screen
login( )
Verification( )
Valid( )
Invalid( )
re-login( )
http://
2. View Reports
request ID( )
Enter ID( )
Verification( )
Valid( )
Generate report( )
Invalid( )
re-enter ID( )
http://
3. View Stock
Verify( )
Verified( )
Generate report( )
not filled properly( )
error message( )
4. Maintain Stock
to avail options( )
add books( )
Sequence
diagram...
update books( )
Sequence
diagram...
delete books( )
Sequence
diagram-...
http://
4.1 Add
Verification( )
filled properly( )
Generate ID( )
Error message( )
4.2 Modify
Selecting books( )
intimate database( )
Retrieve datas( )
modify( )
Verification( )
improper modification( )
http://
4.3 Delete
Select order( )
retrieving datas( )
Deleting( )
update( )
5. Purchase Orders
avail options( )
create orders( )
Sequence
diagram-...
change orders( )
Sequence
diagram...
delete orders( )
Sequence diagram-...
http://
5.1 Create Order
Verification( )
filled properly( )
Generate ID( )
Error message ( )
Selecting order( )
intimate database( )
retrieve datas ()
modifying( )
Verification ( )
Improper modification ( )
Error message( )
http://
5.3 Delete Orders
Selecting order( )
retrieving datas( )
Deleting( )
Update ( )
COLLABORATION DIAGRAM:
1. Login
Mai
n
1: login( )
8: re-
login( ) 2: Enter username and password(
) Login
form
: Customer
5: Valid(
Error Login ) Welcome
messag controller screen
e
6: Invalid(
)
4: Retrieve from database( )
: Database
http://
2. View Reports
2: Enter ID( )
8: re-enter ID( 3: Verification(
) )
main controller
form
1: request ID(
)
: Administrator
5: Generate report( )
4: Valid( )
7: Displays error message( )
: Database
error
message
6: Invalid( )
3. View Stock
Error
messa
2: Enter book details( 7: error message( )
: Customer )
3: Verify( )
: Administrator
4: Verified( )
Contr
: Database oll
http://
4. Maintain Stock
2: add books( )
3: update books( )
1: to avail options( 4: delete books( )
) option
form book profile
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
4.2 Modify
3: intimate database( )
Selecti
: Database
on1: 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(
)
http://
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 form
order
profil
: Manager
: Database
Error 4: filled properly( ) controll
message er
6: not filled properly( )
http://
5.2 Change Orders
3: intimate database( )
order selection
form
: Database
1: Request to select order(
4: retrieve datas ()
: Manager
8: Error message( ) 6: Verification ( )
error
modification
message
controller
7: Improper modification (
)
5.3 Delete Orders
1: Selecting order( )
Selection
form
: Manager
3: Deleting( ) 2: retrieving datas( )
4: Update ( )
Deletion form
: Database
http://
CLASS DIAGRAM:
1. Login
Main form
+1
login ()
+1
Welcome screen
Error Message Login Controller
+1 +1
correct()
verification() enter()
incorrect()
Login form
username()
password()
re-login()
2. Maintain Books
Delete books
retrieve details
confirm()
verify()
delete specified()
http://
3. Purchase Orders
Create purchase orders
assign order
name of the book() quantities() edition()
Delete purchase
Change purchase order order
view stock
verification()
http://
3.5 Component diagram
Login
http://
SOURCE CODE
1. Login
Option Explicit
End Sub
2. Maintain Books
Option Explicit
End Sub
End Sub
End Sub
http://
3. Purchase Orders
Option Explicit
End Sub
Public Sub
Public Sub
4. View stock
Option Explicit
Private books_available As
book_required()
End Sub
End Sub
http://
View publication
End Sub
http://
View publication