Co-funded by the European Union Semantic CMS Community Designing Interactive Knowledge- supported Ubiquitous Information Systems Results from the IKS AmI Case Copyright IKS Consortium 1 Lecturer Organization Date of presentation

Page: Copyright IKS Consortium Introduction of Content Management Foundations of Semantic Web Technologies Storing and Accessing Semantic Data Knowledge Interaction and Presentation Knowledge Representation and Reasoning Semantic Lifting Designing Interactive Ubiquitous IS Requirements Engineering for Semantic CMS Designing Semantic CMS Semantifying your CMS Part I: Foundations Part II: Semantic Content Management Part III: Methodologies (2) (1) (3) (4) (5) (6) (7) (8) (9) (10)

Page: What is this Lecture about?  We have introduced... ... software engineering methods for semantic CMS as „traditional“ information systems.  What‘s next?  Methods for the development of ubiquitous information systems need to consider additional aspects, like characteristics of the physical environment. Copyright IKS Consortium 3 Designing Interactive Ubiquitous IS Requirements Engineering for Semantic CMS Designing Semantic CMS Semantifying your CMS Part III: Methodologies (7) (8) (9) (10)

Page: Copyright by Nike Designing Information Systems Copyright IKS Consortium 4 "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)

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.) Copyright IKS Consortium 5

Page: Principles towards the Design of Information Systems Copyright IKS Consortium 6 P1IS has to be "linked“ within the real world, e.g., specification of requirements, use cases and scenarios P2Design method has to integrate diverse design steps and stakeholders P3Option of discussions about diverse design proposals, e.g., supported by feedback loops P4Evaluation of concepts and prototypes P5Formalization of system design P6Development of functional (rapid) prototypes and their iteration P7Guidance through development process in all design steps (Markus et al., 2002)

Page: Principles towards the Design of Information Systems Copyright IKS Consortium 7 P1IS has to be "linked“ within the real world, e.g., specification of requirements, use cases and scenarios P2Design method has to integrate diverse design steps and stakeholders P3Option of discussions about diverse design proposals, e.g., supported by feedback loops P4Evaluation of concepts and prototypes P5Formalization of system design P6Development of functional (rapid) prototypes and their iteration P7Guidance through development process in all design steps User requirements derived from kernel theories Methodical development process Design of System (Markus et al., 2002)

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 Copyright IKS Consortium 8 (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

Page: Analysis of 12 Existing Design Methods Copyright IKS Consortium 9 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., ●● -- ○ Aaen, 2008 n/a ○ (● =Complete; ○ =Partly; - =No match; n/a =Not applicable)

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) Copyright IKS Consortium 10

Page: Copyright IKS Consortium 11 ..

Page: Situational Design Method for Information Systems (SiDIS)  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. Copyright IKS Consortium 12

Page: Towards Explicit Domain Knowledge Copyright IKS Consortium 13 Implicit domain knowledge Explicit domain knowledge expressed by a non-formal language Explicit domain knowledge expressed by a formal language Individual Conceptual Modeling System Design, Implementation, Execution Translation 1Translation 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

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.” Copyright IKS Consortium 14

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 Copyright IKS Consortium 15 It’s Thursday morning. Anna get site- specific weather information when she is brushing her teeth in the bathroom. ① ② ③

Page: Principles towards the Design of Information Systems  SiDIS Copyright IKS Consortium 16 PrincipleFulfillment of principle by SiDIS P1 IS has to be "linked“ within the real world, e.g., specification of requirements, use cases and scenarios Resulting UIS is linked to real world through creativity workshops and work with real world situations P2 Design method has to integrate diverse design steps and stakeholders Integration of diverse design steps and stakeholders, e.g., domain experts, users etc. P3 Option of discussions about diverse design proposals, e.g., supported by feedback loops 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 P6 Development of functional (rapid) prototypes and their iteration Development of rapid prototypes, i.e. mock-ups P7 Guidance through development process in all design steps Guidance during all design steps according to design method pattern

Page: Situational Design Method for Information Systems (SiDIS) Copyright IKS Consortium 17 Applied in IKS Identification of Problem and Needs Design of Solution based on Scenarios, Use cases, Requirements etc. Development of Solution Evaluation of Solution and Specification of Design Theory It’s Thursday morning. Anna get site-specific weather information when she is brushing her teeth in the bathroom.

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 Copyright IKS Consortium 18

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 windows to the digital world“  Holistic product design  USP compared to competitors Copyright IKS Consortium 19 Copyright by Duravit

Page: Situational Design Method for Information Systems (SiDIS) Copyright IKS Consortium 20 Applied in IKS Identification of Problem and Needs Design of Solution based on Scenarios, Use cases, Requirements etc. Development of Solution Evaluation of Solution and Specification of Design Theory It’s Thursday morning. Anna get site-specific weather information when she is brushing her teeth in the bathroom.

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 Copyright IKS Consortium 21

Page: What is a Situation? Copyright IKS Consortium 22 “(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)

Page: What are Narratives? Copyright IKS Consortium 23 “[…] 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ë)

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 Copyright IKS Consortium 24

