LAB MANAGEMENT SYSTEM

Software Requirements Specification

8-8-2012 Version 1.0

Approvals Signature Block

Project Responsibility
Project Guide (Internal) Project Guide (External) Documentation Leader

Signature

Date

Department of Information Technology

Software Requirements Specification

Table of Contents
1.INTRODUCTION ...............................................................................................................................2 1.1 PURPOSE ......................................................................................................................................................3 1.2 SCOPE...........................................................................................................................................................3 1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS....................................................................................................3 1.4 REFERENCES...................................................................................................................................................4 1.5 OVERVIEW.....................................................................................................................................................4 OVERALL DESCRIPTION................................................................................................................................4 PROBLEM STATEMENT...........................................................................................................................................5 1.6 PRODUCT PERSPECTIVE....................................................................................................................................5 PRODUCT POSITION STATEMENT.............................................................................................................................5 1.7 PRODUCT FUNCTIONS.......................................................................................................................................7 1.8 ASSUMPTIONS AND DEPENDENCIES.....................................................................................................................7 SPECIFIC REQUIREMENTS............................................................................................................................7 1.9 FUNCTIONS.....................................................................................................................................................7 1.10 LOGICAL DATABASE REQUIREMENTS................................................................................................................8 1.11 SOFTWARE SYSTEM ATTRIBUTES.....................................................................................................................8

1. INTRODUCTION
.

v. 1.0 2011

Software Requirements Specification 1.1 PURPOSE The purpose of the Software Requirements Specification (SRS) is to give the customer a clear and precise description of the functionality of the assessmentsupport software to be developed and to eliminate ambiguities and misunderstandings that may exist. For the customer, the SRS will explain all functions that the software should perform. For the developer, it will be a reference point during software design, implementation and maintenance. To clarify keywords used throughout the document, a set of definitions, acronyms and abbreviations is provided in section. The SRS divides the system requirements into two parts, behavioral and nonbehavioral requirements. The behavioral requirements describe the interaction between the system and its environment. Non-behavioral requirements relate to the definition of the attributes of the product as it performs its functions. This includes the level of security, efficiency, reliability, maintainability, portability, capacity, and the standards of compliance of the product.

1.2 SCOPE Every Cell-phone possesses a unique device ID i.e. IMEI number (considering GSM family of protocols). The system will retrieve the IMEI number of every Smartphone device that tries to connect with the server. The user giving correct ID and password and having authenticated device will only get the access to the companys server. Further, the system will monitor the user activities in order to check whether the user is accessing the system within his privileges. The system will successfully block all the Smartphones connected through USBs. The system will only allow those the devices that work on GSM family of protocols. The system will use database for keeping the records of authenticated users. The major benefit to the organization is the secured connectivity of the user to the company server. The scope of the system doesnt include CDMA family of protocols such as 1x, EV-DO, W-CDMA. Further, the system will not allow devices that try to connect through WiFi, Bluetooth or USB.

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

v. 1.0 2011

Software Requirements Specification Term or Acronym IDPS CDMA GSM 3G IMEI GPRS EDGE Wi-Fi MAC Definition Intrusion Detection and Prevention System Code Division Multiple Access Global System for Mobile Communications 3rd generation mobile telecommunications International Mobile Equipment Identity General Packet Radio Service Enhanced Data Rates for GSM Evolution Mechanism for wirelessly connecting electronic devices. Media Access Control

Table 1. Definitions and Acronyms

1.4 REFERENCES 1) Mobile Computing Talukder, Ahmed, Yavagal, 2nd Edition 2) www.3gpp.org

1.5 OVERVIEW
.

The SRS is organized into two main sections. The first is The Overall Description and the second is the Specific Requirements. Overall Description section of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next section. Requirement Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product. Both sections of the documents describe the same software product in its entirety, but are intended for different audiences.

OVERALL DESCRIPTION

v. 1.0 2011

Software Requirements Specification When accessing a companys server, only known users should be granted access in order to have a secure environment. Usually, a user is identified uniquely through a user name and password. It may happen that an intruder obtains this log in information. In such a case, he can get access to the server and create havoc for the company. This can be prevented by allowing access only to those users whose devices have been uniquely identified by the server, as each device has a unique ID. Thus, a user having correct login credentials as well as matching device ID can get access. Also, the system can monitor the traffic on server/network by analyzing packets and can detect any malicious activity, thus preventing intrusions. PROBLEM STATEMENT

