- Specify City Service and Domain
- Specify the service and the domains where it belongs to (e.g. health, mobility, environment).
- Identify Function
- Identify the core function of the service, as well as positioning it within the smart city domain.
- Articulate Use Case
- Identify a marketable use case (i.e. primary business case) for the service.
- Clarify Exchange Medium
- Identify a number of remuneration options for the service.
- List Service Actors
- Identify service actors involved in the service co-creation activities.
- Identify Actor Resources
- Identify the resources (e.g. information, skills, knowledge) and assign to the specific actors.
- Define Experience and Value Proposition
- Define a value proposition of the service.
- Perform PESTLE Analysis
- Understand the context within which the service will operate.
- Citizens Feedback in Service Design
- Include the feedback of citizens during the design of the service for effective and better quality of the services.
- Produce Service Description
- Structure and synthesize the information acquired for the purpose of modeling and development.
The Service Architecture process sets in motion the process of Service Description. The purpose of a service description is to provide sufficient amount of information toward the service system modelling and design. The service description includes the “operant” resources of the service system, specifically, the service actors and their interactions. The types of service actors can be private persons, organisations, governments, and even countries, depending on the context (Spohrer et al. 2008) and the depth of the service and the service system analysis.
The Service Architecture lifecycle stage of the Service Design Process (see fig. 1) includes the following main activities and subprocesses:
- Haren, V., 2011. TOGAF Version 9.1. Van Haren Publishing.
- The Open Group. “Open Group Standanotepadrd TOGAF Version 9.1”, 2011.
- Spohrer, J., Anderson, L., Pass, N., & Ager, T. (2008). Service science and service-dominant logic. In Otago forum, 2(2), 4 18.