Online Client Management System

SOFTWARE REQUIREMENTS SPECIFICATION

DOCUMENT
Submitted by
Name: Shazmeen
Roll#: 171209
Class: MCS 3rd
Session: 2017-2019

Department Of Computer Science

03-07-2019

[SHAZMEEN]
SESSION: 2017 - 2019 | <THE BROOKS POST GRADUATE COLLEGE
BAHAWALPUR>
 Online client management system

Revision History
Date Description Author Comments
<03-07-2019> <Version 1> Shazmeen <First Revision>

Document Approval
The following Software Requirements Specification has been accepted and approved by
the following:
Signature Printed Name Title Date
Muhammad Faheem Supervisor, CSIT 03-07-2019
21306

ii
 Online client management system

Table of Contents

1. Introduction 1
1.1 Purpose 1
1.2 Scope 2
1.3 Definitions, Acronyms, and Abbreviations. 2
1.4 References 2
1.5 Overview 3

2. The Overall Description 3

2.1 Product Perspective 3
2.1.1 Operations 4
2.1.2 Site Adaptation Requirements 4
2.2 Product Functions 4
2.3 User Characteristics 4
2.4 General Constraints 5
2.5 Assumptions and Dependencies 5

3. Specific Requirements 5
3.1 External Interface Requirements 5
3.1.1 System Interfaces 5
3.1.2 Interfaces 5
3.1.3 Hardware Interfaces 6
3.1.4 Software Interfaces 6
3.1.5 Communications Interfaces 7
3.2 Functional Requirements 8
3.2.1 <Functional Requirement or Feature #1> 8
3.2.2 <Functional Requirement or Feature #2> 9
3.3 Use Cases 10
3.3.1 Use Case #1 10
3.3.2 Use Case #2 11
3.4 Classes / Objects 11
3.4.1 <Class / Object #1> 11
3.4.2 <Class / Object #2> 12
3.5 Non-Functional Requirements 12
3.5.1 Performance 12
3.5.2 Reliability 13
3.5.3 Availability 13
3.5.4 Security 13
3.5.5 Maintainability 13
3.5.6 Portability 14
3.6 Inverse Requirements 14
3.7 Logical Database Requirements 14
3.8 Design Constraints 14
3.8.1 Standards Compliance 14

iii
 Online client management system
4. Analysis Models 14
4.1 Sequence Diagrams 15
4.2 Data Flow Diagrams (DFD) 16
4.3 State-Transition Diagrams (STD) 17

5. Supporting Information 17
Appendix A – Background Research on: 17
Appendix B – Data Dictionary 17

iv
 Online client management system

Introduction

The client management system is the most underrated tool in the small business owner’s
toolbox today. Of course the Client management system helps with organization, but
having all of your customers, past customers and prospective customers in one place is a
“must have” for anyone serious about their business.

It's not just about getting organized. It's about having a client management software in
place that will follow up with your customers and prospects, remind you about important
client tasks, and bring in new leads to your business.

Too often the small business owner glosses over the need to put all contacts in a single
place. In many cases he or she has had a bad experience with a previous client
management software suite and is afraid to jump into another one.

Most client databases try to be everything to everyone. They try to cram as many OCMS
software features into their product as possible. This will make them look good on a
feature for feature comparison chart against the competition, but the actual business
owner who has to use the OCMS product almost always suffers as a result.

Purpose
A centralized Client Project Management platform designed to help Project teams work
together with in a single environment, enabling them to share tasks, discuss ideas,
Manage and allocate resources, and collaborate more efficiently among other, resulting in
faster delivery of projects with results that meets or even exceed.
It is intended to be a complete specification of what functionality the system provides.
Specific design and implementation details will be specified in a future document.

SRS Document 1.0 Page 1 of 17 03-07-2019

 Online client management system

Scope
A quality project scope define all expectations from day one to completion the
deliverables, tasks, deadline and required resources associated with the life cycle of a
project…..project scope management is the aspect of planning that involves determining
and documenting what is and is not part of the project’s scope.
This project’s aim is to automate the system, calculating the fare, collecting fare,
collecting all necessary information of the client and then serve the client. The data used
by the system is stored in a database that will be the centre of all information held clients
and employees and the base for the remainder of the process after the initial application
has been made. This enables things to be simplified and considerably quickened, making
the jobs of the people involved easier. It supports the current process but centralizes it
and makes it possible for decisions to be made earlier and easier way.

