Services (applications) that can be loosely coupled and bind dynamically with other services over the Internet
Exposing applications while hiding private business logics
Public interfaces and defined bindings
Discoverable by other software systems
Other services may interact as prescribed
Promising technology
Several critical unresolved problems
Need for Theory
Current status
Use of formal theories
Narrow concerns
Piecemeal approach
Lack of holistic perspective
Complexity of the domain
Complex and overlapping standards
Adoption delays
Core of Web Services
Communication is the core
Used for performing actions such as advertising, searching, requesting
A Candidate Theory
Language-Action Perspective (LAP)
Work in organizations is performed through language (Weigand 2006)
Language is used to perform actions as in promises, orders, requests, and declarations
Foundation: Speech Act Theory (Searle 1969)
Long history:SAMPO (Auramaki et al. 1988), DEMO (Dietz 1994), BAT (Goldkuhl 1996), FLBC (Moore 2001)
The Key Challenge
Opportunities
Both LAP and web services share the core: communication to achieve business goals
Challenges
LAP is founded on human to human communication theories
Constraints / modifications needed to support communication among services
Research Questions
Research Methodology
RQ1. Conceptual development and logical argument (Weick 1989)
RQ2. Design science research (Henver et. al. 2004)
RQ3. Controlled experiment (Shadish et al. 2001)
Essay 1
RQ1: Can LAP constructs describe and explain the web services architecture?
LAP-Inspired Framework
Essay 1: Outcomes
LAP-inspired reference framework
A Theoretical Investigation of the Emerging Standards for Web Services. Information Systems Frontiers (ISF), March 2007. 9 (1), pg. 119-134.
Special issue on web services
Service-oriented Computing: An Opportunity for the Language-Action Perspective? International Working Conference on the Language-Action Perspective on Communication Modelling (LAP), 2004
Introducing the early ideas to the LAP community
Essay 2
RQ2: How can LAP constructs be used for supporting design of web service solutions?
Selected domain: Enterprise Integration
Integrating disparate system functionalities (Lee et. al. 2003)
Enterprise integration tasks
Understanding requirements (as business processes)
How to design good web services-based integration solutions?
Enterprise Integration using Web Services
Enterprise Integration using Web Services
A Methodology
Design Support
Essential Components
Parsimonious set of speech acts (9 speech acts)
Source: Electronic messaging systems (Moore 2001) and Design principles for application integration (Johannesson and Perjons 2001)
Representing EI patterns as sequence of speech acts (22 patterns)
Source: Enterprise Integration Pattern (Hohpe and Woolf 2004)
Action types to depict high-level business actions (11 Actions types)
Source: Business activity descriptions in UML specification (UML 2005)
Associations between action types and speech acts
Inferring patterns and composing a solution
Knowledge base represented with OWL (OWL 2004)
Inference rules with Bossam OWL reasoner (Bossam 2006)
Individual patterns need to be composed into integration solution
Implementation Support
Research Prototype
Essay 2: Outcomes
Methodology and Prototype along with Several Components
Domain: Enterprise Integration with Web Service
Utilizing: Mapping with Speech Acts
Assessment of Web Services Specifications to Support Long-Running Conversations. Workshop for Information Systems and Technology (WITS). 2006
Designing Enterprise Solutions with Web Services and Integration Patterns. IEEE Service Computing Conference (SCC). 2006
Designing Under the Influence of Speech-Acts-based Enterprise Integration Patterns. Conceptual Modeling Conference (ER). 2006
Facilitating Conversations among Web Services as Speech-act based Discourses. Workshop for Information Systems and Technology (WITS). 2003
Essay 3
RQ3: Is design support with LAP constructs effective for designing web service solutions?
Justify utility of LAP constructs for accessing integration patterns
Evaluating effectiveness of the integration solutions produced
Presence or absence test
Dependent variables
Design errors
Design effort
Hypotheses
H1: Designs produced with the support of LAP constructs contain fewer design errors than designs produced without the support of LAP constructs
H2: Designs produced with the support of LAP constructs require less design effort than designs produced without the support of LAP constructs
H3: The use of design support with LAP constructs lead to greater reduction in design errors for complex integration problems than for simple integration problems
H4: The use of design support with LAP constructs lead to greater reduction in design effort for complex integration problems than for simple integration problems
Data Collection
Design errors
Number of design defects in the solution
Type I (omission errors)
Type II (commission errors)
Type III (inconsistency errors)
Design effort
Number of tasks performed and time taken
Research prototype records user activities with time stamp in a log file
Pre and post questionnaire to gather user details on demographics, skill sets and knowledge on enterprise integration
Subjects
Students who have taken or enrolled in an enterprise integration course
Recap
ITP: a possible mapping
Next Steps
Refinement of research prototype
Develop enterprise integration problem scenarios
Develop pre and post questionnaires
Get IRB approval
Conduct pilot study
Determine number of requirements to distinguish simple and complex problems
Determine time and procedure for final experiments
Perform mock analysis on the sample data set
Conduct final experiments
Data analysis
Expected Contributions
Research
Demonstrating effectiveness of LAP as a theory-base for web services
Insights for development and refinement of web service standards
Model and approach for using integration patterns as design knowledge
Mechanism for translating integration solutions into service conversations
Practice
Guidance to stakeholders to understand interoperable architecture
Mechanisms to design and develop web service-based EI solutions
Demonstrating practical utility of LAP constructs to solve web service problems
Expected Contributions
To the web services community
Establishing need for holistic theoretical framework
LAP-inspired framework to identify missing elements
Possible extension to Service Sciences
Contribution of ‘theory’
To the LAP community
Web services as opportunity to reach mainstream
To the IST community
Using multi-disciplinary theories to develop solutions
Using multiple methodologies at different levels
Thank You!
Commonalities Among Initiatives
Evaluation Against Theory Selection Criteria
Selected theory’s historical context
Historical application of LAP to message-oriented phenomena
Selected theory’s sensitivity towards details of the phenomenon under study
Focus on communication instead of data
Selected theory’s impact on the choice of research method
Inapplicable in the context of this work because our research method relies on the conceptualization of a new reference architecture
Selected theory’s contribution to cumulative theory-building
By suggesting LAP as a theoretical framework, our selection directly contributes to theory-building in the domain of web services
LAP-Inspired Framework
Assessment of LAP-Inspired Framework
Insights from LAP-Inspired Framework
Enterprise Integration
Capability of integrating disparate system functionalities (Lee et. al. 2003)
Integration difficulties
Enterprise systems are autonomous by design
Heterogeneity of the platforms and languages
Understanding requirements
Business Process Example
A fragment from customer order processing business process from WS-I Supply Chain Management scenario
Enterprise Integration Pattern Example
Publish-Subscribe Channel
Delivers a copy of a particular event to each receiver
Speech Acts and Action Types
Representing Integration Patterns
Business Process Modeling Notation
Graphical notation for drawing a Business Process (BPMN 2006)
Follows control chart technique, easy to understand
Develop business process model to describe integration requirements
Core elements:
Enterprise Integration Patterns
Provides abstraction of integration strategies and tactics
Follows message-oriented integration
Individual integration patterns can be composed into integration solution
Source
Gregor Hohpe and Bobby Woolf, Enterprise Integration Patterns. Addison-Wesley, 2004
Contains 65 patterns
Six categories
Speech Act Theory
Developed for natural language
Views communication as performance of an action (Searle 1969)
Core aspect is illocution of a message
Intention of the speaker to utter a message to receiver
e.g., a request to turn on the air conditioner or an assertion about the temperature
Knowledge Base
Knowledge base capturing relationship between components