Robert Laird

Subscribe to Robert Laird: eMailAlertsEmail Alerts
Get Robert Laird: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Robert Laird

Service Oriented Modeling and Architecture (SOMA) is a modeling and design technique developed by IBM that provides prescriptive steps for how to enable target business processes by defining and developing a service-based IT solution. SOMA provides the communication link between the business requirements and the IT solution. It provides guidance on how to use business model and information as inputs to derive and define a service-based IT model. SOMA, as a methodology, addresses the gap between SOA and object orientation. This methodology approach provides modeling, analysis, design techniques, and activities to define the foundations of an SOA. It helps to define the elements in each of the SOA layers (see Figure 1) and also to take architectural decisions at each level. At the heart of SOMA is the identification and specification of services, components, and proc... (more)

SOA Book Excerpt: The First-Class Constructs of SOA - Part 3

Normal 0 false false false MicrosoftInternetExplorer4 In SOA, the main emphasis is on the identification of the right services followed by their specification and realization. Although some might argue that object-oriented analysis and design (OOAD) techniques can be used as a good starting point for services, its main emphasis is on microlevel abstractions. Services, on the other hand, are business-aligned entities and therefore are at a much higher level of abstraction than are objects and components. In Part 1 of this book excerpt, we discussed the different layers of an SOA ... (more)

SOA Book Excerpt: A Methodology for Service Modeling and Design - Part 1

When the programming model shifted from the traditional procedural model to that of object-orientation, a major paradigm shift occurred in the world of IT development. The focus was on encapsulating the state and behavior of entities and calling that encapsulation a class. Instances of a class were called objects, which occupied some space in the memory. Object orientation (OO) brought in concepts of inheritance, encapsulation, and polymorphism that could be applied to define relationships between classes. With the prevalence of the use of OO in the programming world, developers ... (more)