The main objective of most iRise simulations is to give project stakeholders an opportunity to experience software requirements, rather than merely reading them. This is where iRise Reader comes in.
iRise Reader allows reviewers to control the simulation experience. Whether a project is reviewed on a Definition Center or an iDoc is opened from the reviewer’s desktop, iRise Reader enables stakeholders to interact and engage with the simulation in their default web browser.
Your goal as a modeler is to ensure that reviewers experience your simulation the way you intended. To this end, the most important thing you can do is test your simulation often as you build, and as you will see in this tutorial, testing is a seamless, efficient process with the iRise platform.
Watch this video to see a quick demonstration of some of the testing features in iRise Reader:
While working in iRise Studio, you can launch your simulation at any time by clicking the green launch button above the Widget Toolbar. The chapter you are currently viewing will open in iRise Reader ready for review.
Rather than launching a new browser window each time you want to test your simulation, you can keep the initial window open and simply refresh the page to see any changes you made in Studio.
Note: iRise Reader installs with iRise Studio. For non-Studio users, offline iDoc reviews (those for projects not hosted on a Definition Center) require that users download the free iRise Reader application from our web site.
The Directory and toolbars that frame the simulation in iRise Reader provide access to features that support simulation review. The Directory enables quick navigation of the project, and the toolbars (top and bottom) provide access to Guides, Comments and other simulation controls. Some of these elements are particularly suited to simulation testing as opposed to stakeholder reviews. Let’s look at these elements in more detail.
The project Directory that appears in iRise Reader is a read-only version of the Directory in Studio. The structure is identical, but the editing tasks and other functions you can access in Studio are not available.
Ideally, your simulation reviewers should not be required to use the Directory to navigate your project. Since the objective is to simulate the experience of using the real application, all navigation should be accomplished from within the pages of your simulation. The Directory is present in the Reader framework mainly as a convenience for you as the modeler, since it enables you to navigate manually in your project without having to switch back to Studio and relaunch the simulation from another page. The same can be said of the page navigation controls in the Reader’s status toolbar.
When testing your simulation from the reviewer’s perspective, you should look for dead-ends that require you to use the Directory or page navigation controls. Usually, these indicate flaws in your simulation flow that should be fixed before conducting a real project review.
Guides are annotations that you can add to your simulations to provide additional information to reviewers. The toggle button in the Reader’s status toolbar enables a reviewer to turn Guides on or off. When you launch a simulation from Studio, Guides are turned off by default so you can focus on the simulation. When testing your simulation from the reviewer’s perspective, turning Guides on will allow you to check their functionality and contents to make sure they provide the intended assistance without hindering the stakeholder’s review. (Note: Guides are turned on by default when a simulation is launched from an iDoc or on a Definition Center.)
The Reader framework can be customized to your current task or to suit your preferences.
There are a number of features in iRise Reader that were designed primarily as simulation testing tools for the modeler. Two of these are the Set page views dialog and the Data Tracker.
A dynamic display is a method of embedding dynamic content on a page that involves alternate “Views.” These Views are invoked when the reviewer interacts with the simulation, which should be a transparent process. When testing your simulation, however, having the ability to switch manually between the different Views in a dynamic display can come in handy.
The Views toggle button on the left side of the Reader’s status bar works the same as the corresponding one in Studio. The button is only active when a dynamic display is present on the current page. Clicking the button opens a pop-up box that lists the dynamic displays on the page and enables you to switch between the associated Views manually.
Choosing View > Data tracker from the Reader’s menu bar reveals the Data Tracker window. The Data Tracker can be used to see how data is passed through the simulation and how the simulation logic executes.