Page: Application of SiDIS Task 2 in IKS Copyright IKS Consortium 25 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:

Page: Application of SiDIS Task 2 in IKS  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 Copyright IKS Consortium 26 Narrative 1 Anna 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?”

Page: Situational Design Method for Information Systems (SiDIS) Copyright IKS Consortium 27 Applied in IKS Identification of Problem and Needs Design of Solution based on Scenarios, Use cases, Requirements etc. Development of Solution Evaluation of Solution and Specification of Design Theory It’s Thursday morning. Anna get site-specific weather information when she is brushing her teeth in the bathroom.

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 Copyright IKS Consortium 28

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]. Copyright IKS Consortium 29  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

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 Copyright IKS Consortium 30

Page: SiDIS Task 3: Pre-Artifacts Copyright IKS Consortium 31

Page: SiDIS Task 3: Pre-Artifact Patterns Copyright IKS Consortium 32 Role P1: Role Interaction P4: Service Interaction P2: Service takes Role Role r-interacts Information Object usedIn s-interacts Information Object usedIn Internal Service Interface Service takesRole Interface Service P3: Service uses Information Object Internal Service Interface Service Information Object receivedBy P5: Role uses Information Object Information Object receivedBy Information Object creates Role or Interface Service supportsAction Internal Service Interface Service uses or Internal Service Interface Service uses or supportsAction Information Object creates Role takesRole Interface Service Role supportsAction P6: Role uses Service P7: Role creates Information Object

Page: SiDIS Task 3: Exemplary Pattern RoleInteraction Copyright IKS Consortium 33 Role P1: Role Interaction Role r-interacts Information Object usedIn Interface Service supportsAction Boss P1: Role Interaction Dogbert r-interacts Question usedIn Hotline Service supportsAction

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 Copyright IKS Consortium 34

Page: Application of SiDIS Task 3 in IKS  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 Copyright IKS Consortium 35

Page: Application of SiDIS Task 3 in IKS: Exemplary Translation of Narrative CM into Pre-Artifact Copyright IKS Consortium 36 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

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! Copyright IKS Consortium 37

Page: SiDIS Task 3: Construction of Pre-Artifacts Step 2  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 Copyright IKS Consortium 38

Page: Application of SiDIS Task 3 in IKS: Exemplary Translation of Narrative CM into Pre-Artifact 39 Slide 39 Mai 2011 © Prof. Dr.-Ing. Wolfgang Maass Role Internal Service Information Object Interface Service Service System Social System Infosphere 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

Page: SiDIS Task 3: Construction of Pre-Artifacts Step 3  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 Copyright IKS Consortium 40

Page: Application of SiDIS Task 3 in IKS: Exemplary Translation of Narrative CM into Pre-Artifact 41 Slide 41 Mai 2011 © Prof. Dr.-Ing. Wolfgang Maass Role Internal Service Information Object Interface Service Service System Social System Infosphere 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 takes Role create s supports Action Step 3: Definition of Roles taken by Services It's Thursday morning. I get site-specific weather information when I am brushing my teeth in the bathroom.

Page: SiDIS Task 3: Construction of Pre-Artifacts Step 4  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 Copyright IKS Consortium 42

Page: Application of SiDIS Task 3 in IKS: Exemplary Translation of Narrative CM into Pre-Artifact 43 Slide 43 Mai 2011 © Prof. Dr.-Ing. Wolfgang Maass Role Internal Service Information Object Interface Service Service System Social System Infosphere 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 takes Role create s supports Action Weather Service s-interacts usedIn User Context Service s-interacts usedIn Step 4: Definition of supporting Internal Services

Page: SiDIS Task 3: Construction of Pre-Artifacts Step 5  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 Copyright IKS Consortium 44

Page: Literature on SiDIS Copyright IKS Consortium 45  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,  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,  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.

Page: Further Publications Copyright IKS Consortium 46  Walls, J.G., Widmeyer, G.R., Sawy, O.E.: Building an information system design theory for vigilant eis. Information Systems Research 3(1) (1992)  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)  Markus, L.M., Majchrzak, A., Gasser, L.: A design theory for systems that support emergent knowledge processes. MIS Quarterly 26(3) (2002)  Pries-Heje, J., Baskerville, R.: The design theory nexus. MIS Quarterly 32(4) (January 2008)  Hevner, A.R., March, S.T., Park, J., Ram, S.: Design science in information systems research. MIS Quarterly 28(1) (2004)  March, S.T., Smith, G.F.: Design and natural science research on information technology. Decis. Support Syst. 15(4) (1995)  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)  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)  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)  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)

Page: Further Publications (cont.) Copyright IKS Consortium 47  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)  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)  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)  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)  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)  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)  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)  Gangemi, A.: Ontology design patterns for semantic web content. In: Proceedings of the Fourth International Semantic Web Conference, Springer (2005)  Y. Yoo, Computing in Everyday Life: A Call for Research on Experiential Computing, Mis Quart, 34(2) (2010)  P. Chen, The Entity-Relationship Model--Toward a Unified View of Data, ACM Transactions on Database Systems, 1(1) (1976)  Davis, F.D. (1989). Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology. MIS Quarterly, 13(3),