co-funded by the european union semantic cms community designing interactive knowledge- supported...

Co-funded by the European Union

Semantic CMS Community

Designing Interactive Knowledge-supported Ubiquitous Information Systems

Results from theIKS AmI Case

Copyright IKS Consortium1

NameAffiliation

Date

www.iks-project.eu

Page:

Copyright by Nike

Designing Information Systems

Copyright IKS Consortium

2

"What developers think makes a good system - it works, it's technically elegant, and it's easy to use - is not necessarily what makes people want to use it

- a good fit with their natural incentives and motivation.“ (Markus & Keil, 1994)

www.iks-project.eu

Page:

Designing Information Systems Design process deals with 3 components (Walls et al., 1992)

(1) Design method - describes procedure(s) for the construction of the artifact

(2) Kernel theories - from the natural or social sciences inform the design method, e.g., domain knowledge

(3) Design process hypotheses - as testable results of design process, e.g., theorems or proofs

“A good design of an information system is not only concerned with technically issues but also with managerial ones that affect organizations and their individuals.” (ibid.)


3

www.iks-project.eu

Page:

Principles towards the Design of Information Systems


4

P1 IS has to be "linked“ within the real world, e.g., specification of requirements, use cases and scenarios

P2 Design method has to integrate diverse design steps and stakeholders

P3 Option of discussions about diverse design proposals, e.g., supported by feedback loops

P4 Evaluation of concepts and prototypes

P5 Formalization of system design

P6 Development of functional (rapid) prototypes and their iteration

P7 Guidance through development process in all design steps

(Markus et al., 2002)

www.iks-project.eu

Page:

Principles towards the Design of Information Systems


5




P4 Evaluation of concepts and prototypes

P5 Formalization of system design



User requirements derived from kernel theories

Methodical development process

Methodical development process

Design of System

(Markus et al., 2002)

www.iks-project.eu

Page:

Design Method Pattern 5 generalized phases taken from leading design science

approaches(1) Identification of problem and needs

(2) Design of solution based on scenarios, use cases or requirements

(3) Development of solution

(4) Evaluation of solution and resulting design

(5) Specification of design theory based on experiences and results during application of design method


6

(Hevner et al., 2004; March & Smith, 1995; Pfeffers et al., 2006; Rossi & Sein, 2003; Kuechler & Vaishnavi, 2008)

Identification of Problem and Needs

Design of Solution based on Scenarios,

Use cases, Requirements

etc.

Development of Solution

Evaluation of Solution

Specification of Design

Theory

www.iks-project.eu

Page:

Analysis of 12 Existing Design Methods


7

P(1) P(2) P(3) P(4) P(5) P(6) P(7)Taylor & Swan, 2005 ● ● n/a - - - -

Ross & Keyson, 2007 ● ○ n/a ● - - ●

Le Rouge & Niederman, 2006

● ● ● - ● - ○

Crabtree & Rodden, 2004

● ● n/a - - - -

Schmidt et al., 2007 ● ● ○ - ● ● ○Peronne et al., 2005 ● ● ○ - ● ● ○Strömberg et al., 2004 ● ● n/a - - - -Mackay, 2004 ● ○ n/a - - - -Maiden et al., 2004 ● ● ● - - - -Buur et al., 2004 ● ● ● - - - -Chung et al., 2004 - - ● ● - - ○Aaen, 2008 n/a n/a n/a n/a n/a n/a ○

(● =Complete; ○ =Partly; - =No match; n/a =Not applicable)

www.iks-project.eu

Page:

Design Method for Interactive Knowledge-supported Ubiquitous Information Systems

Requirements:(1) Focus on social interactions between agents supported by

technical services

(2) Consideration of physical objects

(3) Environments of Ubiquitous Information System (UIS) cannot be fully specified, i.e. UIS designs should be flexible enough to cope with a range of unpredictable events and entities.

(4) Flexibility is supported by strongly modularized computing environments (Yoo 2010)

Situational Design Method for Information Systems (SiDIS)


8

www.iks-project.eu

Page:


9 .

www.iks-project.eu

Page:


Methodological approach of SiDIS is based on three Conceptual Model (CM) types

Abstract from technical issues and focus on aspects of situations in which users and user groups perform activities supported by information and communication services (Wand et al., 1995)

Shared understandings and vocabularies between different stakeholders during design process (Wand et al., 1995; March & Smith, 1995)

Described by various notations conceptual modeling language (CML) , e.g., Entity-Relationship (Chen,1976) models; Unified Modeling Language (UML) etc.


10

www.iks-project.eu

Page:

Towards Explicit Domain Knowledge


11

Implicit domain knowledge

Explicit domain knowledge expressed by

a non-formal language

Explicit domain knowledge expressed by a formal

language

Individual Conceptual Modeling Conceptual Modeling

System Design, Implementation, Execution

