CSCE 826 Cooperative Information Systems

1
CSCE 826Cooperative Information Systems

• Prof. Michael N. Huhns
• Department of Computer Science and Engineering
• University of South Carolina
• huhns_at_sc.edu

2
Global Best Practices (Arthur Andersen)
Produce and deliver for manufacturing organization
Understand markets and customers
Develop vision and strategy
Design products and services
Market and sell
Invoice and service customers
Produce and deliver for service organization

• Develop and manage human resources
• Manage information
• Manage financial and physical resources
• Execute environmental management program
• Manage external relationships
• Manage improvement and change

3
Multi-Industry Process Technology (Price
Waterhouse)
Define products and services
Perform marketing and sales
Produce products and services
Manage logistics and distribution
Perform customer service

• Perform business improvement
• Manage environmental concerns
• Manage external relationships
• Manage corporate services and facilities
• Manage financials
• Manage human resources
• Provide legal services
• Perform planning and management
• Perform procurement
• Develop and maintain systems and technology

4
What is CIS?

• CIS is concerned with how decentralized
  information system components, consisting of
  resources, applications, and human-computer
  interfaces, should coordinate their activities to
  achieve their goals. When pursuing common or
  overlapping goals, they should act cooperatively
  so as to accomplish more as a group than
  individually when pursuing conflicting goals,
  they should compete intelligently

5
Properties of CIS

• Decentralization
• Complex components, best described at the
  knowledge level
• Complex interactions
• Adaptive behavior
• Coordination

6
Heritage of CIS
Semantic Web
Databases
Economics
Most work
Sociology
Linguistics
Cooperative Information Systems
Cognitive Science
Psychology
Systems Theory
Distributed Computing
7
Service-Oriented Computing Web Services and
Beyond

• Munindar P. Singh
• Dept. of Computer Science
• North Carolina State University

Michael N. Huhns Dept. of Computer Science
Engr. University of South Carolina
John Wiley Sons, Ltd. West Sussex, UK 2004
8
The Web As Is

• Designed for people to get information
• HTML describes how things appear
• HTTP is stateless
• Sources are independent and heterogeneous
• Processing is asynchronous client-server
• No support for integrating information
• No support for meaning and understanding

9
Trends in Services

• Toward the Semantic Web
• Human ? Machine
• Passive ? Active
• Client-Server ? P2P
• Syntax ? Semantics

10
Beyond the Semantic Web

• Client-Server and P2P ? Cooperative
• Semantics ? Mutual Understanding ? Pragmatics and
  Cognition
• Services ? Processes

Future Web Services focus on organization and
society
Pragmatics (getting work done) - Workflows,
BPEL4WS
Distributed Cognition - Decisions and Plans
Semantics and Understanding - Ontologies, DAML-OIL
Syntax, Language, and Vocabulary - FIPA ACL
Current Web Services focus on individual and
small group
11
What is a Web Service?

• " a piece of business logic accessible via the
  Internet using open standards (Microsoft)
• Encapsulated, loosely coupled, contracted
  software functions, offered via standard
  protocols over the web (DestiCorp)
• A set of interfaces, which provide a standard
  means of interoperating between different
  software applications, running on a variety of
  platforms and/or frameworks (W3C)
• Our working definition A WS is functionality
  that can be engaged over the Web

12
Viewpoints on Services

• Networking a service is characterized by
  bandwidth and suchlike properties.
• Telecommunications Narrow telephony features
  such as caller ID and call forwarding, and basic
  connection services like narrowband versus
  broadband (itself of a few varieties).
• Systems Services are for billing and storage and
  other key operational functions. These functions
  are often parceled up in the so-called
  operation-support systems.
• Web applications Services correspond to Web
  pages, especially those with forms or a
  programmatic interface thereto.
• Wireless Wireless versions of the Web, but also
  things like messaging, as in the popular short
  message service (SMS).
• If there is agreement here, it is that a service
  is a capability that is provided and exploited,
  often but not always remotely.

13
NSF Workshop WS Scope
All
Any html page
People
Program
amazon.com
Hard code
Standard
currency.com
Self-described
Semantic
Formally described
14
Motivations for Composable and Cooperative
Services
15
Applications of Composition

• Portals
• Organized by topic or affinity
• Best when personalized
• E-commerce
• Legacy system integration
• Virtual enterprises
• Grid computing

16
Open Environments Characteristics

• Cross enterprise boundaries
• Comprise autonomous resources that
• Involve loosely structured addition and removal
• Range from weak to subtle consistency
  requirements
• Involve updates only under local control
• Frequently involve nonstandard data
• Have intricate interdependencies

17
Open Environments Technical Challenges

• Coping with scale
• Respecting autonomy
• Accommodating heterogeneity
• Maintaining coordination
• Getting work done
• Acquiring, managing, advertising, finding,
  fusing, and using information over uncontrollable
  environments

18
Autonomy

• Independence of users
• Political reasons
• Ownership of resources
• Control, especially of access privileges
• Payments
• Technical reasons
• Opacity of systems with respect to key features,
  e.g., precommit

19
Heterogeneity

• Independence of component designers and system
  architects
• Political reasons
• Ownership of resources
• Technical reasons
• Conceptual problems in integration
• Fragility of integration
• Difficult to guarantee behavior of integrated
  systems

20
Locality

• Global information (data, schemas, constraints)
  causes
• Inconsistencies
• Anomalies
• Difficulties in maintenance
• Global information is essential for coherence
• Locations of services or agents
• Applicable business rules
• Relaxation of constraints works often
• Obtain other global knowledge only when needed
• Correct rather than prevent violations of
  constraints often feasible
• When, where, and how of corrections must be
  specified, but it is easier to make it local

21
Dynamism

• Entities change dynamically in their
• Architecture and implementation
• Behavior
• Interactions