Pri Sample

Sheet1

Project Requirement information

SNA process document available in Tarang

Reference Document History

Version #

Author 1 Rajesh.B.S

Date DD-MMM-YY

Reviewer

07/19/06

Introduction

The objective of this document is to plan and specify the project requirements to 1. Specify the process to manage changes and references, 2. Measure the SLA’s The scope of this document is to describe the process to be followed for Project The target audience for the document is project sponsor (<project name> users/m

Project Details

Let us know about the project based on which we would be able to prepare to fu

Project Group id

Group email address consist your team members. All Tarang employees will be able to send email to this group by default, If need

Clients (Desktop configuration)

What is are users desktop software (OS,IDE,Database,Configuration client) and

Servers

What are servers software (OS,IDE,Database,Configuration client )and hardwar

Network

Do you need Backup Project Folder / Separate Network / Publishing / VOIP / W

Procurement

Here, Fill the details of the hardware and software requirement. A note before you fill up the requirement : 1. Does client will cover the procurement of requirements? 2. OR Does requir Tarang Procurement Process will take you 1 Week or 3 Weeks and above for pr and vendor's delivery schedules.. This procurement budget should be included in the project cost.

Rentals

Any Hardware or Software requirement Tarang Rental Process would hire equipment within 48hrs depending on volume This procurement budget should be included in the project cost.

Repository

Here,Fill the repository type like CVS or VSS and provide the repository directo 1. You will need repository access tools like VSS Client for VSS Repository and 2. If any change required other than default directory structure for repository Default Directory: Refer the Note

Bug Tracking System

Here,Fill the Project component (basically modules in your project) with initial Note that the component and version are must to raise bugs in your project. Can Edit and Can Confirm are default privileges for all users.

Page 1

Sheet1

Backup and Restoration Feedback Project Closure Communication (Sheet 3)

Specify any backup project folders / Client Software/ Client Database to be back be restored. Your valuable feedback on this(PRI) document. All of the above will be disabled and taken back to SNA department.

Provide details of SNA Commitments. (SLA for PRI fullfillment, Role and Resp

For Reviewer only.

Reviewer Sunitha

Please fill in your remarks here.

The sheet 3 Details are specified in the SNA Process Document. Do you

Page 2

Sheet1

ment information

nt available in Tarang-QMS Approver

Changes made Initial Version

ecify the project requirements to SNA. eferences, 2. Measure the SLA’s ocess to be followed for Project requirements. sponsor (<project name> users/managers) and SNA Team only.

Directory Structure on CVS Repository /cvs/workspace – Directory provided by sysadmin for your project. Pattern of repository Directory structure of your project files.

we would be able to prepare to fulfill the project requirement

s. l to this group by default, If need to restriction, specify who needs this access?

tabase,Configuration client) and hardware requirement

Parent_tree (Parent Tree - would be your parent module) |_ _ _ _ General |_ _ _ _ Project_Data |_ _ _ _ Feasibility_Study |_ _ _ _ Transitory_Information |_ _ _ _ Standards_Methods_Tools |_ _ _ _ Requirement Specification |_ _ _ _ Design |_ _ _ _ Source_Code |_ _ _ _ Testing |_ _ _ _ Release |_ _ _ _ Support_Documents |_ _ _ _ Configuration |_ _ _ _ Minutes_of_Meetings If you have a phase one two etc....

onfiguration client )and hardware requirement.

Network / Publishing / VOIP / Web Site or Chat Access / Bandwidth requirement?

re requirement.

uirements? 2. OR Does requires Tarang procurement? eek or 3 Weeks and above for procurement based on the equipment

the project cost.

thin 48hrs depending on volume. the project cost.

nd provide the repository directory name. S Client for VSS Repository and TCL/WinCVS for CVS Repository ctory structure for repository

ules in your project) with initial owner and initial qc for each component. o raise bugs in your project. s for all users.

Page 3

Under Parent_Tree |_ _ _ _ _ _ _ __ _ _ Phase I | |_ _ _ _ General | |_ _ _ _ Project_Data | ........ |_ _ _ _ _ _ _ __ _ _ Phase II | |_ _ _ _ General | |_ _ _ _ Project_Data | ........... |_ _ _ _ _ _ _ __ _ _ Phase III | |_ _ _ _ General | |_ _ _ _ Project_Data

Sheet1

ware/ Client Database to be backup and Any old / previous repo or information avaliable to

to SNA department.

r PRI fullfillment, Role and Responsibilities of both SNA?/DEV?)

A Process Document. Do you need this in this Sheet.

Page 4

Sheet1

VS Repository Directory provided by sysadmin for your project. ory Directory structure of your project files.

ee (Parent Tree - would be your parent module) _ _ _ _ General _ _ _ _ Project_Data _ _ _ _ Feasibility_Study _ _ _ _ Transitory_Information _ _ _ _ Standards_Methods_Tools _ _ _ _ Requirement Specification _ _ _ _ Design _ _ _ _ Source_Code _ _ _ _ Testing _ _ _ _ Release _ _ _ _ Support_Documents _ _ _ _ Configuration _ _ _ _ Minutes_of_Meetings

wo etc....

ee _ _ _ _ _ _ _ __ _ _ Phase I |_ _ _ _ General |_ _ _ _ Project_Data ........ _ _ _ _ _ _ _ __ _ _ Phase II |_ _ _ _ General |_ _ _ _ Project_Data ........... _ _ _ _ _ _ _ __ _ _ Phase III |_ _ _ _ General |_ _ _ _ Project_Data

Page 5

Sheet1

Page 6

Sheet2

Project Requirement Information Project Details

Project Name Project Code Description Duration

From

To

Project Manager Project Lead Project Team and Testing Team

Project Group id

Group Members Group E-Mail ID

Desktops (Desktop configuration)

Hardware Configuration (RAM, Processor)

Servers

Database Server (Shared or Dedicated)

0

OS Requirement Application and Tools Database Client requirement VPN Client

Page 7

Sheet2 (Server Configuration) Application Server (Shared or Dedicated)

Network

Procurement

VPN client details Separate Network Publishing server Any Remote connectivity (CVS, VSS, FTP,Servers,Bugzilla,) Bandwidth Requirement (VOIP/FTP Upload/Download, Client Demo WebSites) Instant Messenger Skype,Yahoo Voice Customer website Direct Access Owner of the software (Tarang / Client) Name of the client Registration for Client / Tarang Product & No of license

Rentals

If Any

Repository

Repository Type (VSS or CVS) Repository Name Account User Name/Password Access

0

Page 8

Sheet2

Bug Tracking System Tarang Bugzilla URL:

http://bugdev.tarangtech.net/

Project Name: Purpose Components -

0

Component Name Description Initial Owner Initial QA Contact Version New Account creation User Access

Backup and Restoration

Any backup project Folders / Client Software/ Client Database Any previous repository restoration

Feedback

Scope for improvement in this document Points for appreciate in this document

Page 9

Sheet2

t Requirement Information

Page 10

Sheet2

Page 11

Sheet2

Page 12

Sheet3

Project Closure Users are rquest to return all the software and hardware and any related access provided to project group to SNA. Software License, if purchased for the project. SNA will update into Tarang Software assets

Service Level Agreement Project Group id Desktops Servers Network Procurement Rentals Repository Bug Tracking System

Role and Responsibilities SNA Department Users of PRI Form

To keep track of the capture information To capture every changes or addition in the Project information

Page 13

Sheet3

Page 14