05782nam 2200721Ia 450 991013951540332120230124183421.01-282-16544-597866121654430-470-61174-X0-470-60803-X(CKB)2550000000005866(EBL)477654(SSID)ssj0000398063(PQKBManifestationID)11283964(PQKBTitleCode)TC0000398063(PQKBWorkID)10357970(PQKB)10049526(Au-PeEL)EBL477654(CaPaEBR)ebr10360968(CaONFJC)MIL216544(MiAaPQ)EBC477654(OCoLC)520990475(EXLCZ)99255000000000586620081024d2009 uy 0engur|n|---|||||txtccrThe sustainable IT architecture[electronic resource] the progressive way of overhauling information systems with SOA /Pierre Bonnet, Jean-Michel Detavernier, Dominique VauquierLondon ISTE ;Hoboken, NJ Wiley20091 online resource (347 p.)ISTE ;v.126Description based upon print version of record.1-84821-089-2 Includes bibliographical references and index.Sustainable IT Architecture: The Progressive Way of Overhauling Information Systems with SOA; Table of Contents; Acknowledgements; Foreword; Preface; Guide for the Reader; Introduction to the SOA Project at SMABTP; Chapter 1. Initial Perspectives; 1.1. 50 years of computing - an overview; 1.2. What remains today?; Part I. Why a Sustainable Information System?; Chapter 2. Company-oriented Services; 2.1. Consequences of the Internet revolution; 2.2. What do the leading market players say?; 2.3. What do the chief information officers think?; 2.4. The issues faced at general management level2.5. Levels of maturityChapter 3. SOA Maturity Levels; 3.1. Towards the creation of a more agile information system; 3.2. Cosmetic SOA; 3.3. Extended SOA; 3.4. Overhaul SOA; 3.5. The matrices of SOA maturity; 3.5.1. The matrix showing the definitions of SOA; 3.5.2. The matrix showing the quality criteria of SOA; 3.5.3. The matrix showing the strengths and weaknesses of SOA; Chapter 4. Economic and Social Aspects; 4.1. Removal of obstacles that may slow down the progressive overhaul of an information system; 4.2. The future of IT specialists; 4.3. Off-shoring; 4.4. The generation mix4.5. The role of software infrastructure editorsPart II. The Principles of SOA; Chapter 5. The Properties of SOA; 5.1. The definition of service for users; 5.1.1. The user of the service; 5.1.2. A business ambiguity; 5.1.3. An example of a business service; 5.2. The definition of service for IT specialists; 5.2.1. The granularity of service; 5.2.2. The separation of concerns; 5.2.3. The service categories; 5.2.4. Batch services; 5.3. The properties of basic SOA; 5.3.1. Loose coupling; 5.3.2. Communication by messages; 5.3.3. Design by contract; 5.3.4. The limits of the basic properties5.4. The properties of agility5.4.1. The difference between the version and the variant of a service; 5.4.2. Agility of the data; 5.4.3. Agility of the rules; 5.4.4. Agility of the processes; 5.4.5. Agility of the human-computer interface; Chapter 6. Orchestration (BPM and SOA); 6.1. Multiple requirements in orchestration; 6.1.1. Orchestration and SOA maturity levels; 6.1.2. Functional requirements; 6.1.3. Technical requirements; 6.1.4. Enterprise architecture requirements; 6.2. The levels of orchestration; 6.2.1. Orchestration at the process level; 6.2.2. Orchestration at screen level6.2.3. Orchestration at the micro-process level (use cases)6.2.4. Orchestration at the business service level; 6.2.5. Orchestration between domains through the use of ESB; 6.2.6. The orchestration of batches; 6.3. The techniques of orchestration; 6.3.1. The BPM engine; 6.3.2. The business rules engine; 6.3.3. Specific programming; 6.4. Towards the homogenization of orchestration; 6.4.1. Unified modeling; 6.4.2. Unified standard; 6.5. The benefits of orchestration; 6.5.1. Advantages; 6.5.2. Disadvantages; Part III. The Need for an Enterprise MethodChapter 7. The Discovery of Services (Reference Framework and Urbanization)This book focuses on Service Oriented Architecture (SOA), the basis of sustainable and more agile IT systems that are able to adapt themselves to new trends and manage processes involving a third party. The discussion is based on the public Praxeme method and features a number of examples taken from large SOA projects which were used to rewrite the information systems of an insurance company; as such, decision-makers, creators of IT systems, programmers and computer scientists, as well as those who will use these new developments, will find this a useful resource.ISTEService-oriented architecture (Computer science)Information technologyManagementBusiness enterprisesComputer networksService-oriented architecture (Computer science)Information technologyManagement.Business enterprisesComputer networks.004.22658.4/038011Bonnet Pierre1967-863747Detavernier Jean-Michel863748Vauquier Dominique1962-863749MiAaPQMiAaPQMiAaPQBOOK9910139515403321The sustainable IT architecture1927861UNINA