On line Image Management Design Evaluation
By Aces Group
Following is the specification of various diagrams that were developed by the team for the application. All diagrams were assessed by Dr. Hankley
Use Case Diagram
The System has the following Actors and each Actor has the following Use Cases
Customer
Use Cases:
Register
Place Order
Check Order Status
Browse Image
Download Ordered Image
Photographer
Use Cases:
Upload Image
Edit Image Information
Give Permission to View Image
Manager:
Use Cases:
Approve Order
Reject Order
Prepare Invoice
Add Photographer
Class Diagram
User:
This Class represents a User Object.
Specialization of User Class are the Customer, Photographer & Manager Classes
UserFacade
This Class represents a session bean that performs user related functions like:
authenticateUser(user name, password) etc
Order Header
This Class represents an Order object that is created by Customer so as to get images
Order Detail
Each Order Header as Multiple Order Details. Thus if an Order has ten images there will be one order header and ten order details
Order Façade
This Class represents a session bean that performs order related functions like:
createOrderHeader(customer id)
createOrderDetail(order no, image name)
Sequence Diagram
Theoretically, there should be a sequence
diagram per Use Case. However, sequence diagrams were developed for the
following use cases:
- Authenticate User (User)
- Place Order (Customer)
- Upload Image (Photographer)
- Approve Order (Manager)
Thus, at least one sequence diagram was developed per Actor.
Activity Diagram
An Activity Diagram was developed for
Order Processing Function starting from Customer placing order, Manager
approving/rejecting the order, Photographer fulfilling the order and lastly
Manager invoicing the order.