Tutorial: Create Method Content
Exercise: Create Work Products
The goal of this exercise is to create new method content.
Specifically, you will create Work Products of the type Artifact.
You can create any content but some examples are provided if you want to use them.
These examples are referred to in other tutorials.
In general, you create new elements by right-clicking the folder that will contain the new element.
For example, to create a new Role in a content package, right-click on the Roles folder in the tree navigator,
highlight New and then click Role.
- Make sure you are in the Authoring perspective.
- Within My Content Package right-click on the Work Products folder.
- Highlight New and then click Artifact. The Artifact editor is displayed.
- In the Name field, type the new Artifact name. In this instance, we'll call it my_navmap.
- In the Presentation Name field, enter the following:
My Navigation Map
- In the Brief Description field, enter the following:
The Navigation Map expresses the structure of the user-interface elements in the system,
along with their potential navigation pathways.
- In the Purpose field, enter the following:
There is one Navigation Map per system.
The purpose of the Navigation Map is to express the principal user interface paths through the system.
These are the main pathways through the screens of the system and not necessarily all of the possible paths.
It can be thought of as a road map of the system's user interface.
The Navigation Map makes it easy to see how many "clicks" it will take a user to get to a specific screen.
- Click the Preview tab to view the new Artifact.
- Save the Artifact.
Repeat steps 2 through 9 using the following information:
- Artifact Name: my_user_interface_prototype
- Presentation Name: My UI Prototype
- Brief Description: A user-interface prototype is an example of the user interface that is built in order
to explore and/or validate the user-interface design.
- Purpose:
The following roles use the user-interface prototype:
- User-interface Designers, to explore and/or validate the user-interface design before too much is invested in it
- Requirements Specifiers, to understand the user interface for a Use Case
- System Analysts, to understand how the user interface impacts the analysis of the system
- Designers, to understand how the user interface impacts and what it requires from the "inside" of the system
- Managers, to plan development and testing activities
Continue