Welcome to the InfoSci Platform
Reference Hub1
Service Science and Automation Laws

Service Science and Automation Laws

Andrew Targowski
Copyright: © 2009 |Pages: 23
ISBN13: 9781605660042|ISBN10: 1605660043|ISBN13 Softcover: 9781616924935|EISBN13: 9781605660059
DOI: 10.4018/978-1-60566-004-2.ch011
Cite Chapter Cite Chapter

MLA

Andrew Targowski. "Service Science and Automation Laws." Information Technology and Societal Development, IGI Global, 2009, pp.254-276. https://doi.org/10.4018/978-1-60566-004-2.ch011

APA

A. Targowski (2009). Service Science and Automation Laws. IGI Global. https://doi.org/10.4018/978-1-60566-004-2.ch011

Chicago

Andrew Targowski. "Service Science and Automation Laws." In Information Technology and Societal Development. Hershey, PA: IGI Global, 2009. https://doi.org/10.4018/978-1-60566-004-2.ch011

Export Reference

Mendeley
Favorite

Abstract

The purpose of this chapter is to define a scope of service science and service automation in service economy based on ideal generic service systems originally developed by the author. There are two goals of this study: 1) to develop generic service categories and their generic systems, and 2) to define a scope of service science based upon the presented generic models of service systems, which determine the required support from emerging system science. The research methodology is based on the architectural modeling according the paradigm of enterprise-wide systems (Targowski, 2003). The architectural system approach is based on the philosophy of the system approach (Klir, 1985), and management cybernetics (Beer, 1981) which provide comprehensive and cohesive solutions to the problems of systems design, thus eliminating the fuziveness of the “application portfolio” and the “information archipelago” (McFarlan, 1981; Targowski, 1990). The mission of the architectural system approach is to find the ultimate synthesis of the whole system structure that involves appropriate logic, appropriate technological accommodation, operational quality, a positive user involvement, and co-existence with nature (Targowski, 1990). In its nature, the architectural system approach is of deductive rather than inductive nature. It looks for the ideal model of a solution, which in practice is far away from its perfect level. The difference between the architectural system approach and the engineering approach is in the level of abstraction. The architectural models are more conceptual whereas engineering outcomes are more technical and specific. The architectural system approach is the response to the complexity of expected outcomes. Prior to spending a few million dollars for a new information system, one must provide its information architecture and the business and social implications associated with it (Targowski, 2003). In this sense, this study will define service systems’ architectures.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.