Translation 1 Translation 2

Languages: vocabularies, thesaurus, class diagrams, OWL Light, UML in particular diagrammatic languages

Languages: natural language, ‘language of thought’ In particular natural languages

Languages: OWL-DL, OWL2, OWL-Full, PL1, higher-order PL, non-logical mathematical languages in particular symbolic languages

www.iks-project.eu

Page:

Problems with UML (Simons & Graham, 1999)

e.g., Use case diagrams Supposed to be independent of any formal design conceptual

structures by use cases mislead developers about design structures Logical faults are introduced; prevent use case model from scaling up

to large systems Non-logical relationships development of illogical use case models

that have to be completely deconstructed later during design e.g., Class diagrams

Strength and weakness of UML's class diagram = ability to capture wide variety of semantic relationships anticipated, but not interpreted associations between entities in the analysis domain

Richness of representation confuses developer “They are wrestling simultaneously with analysis and design perspectives, with data modelling and client-server functional dependency perspectives, all in the same diagram.”


12

www.iks-project.eu

Page:

Situational Design Method for Information Systems (SiDIS) – 3 CM Types

(1) Narrative conceptual models of situations

(2) Diagrammatic conceptual models (Pre-Artifacts)

(3) Propositional conceptual models


13

It’s Thursday morning. Anna get site-specific weather information when she is brushing her teeth in the bathroom.

www.iks-project.eu

Page:

Principles towards the Design of Information Systems SiDIS


14

Principle Fulfillment of principle by SiDIS


Resulting UIS is linked to real world through creativity workshops and work with real world situations


Integration of diverse design steps and stakeholders, e.g., domain experts, users etc.


Feedback loops

P4 Evaluation of concepts and prototypes Diverse evaluation steps during design process

P5 Formalization of system design Representation of system design in formalized way


Development of rapid prototypes, i.e. mock-ups


Guidance during all design steps according to design method pattern

www.iks-project.eu

Page:



15

Ap

plie

d in

IKS

Identification of Problem and

Needs



etc.


Evaluation of Solution and

Specification of Design Theory


www.iks-project.eu

Page:

SiDIS Task 1: Identification of Problems and Needs

What is the problem that shall be solved? What is the motivation to design a solution?

Identification of (business or private) problems and needs Workshops with domain experts to identify problem that has to be

solved by the intended solution

Outcome: Description of (business or private) problems and/or needs

Involved stakeholders: Domain experts and computer scientists


16

www.iks-project.eu

Page:

Application of SiDIS Task 1 in IKS Workshops with Duravit (manufacturer of high-end

bathroom furniture) Direct user interaction with contents in the bathroom

Merging physical world of furniture with digital world of contents

No “small windowsto the digital world“ Holistic product design

USP compared tocompetitors


17

Copyright by Duravit

http://youtu.be/Dhpucf3UbxQ

www.iks-project.eu

Page:



18

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 2: Derivation of situations (narrative CMs)

Imagine, the intended solution would be already available: How would it be used in everyday life?

Specification of usage situations in the domain of interest according to problems and needs defined together with domain experts

Situations are textual descriptions of different entities -objects, roles, information, environments, services etc. – performing particular activities and interacting with each other

Outcome: Specification of usage situations in form of narratives Involved stakeholders: Domain experts and computer scientists


19

www.iks-project.eu

Page:

What is a Situation?


20

