There is a company called (SecureU LLC). This company works on a surveillance system project for a university based on the following details:

There is a company called (SecureU LLC). This company works on a surveillance system project for a university based on the following details:

1.     What should the system do?

The security system should provide real time information about the state of the grounds under surveillance to on-duty security personnel.  The system should deny/allow access to resources (buildings, rooms, etc.) to individuals based upon their credentials.

2.     Work Context

Security Guards

Input: commands to cameras/locks

Output: status of system

Cameras, door locks

Input: status

Output: event (lock/unlock, pan, zoom, …)

Police station

Output: emergency event notification

Faculty, students (input via id card)

Input: access request

3.     Risk Analysis

Budget/Funding

Will we be able to develop a marketable system before we run out of money?

Technology

Can we build the necessary equipment to interface with locks/cameras in time?

Can we build the system before the technology being used becomes obsolete?

Client Base

Do we have one?

Will we be able to build a large enough client base such that our system becomes profitable?

Technical Staff

Will be able to hire and retain the necessary staff to not only develop the system but to install it.

Electricity

What happens if the electricity goes out and there is no system to control security?

Interference

What happens if signals are interfered with (whether accidental via cell phone or intentional hacking) and the system is unable to react?

Performance

Will the system be able to authenticate users and provide access to resources in a reasonable amount of time?  (What is “reasonable”?)

ID Theft/Hacking

What if the system allows access to an unauthorized individual due to id theft or hacking into the system?  Are we liable for bad things happening in this case?

4.     Stakeholders

Us, developers

Client/Customer – University

User – Security guards, faculty, students

Investors

Contractors – Suppliers of system components

5.     Terminology

Resource – anything protected by the system (buildings, rooms, people).

Node – a device connected to the network that can accept output from the system and provides input to the system (a lock, camera, pda).

Network – a collection of nodes that make up the security system.

User – any person interacting with the system (security guard, student, faculty).

Infrastructure – the basic components of system that allow it to maintain connectivity (wires, wireless access points, cameras, locks).

Camera – device that delivers real-time images of the grounds under surveillance.

Lock – device that can be controlled to allow or deny access to a resource.

ID Card – a magnetic user identification card (like credit card)

6.     Project Constraints

The system will support a network of both indoor and outdoor surveillance cameras.

The system will control access to all campus doors.

The system will support communications among security personnel.

The system will have a command center.

The system should be viable for any size campus:  very small to very large.

7.     Domains of Interest

Wireless communication

Control mechanisms and interfaces

Locking mechanisms

Backup power

Emergency override of the system

Information display (user interface)

Distributors of system components

Human factors (ease of use of system)

Current security procedures/protocols

Tasks:

Write two sets of requirements (one set functional, another nonfunctional)

Table 1: Functional Requirements Table

Description

Rationale

Fit Criterion

Table 2: Non-Functional Requirements Table

Type (Characteristics)

Description

Rationale

Fit Criterion