All Collections
Using Reader and Player
Reviewing a Project in a Web Browser
Reviewing a Project in a Web Browser
This articles describes reviewing a project in your browser using Player.
Jamie Gutierrez avatar
Written by Jamie Gutierrez
Updated over a week ago


iRise is an incredibly versatile platform for visualizing software requirements. However, the true power of the platform is realized when project stakeholders have the opportunity to experience the visualization and provide feedback.
The iRise Player enables reviewers to see, interact with, and comment on visualizations in a familiar Web browser environment. Simple and easily-accessed features enable common tasks—such as adding comments or reviewing text requirements—and specialized tools provide modelers with testing and debugging capabilities.

Launching the Player

How Player is launched depends on the context. While working in iRise Studio, the modeler can always launch the Player by clicking the green Play button.

Opening a project on a Definition Center launches the Player, whether the project is opened from within the project browser in iRise Reader, from a direct link provided by the project owner, or from the Definition Center Web application.
Opening an iDoc also launches the Player. Note that the iRise Reader application is required to open an iDoc file for review.

Reviewing the Project

Once the project has been launched in the Player, you can interact with the simulation, read text requirements, view guides and add comments. Much of this is accomplished through the Player toolbar.

You can collapse the Player toolbar by clicking the button on the far right of the toolbar.

The Project Directory

The button on the far left (the list icon) opens the Player's Directory panel. This panel contains a list of project assets (e.g. scenarios, screens, masters) so reviewers can navigate manually within the project.
Typically, reviewers navigate through a project by following the modeler's instructions (in the form of guides) or simply by interacting with the simulation as if it were a real application. Using the Directory panel might decrease the effectiveness of your review by revealing incomplete screens or by disrupting the intended flow of the simulation.

Did this answer your question?