“(1) Manner in which an object is placed; location, esp. as related to something else; position; locality site; as, a house in a pleasant situation. (2) Position, as regards the conditions and circumstances of the case. (3) Relative position; circumstances; temporary state or relation at a moment of action which excites interest, as of persons in a dramatic scene. […] (Webster's Revised Unabridged Dictionary)

„(1) The way in which something is positioned vis-à-vis its surroundings. (2) The place in which something is situated; a location. (3) Position or status with regard to conditions and circumstances. (4) The combination of circumstances at a given moment; a state of affairs. […]“ (Wiktionary)

(Century Dictionary Online)

www.iks-project.eu

Page:

Narratives?


21

“[…] To-day we shall not meet. Yesterday, when we said good-bye, the clouds began gathering over the sky and a mist rose. I said that to-morrow it would be a bad day; she made no answer, she did not want to speak against her wishes; for her that day was bright and clear, not one cloud should obscure her happiness.[…]” (White Nights, Fjodor Dostojewski)

“I have just returned from a visit to my landlord — the solitary neighbour that I shall be troubled with. […]” (Wuthering Heights, Emily Brontë)

www.iks-project.eu

Page:

Application of SiDIS Task 2 in IKS

Creativity workshop with Duravit Part A: Generation of ideas via Brainwriting Pool method

Development of situations together step by step Selection of situations via Spot method 12 resulting situations

Part B: Application of situations in real bathroom environment Specification of thematical scopes, e.g., emotion,

personalization; information types and forms, physical devices


22

www.iks-project.eu

Page:



23

Retrieval of site-specific weather information as well as free-time event suggestions according to weather forecast. Synchronization with calendar.

green: IT; red: information; yellow: realization of information

Example situation:

www.iks-project.eu

Page:


Derivation of narrative CMs based on situations

How to write a narrative within SiDIS?- Focus on entities of situation (actors, roles, information,

environments) and interactions between them- Instance level not type level- No technical or implementatory aspects- Understandable for everyone- Short and sweet


24

Narrative 1Anna gets site-specific weather information when she is brushing her teeth in the bathroom. Based on weather information and her calendar, free-time event suggestions are given, e.g. "Today, 8 p.m. - Miss Marple Night at CinemaOne. Do you want to order tickets?”

www.iks-project.eu

Page:



25

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 3: Derivation of diagrammatic CMs

How to represent narratives in a structured, diagrammatic form?

Translation of narrative CMs into semi-formal, diagrammatic CMs

Highlighting essential elements of each narrative

Outcome: Representation of narrative CMs in form of semi-formal diagrammatic CMs

Involved stakeholders: Knowledge engineers and computer scientists


26

www.iks-project.eu

Page:

Generic Model of Conceptual Modeling

Useful conceptual modeling approaches “should enable both mappings without

loss of information” [Wand et al. 1995].

The distinction between CMs and design models for information systems gets

blurred if CMs can be executed [Wand et al. 1995] based on formal ontologies

[Evermann 2009].


27

Consistency, syntactic, and

semantic interoperability are

major obstacles for working with

different CMLs [Booch &

Rambaugh 1999], e.g., Rational

Unified Process (RUP) provides

159 key resulting artifacts that

are created and used during the

software development process

[Kruchten 2003].

Conceptual Modeling

CMα(Dα, Lα, Oα)

CMγ(DΥ, LΥ, OΥ)

IS Ontology O

Modeling Method M

Conceptual Modeling

Language L

CM(D, L, O)

Domain Ontology D

www.iks-project.eu

Page:

SiDIS Task 3: Diagrammatic CMs Pre-Artifacts

Information System composition of Information Sphere, Social System, Service System (Lamb & Kling, 2003; Lechner & Schmid, 2001; Orlikowski & Barley, 2001)

UIS additional fourth level: Physical Object System (Abstract Information System Model (AISM), Maass & Janzen, 2011)

Pre-Artifacts conceive usage situations by highlighting requirements on social structures, information objects, physical objects and services of the UIS


28

www.iks-project.eu

Page:

SiDIS Task 3: Pre-Artifacts


29

www.iks-project.eu

Page:

SiDIS Task 3: Pre-Artifact Patterns


30

Role

P1: Role Interaction

P4: Service Interaction

P2: Service takes Role

Roler-interacts

Information Object

usedIn

s-interacts

Information Object

usedIn

Internal Service Internal ServiceInterface Service

Interface Service

takesRole

Interface Service

P3: Service uses Information Object

Internal ServiceInterface Service

Information Object

receivedBy

P5: Role uses Information Object

Information Object

receivedByInformation

Object

creates

Role

Role

or

or or

Interface Service

supportsAction


uses

or


uses

or

supportsAction

supportsAction

Information Object

creates

Role

takesRole

Interface Service

Role

supportsAction

P6: Role uses Service

P7: Role creates Information Object

www.iks-project.eu

Page:

SiDIS Task 3: Exemplary Pattern RoleInteraction


31

Role


Roler-interacts

Information Object

usedIn

Interface Service

supportsAction

Boss


Dogbertr-interacts

Question

usedIn

Hotline Service

supportsAction

www.iks-project.eu

Page:

SiDIS Task 3: Construction of Pre-Artifacts in 5 Steps

Step 1: Definition of Information Objects (IO) in Infosphere Step 2: Definition of user-system or user-user interactions related to IO Step 3: Definition of Roles taken by Services Step 4: Definition of supporting Internal Services Step 5: Definition of user initiative


32

www.iks-project.eu

Page:

Application of SiDIS Task 3 in Duravit Case

Empirical study (n=46) to validate 12 narratives 7 relevant narrative CMs

Derivation of 17 Pre-Artifacts that represent narratives in a diagrammatic form In case of high complexity of narrative multiple Pre-Artifacts

are generated to avoid overloading of diagrammatic structure

Library of diagrammatic conceptual models


33

www.iks-project.eu

Page:

Application of SiDIS Task 3 in Duravit Case: Exemplary Translation of Narrative CM into Pre-Artifact


34

It's Thursday morning. I get site-specific weather information when I am brushing my teeth in the bathroom. Based on weather information and my calendar, free-time event suggestions are given, e.g. "Today, 8 p.m. - Miss Marple Night at CinemaOne. Do you want to order tickets?”

Copyright by Duravit

www.iks-project.eu

Page:

SiDIS Task 3: Construction of Pre-Artifacts Step 1

Step 1: Definition of Information Objects in Infosphere

All information objects that occur in a narrative are defined as Information Objects (IO) in the Infosphere.

Why? Information Objects are subjects of any later interaction!

Description of goal, i.e. intention of user in situation

Note always take the perspective of the user when modeling!


35

www.iks-project.eu

Page:


Step 2: Definition of user-system or user-user interactions related to Information Objects.

interactions between users or user and system related to newly generated information objects have to be defined

interactions take place between Roles in the Social System exclusively

Interactions between user and system are always supported by a service of the Service System (defined later in Step 3)

Application of Role Interaction pattern


36

www.iks-project.eu

Page:


37

Slide 37Mai 2011

© Prof. Dr.-Ing. Wolfgang Maass

Role

Internal Service

Information Object

Interface ServiceS

erv

ice

Sy

ste

mS

oc

ial

Sy

ste

mIn

fos

ph

ere

It's Thursday morning. I get site-specific weather information when I am brushing my teeth in the bathroom.

Goals

a) Getting weather information for user‘s location[User]

