58,79 €
Mehr erfahren.
- Herausgeber: Packt Publishing
- Kategorie: Wissenschaft und neue Technologien
- Sprache: Englisch
As the complexity of software applications increases and the length of the implementation life cycles decreases, companies are looking for effective ways of training users in new applications, and the new releases of existing applications. Oracle's User Productivity Kit solves these problems by enabling the rapid creation of software application simulations, which are used for training purposes or to generate business documents. Although UPK provides such advanced features, nothing has been written about this application yet.
This book provides a guided approach to building high-quality, re-functional simulations of tasks performed in software applications. With this book in hand, it is easy for organizations that are implementing or upgrading software to meet their full training and documentation requirements. This book explains how to harness all of the functionality provided by Oracle's User Productivity Kit, formerly known as OnDemand, to develop better quality training. It also covers the advanced topics of customizing UPK's built-in delivery formats, and defining new ones to extend the capabilities of UPK.
This book explains how to make the most of Oracle User Productivity Kit's available functionality to create high-quality simulations. These simulations can be used during instructor-led training, self-directed learning, or refresher training. By following the approach described in this book, you will create world-class training material that your trainees will find useful, engaging, and informative. As a result, they will remember more of what they are taught, and will be better equipped to use the application on which you are training them. In turn, they will become more productive sooner, make fewer mistakes, and require less support. To ensure effective knowledge transfer through training simulations, it is necessary to add a business context to recordings, and to provide additional explanations. This book will teach you more than simple mouse-clicks and keystrokes.
Das E-Book können Sie in Legimi-Apps oder einer beliebigen App lesen, die das folgende Format unterstützen:
Seitenzahl: 619
Veröffentlichungsjahr: 2009
Ähnliche
Table of Contents
Oracle User Productivity Kit 3.5
Dirk Manuel
Oracle User Productivity Kit 3.5
Copyright © 2009 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.
First published: September 2009
Production Reference: 2240909
Published by Packt Publishing Ltd.
32 Lincoln Road
Olton
Birmingham, B27 6PA, UK.
ISBN 978-1-849680-16-5
www.packtpub.com
Cover Image by Parag Kadam (<[email protected]>)
Credits
Author
Dirk Manuel
Reviewer
Sjoerd De Vries
Acquisition Editor
James Lumden
Development Editor
Chaitanya Apte
John Antony
Technical Editor
Chaitanya Apte
Indexer
Monica Ajmera
Editorial Team Leader
Akshara Aware
Project Team Leader
Priya Mukherji
Project Coordinator
Ashwin Shetty
Proofreader
Chris Smith
Jeff Orloff
Lynda Sliwoski
Graphics
Nilesh R. Mohite
Production Coordinator
Aparna Bhagat
Shantanu Zagade
Cover Work
Aparna Bhagat
About the author
Dirk Manuel is a freelance documentation and training consultant, specializing in projects for the large-scale implementation of SAP. Dirk has been using UPK and its precursor OnDemand for five years, during which time he has developed hundreds of well-received simulations. Dirk has provided training on UPK and OnDemand to UPK developers in Europe, Asia Pacific, and the Americas.
Originally from the United Kingdom, Dirk has lived and worked in England, Germany, Belgium (twice), and Singapore, before settling in Houston, Texas.
Dirk has a B.Sc. (Hons.) in Computer Science, and a City & Guilds in the Communication of Technical Information. He is a Fellow of the Institute of Scientific and Technical Communicators (ISTC) and a Senior Member of the Society for Technical Communication (STC).
Acknowledgment
This book has been neither a labor of love nor a life's work. Being a Technical Writer by trade, documenting what I know is almost impossible to avoid. After being asked on several occasions if I could recommend a good book on UPK/OnDemand, and always having to reply that there simply weren't any books, good or bad, I decided to write my own.
This book is a distillation of five years' experience with UPK and OnDemand, and of teaching it to other developers.
I have seen many poor examples of simulations created using UPK or OnDemand, due primarily to a lack of knowledge on the part of the developers of the capabilities of UPK. My sole intention with this book is to show developers that it is not difficult to create truly impressive training simulations, with the correct knowledge and just a little effort.
I would like to thank the staff at Packt for their support, my long-standing client, ExxonMobil, for giving me the opportunity to learn so much about UPK and OnDemand, and the extremely knowledgeable Sjoerd De Vries, for doing such a great job on the technical review. I would also like to thank Seigun Kosabayashi and Yuki Iida for the Japanese texts, and Marc Wilms for the (petit) French.
About the reviewer
Sjoerd de Vries is a senior e-learning consultant and project manager for customers of SMS implementation engineers (http://www.smsnet.nl) in The Netherlands. In his work, he combines e-learning, documentation, and change management aspects to "engineers" in larger ERP and CRM software-implementation projects, for customers like SaraLee, Philip Morris, Ericsson, ExxonMobil, Hunter Douglas, ABN-AMRO, Dutch Ministry of Defense, and many others.
In these projects, the users of the software will have an important place in "learning by doing" and increasing performance support within their company. One of the preferred tools for almost 8 years is OnDemand software, currently renamed as Oracle's User Productivity Kit (UPK) as well as Knowledge Pathways (UPK Pro), also by Oracle.
As the first Dutch partner of OnDemand Software, SMS implementation engineers have implemented, trained, and supported OnDemand Software in Europe since 2001. Since 2004 the company also became a partner of Oracle to support the User Productivity Kit that was created by OnDemand Software to support Oracle implementations only. In 2008 OnDemand Software was acquired by Oracle and SMS implementation engineers became a Certified Partner of Oracle and also won the Best Partner Award.
The many years of experience in implementing, consulting, training, and content creation means that OnDemand and UPK have hardly any mysteries for Sjoerd. He became an appreciated and highly involved member of the OnDemand Software community (currently transitioned to the Oracle Support and LinkedIn communities about the UPK). At the last UPK Users' Conference in 2008, Sjoerd also won an "OSCA" award in an UPK contest. For his years of contribution to OnDemand and the later UPK, Sjoerd was asked to contribute to this book as a technical reviewer. Because sharing ideas and knowledge is his main job, he gladly cooperated and hopes that the readers of this book also will learn to like the UPK and understand its big advantage as a training and performance support tool.
Sjoerd has a Masters degree in Science and graduated after his study at the "Vrije Universiteit" in the Netherlands as a teacher (1st degree). After several jobs as a Biology teacher he joined SMS implementation engineers in 1998 and became an e-learning expert. Sjoerd is also chief editor of a Dutch web site for E-learning & Education.
Sjoerd is a real Dutch name and since it is often asked, it is pronounced as "shoe 'rd". Feel free to contact him via his company or LinkedIn.
LinkedIn: http://www.linkedin.com/in/somdv.
I would like to dedicate this book to my children, Finn, Freya, and Gil, who are the reason why I still do what I do (even if they have no idea what that is).
Preface
This book is a developer's guide to Oracle UPK version 3.5 (and its predecessor, OnDemand version 9.1, with which it shares 95% of its functionality). It covers all aspects of UPK's functionality, and explains how to get the most out of these features in order to build high-quality training exercises that will ensure the most effective knowledge transfer possible for your trainees.
Documentation on UPK has been (until the publication of this book) almost nonexistent (consisting solely of the Content Development Guide shipped with the software), and training is prohibitively expensive.
This book fills the documentation gap by providing developer-friendly, visually-appealing, and easy-to-read documentation on the core functionality of UPK. It fills the training gap by taking a guided approach to this functionality, introducing new concepts and functionality with each chapter, and building on the knowledge gained in the previous chapters. In this way, readers can start with the basics, and then progress to more advanced topics as they need them, rather than being presented with "everything you need to know" at once, in a dry and difficult-to-digest manner (as is the case with the Oracle-provided documentation).
Although it is primarily aimed at new or intermediate users, this book contains enough advanced information to keep all but the most hardcore of UPK developers happy. It includes tips on how to get the most out of UPK, suggestions on best practices for training material development with UPK, and advice on how to avoid some common mistakes.
What this book covers
This book provides a guided tour of UPK 3.5. Each chapter focuses on a specific task, based around specific functionality within UPK. Throughout the book, we will develop, and build on, a sample simulation, and use this to introduce, and explain, new functionality by applying this functionality to the sample simulation.
By chapter, this book covers the following topics:
Chapter 1, An Introduction to UPK provides a high-level overview of what UPK is, and what its main capabilities are.
Chapter 2, Organizing your Library provides a first look at the developer's working environment. It starts by explaining the various components of the Developer screen, and provides some basic navigation techniques. It then provides guidelines on how to choose a suitable folder structure for your Library, and explains how to implement the chosen structure.
Chapter 3, Recording a simulation explains how simulations are recorded in UPK, and provides instructions for creating the initial simulation that is built upon throughout the remainder of this book.
Chapter 4, Editing a Topic provides a comprehensive description of the functionality provided by the Topic Editor. It does this by editing the simulation recorded in the previous chapter, changing the Bubble Text, providing Custom Text, inserting missing Frames, and editing screenshots.
Chapter 5, Building an Outline introduces the concept of an Outline, and provides a full description of the capabilities of the Outline Editor. It explains the difference between Modules and Sections, and explains how best to use these to organize Topics into a structure suitable for presenting to the trainees.
Chapter 6, Publishing Content explains, how to preview and publish recorded Topics. It explains, with examples, the various online and document-based output formats, and provides instructions on how to generate each of them. This chapter also covers the quality assurance activities that should be carried out prior to publication, including spell-checking and testing. Finally, this chapter explains how to integrate UPK's output with other applications.
Chapter 7, Version Management is primarily aimed at developers working in a client/server environment. It explains the check-in and check-out functionality of UPK, including the version history, reverting to prior versions of content objects, and restoring deleted objects. The final sections of this chapter are applicable to both client/server installations and stand-alone installations, describing the importance of backups and explaining how to import and export content.
Chapter 8, Allowing Alternatives is concerned with expanding the usefulness of recorded simulations by providing Alternative Paths, along with Branches and Decision Frames. It also explains how to improve the realism of simulations by providing Alternative Actions, and explains how to capture these automatically.
Chapter 9, Adding Value to Your Topics is probably the single most important chapter in this book. It explains how to improve the quality of simulations by providing context through the use of Custom Text, and by using Explanation Frames, Web Pages and Packages. It also explains how to build and implement a Glossary.
Chapter 10, Adding Value in the Player explains the things that can be done to improve the quality of the trainees' interaction with the UPK Player. This includes using roles, jump-in points, and keywords. This chapter also explains how to prevent trainees from skipping through exercises without performing the required actions.
Chapter 11, Incorporating Sound into your Topics explains the auditory capabilities that UPK provides, and discusses how best to utilize these. It explains how to record new sound files, as well as how to import and export sound files.
Chapter 12, Configuring UPK covers the advanced topic of configuring UPK to meet your individual requirements. The chapter explains how to customize Template Text, and how to define new object types. It also explains how to customize the UPK player, and how to create a new document format.
Chapter 13, Localizing Your Content explains how to convert your recorded Topics into another language. This includes using local language texts, deploying content in local languages, translating custom text, and replacing screenshots with localized versions.
Appendix A, Installing UPK explains how to install the UPK developer environment, either as a stand-alone application, or as part of a client/server environment. It also explains how to install the UPK Standalone Topic Player.
Appendix B, Object Types provides a reference list of all of the predefined object types in UPK, and shows the template text that is generated for each of these using the Standard Template and the Microsoft Template.
Who this book is for
This book has been written with the following audiences in mind:
Conventions
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "We can include other contexts through the use of the include directive."
A block of code will be set as follows:
When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be shown in bold:
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "clicking the Next button moves you to the next screen".
Note
Warnings or important notes appear in a box like this.
Tip
Tips and tricks appear like this.
Reader feedback
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply drop an email to <[email protected]>, and mention the book title in the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Customer support
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Downloading the example code for the book
Visit http://www.packtpub.com/files/code/0165_Code.zip to directly download the example code.
Errata
Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration, and help us to improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the let us know link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata added to any list of existing errata. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
Questions
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.
Chapter 1. Oracle User Productivity Kit
The things we have to learn before we do them, we learn by doing them.
- Aristotle
In this first chapter, we will start with the absolute basics. We will look at what UPK is, and what it can do for us.
In this chapter, you will learn:
What is UPK?
UPK (User Productivity Kit) is a software application that can be used to create simulations of tasks performed in a software application for, use during training on that application. It can also generate various forms of documentation—such as job aids, test scripts, and business process procedures—based on these same recordings. UPK's deliverables can also be incorporated into an application's online help system to provide in-application performance support.
UPK does all of this by capturing a user's interaction with an application (typically, to perform a discrete business task), and then repurposing this information to create the various output formats.
UPK has found a strong market in large corporations for developing training material for large-scale software implementations. Although it is most commonly-used for providing training on enterprise-level software applications, such as those offered by Oracle, SAP, Siebel, JD Edwards, and so on, UPK can be used to record and publish simulations for any Windows-based application. However, the success with which UPK manages to capture the context of the user's interaction with these 'non-targeted' applications may vary.
A brief history of UPK
UPK is the latest incarnation of a product that has been around for over ten years. Starting as an offshoot from SAP Tutor (now itself called iTutor), UPK began life as OnDemand, which was developed and marketed by OnDemand Software. OnDemand Software was acquired by Global Knowledge Software (GKS), a division of Global Knowledge, Inc. In July 2008, GKS itself was acquired by Oracle Corporation. GKS was a long-time partner of Oracle, and OnDemand has been used extensively by Oracle and its customers for providing training on Oracle products.
As Oracle already had a product called On Demand (with a space), the decision was made to rename OnDemand to User Productivity Kit, or UPK. Concurrent with this, Oracle realigned the version numbering of UPK so that OnDemand version 9.1 was renumbered as UPK version 3.1. To confuse users even more, UPK 3.5.0 is, for all intents and purposes, a slightly enhanced version of OnDemand 9.1.7. This was the last official OnDemand release (and was itself released as UPK 3.1.7).
Oracle refers to "pre-takeover" versions of OnDemand as "UPK 2.x". I interpret "UPK 2.x" as referring to OnDemand version 8.x, and treat UPK 3.5 and OnDemand 9.1 as generally the same product, save some minor differences in functionality highlighted as such in this book.
Why use UPK?
Despite Oracle (and Global Knowledge before it) espousing the single-source document-creation capabilities of UPK, the primary use of UPK is for the creation of simulations for use in training. And for this, it can work very well—if the developer is willing to put in the effort.
Simulations are captured in the application for which the training is being developed. This means that the simulations have the "look and feel" of the actual system. When these simulations are executed, the trainee gets the impression that they are interacting with a real system, whereas in reality, they are working within the safe confines of a training tool.
An example of a UPK simulation screen is shown in the following screenshot:
You will notice in this example that the simulation is played back in full screen, with the UPK-provided information overlaid on top if it. This information comprises a red rectangle indicating the area of the screen with which the user needs to interact, and a "bubble" that provides the user with instructions. The user types the specified information into the field indicated, just as they would with the actual system. Instead of interacting with SAP, they are in fact looking at a static screenprint and interacting with some clever JavaScript code that provides the "look and feel" of the system.
It is this actual "look and feel" that provides the greatest argument for using UPK.
Instructor-led training
It is a generally accepted fact in learning theory that most people (certainly in the sphere of adult learning) learn more effectively by doing (practicing). In many large corporations, this practice has traditionally been achieved through the use of a training system (or a dedicated part of the 'development' system) in which trainees can carry out predefined training exercises.
However, there are a number of problems with this approach:
UPK solves these problems by capturing what is effectively a snapshot of the application, using a single set of data. This recording is external to the application, which means that once it has been captured the system is no longer required. Trainees do not need to log onto the system, and it does not matter if the developers change anything—or even crash the system. Additionally, any information that the trainee requires regarding data values is built directly into the simulation, so there is no need for separate data sheets.
More importantly, because UPK generates a single, stand-alone simulation, every trainee can carry out the same simulation, at the same time, and see the same result. Furthermore, a trainee can carry out a single simulation multiple times and see
exactly the same result every time. This is important, as it means that the trainee can return to a simulation after the course conduct (for example, when they are back in the office, performing the task for real) and see exactly what they saw during training, as a refresher.
Given this, UPK simulations are increasingly being seen as a good choice for providing exercises for classroom-based training. The classroom conduct still takes place, but instead of the instructor asking trainees to log on to the training system to carry out an exercise, they now ask the trainees to run a UPK exercise.
Self-paced learning
The fact that UPK simulations are self-contained, and do not rely on a system or instructor being available, means that they are well-suited to providing self-paced training (what used to be called computer-based training, before that term went out of vogue).
By placing all of the UPK output on a central server, or in a Learning Management System (LMS), users can access the training simulations on their own, and receive training at their own desks at a time that suits them best.
However, it is important to understand that UPK does not instantly replace the need for a trainer. Yes, they can replace trainers, but doing so takes a significant amount of time. In a classroom environment, the trainer is there to explain an exercise, point out interesting information, and provide additional business-specific information. They add context to the mechanics of the key-strokes and mouse-clicks captured in the recording.
If the trainer is not present to provide this information, then it needs to be provided to the trainee through some other medium. Thankfully—as we shall see in this book—UPK works very well as this medium. But the information still needs to be entered into UPK so that the trainee has access to it.
How does UPK work?
It is a common misconception that UPK simulations are actual "recordings". UPK (and this book, on occasion) uses the term recording, and although this is probably the most apt term, it is important to understand that a UPK simulation is not a "recording" in the strict sense of the word. UPK does not capture "live-motion" actions in the way that Camtasia or other video capture software does. Sure, a UPK simulation may look like a recording when you play it back in See It! mode, but it isn't. What UPK captures when it "records" are screenshots and the actions that trigger the transition from one screenshot to the next.
For example, if you use UPK to create a simulation of someone entering a text string into an input field on a screen, UPK captures the following:
In terms of the actual files (or assets) created for this simulation, there will be two .png files for the screenshots, and a snippet of JavaScript that defines the text and the coordinates. There is no .wmf, .swf, .mp4, or any other movie-type file.
When this simulation is played back (in See It! mode), UPK displays the first screenshot, displays the text on the screen one character at a time (so that it looks as though it is being typed), and then displays the second screenshot. Smoke and mirrors; that's all.
However, this simplicity has a couple of strong benefits. First, because the recordings consist purely of standard, browser-friendly assets (HTML files, .png images files, and JavaScript), the simulation can be played back in a simple web browser without the need for any add-ins, codecs, or proprietary players. Second, these assets all have very small individual file sizes, which means that they work well even over low-bandwidth connections.
But what is really clever is the way that UPK makes use of these assets. UPK allows exactly the same recording to be used to generate several different output formats, including four formats designed for online use, and six documentation formats.
Output formats
As stated above, UPK can provide output in four different formats designed for online use and six formats designed for printing. This seems to be pretty good value for money (ten-for-one), but it is important to understand that all of the output formats are generated from the same, single recording. This provides true single-sourcing, but it also means that, for example, a test document can (by default) only contain the same content as the training simulation, which can only contain same content as the business process procedure, and so on.
Unfortunately, what you want to teach a trainee during a classroom conduct (or in a self-paced training presentation) is not necessarily the same thing that you want described in your documentation. In training, you may want to look at certain scenarios. Maybe you want the trainee to hit a certain problem, and then explain how to overcome this. Maybe you want to take a bit more time and explain some related information on a screen, or point out how this ties in with that. In your documentation, and certainly for business process procedures (a.k.a. work steps, user procedures, work instructions, and so on), you are more likely to want to provide clear, concise instructions on how to do something the single, correct way.
So yes, UPK can generate documents, but this doesn't mean that you necessarily want to use them.
Online delivery
For online delivery, UPK provides four different output formats. These are all variations on the same theme: online simulations with which a trainee interacts. The four formats are:
All of these formats are explained in greater detail in Chapter 6, Publishing Content. Because the Player format is the most commonly-used format, and because the other three modes are effectively variations on this, the Player format (only) is discussed in more detail in this chapter.
An example of the UPK Player is shown in the following screenshot:
Tip
This example shows the finished product of this book, using Web Pages, images, roles, hyperlinks, and a custom deployment format. If your first Player does not look like this, then don't worry; that's why this book was written—to get you there.
When a trainee selects a specific exercise from the list in the left-most pane of the Player, additional information about that exercise is displayed on the right-most side of the screen, along with option buttons for the five modes in which the exercise can be used (actually, four playback modes, and a single document format). An example of this exercise-level screen is shown in the following screenshot:
The five modes in which the training exercise can be 'experienced' are shown in the dark blue heading across the top of the lower-right portion of the screen. Each of these modes is explained separately, below.
See It! mode: Demonstrations
In See It! mode, the UPK player automatically displays the screenshots and carries out the required interactions. This looks like the playback of a video, and can be completely hands-free. This mode is best considered as a demonstration mode. When used in a classroom environment, the instructor would set this mode running and then provide additional commentary during the playback. Although this requires fairly close coordination between the instructor's speech and the playback, it does have the advantage (over the other modes) that the instructor does not need to interact with the simulation themselves, and can therefore better focus on the needs of the trainees.
Try It! mode: Exercises
In Try It! mode, the UPK player will display a screenshot, and then wait for the trainee to perform the action, before advancing on to the next screenshot. The trainee is required to carry out exactly the same action as the one that was performed during the initial capture of the simulation, although this can be configured in various ways, as we will see later in this book. The user is given instructions on what action to perform, and where on the screen to perform this action. For example, if the action was to click on a button on the screen, the user is asked to click on the button and the area of the screen containing the button is highlighted. The trainee must click in this exact area of the screen in order to proceed to the next screen (which gives the impression of progressing through the application). This mode is best considered as a true exercise mode, in that the user is interacting with the system. This is probably the most commonly-used mode.
Know It? mode: Tests
The Know It? mode is very similar to Try It! mode in that the UPK player displays a screenshot and the trainee is required to perform the action. However, in Know It? mode, the trainee is given no (or greatly reduced) instructions and there is no indication of the area of the screen with which the trainee is required to interact. This is because the trainee is expected to know what they are doing. Another unique feature of the Know It? mode is that once they have completed the exercise, the user is presented with a "score" that indicates what percentage of the exercise they managed to perform correctly, without assistance. This score can also be provided to an LMS, or some other system for monitoring trainee progress. This mode is therefore best thought of as a test (or verification) mode.
Do It! mode: Performance support
The Do It! mode differs from the other three playback modes in that it is specifically designed to provide assistance to users of the system (not trainees) while they are actually using the real system. With Do It! mode, the instructions for the actions are displayed in a help panel that floats above any other windows on the user's screen. The theory is that the user has the application open, and is working directly in it, with the UPK instructions being constantly visible at the same time. The truly clever part is that if the UPK system is configured to use auto-advance, as the user performs each action in the system, the UPK instructions will automatically advance to the next action. This way, the instructions keep pace with the user. If auto-advance is not configured, the user must manually move from one step to the next in the UPK simulation, although a keyboard shortcut can be used to do this from within the application itself, so that the user does not have to continually flip between the application and the UPK recording. This mode, therefore, is best thought of as performance support (or as providing an electronic performance support system, to use the latest buzzwords).
Print It!: Documentation
The fifth mode available through the Player is Print It!. This allows the trainee to print a hardcopy version of a simulation. This hardcopy is actually one of the (six) standard document formats discussed below—the developer can choose the format to use (for the entire Player) during publication. By default, this is the Job Aid, using the Do It! mode texts.
Tip
Version Difference
Print It! mode was introduced with UPK 3.5.0.
An understanding of the four playback modes is absolutely crucial when it comes to creating the simulation content, or specifically, when choosing the words to be used for describing (or not, depending on the mode) the actions that the trainee is required to carry out in the simulation. This is covered in detail in Chapter 4, Editing a Topic.
Documentation
As stated above, UPK can generate a number of different types of documentation. Again, these are all built from the same single recording, so the variation between them is extremely limited. Most of the uniqueness of a given document stems from a few small pieces of additional information that are entered outside of the actual recording, some minor formatting differences, and the display or suppression of certain elements of the recording.
The six available documents are explained below.
Training Guide
The Training Guide is effectively a hard-copy version of a training course for use by the trainee. Quite why they would want a two-dimensional printout when they have the full interactive version online is unclear. That said, some people like to receive handouts during training, and this will give them that. Additionally, because the Training Guide contains the full content of the simulation (all screenshots and all texts) it is useful for providing review copies of the training material to people who do not have access to the interactive, online version.
Instructor Manual
The Instructor Manual is, as the name suggests, designed to be a reference document for the instructor to use during a classroom conduct of a course. The content is the same as that of the Training Guide, with one additional (and optional) piece of information that the developer can provide in free-text form. The instructor may find it useful to refer to this document during demonstrations, or prior to the trainees carrying out the exercise, in order to familiarize themselves with the content of the simulation.
Job Aid
The Job Aid is a scaled-down version of the simulation. It does not include screenprints, and simply lists all of the actions as a single numbered list, formatted in a table. This format can be used as a 'quick reference'.
System Process Document
The System Process Document contains all of the actions carried out in the recording, including screenshots, plus some other developer-provided text describing the context of the process. The System Process Document is effectively a user procedure. This document format is sometimes referred to as a business process procedure, work instruction, job script, and so on.
Tip
Version Difference
Prior to UPK 3.5, the System Process Document was referred to as a Business Process Document, although the content of the document is identical in both cases.
Test Document
The Test Document provides the instructions from a simulation, but not the screenprints. It can also contain several additional pieces of information related to testing such as the purpose of the test, set-up instructions, expected time to complete, additional validation instructions, and so on. For each step in the procedure, the Test Document includes space to record the input (data entered or action taken), expected result, and whether the test (or step) was passed or failed.
HP Quality Center Test Script
The HP Quality Center Test Script format generates a Microsoft Excel file that is identical in format and content to those produced by HP Quality Center (previously known as Mercury TestDirector). Testers can record their results in this worksheet, and then load the worksheet back into HP Quality Center for testing progress monitoring.
Deciding how you will use UPK
Now that you understand what UPK can do for you, you need to think about exactly what you want it to do for you.
Choosing delivery formats
You need to decide whether you are going to use your simulations as an integral part of classroom training conducts, or will be providing your training as stand-alone deliverables suitable for self-paced learning. Or both.
If you only plan on using your exercises within a classroom environment, then you may be able to get by with providing less business context in your simulations because the trainer will be able to provide this context during the classroom conduct. However, if you do this you will be selling yourself short. There will undoubtedly come a time when your UPK exercises will be used for self-paced training, even if this is not the initial intention. Providing this capability up-front will save re-work in the long run.
If you will publish to any of the true interactive formats (Player, LMS, Standalone Topic Files), you need to decide which of the playback modes you will use. Editing Topics so that they will make sense in several different modes takes time—especially if you are using Custom Text extensively (which you should, if you want to provide quality training). If there are certain modes that you know you will never use, then you can save yourself some development time. However, bear in mind that the printed output formats can also make use of these playback modes, so you need to make sure that you develop your online content with these modes in mind, as well.
Consider which (if any) of the printed document formats you will use. As explained above, training is not the same as documentation. You can have high-quality, effective training simulations, but this does not necessarily mean that the documents generated from them will be as good.
Examine the available document formats and decide if you have a use for them. If you do not have a proven need for a document type, then do not generate it "just because you can". If you decide to use one of the document formats, then think about how these documents will be made available to the trainees or users. If you use only one document format, then you can provide access to this via the Print It! mode. If you provide more than one document format (which I'd question the need for, as they all provide basically the same information), decide how you will deliver these. If they are not immediately accessible to the people who need them, re-examine the wisdom of providing them at all.
UPK allows you to tag the text that is displayed to the users so that it appears only in specific modes. When you generate one of the document output formats, you need to tell UPK from which one of these (three) modes the text for the document should be taken. You should, therefore, make sure that text is tagged for the appropriate mode in the Topic so that when the document is generated from this mode, it includes the required text. Tagging text for different modes is described in Chapter 4, Editing a Topic.
Styles and standards
UPK does a very good job of ensuring consistency and adherence to styles and standards, via its built-in templates, which define the default texts shown in the yellow bubbles that are overlaid on the screenshots. One of the templates that it provides is even designed to be compatible with the terminology and formatting standards espoused by Microsoft's Manual of Style for Technical Publications.
You should check these default templates (Standard and Microsoft) to determine if they meet your in-house standards. If neither of them seems suitable, then you may want to consider creating your own template—or at least customizing one of the two provided templates to meet your requirements.
Over and above the Bubble Texts that are controlled by the template, you should develop your own style guide to specify the following things:
Don't worry if most of these terms do not mean anything to you yet; you will be intimately familiar with them by the end of this book.
Developing an unequivocal style guide, and then ensuring that all developers adhere to this for all simulations, will ensure that your training deliverables are seen as parts of a cohesive whole rather than "a bunch of stuff done by different people at different times".
When to record
You need to decide on the stage during the application development cycle at which you will capture your simulations. Ideally, your simulations should be captured in the final version of the system.
The whole point of simulations is that they should have the "look and feel" of the actual system. Specifically, they should match reality as closely as possible—there should be a willing suspension of disbelief on the part of the trainee that they are actually looking at static screenshots. This is a common fault with poor-quality UPK exercises: they do not allow for this suspension of disbelief because it is glaringly obvious that the trainee is not using an actual system. With a high-quality exercise, however, the trainee has the impression that they are using a "live" system. One of the common complaints that trainees have with training conducted using UPK simulations is that they would rather have a "real" system to play with. The easiest way to avoid such comments is by providing simulations that are as close to reality as possible.
That said, it is often impractical to wait until development for the entire application is complete before developing your training. Often, training development and application development will run in parallel. Fortunately, development is often gradual, with different parts of the application being completed over time (as opposed to nothing being ready until the whole thing is ready). You should therefore work closely with your development team to ensure that the training developers are informed as and when different pieces of the functionality are finalized, so that you can start developing training for these pieces, while the development teams work on the next piece of functionality.
What to record
Although you might think that what to record is obvious—just whatever the user will actually do—this is not necessarily the case. You need to think about whether you will demonstrate a specific scenario, or provide general instructions, or show everything that the user can do in the application (or transaction), regardless of whether they actually will do this.
You should also decide whether you want to teach only one way to do something, or will provide alternative actions and alternative paths (both of which are covered later in this book).
A useful technique when making these decisions is to produce a 'storyboard', or a simple flowchart of what screens you will go through in the application, what you will do on each screen, and how you will get from one screen to the next. Having this information available beforehand will save you from having to decide these things during the recording itself, and potentially missing things. Storyboards are also useful if you have less-experienced developers who perhaps need some more guidance for their recordings.
Summary
UPK captures a user's interactions with a software application. It can then generate a number of deliverables based on this recording. Some of these deliverables are more useful than others.
Before creating training deliverables using UPK, you should decide which of these deliverable formats you want to use. Although you can choose the required deliverables at the time of final publication, knowing which deliverable formats you want to use, and in what modes, will allow you to better focus your editing of the simulations.
Chapter 2. Organizing your Library
In Chapter 1, we looked at what UPK is and how we can use it to develop quality training material. In this chapter, we get right down to business and start using UPK. However, before you can create content, you need to decide where you are going to store it, and this is in the Library. The Library is the main workspace in UPK. Content objects are created in, and exist within, the Library.
One of the key changes introduced with UPK 3.5 is the separation of the environment in which you—the developer—works, and the Player that the trainee sees. In OnDemand 8.7 and earlier, these were effectively one and the same, that is, the developers worked within a Title, which contained all of the Topics (the recorded simulations) for an application. These were then grouped into Modules and Lessons. Typically, one or more selected Modules from within this Title were published to a Player, which is what the trainee saw. This contained exactly the same (selected) Modules, Lessons, and Topics, organized in exactly the same structure as they did in the Title. Starting from OnDemand 9.1, developers work within a Library which will typically contain Topics for multiple applications. Topics are now organized via Outlines, and it is these Outlines that are used to create the Player packages. The way in which Topics are organized within an Outline need not bear any resemblance to the way in which the Topics are organized in the Library. In this chapter, we will look at the Library, and in Chapter 5, Building an Outline we will look at Outlines.
In this exercise, you will:
Accessing the Library
When you start UPK (other than for the very first time—see the note below), the Start Screen window is displayed. (Unless you deselect the Show this screen at startup option at the bottom of this window—see the comments after the following screenshot.) This window allows you to easily find the modules that you most recently accessed, and create outline elements and content elements. You can also choose to convert content from a prior version of UPK, or import content from another implementation of UPK. It also provides you with links to open the Library, or open a specific content object. An example of the Start Screen is displayed in the following screenshot:
Note that you can prevent the Start Screen from being displayed whenever you start UPK by deselecting the Show this screen at startup option at the bottom of the dialog box. If you do this, then UPK will start up from the Library screen.
Tip
The very first time that you access UPK you will be required to go through a few additional steps. These are explained in Appendix A.
If you have access to multiple Libraries, you will also be prompted to select the Library that you want to access, via the Profile Wizard.
To access the Library, click on the Library link. The Developer screen is displayed, showing the selected Library. When you first install UPK and access the Library, it will be almost empty, as shown in the following screenshot:
Note that if you are working in a client/server environment and are accessing an existing Library for the first time, you will see all of the content that you have been given access to. Also, bear in mind that different groups or projects within the same organization may have their own Libraries within the same implementation of UPK, so it is possible that the Library that you see does not reflect the entire content of the UPK server—just the content to which you have been given access.
Working in the Developer screen
The structure of the Developer
