Академический Документы
Профессиональный Документы
Культура Документы
FEBRUARY,2011
Warning This is a hard copy of a document maintained on electronic media. It may not be the latest version. Kindly ascertain the latest version from the Document Master List available with the Project Leader.
This document and any revised pages are subject to document control. Please keep them upto-date using the release notices from the distributor of the document. Approved by: Authorised by: Date: Date:
PREFACE
Purpose of this Document
This document describes the System Requirements Specifications of the Problem Tracking Tool. This document lays down the software requirements for the application that have been captured through a detailed study of the business workflow and functions.
Intended Audience
This document is intended for use by the designers of the system, and for those who may be required to maintain it. The document will enable them to understand all aspects of the system in detail. It will enable HP to know that TCS has captured all the requirements. The document will also be used by HP for carrying out the acceptance testing for which it will form the.
ii
TABLE OF CONTENTS
1. INTRODUCTION..................................................................................................................4 1.1 BACKGROUND.......................................................................................................................4 1.2 SCOPE...............................................................................................................................4 3.1 OUT OF SCOPE....................................................................................................................4 3.2 BUSINESS JUSTIFICATION FOR INVESTMENT..................................................................................5 3.3 PRODUCT PERSPECTIVE..........................................................................................................5 3.4 KEY ASSUMPTIONS, DEPENDENCIES, CONSTRAINTS AND OVERRIDING PRIORITIES.................................5 3.5 USER CLASSES AND CHARACTERISTICS......................................................................................5 3.6 HARDWARE AND SOFTWARE PLATFORM......................................................................................6 3.7 SITE ADAPTATION.................................................................................................................6 3.8 APPLICATION SECURITY..........................................................................................................6 3.9 MIGRATION REQUIREMENTS....................................................................................................6 4. FUNCTIONAL REQUIREMENTS.........................................................................................7 5. USER INTERFACE SPECIFICATIONS................................................................................9 5.1 GUI SCREEN LAYOUTS........................................................................................................10 5.1.1 Navigation Chart.....................................................................................................10 5.1.2 Screen Layout : <Screen Title>.............................................................................10 5.1.3 Screen Description.................................................................................................10 5.2 GUI REPORT LAYOUTS........................................................................................................10 5.2.1 Report Layout.........................................................................................................10 5.2.2 Report Description..................................................................................................10 6. EXTERNAL INTERFACE SPECIFICATIONS....................................................................11 6.1 SYSTEM INTERFACES............................................................................................................11 6.2 INTERFACE DESCRIPTIONS.....................................................................................................11 6.2.1 Message/Interface Specifications...........................................................................11 7. OTHER REQUIREMENTS..................................................................................................13 7.1 GENERIC REQUIREMENTS......................................................................................................13 7.2 USER ACCESS CONTROL AND SECURITY..................................................................................13 7.3 ARCHIVING AND HOUSEKEEPING..............................................................................................13 7.4 PERFORMANCE REQUIREMENTS..............................................................................................14 Total Number of pages: 16
iii
1. Introduction
1.1 Background
This document outlines the software requirement specification for the Problem Tracking tool. It is the outcome of the Analysis Phase during which discussions were held with the users. The objective of this Analysis Phase was to: Define the scope for the Problem Tracking Tool. Serve as the baseline for the design of the <specify name of the system>.
Any changes to requirements after acceptance of this document will be through appropriate change Management procedure, as detailed in the contract. Both the user and designer should go through the document carefully in order to ensure that: All the user requirements which need to be supported by the system have been identified and detailed. The document is a clear and unambiguous statement of functionality required from the system for the design and development team. The document can be used as a basis for development of the System Test data. It is essential to identify the problems, if any, with the basic structure of the proposed system at this stage. If these are not taken care of at this stage, it may be difficult to incorporate the desired modifications to overcome the shortcomings at a later stage.
1.2 Scope
1. The system to be developed is a stand-alone one. It is not meant to be integrated with any other existing system operating at the clients site. The proposed system shall provide access to Customers, Support, Manager, Administrator and Developers. Responsibilities for each action are access based where actions here refer to create, modify, search and delete of case/CR/solution.
2.
3.
The following entities will be a part of the Problem Tracking Tool: Requesters are used to interact with the customer and send requests for creation, deletion, modification and searching. Servers are used for creation, deletion, modification and searching of details pertaining to problems in the database. An authentication module will be implemented to validate users and entities like Case_Id etc. A problem is reported by the customer to the support people who interacts with the system to log a new case. Analysis of a case by a developer or support is treated as a Solution. The design, code and test information for a fix provided by a developer is treated as a Change Request (CR).
The system will not provide report generation facilities. Functionality of wild card is not present.
Internal Use Only 4
Dependencies The availability of "pathway environment" to facilitate proper "requester-server" interaction. Constraints The system is not portable on non-Tandem systems.
Customers - Has complete access to view cases and solutions of the problems and however he cannot view CR. Support People- Can log and edit Cases ,solutions and view cases, CR, solutions and search fixes. Developers- Can create, edit, and delete solutions and CRs of which he is the owner. Manager - Can search for a record, update status of problem and create an entity linked to a developer. Can also edit all other information and assign solutions to developers. Developers can only assign CRs to themselves. Administrator- Can View, Create, Modify, Delete Cases, CRs, Solutions provided it does not violating referential Integrity. This is taken care by the application through an error message.
Software Requirement
TNS/E RVU Version: H06.22.180 Testware: TACL/ Macros Debugger: Visual Inspect C programming on requester side. TAL programming on server side. SQL Database
Functions
The output screen supported by System is capable of displaying only 24 rows at a time, each row having a maximum of 80 characters .
4.Functional Requirements
Login Module:
Shall authenticate each user of the system and accordingly provide him associated functionality. The fields of Login will be o UserId. o Password.
iii.
Delete Module:
Delete permissions on specific entities are given to those people who have the right to create those entities. e.g. Administrator can delete Case, Solution and CR. Manager can delete Case and Solution. Developer can delete CR and Solution. Support can delete Case.
Shall allow Administrator, Managers and Developers to modify all fields(except IDs and date) of Case Solution CR Example: developer and manager can modify description of case. Support people can modify Case.
Modify Module:
Search Module:
Allows each user to search information pertaining to Problems on the basis of Case Id Solution Id CR Id (except Customer). The search will have two options:1. Search all the related entities for a given Case_Id, Solution_Id and CR_Id. 2. Search for a specific Case_Id, Solution_Id and CR_Id.
10
11
12
7.Other Requirements
<Give a brief description of the section>
13
14