Interaction Space

[drleidig]

A Service Interface has an InteractionType*, which specifies two aspects:

*shouldn't it be InterfaceType?

1. How the inteface is used (manually or automated)
2. Where the interaction takes place

The second topic:

They can be used to model on-site/"we go to them". Nonetheless, the onsite/"they come to us" is not captured.

Maybe the business models bricks and clicks can be use.

3 cases exist:

1. Remote (anywhere via click or phone or WS), aka ubiquitous
2. On-site provider (customers need to go to provider) - brick-and-mortar
3. On-site customer. Can be fixed or dynamic. Fixed = always the same location (e.g. home); dynamic = location varies (e.g. on the road assistance)

Best,
Jorge

[jorge-cardoso]

For the location where the service is provided, 4 cases exist:

1. Remote (anywhere via ICT click or phone or WS), aka ubiquitous, virtual or digital for both
2. On-site provider (customers need to go to provider) - brick-and-mortar
3. On-site customer (provider needs to go to customer) . Can be fixed or dynamic. Fixed = always the same location (e.g. home); dynamic = location varies (e.g. on the road assistance)
4. Other place/location (both provider and customer need to move somewhere)

This would make the concept simple and complete. I would assume that any additional information needed is domain-dependent, and, thus should not be part of the model.