Definitions, Acronyms, and Abbreviations.

OCMS: Online Client Management System
HTML: Hyper Text Markup Language
CSS: Cascading Style Sheets
FR: Funcational Requirements
NFR: Non Funcational Requirements
URL: Uniform Resource Locator
SQL: Structure Query Language
UML: Unified Modeling Language
CRM: Client Relationship Management
PHP: Hypertext Preprocessor
SRS: Software Requirement Specification
HTTP: Hyper Text Transfer Protocol
TCP/IP: Transmission Control Protocol/Internet Protocol
OS: Operating System
ESO: Engineering Services Outsourcing
LCU: Last Cluster Used
ATCS: Advanced Tactical Communication System
VME: Virtual Machine Environment
EJB: Enterprise Java Beans

1.4 References
www.google.comwww.zoho.com
www.workflowmax.com
www.allclients.com
www.hubspot.com
www.vcita.com
www.financesonline.com
http://msdn.microsoft.com/en-us/library/ms130214

SRS Document 1.0 Page 2 of 17 03-07-2019

 Online client management system

http://www.chambers.com.au/glossary/software_requirements_specification.php
http://ac.aup.fr/~croda/SampleStudentsWork/cs348/finalProjectS07/final%20presentation
/final/Volere_Specifications_FV.pdf

1.5 Overview
SRS will include two sections.
Overall Description will describe major components of the system, interconnection and
external interfaces.
Specific Requirements will describe the functions of actors, their role in the system and
constraints.

2. The Overall Description

Overall Description will describe major components of the system, interconnection and
external interfaces.
Overall Description: The rest of this document will give further details on the overall
product description, including the hardware, software, and communications interfaces,
product functions, user characteristics, and any assumptions that will be made.

2.1 Product Perspective

Figure 1: Model of the System

 The web pages (XHTML) are present to provide the user interface on customer
client side. Communication between customer and server is provided through
HTTP/HTTPS protocols.
 The Client Software is to provide the user interface on system user client side and
for this TCP/IP protocols are used.

SRS Document 1.0 Page 3 of 17 03-07-2019

 Online client management system

 On the server side web server is EJB and database server is for storing the
information.

2.1.1 Operations
Update Details: Employees and clients will all have the ability to update their personal
details at any time. Clients, however, will also be able to update their booking details.
After the user has confirmed the update, an e-mail is dispatched with the original and new
details as confirmation. The only time an booking will be locked for editing will be when
an employee is employed to serve the client.
Manage Emails: Now you can send Emails to your Leads, Contacts and Potentials
modules. You need not go to your favorite Email service to communicate with your
contacts.

2.1.2 Site Adaptation Requirements

Online Client Management System would run on every platform having a modern
browser (listed in non-functional requirements section) that can be run on any operating
system; so it does not need any adaptation to a particular platform. No site adaptation is
necessary in this project.

2.2 Product Functions

Some of the features are identified for the software. They are listed below:

 Feedback: The administrator can able to see the feedback given by each client so
that he can take appropriate actions for future improvement.
 Report Generation: The system supports generation of reports based on different
criteria.
 Record maintenance: The system also must keep track the statistical reports of
daily activities of the online booking.
 Discount Offer: The admin can create discount codes and the client can get
discount on fares using the codes.

2.3 User Characteristics

The client should have the basic idea to operate (use) the system and he already has the
experience to work in the internet (browser). Default Language is English.

There are three types of users of the system.

 Administrator
 Content Managers
 Users / Clients

Administrators will be able to manage permissions for the website using out of the box
SharePoint features.

Content Managers will have permission to add/update content in the system that is
visible to the normal Users/Clients. Information added by content managers will be
approved by Administrators/Approvers to approve/reject the content Viewers of the
website will only use the website to obtain information.

SRS Document 1.0 Page 4 of 17 03-07-2019

 Online client management system

2.4 General Constraints

Web Based Product
The computers must be equipped with web browsers such as Firefox, Chrome. The
product must be stored in such a way that allows the client easy access to it. Response
time for loading the product should take no longer than five minutes. A general
knowledge of basic computer skills is required to use the product
 Internet is necessary.
 The browser (Google chrome, opera etc.)
 It can run on every system and it is very easy to handle.