Notation

Global Weather

Information

Site-specific Weather

Information

User

Location

Personalized Weather Assistant

r-interacts

usedIn

Action

Personalized Weather Service

supports Action

Step 1 & 2: Definition of Information Objects (IO) in Infosphere; Definition of user-system or user-user interactions related to IO

www.iks-project.eu

Page:


Step 3: Definition of Roles taken by Services

interface service has to be defined that takes a role for creating the new information object that will be used in the interaction

service has to take a role in the interaction

Option (1) service is linked to a role that was already defined in step 2 or option (2) it adds a new role

Application of RoleCreatesInformationObject and ServiceTakesRole pattern


38

www.iks-project.eu

Page:


39

Slide 39Mai 2011


Role

Internal Service

Information Object

Interface ServiceS

erv

ice

Sy

ste

mS

oc

ial

Sy

ste

mIn

fos

ph

ere

Goals


Notation

Global Weather

Information


Information

User

Location


r-interacts

usedIn

Action


supports Action

takes Role

creates

supports Action

Step 3: Definition of Roles taken by Services


www.iks-project.eu

Page:


Step 4: Definition of supporting Internal Services

To create new information objects, generic information sources are needed interface service that supports the creation of a new IO needs access to these sources

Internal Services for all remaining information objects in the Infosphere have to be specified

Interaction between services regarding information objects is realized by applying the Service Interaction and ServiceUsesInformationObject pattern


40

www.iks-project.eu

Page:


41

Slide 41Mai 2011


Role

Internal Service

Information Object

Interface ServiceS

erv

ice

Sy

ste

mS

oc

ial

Sy

ste

mIn

fos

ph

ere


Goals


Notation

Global Weather

Information


Information

User

Location


r-interacts

usedIn

Action


supports Action

takes Role

creates

supports Action

Weather Service s-interacts

usedIn

User Context Services-interacts

usedIn

Step 4: Definition of supporting Internal Services

www.iks-project.eu

Page:


Step 5: Definition of user initiative

If a user role initiates an interaction with the system situation is modeled by using the Role uses Service or Role uses Information Object pattern

role uses a service to create or receive an information object, for instance, the user wants to leave a message for another user

action is indirectly supported by a service


42

www.iks-project.eu

Page:



43

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 4: Evaluation of diagrammatic CMs

Will services represented in Pre-Artifacts be accepted by future users?

Pre-Artifacts are evaluated to generate preliminary implications regarding user acceptance

Usage of mock-ups at early stage of design process Focus on information objects delivered by services that are

represented in Pre-Artifacts

Outcome: Preliminary implications for design of IS regarding user acceptance

Involved stakeholders: Potential early adopters of IS, domain experts


44

www.iks-project.eu

Page:


111 potential early adopters participated in evaluation

Subjects came from 3 countries in Europe: Germany, Switzerland and Turkey

Pre-Artifacts were presented with the help of a mock-up, i.e. a midget bathroomwith dolls, and a slideshow that exemplifiedthe information delivered by services


45

www.iks-project.eu

Page:


After presentation of situations covered by Pre-Artifacts, participants had to rate the relevant services within questionnaire


46

Rank Situation Service Intention to Use Perceived FitNo Name Mean SD Mean SD

1. 6 4 Personalized Music Service

6.28*** 0.87 6.07***

1.13

2. 1 1 Weather Information Service

5.64*** 1.54 4.87***

1.69

3. 6 5 Personalized News Collage Service

5.11*** 1.94 4.84***

1.83

4. 1 2 Event Recommendation Service

4.65*** 1.69 4.12 1.65

5. 11 6 Adaptive News Service 4.17 1.85 3.88 1.82