The problem of

Intrusions into a network through Smartphones Affects The organizations server and network, also poses threat to individuals in the network The impact of which is Confidential information of an organization or individual is at stake A successful solution 1) Strengthen security by adding another would line of defense (unique device IDs) 2) Detect and prevent intrusions by monitoring network traffic on server and in network

1.6 PRODUCT PERSPECTIVE The system will reside on the server of the organizations network. It will communicate with other nodes connected to it through a wired connection. The system receives connection requests from clients and it must decide whether to grant access or block it. This decision is based on whether the client device is registered with the server. Registered devices are identified by the unique device IDs such as IMEIs in case of Smartphones. If the IMEI matches the clients login credentials, it is granted access, else its request is rejected.

PRODUCT POSITION STATEMENT

v. 1.0 2011

Software Requirements Specification

For Who The IDPS for Smartphone network traffic on servers That Network Administrator of an organization Needs to authenticate devices in network and monitor network traffic for intrusions is a Server-side software system

Unlike Our product

that will detect and prevent intrusions on a server or the network by incorporating a unique defense mechanism that will block unidentified device IDs from accessing the network or server None Identifies clients through their device IDs in addition to user name/password.

1.6.1

System Interfaces

Back-end: The system will maintain a database of the registered users, consisting of information such as User Name, Password and Device ID. Another database can be maintained for devices that are currently active in the network. Front-end: The system would be implemented using the Java programming language. We are using Java as it provides libraries such as AWT and Swing which are widely used in developing interfaces. Java is a powerful programming language as it uses Object-oriented principles. It is platform-independent, so it can be used for developing on multiple platforms. Operating System: The system will be deployed on a Linux-based OS.

1.6.2

User Interfaces

The software interface would provide a means of communication between the Network Administrator and the system. The administrator would easily be able to understand the activities performed by the system through the interface. A simple interface would be designed that is easily understandable to the administrator. The interface would provide a list of clients that are currently in the network and connected to the server. It would display details such as the network traffic of the devices. It would provide alert messages to the administrator when a device tries to perform illicit activities. The administrator will be provided with an option of managing the databases, where he can make changes and updates to the client information database.

v. 1.0 2011

Software Requirements Specification

1.7 PRODUCT FUNCTIONS 1) Installing software onto the client terminal to extract the IMEI number of that terminal device that tries to contact the companys server. 2) Retrieve the IMEI number and send it in packetized form to the companys server for further authentication process. 3) Check for valid user-ID, password and IMEI in order to grant the access to the server. 4) Further, after the access is granted, record the user activities in order to identify malicious intent. 5) Check whether the user misusing his privileges and tries to acquire more privileges. 6) Report to the network administrator accordingly if such activities are detected.

1.8 ASSUMPTIONS AND DEPENDENCIES It is assumed that the devices work on GSM family of protocols (i.e. GSM, GPRS, and EDGE) and not CDMA. Moreover, the server is Wi-Fi, Bluetooth disabled. All the client terminals in the network will have USB access disabled. The client side device has to be programmable in order to access IMEI number of the device.

SPECIFIC REQUIREMENTS

1.9 FUNCTIONS

v. 1.0 2011

Software Requirements Specification Goal 1: System shall perform authentication of client and device Objective 1: Authenticate client using the log-in credentials Objective 2: Authenticate device using unique device ID Goal 2: System shall monitor traffic for detecting intrusions in network Objective 1: Capture packets across network. Objective 2: Identify the client performing the intrusion through IMEI

1.10

LOGICAL DATABASE REQUIREMENTS

The following databases will be required in the system. A database to save the login credentials of the registered users and the respective IMEI numbers of their devices. We will call it Client Database. A database to keep the reports of the monitoring as well as the list of users who have performed (or tried to perform) malicious activities (called as Blacklist)

1.11

SOFTWARE SYSTEM ATTRIBUTES

1.11.1 Availability This system will be available to the network administrator. Only thee personnel having the required privileges will be able to access the system. In other words, the system will not be an Open to all system. 1.11.2 Security The basic aim of the system is to provide security against attacks on the server via Smartphones. Security will be provided using methods described in details in this document.

v. 1.0 2011