2.5 Assumptions and Dependencies

1. Username is valid email addresses of respective user
2. Administrator has the authority to add/delete employee accounts.
3. Administrator has the authority to delete client.
4. Roles and responsibilities are already established.
5. Administrator is already created.

3. Specific Requirements
The document will also include the specific requirements needed. These will include the
functions, performance, design, and software attributes. This document is organized in a
logical manner and is easy to follow. Readers should refer to the table of contents,
appendices, or index if looking for something in specific. Otherwise, reading this
document from start to finish will start with a vague description and get more specific
and detailed as changing sections and reading further.

3.1 External Interface Requirements

This chapter is an outline of the inputs and outputs of the ATCS. It is a complement of
what has been mentioned in General Requirements - Control Software.

3.1.1 System Interfaces

 Client on Internet: Web Browser, Operating System (any)
 Client on Intranet: Client Software, Web Browser, Operating System (any)
 Web Server: Apache, Operating System (any)
 Data Base Server: MySQL, Operating System (any)
 Development End: HTML, MySQL, OS (Windows), Web server.

3.1.2 Interfaces
Specify:

SRS Document 1.0 Page 5 of 17 03-07-2019

 Online client management system

The user interface requirements for the VLT SW are dictated by and described in their
implementation in. The ATCS shall inherit them completely. Therefore, as already stated
at the end of the General Requirements - Control Software of this document, the explicit
requirement for the ATCS is to use the CCS/User Interface to create all the graphical
panels, which will interact with the observer at the level of the ISS/User Interface. Since
the user interface environment shall be organized during the development phase as a
flexible, easy-to-update, dynamically configurable system, which access mainly values
stored in the on-line database, it is not necessary (if not worthless) to define the layout
and hierarchy of panels at requirement level. Discussions with potential users and
preliminary tests on the field will suggest how functions have to be grouped and how data
have to be displayed to achieve the best ergonomics.
The graphical user interface will rely on the ESO Graphical UIF Common Conventions.
For the implementation of the graphical user interface framework the current standard
will be used.

3.1.3 Hardware Interfaces

The hardware interfaces shall obey to the two statements written in and repeated here for
reader's convenience:
All hardware interfaces to the controlled devices shall be realized using I/O boards in the
LCUs
The WSs shall not have hardware interfaces to the controlled devices, but they shall
control them indirectly by means of the LCUs, which will receive commands through the
LAN.
Reliable software device drivers shall be provided for every I/O board used in the AT
Control System. They shall be completely tested to prove the full access to the required
board's functionality and the correct exploitation of its resources. All necessary device
drivers are available from the VLT Common Software, since all boards foreseen are
VME Standard boards, or fully compatible with existing boards (the exception here is the
beacon interface board which is 100% compatible with the Acromag Digital I/0 board).

All interfaces between the ATCS and the Electro Mechanical Hardware are described in
the specific Interface Control Document.

Server side hardware

 Hardware recommended by all the software needed.

 Communication hardware to serve client requests
Client side hardware

 Hardware recommended by respective client’s operating system and web browser.

 Communication hardware to communicate the server.

3.1.4 Software Interfaces

The ATCS has different types of software interfaces (this term is used in a very broad
meaning) to external packages, depending how the interaction is realized:

Programmatic interface: the ATCS will access the functions of the external software
through a library (CCS, Astronomical Catalogue Library, ASM)

SRS Document 1.0 Page 6 of 17 03-07-2019

 Online client management system

Message interface: the ATCS will receive commands from a software client
(Interferometer Supervisor Software - ISS)
Database interface: the ATCS will exchange information retrieving and storing data
from/into a database (VLT Archive System, within the VLT Data Flow System)
The following sections will define the general characteristics of these interfaces, but the
detailed description pertains to specific ICD documents.
Server side software

 Web server software, Apache

 Server side scripting tools: PHP
 Database tools: My SQL
 Compatible operating system: Linux, Windows
 Client side software
 Web browser supporting JavaScript, refer Browser Compatibility 2.3.1
