Clearly
spelt out goals, such as passing the product to users, to ISD or to the
research faculty.
Identifying the features provided in the product being transitioned, consistent
with the Release documents
Addressing the developer team role post transition
1.2 Transition Process Strategy
As per
guidelines, need to consider the short time available for transitioning.
2. Preparing for Transition (6)
2.1 Hardware Preparation
Consistent
with SSRD, LCP and reasonable additional needs. Exact identification of
the necessary hardware and who and how it has to be prepared
2.2 Software Preparation
Consistent
with SSRD, LCP and FRD in identifying any COTS preparation needs. Identifying
all the external components to be transitioned and the licensing/procurement
issues
2.3 Site Preparation
Facilities
required should be identified
2.4 Staff Preparation
Training
Deliverables
Identification of the training materials, data and personnel
Training Schedule
Preparing a top level plan for training
Measure of success
Specify who will measure and how
2.5 Operational Test and Evaluation
Evaluation
Criteria
Should reflect the SSRD System and Level of Service Requirements
Procedures
Consistent with the OCD Identify the top level scenarios to be tested.
Evaluation Report
Template like document for reporting evaluation
3. Stakeholder Roles and Responsibilities (2)
Consistent
with LCP and FRD.
Should require reasonable participation from non-team members.
Consistent with and assigning a role for each task of Section 2 in this
document to appropriate stakeholder
4. Milestone Plan (1)
Detailed
milestones and tasks for transition phase.
Consistent with Section 1 of this document
5. Required Resources (1)
Consistent
with Section 2.1, 2.2, 2.3 and 2.4 as well as 3.
Identify budgets as well as estimated cost of customer man-hours spent.
User Manual (30)
1. Introduction (3)
System Overview
Synopsis
of the system, identify audience of manual
Consistent with Release notes
System Requirements
Clear
description of hardware, software and facilities needed to run the system.
Consistent with Section 2 of TRR
2. Operational Procedures (15)
Consistent
with OCD
Present each use scenario with screenshots, examples and step wise instructions
for using the system
Identify the individual features and describe their use consistent with
SSRD.
Correct spellings and grammar usage
Politically correct in terms of use of gender.
An intuitive flow of system use information in terms of features such as
startup, initial operations, advanced operations, and shut down
3. Installation Procedures (5)
Initialization
Preparing
to install
Steps to be performed
Problems to avoid
Re-installation
Identify
recovery and upgrade steps
De-installation
Saving
information before removal.
Consequences of de-installation
4. Troubleshooting (5)
FAQ
Q and
A format
Cover a large variety of possible questions, especially when something
goes wrong
Consistent with Off-nominal requirements from SSRD
Error messages
Descriptiong
of error codes and messages
Likely problem synopsis
Suggested action
5. Notes (1)
Describe
terms used, contact information and availability and distribution policy.