Software Requirements Specification October 19, 2010

Software Requirements Specification
Version 1.1
October 19, 2010
Client Processing System (CPS)
Lewis Saliza
Submitted in partial fulfillment

Of the requirements of
Postgraduate Diploma in Computer Science
Table of Contents
Page #
Introduction.................................................................................3
Purpose...................................................................................................................................3
Scope of the System................................................................................................................3
References...............................................................................................................................4
Overview of the Document.....................................................................................................4
Overall Description.......................................................................5
System Environment...............................................................................................................5
Product Features.....................................................................................................................6
User Classes and Characteristics............................................................................................6
Operating and Development Environment.............................................................................6
General Constraints ...............................................................................................................7
Assumptions and Dependencies ............................................................................................7
Documentation Requirement..................................................................................................7
User View of the System........................................................................................................7
Requirement Specifications...........................................................8
Functional Requirements........................................................................................................8
External Interface Requirements..........................................................................................19
Non-Functional Requirements .............................................................................................20
Introduction
Purpose
The purpose of this document is to present a detailed description of the Client

Processing System (CPS). It will explain the purpose and features of the
system, the interfaces of the system, what the system will do, the constraints
under which it must operate and how it will be integrated with other existing
systems.
This document is intended for both the stakeholders and the developers of the
system and will be proposed to ComputerTech Solutions (T) Ltd for its
approval.
Scope of the System
CPS is a web-based application which encapsulates automatic call logging and

reminder capabilities. The Software will help users to handle customer
information effectively.
The CPS system will:
 Allow problem calls to be logged in automatically by synchronizing with a

telephone and e-mail system.
 Keep track of employees assigned to various jobs.
 Keep track of job orders and their status.
 Allow report generation for billing purpose and annual reviews.
 Notify clients if their problem has been recorded for processing.
 Remind users of any outstanding job to be attended.
 Facilitate access, security and integrity of data
 Print reports detailing list of jobs attended and their status per customer
bases.
The CPS system will run behind a database and it will interface with a
telephone system and an e-mail system. The system shall not need to print
worksheets.
References
 Feasibility Report; prepared on 10th October, 2010 by the development

team.
 “Software Engineering: A Practitioner’s Approach.” Roger S. Pressman,
sixth edition.
 System Requirement for e-learning tool.
http://asaha.com/download/MOTQ50DC
 Requirement Analysis-1, BITS c461/IS c341 Software Engineering.
www.cs.purdue.edu
 Writing Software Requirements Specification, by Donn Le Vie, Jr
www.techwr-
l.com/magazine/writing/softwarerequirementsspecifications.html
 The principal source of textbook material is “Software Engineering” by Ian
Sommerville, eighth edition.
Overview of the Document
The remainder of this document is in four chapters. The next chapter, the
Overall Description chapter 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 chapters. The
last three chapters of this document are written primarily for the developers
and describe in technical terms the details of the functionality of the product.
Overall Description
The CPS encompasses data from the telephone and e-mail systems. This
system will be completely web-based, linking to the remote web server from a
standard web browser. An Internet connection is necessary to access the
system.
System Environment
CPS System
Telephone
Users
Em ployee
CPS M anager
Database
Client
e-m ail
Helpdesk
Figure 1: System Environment
The CPS system has three active actors and two cooperating systems. Any
client communication with the system is through the email or telephone
systems. The helpdesk and other users interact directly with the CPS system
through a standard web browser. There is a link to the employee database.
Product Features
The system has the following major functions;
1. Allow calls to be logged automatically for reference purposes.

2. Keep track of employees assigned to various jobs.
3. Keep track of job orders and their status.
4. Allow report generation for billing purpose and annual reviews.
5. Notify clients if their problem has been recorded for processing.
6. Remind users of any outstanding job to be attended.
7. Facilitate access, security and integrity of data
User Classes and Characteristics
The Helpdesk is expected to be Internet and windows literate and to be able to

use button, pull-down menus, and similar tools. The main screen of the CPS
system will have the login function and a link to employee information.
Users are CTS employees from technical and other departments and they are
expected to be Internet and windows literate and to be able to use button, pull-
down menus, and similar tools.
Clients are expected to be Internet literate and to be able to use email and
voicemail function of the telephone.
The detailed look of these pages is discussed in section 3.2 below.
Operating and Development Environment
This product shall be developed using ASP.NET and SQL Server 2008. So we
would preferably use Windows Operating System for developing this software.
The Programming Environment shall be Microsoft Visual Studio 2008 and the
platform shall be Windows.
The following minimum system requirement is recommended for the system to

