Dive Planed Extentions

Scenarios

Use Cases

Change Servicedescription

• Participating actors: User, Service-Manager
• Entry condition: Click on an Attribute in the Servicedialog
• Flow of events:
  1. User edits the Attributes or creates new Attributes
  2. User confirms the Changes
  3. The Servicedescription is updated by DIVE
• Exit condition: User confirms the Changes by pressing the OK-Button

Connect Services

• Participating actors: User, Service-Manager
• Entry condition: Click on a Servicewidget followed by Click on the a "Connect Services"-Button
• Flow of events:
  1. The User right-clicks on an Ability or a Need and choses "connect to ..."
  2. The User clicks on the Target Ability or Need.
  3. DIVE sets the Atributes of the two Services so that the Servicemanager will connect them.
• Exit condition: Service-Connection-Procedure finished

Introduce new Service

• Participating actors: User, Service-Manager

• Entry condition: Click on a "Service"- or "new Service"-Button (see picture)
• Flow of events:
  1. User Clicks on a Service-Button
  2. DIVE starts the Service
• Exit condition: Service is visible in DIVE or an Error has occured

Introduce and Configure a new Service

• Participating actors: User, Service-Manager
• Includes: Change Servicedescription, Connect Services, Introduce new Service
• Entry condition: User choses to introduce a new Service
• Flow of events:
  1. Introduce new Service
  2. User changes the Servicedescription and Connects the Service
• Exit condition: User is happy with his new Service

-- MarkusGeipel - 11 Nov 2003

• Dive.png: