| ID | 5.3.1 |
| Title | Mechanisms for design-time and run-time dynamic service composition |
| Expert | Maarten Steen (TELIN) |
| Priority | mandatory |
| Description | Service composition needs to be done at design-time and at run-time. Design-time composition ranges from support for professional service developers to ad-hoc creation of a new service, e.g. through natural language input. Run-time composition resolves the abstract interface descriptions of the component services to actual, vailable service instances, e.g. through the use of a service broker. |
| Rationale | Design-time composition will support the service creation process directly. It also includes ad-hoc service creation, maybe by end-users. Run-time composition supports various forms of dynamic selection of a used service needed during the lifetime of the system (new versions, better offers, competing services) or when users are roaming. |
| Type | functional |
| Depends on | |
| Child dependencies | |
| Environment | |
| Other_info | |
| Category | technical |
| Subcategory | SPICE Service Creation Environment |
| Subcategory2 | service composition |
| Scenario_scene | unified.scene2 |
| SPICE_value | service creation;service execution |
| Demo | concept |
| Keywords | service creation;SCE;service description language;service composition;service brokering;design-time composition;runtime composition;ad-hoc composition;composition;broker;ACE |
