Situational Enterprise Services

Situational Enterprise Services

Paul de Vrieze (Bournemouth University, UK), Lai Xu (Bournemouth University, UK) and Li Xie (GuangDong Polytechnic Normal University, China)
DOI: 10.4018/978-1-4666-9787-4.ch060

Chapter Preview



The ability to rapidly find potential business partners as well as rapidly set up a collaborative business process is desirable in the face of market turbulence. Collaborative business processes are increasingly dependent on the integration of business information systems. Traditional linking of business processes has a large ad hoc character. Implementing situational enterprise services in an appropriate way will deliver the business more flexibility, adaptability and agility.

Service-oriented computing paradigm continues to transform traditional enterprise systems from close, centralized control systems into systems that feature dynamic information exchange and flexible business processes. Traditionally enterprise applications are defined as software designed to integrate all aspects of a company's operations and processes such as accounting, finance, human resources, inventory control, manufacturing, marketing, sales, and distribution, and resource planning. Advanced enterprise applications provide linkages with customers, business partners, and suppliers (Markus & Tanis, 2000). Normally enterprise applications are complex. These are mission critical applications which are developed, deployed and maintained by central IT with long development deployment cycles and dedicated IT budgets. A significant part of the value of these systems derives from links among systems. When these components were not initially designed for linking, this often makes the resulting systems brittle due to the workarounds used (de Vrieze et al. 2011).

At the same time, the current highly dynamic business environment provides increased pressure to build enterprise applications quickly in order to respond in an agile way to these situational needs of the business. Unfortunately, many of these applications (reflecting situational business needs) never get delivered because they are too difficult to write, too costly to implement, and too brittle to customize and maintain once deployed. As a result, many of the needs of the business are addressed by business people who have some knowledge on IT techniques and who devise ad-hoc partial solutions using tools like Excel, Access and Visual Basic. These solutions are often inadequate from many perspectives, including manual processes needed, maintenance and visibility.

With a growing number of services on the Web, these situational needs can now be satisfied more easily and effectively. These development and deployment services, combined with a “situational” mindset and methodology, can offer significant advantages. Unlike traditional enterprise applications, situational enterprise applications are relatively simple. They are not missioning critical for organizations. Lots of them can be developed at the point of need, with short development cycles, outside the direct central IT control, and with little or no recognized budget. The centralized platform at the same time does allow for corporate monitoring.

These situational enterprise applications will not replace core business applications, such as ERP (Enterprise Resource Planning), SCM (Supply Chain Management), CRM (Customer Relationship Management) etc. They address different needs which are built for just handfuls of users, and may be used for only a few weeks or months, or to address a small piece of functionality. For example, within the perimeter ERP applications, departmental operational solutions, such as vacation scheduling, seminar and presentation management, purchase procedure management within a work unit, etc, normally are not included in an corporate ERP system. The functionality can however be desired by department staffs. From a corporate government perspective, the use of “free” external solutions is problematic, and as such this a typical situational applications for the department staff who manage those matters on a daily basis.

The types of situational enterprise applications can be divided into data-oriented applications and process-oriented applications. Enterprise widgets, gadgets, pipes and mash-ups belong to data-oriented applications. Lightweight process-oriented applications have been, and continue to be under research. The EU project SOA4All (

Key Terms in this Chapter

Service-Oriented Architecture (SOA): A software design paradigm in which designers use loosely coupled services for building complex services or for incorporating them into systems.

Situational Enterprise Applications: Enterprise applications which are relatively simple and not missioning critical for organizations. Lots of them can be developed at the point of need, with short development cycles, outside the direct central IT control, and with little or no recognized budget.

Situational Enterprise Services: Services as semantically annotated web services, enterprise services and semantically annotated web-based resources, such as annotated widgets, gadgets, pipes, feeds and mash-ups.

Web Services: Software services designed to support interoperable XML based machine-to-machine interaction over the Internet.

Data-Oriented Enterprise Applications: Enterprise applications with aggregating and processing data.

Process-Oriented Enterprise Applications: Enterprise applications with an essential sense of state or process.

Enterprise Services: Highly-integrated web services combined with business logic and semantics that can be accessed and used repeatedly to support a particular business process.

Complete Chapter List

Search this Book: