surface, much like any other custom development projects for
distributed applications. Services are designed, developed, and
deployed alongside the usual supporting cast of front and back-end
technologies. Once you dig a bit deeper under the layers of
service-orientation, though, you'll find that in order to properly
construct and position services as part of a standardized SOA,
traditional project cycles require some adjustments.
As we can see in Figure 1 (see below), common delivery lifecycles
include processes specifically tailored to the creation of services in
support of SOA. In the service-oriented analysis stage, for example,
services are modeled as service candidates that comprise a preliminary
SOA. These candidates then become the starting point for the
service-oriented design phase, which transforms them into real world
service contracts.
Service-oriented analysis (and a related sub-process known as service
modeling) represent an important part of service delivery that
requires the involvement of business analysts and very much
demonstrates how business analysis in general is affected by SOA.
We'll discuss these processes in more detail later in this series. For
now, our focus is on the project lifecycle and its relationship to
business analysis.>>
You can read the article in full at:
<http://searchwebservices.techtarget.com/tip/1,289483,sid26_gci1189469,00.html?track=NL-451&ad=553467>
Gervas
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
