Book Image

SOA Made Simple

Book Image

SOA Made Simple

Overview of this book

SOA is an industry term which is often preached like a religion rather than taught like a technology, and over time, grasping the concept has become unnecessarily difficult. Many companies proclaim that they don't know where to begin with SOA, while others have begun their SOA effort but haven't reaped the benefits they were convinced it would bring. "SOA Made Simple"ù unveils the true meaning of Service Oriented Architecture and how to make it successful so that you can confidently explain SOA to anyone! "SOA Made Simple"ù explains exactly what SOA is in simple terminology and by using real-life examples. Once a simple definition is clear in your mind, you'll be guided through what SOA solves, when and why you should use it, and how to set up, design and categorize your SOA landscape. With this book in hand you'll learn to keep your SOA strategy successful as you expand on it. "SOA Made Simple"ù demystifies SOA, simply. It is not difficult to grasp, but for various reasons SOA is often made unnecessarily complex. Service-orientation is already a very natural way of thinking for business stakeholders that want to realize and sell services to potential clients, and this book helps you to realize that concept both in theory and practice. You'll begin with a clear and simple explanation of what SOA is and why we need it. You'll then be presented with plain facts about the key ingredients of a service, and along the way learn about service design, layering and categorizing, some major SOA platform offerings as well as governance and successful implementation. After reading "SOA Made Simple"ù you will have a clear understanding of what SOA is so you can implement and govern SOA in your own organization.
Table of Contents (17 chapters)
SOA Made Simple
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Application management


Application management is about changing existing applications, or solutions, in a structured way to solve errors, implement new functionality, or implement new rules and regulations. Creating new solutions is out of the scope of application management.

Changes that application management needs to realize come from demand management or directly from end users when demand management does not need to be involved (for example, errors that can easily be pinpointed and for which the fix has only local impact) or smaller organizations that haven't implemented demand management separately. Application management is on the supply side of IT and can be outsourced.

Examples of activities that are part of application management are:

  • Changing a financial application to support IBAN bank account numbers besides country-specific bank account numbers

  • Creating a new web page for the organization's website in the CMS application, or changing text labels of the HRM system

  • Correcting customer...