6. 1 3 Ticket Order Service 3.82 1.73 3.47** 1.77

www.iks-project.eu

Page:



47

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 5: Derivation of formal propositional CMs

How can diagrammatic representations of situations be processed by the future system?

Translation of Pre-Artifacts into propositional CMs Manual, automatic or semi-automatic translation possible Creation of specifications for later system designs (Wand

et al., 1995) and machine-processable CMs that can be verified (Bera et al., 2010)

Outcome: Library of formalized design patterns Involved stakeholders: Knowledge engineers


48

www.iks-project.eu

Page:

SiDIS Task 5:Use of Web Ontology Language (OWL)

Use of computational ontologies for conceptual modeling by means of a pattern-based approach (Clark et al., 2000, Gangemi, 2005)

Pros Web Ontology Language (OWL) is implementable, which means

OWL ontologies are machine-readable, and thus computational. OWL constructs are independent, i.e. classes can exist

independent of instances or properties and properties are independent of classes.

Verification: OWL allows inferences and automated reasoning support.


49

www.iks-project.eu

Page:

SiDIS Task 5: Approach – Use of Web Ontology Language (OWL)

Cons no clear rules how to map from domain information as

represented by Pre-Artifacts to OWL constructs similar to the intended propositional CMs

How to generate propositional CM based on propositional Pre-Artifact Patterns?


50

www.iks-project.eu

Page:

SiDIS Task 5:Approach of Generating Propositional CM


51

Creation of Pre-Artifact Model = “vocabulary”of Pre-Artifact patterns (basic entities and relations of AISM)

Import of Pre-Artifact Model by each pattern ontology

www.iks-project.eu

Page:



52

Specified object properties by

ServiceInteraction, RoleInteraction and RoleUsesIO pattern

Each pattern imports Pre-Artifact Model Specification of pattern-specific object

properties through inheritance structures Definition of sub properties of generic object

properties imported from the model super-properties and concepts of Pre-

Artifact Model remain unchanged

www.iks-project.eu

Page:



53

Clear assignments of object properties to specific patterns

Support by modeling guidelines - canalization of modeling options

Incremental modeling of propositional CM by importing patterns step by step according to the requirements of the Pre-Artifact

Super properties of Pre-Artifact Model filled automatically

Sub properties by three patterns regarding individual of type InterfaceService: PersonalizedWeatherService

www.iks-project.eu

Page:

Application of SiDIS Task 5 in Duravit Case


54

Translation of 17 Pre-Artifacts into propositional CMs OWL files

Modeling in 5 steps similar to procedure of defining Pre-Artifacts

Exemplary modeling of aforementioned Pre-Artifact It's Thursday morning. I get site-specific weather

information when I am brushing my teeth in the bathroom.

www.iks-project.eu

Page:



55

Generating empty OWL file Required Pre-Artifact Patterns can be imported by their URL

Start of modeling according to 5 steps Import of RoleInteraction Pattern

www.iks-project.eu

Page:



56

Instantiation of relevant concepts of pattern Instances of Role: User, PersonalizedWeatherAssistant Instance of R-Interaction to represent interaction between

roles

www.iks-project.eu

Page:



57

Pattern offers specific object properties “initiatesR_ Interaction” and “finalizesR_Interaction” that inherit from super-properties

<owl:ObjectProperty rdf:about="http://im.dm.hs-furtwangen.de/ontologies/preartifacts/2010/RoleInteraction# initiatesR_Interaction">

<rdfs:domain rdf:resource="http://im.dm.hs-furtwangen.de/ontologies/ami-case/preartifacts/PA-Model.owl#Role"/>

<rdfs:range rdf:resource="http://im.dm.hs-furtwangen.de/ontologies/ami-case/preartifacts/PA-Model.owl#R_Interaction"/>

<rdfs:subPropertyOf rdf:resource="http://im.dm.hs-furtwangen.de/ontologies/ami-case/preartifacts/PA-Model.owl#initiatesInteraction"/></owl:ObjectProperty>[…]<Model:Role rdf:about=" http://im.dm.hs-PA1A.owl#PersonalizedWeatherAssistant">

<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Thing"/><RoleInteraction:initiatesR_Interaction rdf:resource="http://im.dm.hs-

furtwangen.de/ontologies/preartifacts/2010/RoleInteraction#R_Interaction1"/></Model:Role>

www.iks-project.eu

Page:



58

Super properties of Pre-Artifact Model are filled automatically Further imports of Pre-Artifact Patterns Role Uses IO and Service

Interaction Final representation of interface service Personalized

WeatherService:

<Model:InterfaceService rdf:about="#PersonalizedWeatherService"><rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Thing"/><RoleUsesIO:supportsCreation rdf:resource="#Creation_1"/><RoleUsesIO:interfaceServiceTakesRole

