Modeling with Nickname
CRC Recreation Club's main aim is to provide all sort of sports and recreation facilities for their members to be involved as a mean to promote healthy lifestyles. The club is planning to computerize some of its services. Now, we are going to study a simple use case diagram which shows the services that CRC Recreation Club want and need to computerize. To facilitate internal communication and ease of documentation, we want to maintain a set of internal naming to those use cases, as well as to record extra information like the risk and the developer(s) involved. These information is not expected to be visible to CRC Recreation Club. To achieve this, we will make use of the feature nickname.
| April 29, 2010 | |
User Rating:
/ 0
|
|
| Views: 2,890 | |
|
PDF
Link
Link: |
Add comments |
| Edition: Standard or above (Edition comparison) | |
- Download the project CRC Recreation Club.vpp attached with this tutorial.
- Start VP-UML.
-
Open CRC Recreation Club.vpp. Open the use case diagram CRC Recreation Club Use Case Diagram and take a look.
To facilitate internal communication and ease of documentation, we want to give those use cases a special code. But due to the design will be reviewed by the end user, we do not want to add the code directly on diagram. To solve this problem, we can make use of nickname. - Select View > Nicknames > Configure Nicknames... from the main menu.
- Click Add in the Configure Nickname dialog box. Enter Internal as name and click OK. Click OK in configure dialog box to go back to diagram.
- Now, the model is under the nickname set Internal. To prove this, take a look at the toolbar and you should see the drop down menu as shown below.
- Now, we can rename the use cases freely. Let's append code U1, U2 and U3 to use cases Workout, Play Mahjong and Apply for Membership. The same action can be done for any other kinds of model element. But in this tutorial we just focus on use case for simplicity.
- Further to the names, we can also provide nickname-specific documentation. Open the specification of use case U1 - Workout first. Right click on it and select Open Specification... from the popup menu.
- In the documentation pane, add development level content as shown in the image below.
- Edit also the documentation of other use cases.
- The changes we have made so far were all under the Internal nickname. If we want to carry on with the original content, switch back to the Original nickname. Select Original from the nickname drop down menu.
- You can immediately see that U1, U2 and U3 are gone.
- Let's check the documentation. Those internal text written under Internal nickname set are gone as well.
- If you switch to Internal nickname again, those internal content will be back. With this, you can define another set of model, like internal in this case, without affecting the primary one.
Resources
Rate this Article
Click on one of the stars below to rate this article from 1 (lowest) to 5 (highest).
Comments (1)
written by Dr Olukunmi 'Lanre OLAITAN, Ph.D. on October 25, 2010
This model is of great benefit to the member and public user of recreational facilities. It creates avenue for good planning, coordinating, management and controlling of the recreational facilities in the Gym and / or community recreation parks.