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 level -- 2.5. Levels of maturity -- Chapter 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 mix -- 4.5. The role of software infrastructure editors -- Part 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 properties.

5.4. The properties of agility -- 5.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 level -- 6.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 Method -- Chapter 7. The Discovery of Services (Reference Framework and Urbanization) -- 7.1. New needs for the information system -- 7.1.1. Expansiveness and progressiveness -- 7.1.2. Mobilizing the many different competences -- 7.2. Why are different methods seldom used within companies? -- 7.3. Reference frameworks -- 7.3.1. Zachman's framework -- 7.3.2. TOGAF -- 7.3.3. Peter Herzum's framework -- 7.3.4. Important information to be taken from the reference frameworks -- 7.4. Essential tools -- 7.4.1. UML (Unified Modeling Language) -- 7.4.2. MDA (Model Driven Architecture) -- 7.4.3. Urbanization of the information system -- Chapter 8. The Praxeme Enterprise Method.

8.1. Praxeme: the initiative behind a public method -- 8.2. The Praxeme method -- 8.2.1. Product -- 8.2.2. Process -- 8.2.3. Procedures -- 8.2.4. Combining the three dimensions -- 8.3. Enterprise system topology according to the Praxeme method -- 8.3.1. Upstream models -- 8.3.2. Logical (SOA), technical and software architecture models -- 8.3.3. Hardware and physical architecture models -- 8.3.4. Enterprise system topology -- 8.3.5. Pre-modeling -- 8.4. What the Praxeme method means for SOA -- 8.4.1. How can we find the correct services? -- 8.4.2. The link between urbanization, the object-oriented approach and SOA -- 8.5. Advantages of the Praxeme method -- 8.5.1. A method that unites different approaches and integrates SOA -- 8.5.2. Risks associated with the Praxeme method -- Chapter 9. Modeling with Praxeme -- 9.1. The modeling of requirements -- 9.2. Semantic modeling -- 9.2.1. The basic principles -- 9.2.2. How to obtain a semantic model -- 9.2.3. How to validate a semantic model -- 9.2.4. Semantic models and property rights - who owns a semantic model? -- 9.2.5. The structure of a semantic model -- 9.3. Pragmatic modeling -- 9.3.1. The basic principles -- 9.3.2. A new procedure for designing processes -- 9.3.3. Usage view -- 9.4. Pre-modeling -- 9.5. Logical modeling -- 9.5.1. SOA's style of logical architecture -- 9.5.2. Service-oriented architecture as logical architecture -- 9.5.3. Types of logical components -- 9.5.4. The strata of logical architecture -- 9.5.5. Pivot language -- 9.5.6. Service algorithm specification -- 9.5.7. Specification of the services' pre- and post-conditions -- 9.5.8. Logical architecture of data -- 9.5.9. Logical architecture of data repositories -- 9.5.10. Logical architecture and user interface -- 9.5.11. Designing a logic for tests -- 9.5.12. Considering ERP -- 9.5.13. Considering existent assets.

9.5.14. Federation of systems -- 9.5.15. Roles of logical modeling -- 9.6. Logical modeling of batch computing -- 9.7. Technical modeling -- 9.7.1. Required competences -- 9.7.2. Technical/logical negotiation -- 9.8. Software modeling -- 9.8.1. General principles -- 9.8.2. Towards the industrialization of programming -- 9.9. Benefits of the methodology -- 9.9.1. Opportunities -- 9.9.2. Obstacles -- Part IV. Mastering Existing Techniques -- Chapter 10. Tools for Industrializing the Method -- 10.1. Requirements in the industrialization of procedures -- 10.2. Frameworks and design patterns -- 10.2.1. From services framework to virtual machines -- 10.2.2. Frameworks and human-machine interfaces -- 10.2.3. Design patterns -- 10.3. Tools for increased agility -- 10.3.1. Rules engine -- 10.3.2. Reference data management system -- 10.4. Representation tools -- 10.4.1. Modeling CASE tool -- 10.4.2. Formal language (pseudo-language) -- 10.4.3. MDA -- 10.5. Tools for tests and management -- 10.5.1. Non-regression tests -- 10.5.2. Designing tests and test data -- 10.5.3. Different levels of tests -- 10.6. Tools for the management of different versions and the configuration of programs -- 10.6.1. The level of versions and variants -- 10.6.2. The level of delivery packages -- 10.7. Benefits of using tools in the method -- 10.7.1. Opportunities -- 10.7.2. Risks -- Chapter 11. Systems Integration and Common Information Language -- 11.1. New requirements in communication -- 11.1.1. Increase of data flow -- 11.1.2. Considering the business -- 11.1.3. Take the bus! -- 11.2. ESB's functions -- 11.2.1. Use perimeter -- 11.2.2. ESB's components -- 11.3. Integrating ESB into SI -- 11.3.1. Towards a common language -- 11.4. ESB's benefits -- 11.4.1. Opportunities -- 11.4.2. Limitations -- Chapter 12. SOA Platform.

12.1. Requirements for the global vision of technical architecture -- 12.2. New technical components -- 12.2.1. The transformation of data -- 12.2.2. From a directory to a registry of services -- 12.2.3. Security -- 12.2.4. Traceability of services in production -- 12.2.5. BAM and CEP -- 12.2.6. Business Intelligence -- 12.2.7. Editing -- 12.3. Managing performance -- 12.3.1. A new order of things? -- 12.3.2. Best practice -- 12.3.3. Testing performance -- 12.4. Managing exploitation -- 12.5. Managing maintenance -- 12.6. Benefits of SOA platforms -- 12.6.1. Opportunities -- 12.6.2. Limitations -- Chapter 13. Rules Management at the Scale of the Whole Enterprise -- 13.1. Overview -- 13.2. Deep view -- 13.3. When to use a rule engine -- 13.4. Logical architecture view -- 13.5. BRMS and SOA -- Chapter 14. Semantic Integration -- 14.1. Enabling the adaptive enterprise -- 14.2. Inhibitors for change -- 14.3. Definition of semantic integration -- 14.4. Parallel track information modeling -- 14.5. Change inhibitors addressed with semantic integration -- 14.6. Putting it to work -- 14.6.1. Canonicalizing the BIM -- 14.6.2. The quick win: a pilot project -- 14.6.3. Using the CIM for integration -- 14.6.4. Tools used -- 14.6.5. Managing change and keeping the models alive -- Conclusion -- Weblinks -- Bibliography -- Special Technical Note -- Index.