Page 1

An Introduction to the Cura Solution Implementation User Acceptance Testing for Cura Assessor (Generic)


CONTENTS

Acceptance Testing ................................................................................................................ 3 Definition ..................................................................................................................................... 3 Roles and Responsibilities ........................................................................................................... 3 Testers/Participants .................................................................................................................... 4 Testing Requirements ............................................................................................................ 4 Testing Schedule ......................................................................................................................... 5 Test Cases ............................................................................................................................. 6 Assessor - Rich client ................................................................................................................... 6 Assessor - Web Client .................................................................................................................. 7 Sign-off and Acknowledgement ............................................................................................. 8

Cura Generic UAT Process

Page 2 of 8


ACCEPTANCE TESTING

DEFINITION The overall purpose of testing is to ensure the Cura Assessor 3.2 application performs at an acceptable level for the customer. This document outlines the detailed plan for user acceptance testing of this application. This test plan will be used to record the customer’s sign off of the documented scenarios. Detailed test cases have been developed and will be used to record the results of user testing. This document is a high level guide, and is not intended as a replacement for any specific user acceptance testing procedures that individual areas might have.

ROLES AND RESPONSIBILITIES

Resource Type

Responsibilities

Name

Communication with customer to agree on format and scope of UAT Project Manager

Business Analyst

Agreement of acceptance criteria with the customer prior to commencing UAT Assist customer with the creation of a detailed test plan Ensure that a detailed test plan is available for test users

Test Lead

Ensure that bugs identified during UAT are logged Ensure UAT process screenshots are taken and contextualised Ensure testing takes place within agreed timeframes

Testers

Execute cases to ensure the application performs at an acceptable level. Document testing results and supporting screenshots.

Cura Generic UAT Process

Page 3 of 8


TESTERS/PARTICIPANTS Testing participants should include representatives from all areas involved in the application. There are benefits to including representatives from across all areas to validate the systems functions before the upgrade goes live in production. The best candidates for UAT are: 

Staff directly impacted by the upcoming system and business process changes.

Frequent users of the application and functions planned in test scripts/cases.

Individuals with a sound understanding of business processes in the areas they represent.

Individuals with the necessary time to commit to this endeavor.

Willing to experiment (to try various methods to see what works and what doesn’t work).

TESTING REQUIREMENTS 

Testing will take place in ______________________________________________. Some testers may choose to perform some testing from their regular workstations where it is possible. Test results must still be coordinated with others.

UAT will take place beginning on ________________________.

Identified testing participants will receive instructions prior to the start of testing.

Identified testing participants will perform the equivalent of their normal business function in the upgraded environment.

Test cases and scenarios will be prepared prior to the start of UAT.

Test participants will conduct the tests and document results.

Tester Name

Cura Generic UAT Process

Department/Area Representing

Area of Testing Focus

Page 4 of 8


TESTING SCHEDULE All upgraded functionality and test data will be migrated to the test environment prior to the start of user acceptance testing.

Activity

Lead Responsibility

Date

Identify and select testers for UAT Develop test scenarios and cases Validate participants availability for testing Review scenarios for accuracy, completeness and sequence (confirm test data is correct) Ensure UAT desktops configured for testing UAT environment validation Testing by UAT participants

Cura Generic UAT Process

Page 5 of 8


TEST CASES ASSESSOR - RICH CLIENT Tasks Rich Client

Problems experienced

Resource

Date Sign off

Log onto database Create an assessment Add a risk Run a report Add a contact Send a task notification to live PC Create and append screenshots of UAT Tasks USER: USER: USER: USER: USER:

Cura Generic UAT Process

Page 6 of 8


ASSESSOR - WEB CLIENT Tasks Web client

Problems experienced

Resource

Date Sign off

Log onto database Copy an assessment Add a risk Run a report Add a contact Create and append screenshots of UAT Tasks USER: USER: USER: USER: USER:

Cura Generic UAT Process

Page 7 of 8


SIGN-OFF AND ACKNOWLEDGEMENT

I understand that by agreeing to participate in this testing through the execution of the testing plan, I approve of the activities defined and authorize my department to participate as documented for the successful implementation of this application in our department.

_______________________________ Resource Name

Date: ___/___/___

_______________________________ Title or Responsibility

_______________________________ Resource Name

Date: ___/___/___

_______________________________ Title or Responsibility

_______________________________ Resource Name

Date: ___/___/___

_______________________________ Title or Responsibility

_______________________________ Resource Name

Date: ___/___/___

_______________________________ Title or Responsibility

_______________________________ Resource Name

Date: ___/___/___

_______________________________ Title or Responsibility

Cura Generic UAT Process

Page 8 of 8


An Introduction to the Cura Solution Implementation Generic Project Plan (Pilot – Live Implementation)


Cura Solution Implementation Generic Project Plan

Page 2 of 2


An Introduction to the Cura Solution Implementation Client System Architecture Technical Audit Sheet


CONTENTS

Client Details ................................................................................................................................ 3 Cura Installation Environment ....................................................................................................... 4 Cura Module Installation .................................................................................................................... 4 Cura Users Setup ................................................................................................................................ 4 Cura Rich Client User Register............................................................................................................ 5 Cura Server Setup ............................................................................................................................... 5 Cura Login Requirements ................................................................................................................... 7 A.D. Controller Details ........................................................................................................................ 7 Sign-Off Sheet ............................................................................................................................... 8

Cura Client Audit Sheet

Page 2 of 10


CLIENT DETAILS

Client Name

____________________________________________________________________________

Client Address

____________________________________________________________________________ ____________________________________________________________________________

Project Sponsor (Names) ____________________________________________________________________________ I.T. Contact (Names)