3.1.4.1 Microsoft SQL Server 7
Microsoft SQL server or more commonly known as MS SQL server is a relational
database server developed by Microsoft Corporation. A database server is basically a
database application which is used to store data and other software applications retrieve
and store data using some language which is called SQL (Structured Query Language) in
case of MS SQL server. The client application which accesses data from the database
server can be on the same machine or on different machine and can access the data via a
set of protocols and internet. Microsoft has developed wide variety if MS SQL server
editions keeping in view the type of audience that use database server products. MS SQL
Server editions are available for large enterprises, medium scale organizations to
individuals.
Advantages
 Easy Installation
 Improved Performance
 Security
 Excellent Data Restoration and Recovery Mechanism

3.1.5 Communications Interfaces

The system shall use the HTTP protocol for communication over the internet and for the
intranet communication will be through TCP/IP protocol suite.
 Client on Internet will be using HTTP/HTTPS Protocol.
 Client on intranet will be using TCP/IP protocol.

SRS Document 1.0 Page 7 of 17 03-07-2019

 Online client management system

3.2 Functional Requirements

A functional requirement describes what a software system should do. Based on functional
requirements, an engineer determines the behavior (output) that a device or software is expected
to exhibit in the case of a certain input.

Functional specifications

1. Types of software development specifications

2. See also

3. References

4. External links

3.2.1 <Functional Requirement or Feature #1>

3.2.1.1 Introduction
A functional specification (also, functional spec, functional specifications document
(FSD), functional requirements specification) in systems engineering and software
development is a document that specifies the functions that a system or component must
perform (often part of a requirements specification)
The documentation typically describes what is needed by the system user as well as
requested properties of inputs and outputs (e.g. of the software system). A functional
specification is the more technical response to a matching requirements document, e.g.
the Product Requirement Document "PRD"[citation needed]. Thus it picks up the results
of the requirements analysis stage. On more complex systems multiple levels of
functional specifications will typically nest to each other, e.g. on the system level, on the
module level and on the level of technical details.

3.2.1.2 Inputs

 Enter client detail

 Name
 Password
 Mail
 Date
 Status

The clients enter the detail and then login in the website.

3.2.1.3 Processing
When the user clicks the OK button, the dialog is closed and the focus is returned to the
main window in the state it was in before this dialog was displayed.
Such a requirement describes an interaction between an external agent (the user) and the
software system. When the user provides input to the system by clicking the OK button,
the program responds (or should respond) by closing the dialog window containing the
OK button.
Check weather all the details that input from the clients are correct or not. If data is not
valid then asks to the client please enter valid data. After getting the details of clients,
receive Contact Detail of clients and prompts the massage Contact Created Successfully.
Solve the problems of Clients.

SRS Document 1.0 Page 8 of 17 03-07-2019

 Online client management system

3.2.1.4 Outputs
After getting the details of client, receive Contact Detail of client and prompts the
massage Contact Created Successfully. Manage the Clients and provide better solution to
client.

3.2.1.5 Error Handling

Error handling helps in handling both hardware and software errors gracefully and helps
execution to resume when interrupted. When it comes to error handlingin software, either
the programmer develops the necessary codes to handle errorsor makes use of software
tools to handle the errors.

 Error handling (retrying, organized panic, false alarm)

 Propagation of error information
 Administration and collection of all information which will be important for the
user or developer to analyze and resolve an error
 Administration of error messages which will be shown to the user in case of
errors (error reporting)
 Once an error is detected the client creates an Error object and supplies necessary
context data.
 A client’s method signals a failure to its caller and passes an Error object to him.
 If the client is a control object within the user interface he may use the Error
Handler to display a message for the error which was signaled to him by another
method.

3.2.2 <Functional Requirement or Feature #2>

The system should satisfy the following requirements:

Administrator Aspect
1. Perform weekly roster of Employees
2. Print reports annually, weekly, and daily
3. Check feedbacks
4. Send newsletters
5. Manage user portfolio
6. Changing the super password.

Employee Aspect
1. Logging into the system.
2. To check their rosters.
3. Maintain daily logs
4. Select availability.
5. Check online bookings

Client Aspect:
1. Make a booking
2. Check their booking status
3. Fair calculation
4. Changing password.

SRS Document 1.0 Page 9 of 17 03-07-2019

 Online client management system

5. Resetting of forgotten password.

