The goal of this exercise is to extend a task by adding
a contribution.
About this task
By now you should start to see the general pattern with this
variability mechanism. Recall that contributions append text in appropriate
fields from one content package to another.
Procedure
- Switch back to the Authoring perspective.

- Create a new task in the contribution_test content
package.
- Use the following attributes for this task:
- Name: my_contributing_task
- Presentation name: My Contributing Task
- Brief Description: Contributing Brief Description text
- Purpose: Contributing Purpose text
- Main Description: Contributing Main Description text
Tip: If the Link name with presentation
name for new method element option in Preferences is selected,
typing a presentation name will auto-generate the name field.
- Click the Steps tab and add two new steps named
"Contributing Step 1" and "Contributing Step 2".
- Click the Description tab. In the Variability
Relationship section, select Contributes and click Select.
The Select Dialog: Tasks window opens.
- Select architectural_analysis and click OK.
This will be the base element for our contribution.
- Go back to the Steps tab and click Order.
Use the Up and Down buttons to reorder the steps. Note
that you can now insert your new steps into the original sequence
of steps inherited from the base. This is a good example of the power
of variability contributions.
- Save the new task by closing the editor panel.
- Switch to the
Browsing
perspective. Make sure that you are using My Basic Configuration.
- Expand Disciplines > RUP Disciplines
> Analysis & Design . Double-click the Architectural Analysis task.
The content panel shows a preview of the generated page.
Look at the steps to see how your new material
was contributed. You should see the text that you included in the
contributing task displayed in the Architectural Analysis task.
- You can also try specifying additional artifacts, guidance,
and additional performer roles in the contributing task (using the
Authoring perspective) and then view the result in the Configuration
view to see the behavior.