Service oriented architecture (SOA) benefits accrue largely at the enterprise’s level in cost avoidance through reuse, plus increased data exchange and agility. This requires a corresponding at the enterprise level to capture its benefits.
Leveraging Federal IT Investments Using Service Oriented Architecture
Download Resources
PDF Accessibility
One or more of the PDF files on this page fall under E202.2 Legacy Exceptions and may not be completely accessible. You may request an accessible version of a PDF using the form on the Contact Us page.
Service oriented architecture (SOA) builds on computer engineering approaches of the past to offer an architectural approach for enterprise systems, oriented around the offering of services on a network of consumers. A focus of this service-oriented approach is on the definition of service interfaces and predictable service behaviors. A set of industry standards, collectively labeled "Web Service" standards in this paper, provide and implement the general SOA concept and have become the predominant set of practical tools used by enterprise engineers for current SOA projects. Some Web Service standards have become foundational and more widely adopted, while many are still seeking broad industry or Government acceptance. SOA is an enterprise effort, and the local perspective of individual legacy projects will not justify an enterprise SOA effort, but this should not be allowed to stop the enterprise SOA from occurring. The SOA benefits accrue largely at the enterprise's level in cost avoidance through reuse, and increased data exchange and agility. Consequently, a corresponding investment is required at the enterprise level, where the benefit is found.