Design de services

Résumé

Le design de services s'intéresse à la fonctionnalité et à la forme des services du point de vue de l'utilisateur, l'usager, le client. Il a pour objectif de s'assurer que l'interface du service est utile, utilisable et désirable du point de vue du client et efficace, performante et - quand il s'agit d'un produit commercialisé - « différenciante » du point de vue du fournisseur. Souvent, un service va être associé à un objet ou à des objets permettant l'interaction avec l'utilisateur (borne, application sur téléphone mobile, service Web…). Le « designer de service » va donc s'intéresser aux attentes et aux comportements de l'utilisateur final, pour adapter l'interface et les modalités d'interactions. C'est un domaine alliant les sciences cognitives, les technologies et la créativité. Le design de services repose sur la scénarisation créative d’une succession d’événements, d’actions et de résultats. Il s’agit d’une activité de conception qui organise des informations et des s

Source officielle

https://fr.wikipedia.org/wiki/Design_de_services

À propos de ce résultat

Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.

Publications associées (23)

Publications associées

Chargement

Personnes associées (4)

, , ,

Personnes associées

Chargement

Unités associées (1)

Unités associées

Chargement

Concepts associés (6)

Concepts associés

Chargement

Cours associés (4)

Cours associés

Chargement

Séances de cours associées (1)

Séances de cours associées

Chargement

A Model-Driven Environment for Service Design, Simulation and Prototyping

Biljana Bajic-Bizumic, Claude Petitpierre, Alain Wegmann

Springer2013

Chargement

[Context] With the expansion of services and service science, service systems have become an important abstraction for the service revolution. Service is defined as the application of resources (including competences, skills, and knowledge) to make changes that have value for another (system). The service system is a configuration of people, technologies, and other resources that interact with other service systems to create mutual value. Many systems can be viewed as service systems, including families, cities, and companies, among many others. Therefore, services became very important for unifying concepts from various disciplines. Service specifications are used to represent service systems on different levels of abstraction: from business down to IT. [Motivation and Problem] Traditionally, high-level service specifications are used only for communication among different participants, to catalyze the discussions between them; but only the specifications modeling IT systems have enough details to be simulated and executed. As a consequence, it becomes difficult to create precise high-level specifications and make sure that the implemented services are those that correspond to the business needs, potentially leading to severe project problems. Therefore, the challenge is to create abstract, yet precise service specifications, while keeping the relation between specifications at different levels of abstraction. [Idea and Results] In this work, we use formal methods and code generation techniques to create service-prototypes from service specifications at any level of abstraction, keeping the relations between different specifications. Stakeholders can try out the prototypes and give feedback regarding services that are being provided. This way, prototypes are used to validate the specifications and detect inconsistencies and unexpected behavior. [Contribution] The contributions of our work are threefold. First, we provide the visual formalism for service specification and simulation, by adding the necessary concepts to the existing method SEAM. Second, we define two design spirals: for service specification and for service validation and verification. The service specification spiral enables us to keep the relation between several service specifications. It includes steps with explicit design decisions on how to refine high-level specifications in order to include all the details necessary for providing the identified services. The validation and verification spiral is used to validate and verify specifications at any level of abstraction. Finally, it provides an environment that enables the simulation and prototyping of service specifications that are then used for their validation and verification. [Relevance] In addition to the theoretical contribution to the knowledge base of service design, we also provide the tools and guidelines that help business and IT analysts create and validate the service model, as confirmed by a survey conducted with practitioners. We illustrate the application of this work with a case study based on a consulting project we conducted at EPFL.

EPFL2015

Chargement

, ,

Verification is a costly task, sometimes burdensome and tedious, requiring strong formal background. To reduce the effort and cost invested in verification, we developed a model-driven approach for automatic verification of service properties, done in the early service design phase. Our approach is based on SEAM, a service modeling method, and it incorporates a verification system called Leon. With our approach service designers do not need substantial understanding of specific formal and verification languages, since the SEAM visual service model is both the input for and output of the alignment verification.

2017

Chargement

EPFL2015