Analysis
1. Authenticating users based on username and password.
2. Keeping session track of user activity.
3. Recording client’s request for booking.
4. Keeping history of courses bookings.
5. Keeping record of feedbacks received from the clients.

Mailing
1. Temporary password will be mailed to the user incase the user forgets the password.
2. Newsletters should go the clients email addresses.
3. The client should get notification email of the booking while confirmed.

3.3 Use Cases

This section contains use cases of the online client management system.

3.3.1 Use Case #1

Use Case Diagram of Online Clients Management System

System

Perform Weekly Roster

Print Reports

Check feedbacks

Administrator
Send Newsletters

Manage user portfolio

Change password

SRS Document 1.0 Page 10 of 17 03-07-2019

 Online client management system

3.3.2 Use Case #2

System

Make a Booking

Check Booking Status

Fair Calculation

Client
Change Password

Reset Password

Give Feedback

3.4 Classes / Objects

This section contains major classes of the Online Client Management System. The client
should have the basic idea to operate (use) the system and he already has the experience
to work in the internet (browser). Default Language is English.

3.4.1 <Class /Object #1 >

Administrators

3.4.1.1 Attributes
 Name
 Mail
 Contact Number
 Status
3.4.1.2 Functions
<Reference to functional requirements and/or use cases>
Perform weekly roster of Clients: The administrator must be able to select and update
the roster a week ahead based on the availability of each clients who further book their
individual availability a week ahead.

SRS Document 1.0 Page 11 of 17 03-07-2019

 Online client management system

Print reports annually, weekly, and daily: Providing administrator to print the weekly,
annually and monthly reports for his organization based on the time frame selected.
Check feedbacks: The administrator will be able to check the feedback posted by the
clients.
Send newsletters: The administrator shall be able to send the newsletters regarding new
promotions if any.
Manage user portfolio: The administrator will provide access to new users and shall be
able to delete the employees no longer working for the organization.

3.4.2 <Class / Object #2>

Clients

3.4.2.1… Attributes
 Name
 Password
 Mail
 Date
 Status
 Contact Number
 Address
3.4.2.2 Functions
<Reference to functional requirements and/or use cases>
Registration and Login System: Clients will carry out their own registration, providing
the system with a way to associate a user to their request(s). This will enable the system
to display personalized information when the user logs in and certain information, such as
name and address, to be added to each booking request automatically.

3.5 Non-Functional Requirements

 The services or function that our system are describe below such as timing
constrains, constrains on the development process .standards ,etc
 These non –functional requirements define system properties e.g. reliability,
response time and storage requirements constraints I/O device capability, system
representation etc.
 The process requirement all specified mandating particular IDE, programming
language or development
 Non-functional requirement may be difficult functional requirement.

3.5.1 Performance
 The information retrieval should be as fast as possible for customer satisfaction.
To ensure this, the consumer should be able to download a page in 5 seconds with a 1024
Kbps modem. The form submission should not take a long time to be processed,
especially in the OCMS module case, in which form applications play a major role.
 Separation of connection handling and data processing
Separation of connection handling and data processing would definitely improve the
overall system performance as well as cost incurred.

SRS Document 1.0 Page 12 of 17 03-07-2019

 Online client management system

 Software runs on an online platform

Slow data retrieval because of poor programming must be absolutely discarded since the
software runs on an online platform.
 Minimize the data transfer time
The size of data sent to the user can be limited to an upper bound, especially for the
multimedia files, to minimize the data transfer time.
 Size of the secondary storage
The larger the primary memory, the faster the applications would run. Moreover the size
of the secondary storage should be sufficient for data swapping, recovery and backup
procedures

3.5.2 Reliability
Back-end Internal Computers
The system shall provide storage of all databases on redundant computers with automatic
switchover.
The system shall provide for replication of databases to off-site storage locations.
The system shall provide RAID V Disk Stripping on all database storage disks.

3.5.3 Availability
Internet Service Provider
The system shall provide a contractual agreement with an internet service provider for T3
access with 99.9999% availability.
The system shall provide a contractual agreement with an internet service provider who
can provide 99.999% availability through their network facilities onto the internet.

