Record of Revisions
Date Of Reasons
Prepared / Reviewed By Approved By
Version Release / For
Revised By
Revision Name Date Name Date Revisions
Konda Draft submitted
Draft P Ravi
reddy for approval
Revised
based o the
Konda
1.0 P Ravi request to
reddy
add new
reports
Table of Contents
1.INTRODUCTION ...................................................................................................... 3
2.SCOPE ................................................................................................................... 3
3.DEFINITIONS, ACRONYMS AND ABBREVIATIONS ........................................................ 3
3.1 DEFINATIONS
3.2 ACRONYMS .......................................................................................................... 4
3.3 ABBREVIATIONS ................................................................................................... 4
4. FEATURES.............................................................................................................. 4
5. ROLES AND RESPONSIBILITIES ................................................................................ 4
6. ASSUMPTION AND DESIGN CONSTRAINTS ................................................................ 4
7. TECHNICAL REQUIREMENTS .................................................................................... 5
7.1 FUNCTIONAL REQUIREMENTS ................................................................................ 5
8. SPECIFIC OTHER SERVICES WITH BANGALORE ONE: .................................................. 5
9. SYSTEM OVERVIEW ................................................................................................ 6
9.1 TECHNICAL REVIEW .............................................................................................. 6
10. SOFTWARE AND HARDWARE REQUIREMENTS ........................................................... 6
10.1 SOFTWARE REQUIREMENTS ................................................................................. 6
10.2HARDWARE REQUIREMENTS ................................................................................. 6
11. INTERFACE REQUIREMENTS ................................................................................... 6
12. NON – TECHNICAL REQUIREMENTS ......................................................................... 7
12.1 PROJECT DELIVARABLE TO THE CUSTOMER ........................................................... 7
1. Introduction
The Tata Trust Project Plan will provide a definition of the project, including the
project’s goals and objectives. Additionally, the Plan will provide information about
Project deliverables, schedules, risks, dependencies, assumptions, estimates, project
team, and change management.
This plan may be reviewed and / or revised at the end of each of the following stages
of development (see the Project Schedule section for current Schedule/milestone
dates):
All changes will be recorded in the Preface section of this document under ‘Document
Control’.
2. Scope
This section provides definitions of all terms, acronyms and abbreviations required to
properly interpret the design document.
3.1 Definitions
Term Definition
NIL
3.2 Acronyms
Acronym Meaning
3.3 Abbreviations
Abbreviation Expansion
SRS Software Requirements Specification
UR User Requirement
UI User Interface
4. FEATURES
The following constraints need to be taken into account while designing the Support
Center System:
The application should be viewable at 1024*768 pixels resolution
The application should be compatible with Internet Explorer 7.0 or higher
7. Technical Requirements
Requirements Overview
Tata Trust application provides a one stop interface with government, citizen
interactions with government departments will be under a single umbrella. The
services provided by this application is Govt Services for citizen, Govt Services for
business, Business to citizen, Payment services, information and other services
Design of the Infrastructure which shall be capable to support future needs,
including but not limited to, Web Content Management, planned capacity needs,
object replication, group and personal folder usage, and link/connection to popular
Tata Trust system as well as other open industry standard system (XML, Web
Service, J2EE, .NET Framework).
9. System Overview
11.INTERFACE REQUIREMENTS
a. User Interfaces
The interface of the application will be part of the user requirements and
will be addressed appropriately.
There are no external hardware devices that the application interacts with.
c. Software Interfaces
The application will be developed using ASP and HTML as front end with all user-
friendly screens. The Application would be deployed into the Documentum
Content Server 6.5 SP2. Data will be stored in Oracle 10.2 database. The system
should run on: Windows 2008 Server (SP2)
UI guidelines