miracle proles hcst srs

8/4/2019 Miracle Proles Hcst Srs

1/14

HELP CENTER STATUS

TOOL

Priyatam Aitha (10101D0043)

Santosh Kumar Miryala (10101D0059)

TEAM

Miracle Proles


2/14

HELP CENTER STATUS TOOL

Software Requirements SpecificationVersion 1.4

Prepared By: Team Miracle Proles

TEAM MEMBERS ROLL NO. EMAIL IDPRIYATAM 10101D0043 [email protected]

SANTOSH 10101D0059 [email protected]

Inspected by:

Approved by:

Date:

Version History:

VERSION NO. DATE CHANGED BY CHANGES

MADE1.1 2/08/2011 Santosh ,Priyatam Draft

1.2 3/08/2011 Santosh, Priyatam Requirements

Gathering

1.3 11/08/2011 Santosh, Priyatam Class Diagram

1.4 12/08/2011 Santosh, Priyatam State Chart Diagram


3/14

Contents

1. Introduction ......................................................................................................................................... 4

1.1 Purpose: ......................................................................................................................................... 4

1.2 Scope ............................................................................................................................................. 4

1.3Overview ........................................................................................................................................ 4

2. Overall description............................................................................................................................... 5

2.1 Product perspective ........................................................................................................................ 5

2.1.2 User interfaces: ........................................................................................................................... 5

2.1.3 Hardware interfaces................................................................................................................. 6

2.1.4 Software interfaces .................................................................................................................. 6

2.1.5 Communications interfaces...................................................................................................... 6

3. Functional Requirements: .................................................................................................................... 6

3.1Object Analysis:.............................................................................................................................. 6

3.2 Class Diagram:............................................................................................................................. 10

3.3 Performance requirements:........................................................................................................... 10

4. Feature Analysis ................................................................................................................................ 10

4.1 Roles: ........................................................................................................................................... 11

4.1.1 User...................................................................................................................................... 11

4.1.2 Admin: .................................................................................................................................. 12

4.1.2 Support staff:......................................................................................................................... 13

5. Nonfunctional Requirements.............................................................................................................. 13


4/14

1. Introduction

1.1 Purpose:

This Software Requirements Specification Document captures the complete software requirements for the

Help Center Status Tool (HCST) .It describes the design concepts, architectural designs which are needed

to implement the software logic. It serves to the software developers with detailed information in the

process. The Help Center Status Tool (HCST) helps to the users by providing the status of the problems

which they are raised. It needs techniques and procedures to develop the software called software

process.

The intended audiences for this SRS are the people related to software industry, people who wish

to develop this product or to add further enhancements, and professionals who wish to improve

their predictability and who wants technical growth.

1.2 Scope

HCST is a web application that used mainly for normal users to check their problem status. It is

a web-application that interacts with admin and database to provide a certain, very specific,

function "on demand" like status of the problem. The system is envisioned to be a tool that helps

to user in knowing about his alternatives. HCST is specifically designed to capture the work

which is assigned to respective person and know the status of the work. The tool will store all the

details like service person name, problem description with Id, so as to accurately determine

where the problem is and who is working on that one?

1.3Overview

This document provides a description of the requirements of the product. It also provides the

Software Requirement Specification with detailed descriptions of the product including the data

requirements and specific functional requirements of the different components of the product and

its performance criteria.


5/14

2.Overall description

2.1 Product perspective

Sometimes users want to know the status that they are posted request because he is in trouble, so in

order to resolve his problem and he might want to know the status. HCST tool can ease this task

because every time the work is progress admin updates the status.

Figure 1: Problem Frame Diagram

2.1.2 User interfaces:

The user interface is divided into three screens:

y User Page.

y Admin Page.

y

Service persons page.

User Page:

y This screen is used to post the problem from the users side. This is accomplished by filling

the form fields like

o Enter the user-Id.

o Enter the problem Description.

User Interface

HCSTSystem

HCSTTool (UI)

