Create use case scenarios

You can generate a "blank" Sequence Diagram from the selected use case. You can also create the set of model elements that allow functional modeling of the selected use case.

About this task

Any Actors connected to the Use Case are added as Lifelines to the diagram.
  • If Harmony-SE structure is being used then the Use Case Block from the FunctionalAnalysisPkg for the use case is added as a lifeline.
  • If not a Harmony-SE structure is used, then the use case is added as a lifeline instead.
In either case, the generated Sequence Diagram is added as a Referenced Sequence Diagram to the selected Use Case/Activity view.

Procedure

  1. Right-click on the use case or activity, and select from the dropdown menu Add New > Use Cases > Use Case.
  2. When invoked, the tool:
    1. Looks for the appropriate package for the selected use case in the Harmony-SE project structure, such as FunctionalAnalaysisPkg > Use Case Package > Use Case BB Scenarios Package.
    2. If not found then the generated sequence is generated into the same package as the Use case:
      • If a use case is selected, then each Actor connected to the use case is added as a lifeline.
      • If an activity is selected then the tool finds the corresponding use case for the activity, and adds it as a lifeline.
      • If the model has a Harmony-SE structure, then the Block that represents the use case is added as a lifeline.
      • If the model has not a Harmony-SE structure, hen the use case itself is added as a lifeline.
      • The generated sequence is added as a referenced sequence diagram to the Activity View or Use Case that invoked the helper.
  3. To create a system model from a use case, right-click on the use case and select use case.
  4. When invoked, the tool:
    1. Checks the validity of the Use Case name, since functional model elements must have names that can be run.
      • Spaces are allowed in Use Case names. The tool automatically removes these spaces from the corresponding functional model names.
      • The use cases names must not start with a digit.
    2. Checks the FunctionalAnalysisPkg Package:
      • The FunctionalAnalysisPkg package must exist at root level.
      • The FunctionalAnalysisPkg package must be read-write. For details, see the Automatic Checkouts topic.
    3. Collects the list of Actors connected to the Use Case.
    4. Creates the Functional Model:
      • Actors collected in a list are moved to the ActorPkg .
      • The Use Case is moved to its corresponding functional package (as shown below)
      • Additional model elements are created in the FunctionalAnalysisPkg as shown in the below example.
      • Additional model elements are created in the FunctionalAnalysisPkg as shown in the below example.
    5. Sets the following properties:
      • ObjectModelGe.Class.ShowPortsInterfaces with a value of 0.
      • ObjectModelGe.Object.ShowPortsInterfaces with a value of 0.
      • ObjectModelGe.Object.ShowAttributes with a value of None.
      • ObjectModelGe.Object.ShowOperations with a value of None.
    6. Sets the WebComponents.Attribute.WebManaged property to a value of True on the generated Block.

Feedback