rdf:resource="#PersonalizedWeatherAssistant"/><RoleInteraction:supportsR_Interaction rdf:resource="#R_Interaction1"/><ServiceInteraction:finalizesS_Interaction

rdf:resource="#S_Interaction_3"/><ServiceInteraction:finalizesS_Interaction

rdf:resource="#S_Interaction_4"/></Model:InterfaceService>

www.iks-project.eu

Page:



59

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 6: Formalization of System Design


60

How does the architecture of the future system look like?

Formalization of system design based on library of design patterns analysis of layers of propositional CMs

Service System and Social System Which services shall be provided by the intended system? Which internal services need to deliver information objects? Which information objects are required by each internal service Which interface services take a role in an interaction with the

user? Which interface services are used by users to interact? Which service interactions take place?

www.iks-project.eu

Page:

SiDIS Task 6: Formalization of System Design


61

Information Sphere Which information objects have to be requested from external services? Which information objects have to be created by the system itself? How about format and storage of information objects (data

infrastructure)?

Physical Object System How will the interaction of user and system be realized? How will information objects be presented? How is the I/O behavior of the system? Does the system need information about the available physical objects?

Outcome: Specification of system design Involved stakeholders: Computer scientists

www.iks-project.eu

Page:

SiDIS Task 6:Approach of setting up the System Architecture

Performing the following steps, based on the answers to the questions on the prior slides: Realization of Service System as independent software modules,

which perform the required functionalities Realization of software modules for the User Interaction based on

the requirements of the Social System Information Objects stored as Knowledge Models for the

representation to the user in the appropriate situations Physical Object System realized by several sensing,

interpretation and output modules

Encapsulation of functionalities required for the management of the UIS in additional software modules


62

www.iks-project.eu

Page:

Application of SiDIS Task 6 in IKS:Modules of Designed System in High-Level Logical Architecture


63

www.iks-project.eu

Page:

Application of SiDIS Task 6 in IKS:Modules of Designed System


64

Interaction & Presentation Device Input/Output Management for the presentation of

content items and the sensing of events and actions in the bathroom environment

Device Integration for the management of devices performing the actions mentioned above

Ambient Management Situation Management for processing of propositional CMs,

the evaluation of the current situation and based on this the next steps that need to be performed by the system

Context Management for the general management of retrieved content items and contextual information (e.g. user profiles, system location etc.)

www.iks-project.eu

Page:

Application of SiDIS Task 6 in IKS:Modules of Designed System


65

Content Retrieval & Semantic Lifting Content Retrieval Pipeline for the retrieval of external (non-semantic)

contents Knowledge Extraction Pipeline for the semantic refactoring, filtering or lifting

of retrieved external contents to standardized content items

Knowledge Representation & Reasoning Knowledge Access and Rules & Reasoning for the management, access

and modification of the situational and contextual knowledge models Content Access for the management, access and modification of content

files (e.g. news videos, images of event recommendations)

Persistence Knowledge Repository for the persistent storing and access of ontology

based knowledge models Content Repository for the persistent storing and access of simple content

objects

www.iks-project.eu

Page:

Application of SiDIS Task 6 in IKS:Conjoint Modules of IKS Semantic CMS and AmI Case System


66

IKS Semantic CMSarchitecture

AmI Case SystemLogical Architecture

The blue marked modules indicate modules that exist in both architectures

www.iks-project.eu

Page:



67

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 7:Implementation of formalized system design


68

Coding!

Formalized system design is transformed into machine-processible code modules in system design realized as software components

Use of propositional CMs as knowledge models for the physical situation management

Information Objects stored as knowledge models for the interaction with the user

UIS code has to be linked with hardware components integrated in the physical environment

Outcome: Prototype of information system Involved stakeholders: Computer scientists

www.iks-project.eu

Page:

Application of SiDIS Task 7 in IKS: Management of Information Objects and Physical Situation

69

Context Ontology Network as knowledge representation of Information Objects Propositional CMs and Current Situation representation as knowledge

representation for the evaluation of the appropriate situation in the UIS Determination of current and upcoming situation based on semantic rule sets

www.iks-project.eu

Page:

Application of SiDIS Task 7 in IKS:Reuse of IKS Stack Components in the System on the Conjoint Layers IKS VIE^2:

Used on the User Interaction layer to enable the user to not only view content items in the bathroom, but also browse semantically referenced resources, i.e. information about actors or the director in case of movie event suggestions

Apache Stanbol Entity Hub,Apache Stanbol CMS Adapter,Apache Stanbol Reengineer and Apache Stanbol Rules:

Used in the Knowledge Access, Content Retrieval & Knowledge Extraction Pipeline and Rules & Reasoning layers to retrieve contents from external content and knowledge sources, lift them on a semantic level and refactor them to be represented as AmI ODPs


70

www.iks-project.eu

