Security Shop Behavioral Model

Introduction

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

Sr No.

Event

Actor

0

 Open the Home page

 All

1

 Create login

 All

2

 Change Username/Password

 All

3

 User login/logoff to/from system

 All

4

 View list of logged in users

 Administrator

5

 Create new Customer information

 Customer

6

 Update Customer Information

 Customer

7

 Delete Customer Information

 Administrator

8

 View Customer Information

 Customer , Administrator

9

Issue Return ID

Administrator

10

Add, modify, delete camera

Administrator

11

Add, modify, delete Dvr’s

Administrator

12

Add, modify, delete accessory

Administrator

13

Issue  Forgotten password

Administrator

14

Account Lock and recovery

Administrator

15

Notifications

Administrator

16

Place order

Customer

17

 Create Shipping address Information

 Customer

18

 Update Shipping address Information

 Customer

19

 Delete Shipping address Information

 Administrator

20

 View shipping address Information

 Customer, Administrator

21

 Generate various report

 Administrator

22

 Generate order list from date to date

 Administrator

23

 Generate sales report by customer

 Administrator

24

Track Vendor List

Administrator

25

Track Customer Info

Administrator

26

Track No of units available and orders

Administrator

27

Update and notifications for new products

Administrator

28

 Convert all report to excel or word

 Administrator

S.no

State Name

State Description

Events handled

0

START

This is the initial state of the system. When the system starts, we initialize and move on to the LOGIN state.

Initialize

1

LOGIN

This is the state where the login information is provided

Login_correct, login_incorrect

2

USER_CHECK

Once the login is validated, the check for type of the user is determined

Display_main_customer

3

CUSTOMER_MAIN

This is the main state for the customer. The state of the application should be here, to perform any valid operations by the users of type CUSTOMER.

Billing_transaction, customer_transaction, order_transaction, logout

4

CUSTOMER_ORDER

This state the customer either requests the order to be placed or requests the return for the purchased item

Return Shipment
New order

5

ADMIN_UPDATE

This state admin does the actions for updating, notifying etc.

Modify
Update
Delete

7

ADMIN_MAIN

This is the main state for the admin. The state of the application should be here, to perform any valid operations by the users of type ADMIN.

Billing_transaction, customer_transaction, order_transaction, logout

8

INTERMEDIATE

When the information is accepted and before we move to READY state, we decide whether to go to OVERDRAWN state or the READY state, based on the initial balance entered by user.

Transaction_complete

9

STOP

This is the end state of the application