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

Software development


The process of software development spans a number of activities:

  • Requirements management: Gathering demands, wishes, and constraints for your project and prioritizing them. Finding out what end users and the business want, what laws and regulations apply for your project, and what architecture guidelines are relevant. Requirements can be functional, as well as non-functional (response time, availability, and so on). Requirements need to be communicated to designers and developers. Based on these requirements testers can create test plans, and code can be designed and developed.

  • Solution architecture: Create the solution architecture for the project based on the requirements and relevant reference architectures. Possibly have the solution architecture validated by the organization's architecture board.

  • Design: Design the software and hardware solution based on the requirements and solution architecture.

  • Development: Develop the software based on the design. Development...