Page:

Application of SiDIS Task 7 in IKS:Reuse of IKS Stack Components in the System on the Conjoint Layers


71

Apache Stanbol Enhancer:

Used in Content Retrieval & Knowledge Extraction Pipeline and Rules & Reasoning to enable the system to prepare the semantic enhanced contents required by VIE^2

Apache Stanbol Ontology Manager:

Used on the Knowledge Repository layer to enable the persistent storage and browsing of knowledge representations by the system or the user by using the Store sub component; the OntoNet sub component is also implicitly used by other components for reasoning and refactoring issues

www.iks-project.eu

Page:



72

Implementation according to OSGi standard 7 IKS Stack/Apache Stanbol components could be re-used for the

realization of the UIS 4 developer teams from Turkey, Italy and Germany • 500 kg of furniture

• 15 sqm bathroom• 5x3 meter walls• 50 liter wall paint• 18 sqm floor• 3 microphones• 2 sound systems• 2 projectors & 3 sqm

projection foil• 1 touch screen• 1 camera• 1 MS Kinect• 2 sensor boards with 4

touch- & 6 distance sensors

• 2 PCs, 1 Mac Mini• app. 100 meter of cable

…

www.iks-project.eu

Page:



73

Ap

plie

d in

IKS


Needs



etc.





www.iks-project.eu

Page:

SiDIS Task 8: Evaluation of solution


74

Does the prototype fit to the natural incentives and motivation of potential end users?

IS is evaluated by traditional empirical studies laboratory experiments field experiments

Outcome: feedback for earlier design phases laboratory experiments: understanding of adoption (ease of use,

utility, risk, task-technology fit, etc.), purchase intentions field experiments: usage behavior, social influence, behavioral

change Involved stakeholders: Computer scientists, end users

www.iks-project.eu

Page:



75

55 subjects have evaluated 6 services in a lab experiment with constructs from Technology Acceptance research (e.g., Davis 1989)

Subjects had to play through the 3 Situations from SiDIS Task 4

IK point Mirror

• Weather Information Service• Event Recommendation Service• Ticket Order Service• Personalized News Collage Service• Adaptive News Service

IK point eScreen

IK point Shower

• Personalized Music Service• Personalized News Collage Service• Adaptive News Service

Interaction Border(touch-sensitive)

• Personalized News Collage Service• Adaptive News Service

Array microphoneArray microphone

Array microphoneSpeaker

SpeakerDistance sensorDistance sensor

www.iks-project.eu

Page:



76

Mean values, standard deviation (in parentheses) and results of one-sample t-tests are shown below; Significance: * = p < .05 / ** = p < .01 / *** = p < .001

Results: Personalized Music Service is ranked highest

www.iks-project.eu

Page:



77

Results from Interviews:

The widgets on the touchscreen are distracting. The mirror as such should be the

“main functionality” in the bathroom. Thus the content should be placed more in

the periphery (23)

There was no design or concept behind the content presentation, e.g., the widgets

on the touchscreen seemed to be positioned without any layout in mind; the IKS

logo should be smaller and more semi-transparent to reduce distraction (10)

Weather information was too lean (e.g., no information about rain probability,

moisture, forecast, morning, noon, afternoon, etc.) (9)

The positioning of the widgets on the touchscreen should be more flexible (9)

Size of the projection on the wall screen was too small (7)

More information about price and category of when ordering a ticket (6)

Note: the number in parentheses reflects the number of subjects that gave this feedback

www.iks-project.eu

Page:

Wrap-up


78

Design Method for interactive knowledge-supported Ubiquitous Information Systems Situational Design Method for Information System (SiDIS)

Consists of 4 phases covering 9 tasks according to Design Method pattern (Hevner et al., 2004; March & Smith, 1995; Pfeffers et al., 2006; Rossi & Sein, 2003; Kuechler & Vaishnavi, 2008)

Bases on 3 types of Conceptual Models (CMs): Narrative CMs of situations Diagrammatic CMs (Pre-Artifacts) Propositional CMs

Closing gap between qualitative requirements (cf. narratives) and formal, machine-processable structures (cf. propositional CMs)

www.iks-project.eu

Page:


79 .

www.iks-project.eu

Page:

Publications


80

Walls, J.G., Widmeyer, G.R., Sawy, O.E.: Building an information system design theory for vigilant eis. Information Systems

Research 3(1) (1992) 36-59

Markus, M.L., Keil, M.: If we build it, they will come: Designing information systems that people want to use. Sloan Management

Review 35 (1994) 11-25

Markus, L.M., Majchrzak, A., Gasser, L.: A design theory for systems that support emergent knowledge processes. MIS Quarterly

26(3) (2002) 179-212

Pries-Heje, J., Baskerville, R.: The design theory nexus. MIS Quarterly 32(4) (January 2008) 731-755