operate effectively;
 233 MHz Intel Pentium class or better processor

 At least 128 MB of RAM
 Windows XP (Service Pack 2 or later), Windows Vista, Windows 7
 Microsoft Internet Explorer (IE) 7+ , Mozilla Firefox
 JavaScript and cookies enabled.
 Recommend ActiveX be enabled (for Internet Explorer).
General Constraints
CPS shall comply with United Nations principals of data protection. The
principals shall be applicable to any kind of the information CPS shall handle. It
shall also follow company’s regulations and policy.
Security – CPS must allow access to data based on levels of access identified
per user and group of users.
Adaptation – The existing website shall be updated to accommodate links to

the CPS system.
Assumptions and Dependencies
The CPS system will contain an SQL server database and it will run on the
Server with high speed Internet capability. The physical machine shall have the
minimum requirement of 2.6 GHz processor, 2GB Ram and screen resolution of
1280 x 800.
The software developed here assumes the use of a tool such as ODBC for
connection between the Web pages and the database. The speed of the user’s
connection will depend on the hardware used rather than characteristics of this
system.
Documentation Requirement
CPS is a very common application like other familiar applications which

requires no expertise; therefore there will be no user manual.
User View of the System
This software will have graphical user interface that are very user friendly. The
user will have no difficulty in working with these user interfaces. The users will
import required commands through the software’s screen, and navigate
through information stored by using tools of the web page provided on the
screen.
Requirement Specifications
Functional Requirements
REQ 1: Opening a call

The purpose of this feature is to allow the user to create a new call record.
Stimulus/Response sequence
Opening a call
Helpdesk
Use case name: Opening a call

Description: The user creates a new call record.
Actors: Helpdesk
Precondition:
Before this use case can be initiated, the user has already accesses the
company’s intranet site.
Basic Flow
1. From the company’s intranet site the user click on the CPS link
2. System prompt user to enter CPS password
3. User enters CPS password
4. CPS verifies and accept CPS password
5. System displays a window in which the user can make a selection of the
access level he/she belongs.
6. The user select the access level he/she belongs to
7. Employee choose the function for opening a new call record
8. System accepts and saves the call record
9. User log-out
Alternative flow 1
1. Password is incorrect and not accepted, system prompt the user to enter
correct password.
2. After three incorrect password attempts, the system blocks the user and
close the CPS.
REQ 2: Closing a call

The purpose of this feature is to allow the user to close a call record to ensure
its work completion or recommendations.
C losing a call
Helpdesk
Use case name: Closing a call

Description: The user closes a call record.
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for close a call record
8. System accepts and saves the call record
9. The user choose to close the Close Call dialogue
10.The system returns the user to the CPS main page.
Alternative flow 1
correct password.
close the CPS.
REQ 3: Call Logging

The purpose of this feature is to allow calls to be logged in automatically.
C all L oggin g
T elephone
e-m a il
Use case name: Call Logging

Description: The system logs calls made by clients automatically
Actors: CPS, telephone system, e-mail system
Precondition:
Before this use case can be initiated, the client has already sent an e-mail or
made a call reporting for a specific problem.
Basic flow
1. The system synchronizes automatically with e-mail or telephone system
to determine if there are any problems reported by clients.
2. The system records a reported problem and assigns it a unique
reference number.
3. The system sends auto-reply message to the client informing the call log
number.
REQ 4: Check job status

The purpose of this feature is to allow the view a list of jobs and their status.
Check job status
Helpdesk
Use case name: View job status

Description: The user checks status of jobs
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for checking job status
8. The system returns a scrollable list of all active jobs with their status.
9. The system returns the user to the CPS main page.
Alternative flow 1
correct password.
close the CPS.
REQ 5: Check employee status

The purpose of this feature is to allow the view employees list and their status.
Check employee
status
Helpdesk
Use case name: View employee status

Description: The user checks status of employees.
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for checking employee status
8. The system returns a scrollable list of all employees with their status.
Alternative flow 1
correct password.
close the CPS.
REQ 6: Assign job to employee

The purpose of this feature is to allow the helpdesk to assigns job to
technicians.
Assign job to
employee
Helpdesk
Use case name: Assign job to employee

Description: The helpdesk assigns job to technician.
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for assigning job to employee
8. System accepts and save changes.
9. User log-out
Alternative flow 1
correct password.
close the CPS.
REQ 7: Check job assignment

The purpose of this feature is to allow employees to check their job
assignments.
Check job
assignment
user
Use case name: Check job assignments

Description: The employees check jobs assigns to them.
Actors: user
Precondition:
Basic Flow
7. Employee chooses the function for viewing an employee and a list of
jobs assigns to him/her.
8. The system returns a scrollable list of jobs assigns to that employee.
9. The system returns the user to the CPS main page
Alternative flow 1
correct password.
close the CPS.
REQ 8: Print report

