Anda di halaman 1dari 5

SOFTWARE DEMONSTRATION SCRIPTS

Purpose: To develop scripts to be used in the software demonstration from an RFP. These scripts would
be prepared during the Business Requirements phase of the project and can be modified by the
evaluation team during the evaluation process.
Project Name

<< Project Name >>

Project Number

<< DTC Number>>

Client:
Author:

<< Person who created the document >>

Version:

<< First version should be 1.0 and increment up >>

Status

<< Enter status of document. i.e., Draft, Pending Sign-off, Final, et cetera >>

Date:

<< YYYY-MM-DD >>

REVISION HISTORY
Version

Date

Summary of Changes

Name

<<YYYY-MM-DD>>

IMPORTANT NOTES FOR COMPLETING THIS DOCUMENT


Each section of the Transition Agreement must be completed in full. If a particular section is not
applicable to this project, then you must write Not Applicable and provide a reason.
Important Note: No sections are to be deleted from this document.
Save the file using the following naming convention Project # - Project Name Software
Demonstration Scripts.doc
Text contained within << >> provides information on how to complete that section and can be deleted
once the section has been completed.
This template is owned and maintained by the Project Management Office (PMO) of the Office of
the Chief Information Officer (OCIO). Direct questions about this template to OCIOPMO@gov.nl.ca

PAGE 1 OF 5

SOFTWARE DEMONSTRATION SCRIPTS


<< This section is the lead in to the demonstration scripts. Include the text in your document exactly as it is
below. Provide any additional information specific to the set of demonstration scripts in this section. For
example, if there are scripts with integration points, describe for the vendor how these points should be
addressed. >>
The following sections contain the detailed demonstration scripts that software proponents are expected to
use as the basis for structuring their presentations to the evaluation team. Individual demonstration or
discussion points may be treated separately, or in combination, as long as the major points are covered in
a way that allows the evaluation team to adequately score the individual items.
<< Note: For each functional area represented (e.g. Human Resources) copy and paste additional
sections as required. >>

<< FUNCTIONAL AREA >> SCENARIOS


The following sections detail the << Functional Area >> scenarios to be demonstrated by the proponent.
The proponent will be required to address each demonstration point identified in the scenario.
<< Note: For each functional process represented (e.g. Hiring, Maintaining Job Information) copy and
paste additional sections as required. >>

<< FUNCTIONAL PROCESS 1 >>


<< Note: For each scenario represented (e.g. Hiring without a Job Posting, Hiring an Employee Referral)
copy and paste additional sections as required. >>
Scenario 1
<< Provide all necessary background information for the vendor. If data values are required and cannot be
easily incorporated within the Demonstration Points column, include them separately within their own data
elements table. >>
The proponent should address each demonstration points of Scenario 1 as identified in Table 1.
#

Demonstration Points

Requirement Addressed

1.

<< State the demonstration point. (e.g. Demonstrate how an employee


can be direct-hired without an electronic posting and show the minimum
data required.) >>

<< Indicate which


requirement is addressed
by this demonstration
point. (e.g. Hiring 1) >>

2.
3.

PAGE 2 OF 5

Data Elements
<< State the field name.

Values
<< State the field values. (e.g. Mary Smith, 1 2 nd Street) >>

(e.g. Name, Address) >>

Scenario <<N>>
<< Provide all necessary background information for the vendor. If data values are required and cannot be
easily incorporated within the Demonstration Points column, include them separately within their own data
elements table. >>
The proponent should address each demonstration point of Scenario N as identified in Table N.
#

Demonstration Points

Requirement Addressed

1.
2.
3.

FUNCTIONAL PROCESS << N >>


Scenario 1
<< Provide all necessary background information for the vendor. If data values are required and cannot be
easily incorporated within the Demonstration Points column, include them separately within their own data
elements table. >>
The proponent should address each demonstration point of Scenario 1 as identified in Table 1.
#

Demonstration Points

Requirement Addressed

1.
2.
3.

Data Elements

Values

PAGE 3 OF 5

Data Elements

Values

Scenario <<N>>
<< Provide all necessary background information for the vendor. If data values are required and cannot be
easily incorporated within the Demonstration Points column, include them separately within their own data
elements table. >>
The proponent should address each demonstration point of Scenario N as identified in Table N.
#

Demonstration Points

Requirement Addressed

1.
2.
3.

PAGE 4 OF 5

OTHER DEMONSTRATIONS
<< Use this section to request demonstrations of items outside of traditional functional processes. Use of
the Demonstration Points table to state demonstration points is optional. >>

The proponent is to provide a demonstration of the following:


<< e.g. System Maintenance Tools >>; and
<< >>;

PREPARED BY
Project Manager
(name)

(signature)

(date)

(name)

(signature)

(date)

APPROVED BY
Project Sponsor

PAGE 5 OF 5