Hevner, A.R., March, S.T., Park, J., Ram, S.: Design science in information systems research. MIS Quarterly 28(1) (2004) 75-105

March, S.T., Smith, G.F.: Design and natural science research on information technology. Decis. Support Syst. 15(4) (1995) 251-

266

Pfeffers, K., Tuunanen, T., Gengler, C.E., Rossi, M., Hui, W., Virtanen, V.e.a.: The design science research process: A model for

producing and presenting information systems research. In: Proceedings of the First International Conference on Design Science

Research in Information Systems and Technology (DESRIST 2006), Claremont, CA, USA (2006) 83106

Rossi, M., Sein, M.K.: Design research workshop: A proactive research approach. (2003)

Kuechler, W.L.J., Vaishnavi, V.K.: An expert system for dynamic re-coordination of distributed workows. Expert Syst. Appl. 34(1)

(2008) 551-563

Ross, P., Keyson, D.V.: The case of sculpting atmospheres: towards design principles for expressive tangible interaction in control

of ambient systems. Personal Ubiquitous Comput. 11(2) (2007) 69-79

Le Rouge, C.M., Niederman, F.: Information systems and health care xi: Public health knowledge management architecture

design: A case study. Communications of the Association for Information Systems 18 (2006)

Schmidt, A., Terrenghi, L., Holleis, P.: Methods and guidelines for the design and development of domestic ubiquitous computing

applications. Pervasive Mob. Comput. 3(6) (2007) 721-738

www.iks-project.eu

Page:

Publications (cont.)


81

Perrone, V., Bolchini, D., Paolini, P.: A stakeholders centered approach for conceptual modeling of communication-intensive

applications. In: SIGDOC '05: Proceedings of the 23rd annual international conference on Design of communication, New York,

NY, USA, ACM (2005) 25-33

Strömberg, H., Pirttila, V., Ikonen, V.: Interactive scenarios|building ubiquitous computing concepts in the spirit of participatory

design. Personal Ubiquitous Comput. 8(3-4) (2004) 200-207

Mackay, W.E.: The interactive thread: exploring methods for multi-disciplinary design. In: DIS '04: Proceedings of the 5th

conference on Designing interactive systems, New York, NY, USA, ACM (2004) 103-112

Maiden, N., Manning, S., Robertson, S., Greenwood, J.: Integrating creativity workshops into structured requirements processes.

In: DIS '04: Proceedings of the 5th conference on Designing interactive systems, New York, NY, USA, ACM (2004) 113-122

Buur, J., Jensen, M.V., Djajadiningrat, T.: Hands-only scenarios and video action walls: novel methods for tangible user interaction

design. In: DIS '04: Proceedings of the 5th conference on Designing interactive systems, New York, NY, USA, ACM (2004) 185-

192

Chung, E.S., Hong, J.I., Lin, J., Prabaker, M.K., Landay, J.A., Liu, A.L.: Development and evaluation of emerging design patterns

for ubiquitous computing. In: DIS '04: Proceedings of the 5th conference on Designing interactive systems, New York, NY, USA,

ACM (2004) 233-242

Aaen, I.: Essence: Facilitating agile innovation. In: XP. (2008) 1-10

Alexander, C.: The timeless way of building. Oxford University Press, New York (1979)

Clark, P., Thompson, J., Porter, B.: Knowledge patterns. In: In Proc. of KR-2000, Morgan Kaufmann (2000) 591-600

Gangemi, A.: Ontology design patterns for semantic web content. In: Proceedings of the Fourth International Semantic Web

Conference, Springer (2005) 262-276

Y. Yoo, Computing in Everyday Life: A Call for Research on Experiential Computing, Mis Quart, 34(2) (2010) 213-231.

P. Chen, The Entity-Relationship Model--Toward a Unified View of Data, ACM Transactions on Database Systems, 1(1) (1976) 9-

36.

www.iks-project.eu

Page:

Publications (cont.)


82

Davis, F.D. (1989). Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology. MIS

Quarterly, 13(3), 319-339.

Maass, W. & Janzen, S.: Pattern-Based Approach for Designing with Diagrammatic and Propositional Conceptual Models,

6th International Conference on Design Science Research in Information Systems and Technology (DESRIST 2011),

Milwaukee, Wisconsin, USA, 2011.

Janzen, S., Kowatsch, T. & Maass, W.: A Methodology for Content-Centered Design of Ambient Environments, DESRIST

2010: Global Perspectives on Design Science Research, St. Gallen, Switzerland, 2010.

Maass, W. & Varshney, W.: A Framework for Smart Healthcare Situations and Smart Drugs. SIG-Health Pre-AMCIS

Workshop at the 15th Americas Conference on Information Systems (AMCIS 2009). San Francisco, USA.

co-funded by the european union semantic cms community designing interactive knowledge- supported...

Documents