The purpose of this feature is to enable users to view reports based on user
specified parameters.
Print report
Helpdesk
Use case name: Print report

Description: The user prints reports
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for printing reports
8. The system prompts the user to enter report parameters.
9. The user provides parameters.
10.The system prints requested report.
11.The system returns the user to the CPS main page.
Alternative flow 1
correct password.
close the CPS.
REQ 9: Send auto-reply message

The purpose of this feature is to notify a client that the reported problem has
been received and scheduled for action.
S en d au to
-reply
m essag e
C lient e-m ail
Use case name: Send auto-reply message

Description: The system sends auto-reply message to client
Actors: CPS, client
Precondition:
Before this use case can be initiated, the system has already generated a
unique call number.
Basic flow
1. The system forwarded the unique call number to e-mail system.
2. The system sends emails to a client giving feedback about the status of
problem reported.
REQ 10: Search client

The purpose of this use case is to allow the user look for client information
easily.
Search client
Helpdesk
Use case name: Search client

Description: The user prints reports
Actors: Helpdesk
Precondition:
Basic Flow
7. Employee choose the function for searching client information
8. The system the system displays client information.
Alternative flow 1
correct password.
close the CPS.
External Interface Requirements
System interfaces
The interfaces for this system are:
1. Telephone system
2. CPS windows
3. Email interface
User interfaces
1. Users will receive reminders for outstanding jobs through the email
interface use.
2. CPS screens and windows give system-user interactions.
Hardware interfaces
1. Computers
2. Telephone PABX
3. CPS server and mail sever
Software interfaces
1. Call transcription software
CPS receives other client calls from this system. The purpose of this
software is to convert all voice message calls onto text and forward it to
CPS.
2. Employee database
CPS accesses employee’s information from the company employees’
database system.
Communications interfaces
1. Network protocols (LAN)
2. Email protocols
Non-Functional Requirements
Logical Structure of the Data

The logical structure of the data to be stored in the CPS software is given
below.
Client
Helpdesk
nt
Se
Logs makes
assignment
Call
sent
A tt en
ds
Technician
Logical Structure of the CPS system Data
Performance Requirements
This software should perform the same way irrespective to its Operating
System environments. Time taken for logging calls and sending auto-reply
message to client should be minimum.
Security Requirements
The server on which the CPS system resides will have its own security to
prevent unauthorized write/delete access. There is no restriction on read
access. The email functionality is on another cooperating system and thus is
external to the CPS system. There should be some protection measures to
ensure no spam mails are forwarded to CPS system.
The PCs on which the users will use to access CPS system have its own
security. Only the authorized personnel will have physical access to the
machines and the program on them. There is no special protection built into
this system other than to provide the users with levels of access to information
on it. Users will access data based on there levels of access.
Reliability and availability

The system should be available for use 24 hours a day, 7 days a week.
Quality Requirements
As a basic characteristic the software needs to be testable to ensure
correctness.

Software Requirements Specification October 19, 2010

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification October 19, 2010

Uploaded by

Copyright:

Available Formats

Software Requirements Specification

Client Processing System (CPS)

Submitted in partial fulfillment

The purpose of this document is to present a detailed description of the Client

Scope of the System

CPS is a web-based application which encapsulates automatic call logging and

The CPS system will:

 Allow problem calls to be logged in automatically by synchronizing with a

 Feasibility Report; prepared on 10th October, 2010 by the development

Overview of the Document

standard web browser. An Internet connection is necessary to access the

Figure 1: System Environment

The system has the following major functions;

1. Allow calls to be logged automatically for reference purposes.

User Classes and Characteristics

The Helpdesk is expected to be Internet and windows literate and to be able to

The detailed look of these pages is discussed in section 3.2 below.

Operating and Development Environment

The following minimum system requirement is recommended for the system to

 233 MHz Intel Pentium class or better processor

Adaptation – The existing website shall be updated to accommodate links to

Assumptions and Dependencies

CPS is a very common application like other familiar applications which

User View of the System

REQ 1: Opening a call

Use case name: Opening a call

REQ 2: Closing a call

Use case name: Closing a call

REQ 3: Call Logging

Use case name: Call Logging

REQ 4: Check job status

Check job status

Use case name: View job status

REQ 5: Check employee status

Use case name: View employee status

REQ 6: Assign job to employee

Use case name: Assign job to employee

REQ 7: Check job assignment

Use case name: Check job assignments

REQ 8: Print report

Use case name: Print report

REQ 9: Send auto-reply message

C lient e-m ail

Use case name: Send auto-reply message

REQ 10: Search client

Use case name: Search client

External Interface Requirements

Logical Structure of the Data

Logical Structure of the CPS system Data

Reliability and availability

You might also like