1.8. Summary
Too many software projects fail. Software engineering practice has not delivered on its promises and needs to change. The chief problem is how best to align IT practice with business need.
Requirements engineering is mainly a modelling problem as is specification. But they are not the same problem. The requirements engineer must look beyond the system boundary and understand the business and the real users of services. Discovering business rules is an important part of requirements engineering.
Service oriented architecture is an architectural concept in software design that emphasizes the use of combined loosely coupled services to support business requirements directly. In SOA, resources are made available to service consumers in the network as independent artifacts that are accessed in a standardized way. This adherence to standardization is definitional. SOA is about raising the level of abstraction, so that requirements and business processes can be discussed in a language understood by business as well as IT people. The main idea behind SOA is the desire to build applications that support a business process by combining a number of smaller business services into a complete business process.
Though built on similar principles, SOA is not the same as eb services. SOA is independent of any specific technologies.
A service is a unit of work carried out by a service provider to achieve some desired result for the service consumer. A service is a loosely coupled black ...
Get Requirements Modelling and Specification for Service Oriented Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