HCSTTool (admin


6/14

o Recent problem Description.

o Contact Details.

o Submit the form

Admin page:

Admin priorities the problem and allows the user to check the status based on Problem Id which admin

is generated. Admin can change the status based on solution given by service person and he also assign

the work to different staff. Besides being able to change a selected problem, admin is to update the

status or he deletes a specific problem which is outdated.

Service persons page:

Service staff can realize the problem when he view the request posted by admin and based on

problem description he made a perfect solution.

2.1.3 Hardware interfaces

The system assumes a color display with at least 800x600 pixels and some method for

supporting persistent storage and related data structures. All components must be able to execute

on a personal computer.

2.1.4 Software interfaces

The system will employ standard Java 2 APIs (SDK v1.5 as a minimum), Apache Tomcat and

later version, Windows Operating system/Linux/Mac OS

2.1.5 Communications interfaces

No external communication interfaces are required.

3. Functional Requirements:

3.1Object Analysis:

In this analysis we identify three types of classes they are named as boundary, entity, and

control. A boundary class is used to model the interaction between the system and its actors. In

Help center Status tool, the user interface classes are the boundary classes. An entity class is used


7/14

to model constant data. In Help Center Status Tool the user, admin and support person are the

entity classes. A control class is used to represent control of entity objects and they usually

contain the business logic of the system. In Help Center Status Tool, there is a control class for

each and every entity classes.

S.No. Class Name / Kind Responsibility Persistent

1 HCST Boundary Object A boundary object that is

used to direct HCST to the

different pages

NO

2 Registration Screen

Boundary Object

A boundary object that is

used to provide account

No

3 Login Screen

Boundary Object

A boundary object that is

used to validate or

authenticate the users,

admin and service person.

No

4 Lodge Complaint screen

Boundary Object

A boundary object used to

Lodge the complaint.

No

5 View Status screenBoundary object

A boundary object thatallows the user to view the

complaint status.

No

6 Profile screen

Boundary object

A boundary object that

allows the user to change

the profile details

No

7 Forgot password screen

Boundary object


allows the user to know the

password

No

8 Manage screen

Boundary object


allows the admin to manage

the actions

NO

9 JDBC Connector A control object that Yes


8/14

Controller Object manages the interactions

between the user interface,

the business model, and

Persistence mechanism.

10 Registration servlets

Controller Object

A control object that

manages the interactions



Persistence mechanism to

store the details of users

Yes

11 Log-in Action

Controller Object





Persistence mechanism to

authenticate the users

Yes

12 Request handler

Controller Object



Between the user interface,

the business model to

handle the request posed by

users.

Yes

13 Status Controller

Controller Object




the business model to view

the status of the problems.

Yes

14 Profile Handler A control object that Yes


9/14

Controller Object manages the interactions



update information of the

users.

15 Manage

Control Object





update information and

manage the users

Yes

16 Complaint

Entity Object

An entity object that

contains information about

problem description and

contact information.

Yes

17 Status

Entity Object

An entity object that

contains information about

problem status informationsuch as in which stage the

problem is?

Yes

18 Persistence Data EntityObject

An entity object whichcontains the persistent data

storage object

Yes

Table 2: Object Definitions


10/14


11/14

4.1 Roles:

1. User.

2. Admin.

3. Support Staff.

4.1.1 User

User consists of two states in terms of the requests that may be performed and the data is

displayed on the screen. This is the initial start up role for user when logs-in when enter with

user Id.

System Feature ID:

User

System Feature Name:

User Operations

Associated Use Cases UC-HCST- UR: User

Description: The User employs this feature to register and

pose the request and view the requests

State, Activity,

Collaboration, and

Class Diagrams:

State Diagrams

: Members States

State Diagrams: User-SD

Operations: Pose request and view Request


12/14

4.1.2 Admin:

Admin is having more privileges than user and support staff. He has privilege that he can manage the

users and staff; he assigns the work to staff and prioritize the different problems based on user problem

description.

System Feature ID:

Admin


Admin Operations

Associated Use Cases UC-HCST- AR: Admin

Description: The admin employs this feature to manage the

members, add members to the database,

remove members from the database and assign

work and to change the status

State, Activity,

Collaboration, and

Class Diagrams:

State Diagrams

: Members States

State Diagrams: Admin-SD

Operations: Managing Users and managing actions


13/14

4.1.2 Support staff:

Support person having less privileges than admin and he came to picture when the admin assigns

work to him and his main action is to resolve the issue and updates the status.

System Feature ID:

Support Staff


Support Staff Operations

Associated Use Cases UC-HCST- SS: Support Staff

Description: The Support Staff works on problems given by

admin and he finds the solution, send it to user.

State, Activity,

Collaboration, and

Class Diagrams:

State Diagrams

: Members States

State Diagrams: Support Staff -SD

Operations: Finding the solution and update the status

5.Nonfunctional Requirements

Requirements Category Sub- category

The tool is to be developed to

have effective User Interface.

Interface Interface

The tool is to be a completely Supportability Configuration


14/14

platform independent

The tool is to be created as anexecutable

Reliability Predictability

The tool should adhere to best performance in terms of

transaction

Performance Throughput, Response time

miracle proles hcst srs

Documents