3.5.4 Security
Some of the factors that are identified to protect the software from accidental or
malicious access, use, modification, destruction, or disclosure are described below.
Specific requirements in this area could include the need to:
 Utilize certain cryptographic techniques
 Keep specific log or history data sets
 Assign certain functions to different modules
 Restrict communications between some areas of the program
 Check data integrity for critical variables
 Later version of the software will incorporate encryption techniques in the
user/license authentication process.
 The software will include an error tracking log that will help the user understand
what error occurred when the application crashed along with suggestions on how
to prevent the error from occurring again.
 Communication needs to be restricted when the application is validating the user
or license. (i.e., using https)

3.5.5 Maintainability
Your client management software needs to be based on a repeatable process that is still
flexible enough to handle particular client requirements or situations. It should be neither
chaotic nor robotic. In other words, clients should not think your organization cannot

SRS Document 1.0 Page 13 of 17 03-07-2019

 Online client management system

manage on boarding correctly, but should not feel they are reduced to an account
reference either. On boarding builds on the great work your salespeople did in getting the
client to sign up, to turn that initial commitment into a mutually beneficial relationship.

The user will be able to reset all options and all stored user variables to default settings.

3.5.6 Portability
Compatible with Operating Systems
 Windows
Compatible with Operating Systems
 Any Operating System
Some of the attributes of software that relate to the ease of porting the software to other
host machines and/or operating systems. This may include: Apache is used to develop the
product. So it is easiest to port the software in any environment.

3.6 Inverse Requirements

 Inverse requirements can be functional and non functional

 When a Client specifies that something must not be done. For example, User ID
should only contain digits.

3.7Logical Database Requirements

This area represent particular the logical requirements for any data that is to be stored
into a database. These consist is:
 it shall be secure and password Security
 The data should not be duplicate
 It maintain the record
 It defines the logical structure of database that is stored logically in database

3.8Design Constraints
Specify design constraints that can be imposed by other standards, hardware limitations,
etc.
Some of the design and implementation constraints identified are listed below:

3.8.1 Standards Compliance

 Clients or employees do not have any rights to edit any data in the system.
 Client pays the service fees.
 Online Payment facility may be restricted if the Company not want this facility
for some reasons.
 This system is not support distributed database Facility.
 System is limited to HTTP/HTTPS Protocols.

4. Analysis Models
The following sections will introduce the numerous requirements of the system from the
point of view of different users and will introduce a number of decisions that have been
made regarding implementation. These sections also attempt to somewhat describe the

SRS Document 1.0 Page 14 of 17 03-07-2019

 Online client management system

role of each user group in the system, discussing their individual roles through the
functions they can perform.

4.1 Sequence Diagrams

Login and Client/User Manage

(A).Admin / (C). Cm system Database

(B).Developer
2.validate()
1.login(mail-
id.password) 3.Pass Data

4.Login Messages

Login

5.Enter client detail(user-

Add Name,Password,Date, 6.Validate Data
User/ Status)
Clien
t 7.Enter proper data 6.Data not
valid
8.Data added for client detail

Creat CL:Create Leader

e
10.execute query for insert lead
9.Lead(User-id,Date)
data

11.data
Destroy
served
Creat
SM:send mail
e
12.mail(email-id,password)

13.mail successfully
14.Client added
Destroy
successfully

15.Redirect to Client profile(User-

16.Enter Contact Detail id)
17.Execute query for enter Contact Data
19.Contact Created 18.Data enterd successfully
Successfully(redirect to
dashboard)

SRS Document 1.0 Page 15 of 17 03-07-2019

 Online client management system

4.2 Data Flow Diagrams (DFD)

DFD of Online Client Management System

Client Management General Client

Report

Client Feedback General Client

Management Feedback Roport

Online Client
Product Management General Product
Management Report
System

Transaction Check Transactions

Management Details

Offering Generate Offering

Management Report

SRS Document 1.0 Page 16 of 17 03-07-2019

 Online client management system

4.3 State-Transition Diagrams (STD)

State Transition Diagram For Online Client Management System

Sales Client
Opportunity Orders
New Client Active/
Current
Client

Invoice Invoice
Additional paid left
services Unpaid/
written
off

Inactive/Former
Client

5. Supporting Information

Appendix A – Background Research on:

Appendix B – Data Dictionary

SRS Document 1.0 Page 17 of 17 03-07-2019