iRise Studio is the authoring tool for iRise projects. It is a desktop application that allows you to create simulations (in Simulation View) and write requirements or annotations (in Document View). The capabilities of iRise Studio are extended by the iBloc™ API, which enables the creation of custom widgets and actions that can be used in iRise projects.
Watch this video for a quick introduction to the Studio modeling environment:
The Studio Welcome Screen appears when you first open iRise Studio. From the Welcome Screen, you can:
If you do not want the Welcome Screen to appear each time you launch iRise Studio, select the checkbox in the lower left corner of the Welcome Screen. You can also choose whether or not to display the Welcome Screen from the Studio Preferences dialog by selecting Edit > Preferences from the iRise menu in Windows or iRise Studio > Preferences in Mac OSX, and either checking or unchecking the Show Welcome Screen checkbox under General Preferences. You can open the Welcome Screen at any time from the View menu (or the Help menu in Studio versions prior to 8.10).
Note: You cannot interact with the Studio workspace, including the main menu, while the Welcome Screen is open. To bypass the Welcome Screen and activate the Studio UI, click the Close button in the lower right corner of the Welcome Screen.
The Studio environment is organized around its two primary purposes: to simulate user interfaces, and to capture text requirements. To make it easy to switch between these activities, two “views” — Simulation View and Document View — are available when you are working in Studio. Toggling between them is simply a matter of clicking the associated button above the workspace or pressing F9 on your keyboard (Command-Fn-F9 on a Mac).
Note: There are two project components for which the Simulation/Document View paradigm does not apply, both of which are covered elsewhere in these tutorials: Datasheets and Notes.
The workspace is the main area in the middle of the Studio window where scenarios are built, pages are assembled, masters are created, decisions are defined, datasheets are maintained, and requirements are written. For components like pages and clouds, the gray area surrounding the page is called the canvas. Navigation and data widgets (e.g., Action, Link and Record widgets) are placed on the canvas, and are therefore referred to as Canvas widgets. Page Layout and User Input widgets (e.g., Text, Image, Text Area and Button widgets) are placed on the page, and are therefore referred to as Page widgets.
The following UI features are present in both Simulation and Document View.
The vast majority of the work you do in iRise will take place in Simulation View. All of your scenario flows, page layout components, interactions, and simulation logic – everything involved with the visualization of your requirements – will be added and configured in Simulation View.
The following Studio UI features appear only in Simulation View:
Document View is the view in Studio that allows you to write annotations or requirements related to your simulation. You can organize your requirements hierarchically and associate them with specific page widgets. You can also apply basic formatting and add hyperlinks.