Lifeguard System
Implementation Project

PVCS Tracker Documentation

Initial Revision 	2/1/2000
2nd Revision		3/13/2000

Table of Contents

Introduction	4
Why is LSIP Using PVCS Tracker?	5
What is the Tracker Process Flow? (As used by LSIP)	6
Testing Team Flow	7
Access to Tracker	10
Logon Information	10
Changing Password	10
Logging Out of Tracker	10
Main Screen at Login	11
Submitting SCRs	12
Viewing SCRs - In Tray, Queries, and Reports	14
In Tray	15
What Does it Do and How Does it Work?	15
Removing an SCR From Your In Tray	16
Queries	17
Running Queries	17
Query Tip	18
Selecting Specific SCRs	19
Placing (or Replacing) a Record in An In Tray	19
Pre-Defined Queries	20
Running Pre-Defined Queries	21
SCR Pre-Defined Queries:	21
Other Query Menu Options	22
Reports	24
QuickView Reports (Summary)	24
Other Reports Available in Tracker	24
Notify Options (Business Analysts/Testers)	25
Notify Options (Managers and Above)	26
Setup of Options	26
In Tray and Notification	27
Closing SCRs	28
Closing an SCR	28
Reopening an SCR	28
For Assistance	29
Glossary of Tracker Terms	30
Appendix A – Projected Workflow – Testing Group	31
Appendix B – PVCS Tracker Screen Fields	32
Appendix C – Standardization of Field Inputs	37

Introduction

The purpose of this document is to provide instruction on how the Lifeguard System Implementation Project (LSIP) team will use Merant’s PVCS Tracker tool for managing the testing process. 

This document describes the PVCS Tracker, and how its use can make testing follow-up more consistent. Screenprints, customized for LSIP, are presented throughout this document. Testing Team process flow appears for both Business and Technical Testing.

Please see the section “For Assistance,” if you have any questions on this document or on the use of Tracker.

Why is LSIP Using PVCS Tracker?

LSIP previously tracked all their issues with “home-grown” tools, like Excel, Word, or Access files. This created issue management that was labor-intensive and had a potential for errors. In 1999, Lifeguard purchased the Merant Corporation  PVCS Tracker tool to more efficiently manage issues logging on many technical projects. 

Tracker will be used initially to track the resolution of software errors and issues uncovered during various testing phases. These errors and issues will include those reported back to Erisco (“Stars” – official Facets bugs), those reported back to Cognizant (programming errors), and those reported back to the Configuration Team (User setup issues) for resolution. 

Management of the testing process (defect reporting, resolution, and re-testing) is simplified through the use of Tracker. When combined with source code control under PVCS Version Manager, Lifeguard can connect all changes to code to a particular Service Change Request (SCR) within Tracker. This provides an even stronger control of any changes within the LSIP implementation.

What is the Tracker Process Flow? (As used by LSIP)

The process flow that has been adopted by the LSIP team effectively manages the testing process. The LSIP testing group is divided into the Technical and Business Testing Teams. The Technical Testing Team is responsible for testing the Conversion Data, Interfaces, Reports, and Letters. The Business Testing Team is responsible for testing the business functionality of the Facets program. Unit Testing and System Testing proceed separately (Business and Technical Teams) until Integrated Testing. At that point, these two Teams merge to handle testing. 

See Appendix A - “Projected Work Flow Testing Group” for communication within the testing team organization. Specific workflow within Business and Technical Test Teams immediately follows this section.

Testing Team Flow

Business Testing
1.	Business Test Coordinator (Colleen Faccini) develops Test Scripts and delivers them to the Business Test Lead (Suzie Branda). 
2.	The Business Test Lead distributes scenarios to the testers.
3.	Business Test Lead schedules testing with the Business Testers.
4.	The Business Test Lead logs errors/issues identified by the testers during the testing process into Tracker. (SCR is generated in Tracker.)
5.	Business Tester works the error, fixes it in fc_systest and informs Configuration Management point of contact (Arlene Bell/Brian Sims). Configuration Management is notified of fix, in order to keep other Facets Environments in sync.
6.	Business Test Lead compiles the Tracker issues and notifies the Business Test Lead.
7.	Business Test Lead communicates the errors/issues to the Configuration Management point of contact.
8.	Configuration Management notifies the configuration team of errors. 
9.	Once the errors are fixed and the testing is successful, the Business Test Lead closes the SCRs. Otherwise, see #8 above.

Technical Testing

1.	Test scenarios are developed by the Business Analysts (BA’s)
2.	Product Managers schedule testing with the Technical Test Lead (Mick Taylor).
3.	Lead BA’s lead the testing effort with other BA’s.
4.	The BA’s log errors/issues identified during the testing process into Tracker. (SCR is generated in Tracker.)
5.	The Product Managers notify Cognizant Lead (Murali Ramnath) or Oleen (Chorng Biann and Mike Wood) or the Technical Lead from the Config Team (Brian Sims) regarding any technical issues that need to be fixed. Hardware Issues are referred to the LSIP Team IT Manager (Bridget Teodoro).
6.	Issue is resolved. Once the issues are fixed, the “fixer” notifies the appropriate Product Manager that re-testing may occur.
7.	Re-testing of the updated code proceeds. If the Testing is successful, the Product Managers close the Tracker SCRs. Otherwise, see #5 above.

Visual flows for Business and Technical Testing immediately follow.

Access to Tracker

Logon Information

The following screens represent initial access to Tracker from an NT workstation where Tracker is loaded.

PVCS Tracker is initiated from Start/Programs on the PC Start Menu.

Enter your ID (your standard Lifeguard Login ID) and your password. First time users enter “welcome” as the password. (Do not input quote marks.) The Project should default to LSIP. If not, use the drop-down list to select the LSIP Project. After pressing the OK button, the next screen displays the current activities that the User is involved in. From this screen, a new SCR may be entered or older SCRs may be worked on.

Changing Password

To Edit your Password, Select Tools and then Set User Information. Enter your Password on the second line, and re-enter it on the third line and press OK. 

Logging Out of Tracker

At the end of your session, always logout of Tracker completely. To Logout, choose Exit from the File menu.