Error message

Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in menu_set_active_trail() (line 2292 of /home/zuhnwktjvuzo/public_html/

Security Shop - Usage Scenario

2.0 Usage scenario
2.1 User profiles
2.2 Use-cases
2.2.1 Use-Case Diagrams
2.2.2 Use-Case Descriptions
2.3 Special usage considerations
2.4 Activity Diagrams

1.0 2.0 3.0 4.0 5.0 6.0 7.0


Usage scenario

Data Model and Description

Functional Model and Description

Behavioral Model and Description

Restrictions, Limitations, and Constraints

Validation Criteria

Surveillance / Security Camera Installation and Maintenance Shop Requirements

Security Camera Installation

2.0 Usage scenario

This section provides a usage scenario for the software. It organizes information collected during requirements elicitation into use-cases.

2.1 User profiles

The administrator has access to make changes into database. He/she can change/update/view/delete/create/Troubleshoot, information, issue Customer Id, track various activities etc.  He/she generates the various reports like sales by customers, customer list, vendor list, employee list, order list, summary of available units list. He also offers and puts discount schemes to the customers, depending on the access levels and number of orders.
A customer has only some privileges of the system. He/she can create/view/update his/her profile, request for pricing, place order, cancel order and also track his/her order. He/she cannot make any change to the system.
The employee should have all the access customer information but he should not be able to modify any of the system configurations.

2.2 Use-cases
Following are different Use cases for various aspects of activities. Click here to download use case diagrams for all above sue cases.

1. Overall Use case

In this Use Case the vendor can modify and update his name, supply, Address etc, these changes are notified to administrator who check the appropriate update and simultaneously stores that information into the database.


2. Use case diagram for Vendor List

In this use case administrator tracks the list of accessories and the supplies that the shop got, when customer requests for the accessories, the system prompts for type of accessory and the ID and relevant compatibility is also displayed, Administrator tracks what are available with reference to the vendor Id and Vendor Name. These all requests are carried In and Out from the Database backend.


3. Use case diagram for list of Accessories

In this use case administrator tracks the list of available cameras and Dvr's with reference to the vendor Id and vendor name, the list is shown or retrieved from the database, When customer requests the list of cameras or Dvr's, appropriate content is retrieved from database.


4. Use case diagram for List of Cameras and DVR's

In this use case administrator keeps track of all available cameras, Dvr's and Accessories available at any point of time, When customer prompts to buy and done checkout the available items are deducted each time when customer makes an order, In this way Admin can know how many are available.


5. Use case diagram for Tracking the no available and purchased

In this use case customer enters onto login page, making way to create the customer account, customer enters the username, the system will validate the username to make sure that its not a duplicate of already existing one, If its ok, then systems promotes for create the password and double check the password, if password did not match it will prompt an error, rest of the field are entered by the customer and the customer ID is notified to the administrator and these are stored in the database.


6. Use case diagram for Creating Profile for Customer

This is an interesting use case as far as in my point of view, once the customer is logged on to the account the browser will pick up the cookie what the customer is repeatedly watching any item and this information is sent to the system and stored in the database, by this customer can get alerts whenever there are any promotions or discounts on that item.


7. Use case diagram for Tracking customers point of interest 

In this use case customer can modify the account information like address, phone, email etc and these changes are stored in the database and appropriate notifications are notified to the admin.


8. Use case diagram for Customer Account Information

In this use case if there is any return's from the customer after checking the appropriate camera receiving to the shop and checking the item in anew condition, administrator will issue a return id and the confirmation number to the customer regarding their payment returns and these are stored in the database.


9. Use case diagram for Return shipment and Receipt Info

In this use case, after all the transactions are done by the month end, which are done by customer (buying the items from the shop) administrator can retrieve the sold items list and the database can generate the monthly balance sheet of the shop sold and available.


10. Use case diagram for Monthly report generation

In this use case customer is prompted with login with the username and password, if the customer forget the password, by providing appropriate emailed and the secret question to the system the administrator or system will issue a new password and the time stamp is noted and stored in the database.


11. Use case diagram for Login for Customer

In this use case the system or administrator will generate a unique customer id for an immediate identification purpose, after a successful creation of the new account by the customer the customer id is generated and sent to the customer and relatively stored in the database.


12. Use case diagram for Customer Id Creation

In this use case, after a successful account login by the customer and providing appropriate details by the customer, if the customer is willing to buy any item the item is selected by the customer and billing electronically, the system generates an electronic receipt with conformation number and with date and time, after these events occur the system will notify the confirmation number and receipt to both admin and the customer these are stored in the database.


13. Use case diagram for Checkout generation and Conformation

This use case describes the security aspect of the system, if the username and password is entered wrong for 3 times the system will lock that particular user for 30 min and this is notified to the administrator.


14. Use case diagram for Account lockdown

In this use case if the administrator wants to update or modify the changes to the item description at that moment the customer cannot read or access the content on the webpage it will simply gives an error and says “system is being updated”. Once the update is made customer then can access pages and these changes are reflected in the database.

15. Use case diagram for Changing Layout and format  

Click here to download use case diagrams for all above sue cases.


2.3 Special usage considerations

This is a web-based application, a standards compliant browser is essential.
At a minimum, the application must work with Internet Explorer 5 and higher and browsers based Mozilla Firefox 1.5 and higher. The browsers must also support per-session cookies and visual basic script.

2.4 Activity Diagrams: Swim lane Diagrams

Following are the list of activity diagrams based on the Swim lane model.

  1. Tracking Vendor List
  2. Return shipment and Receipt generation
  3. Changing the layout and format
  4. Account lockdown
  5. Activity Tracking
  6. Creation of profile by customer
  7. Customer checkout generation and conformation
  8. List of Accessories
  9. Tracking no of available

Click here to download Swim lane Diagrams for the application all use-cases.