____________________________________________________________________________

Cura Business Analyst

____________________________________________________________________________

Cura Installation Date

____________________________________________________________________________

EULA Details (Complete for all client EULAs): Description

Server Licenses

Rich User Licenses

Web User Licenses

Anniversary

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

Cura Client Audit Sheet

Page 3 of 10


CURA INSTALLATION ENVIRONMENT CURA MODULE INSTALLATION Cura Modules

□ □

Assessor/Risk Meth Builder

□ Doc Manager □ Surveys

Quick Capture

Compliance

Convert

Other Modules _______________________________ _______________________________

Installation Process

Demo

Pilot

Dev Install

Live Install

Other Process _______________________________________________________________ Version Control

Current Version ________

Update Required ________

Date/Month Installed

_________________________

Date/Month Upgraded

Upgrade Version

_______

_________________________

CURA USERS SETUP Summary of Cura Users: User Spread

Local (On Site): ________ Rich Users

________ Web Users

Local (Off Site): ________ Rich Users

________ Web Users

National:

________ Rich Users

________ Web Users

International:

________ Rich Users

________ Web Users

Administrators ________ System Administrators Training Conducted

Assessor: Basic Report Writer

□ □

□ Meth Builder □ Advanced

Administrator Doc Manager

□ □

Web Assessor Convert

□ □

Surveys

Other Training ________________________________________________________________ Summary of Environment: Client IT Contact Person

_________________________________

Windows Version ______________

Cura Client Audit Sheet

SQL Version

Contact Details

_______________

__________________________

MS Server Version

________________

Page 4 of 10


CURA RICH CLIENT USER REGISTER If this information is not readily available from your contact, or many users exist, run the Cura Contact List Report in order to extract the user list which must be attached to this audit report. Ensure you have this report available so that you can install it on the client’s Cura system in order to run. This report can then be printed out and attached to this audit sheet. If you are unable to do this, you will need to complete a list of users in the given fields below. An additional page is attached to capture multiple users.

User Full Name

User Logon Name

User Role

CURA SERVER SETUP Only fill in the applicable fields based on the client’s server tiers and environment. One/Two/ Three Tier

Server Type

Server Name

IP Address

Hardware Spec

DEV Web Server

PROD DR DEV

Application Server

PROD DR DEV

Database Server

PROD DR

Cura Client Audit Sheet

Page 5 of 10


Summary of Environment: Client IT Contact Person

_________________________________

Server Installation Date

________________________

Server Backup Method:

Manual

SQL Server Version

________________________

Windows Version & SP

________________________

â–Ą

Automated

Contact Details

__________________________

Last Server Backup Date

__________________________

â–Ą

__________________________

Backup Suite

OS Version/Service Pack __________________________ MS Server Version

_________________________

Comments:

List all applications sharing the Cura Server (Application, Web and/or Database servers). It is also important to indicate the frequency of the maintenance requirements of the application sharing the server with the Cura software. Application Name

Type of Application

Frequency of Maintenance

App/Web/DB?

Comments

Comments:

Cura Client Audit Sheet

Page 6 of 10


CURA LOGIN REQUIREMENTS Cura requires a SQL username to access the database. The minimum required rights are DB owner. Cura Login

Yes/No

Admin Password

Location of Login

Using Cura Login Required? Alternative Login Required? Comments Cura may depend on Windows Authentication as well. Enter these details below: Windows Authentication

Yes / No

Using Windows Authentication? Comments

A.D. CONTROLLER DETAILS Name

Details

Location

Please specify the following Exchange particulars: Exchange Version Exchange SRV Name Exchange SRV IP Address SMTP path Mail Marshall / Spam filter active? Added Cura mail address to trusted list? Comments

Cura Client Audit Sheet

Page 7 of 10


SIGN-OFF SHEET This confirms that the client has been visited by the assigned Cura Business Analyst or representative, and that all necessary information has been gathered and any relevant client issues have been discussed.

For

____________________________________________________________________ (“the Client�)

Name

_____________________________________

Signature

_____________________________________

Date

_____________________________________

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For

CURA SOFTWARE

Name

_____________________________________

Signature

_____________________________________

Date

_____________________________________

Cura Client Audit Sheet

Page 8 of 10


Annexure – Contact Sheet for Cura Users Cura offer product support and expansion services to all clients. Each department recognizes particular roles in ensuring your Cura installation remains updated, working and scalable to suit your needs.

Switchboard Cura South Africa can be reached at the following numbers: Telephone Fax Website Queries

+27 11 483 7640 +27 86 649 3760 www.curasoftware.com

General Product Support: For all your everyday Cura user queries, or to log faults, errors, fixes or to make a request for product enhancements or for a Cura consultant to visit you, please contact our support centre: Telephone eMail

+27 11 483 7650 support@curasoftware.com

Sales & Expansion Queries Should you wish to learn more about additional Cura products, existing product expansion or build enhancements to your Cura system, please contact a member of our Sales Team to discuss your needs and arrange a meeting to evaluate different options and possible submit a quotation based on these. Philip Tilman Blessing Mutambara Paul van der Struys

philipt@curasoftware.com blessing@curasoftware.com pauls@curasoftware.com

Training Cura offer a variety of training sessions for all our products, from beginner to advanced levels, as well as refresher sessions. Please call our training personnel to discuss any training needs you may have. eMail

Cura Client Audit Sheet

curatraining@curasoftware.com

Page 9 of 10


User Full Name

Cura Client Audit Sheet

User Logon Name

User Role

Page 10 of 10

Technical UAT and Customer TakeOn  
Read more
Read more
Similar to
Popular now
Just for you