SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 213 | Next

Michael Bell

"Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture"


Exhibit 6.3 illustrates analysis service abstraction types and their breakdown into documented
and undocumented categories.
Legacy Type. Legacy sources are assets that have passed the abstraction stage of their life
cycle and are regarded as concrete service-oriented software entities, such as physical operating
services, applications, and third-party deployed products in production environments. This may
also include business partner applications (often called B2B), enterprise portals, or existing service
consumers, as depicted in Exhibit 6.4. Legacy entities were designed, architected, and built to
provide solutions for past enterprise challenges. They are also managed and funded by budgets
that were allocated under different circumstances.
So why should these be considered part of the current solutions? Should existing entities
play major roles in future service-oriented strategies? The answers to these questions are intrinsically
strategic for the business. Asset reusability is obviously the main motivation behind the
involvement of legacy entities in the service discovery and analysis process. Indeed, they were
introduced to resolve a different set of enterprise issues, but they can still participate in resolving
current organizational problems. Further analysis activities should determine whether they should
be fully or partially employed.
Service-Oriented Typing 119
Legacy Types
Existing
Services
Existing
Applications/
Systems
Existing
Partner
Applications
Existing
Service
Consumers
EXHIBIT 6.


Pages:
201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225