Evolution of Software Architecture Service Oriented Architecture -- benefits and a model procedure

1. Role of Information Technology in achieving Competitive Differentiation Raman Kannan & Scott Burrill Rosenblatt Securities Inc.

6. Software Architecture The software architecture of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them. The software architecture represents the earliest software design decisions. These design decisions are the most critical to get right and the most difficult to change downstream in the system development life cycle. The software architecture is the first design artifact addressing reliability, modifiability, security, real-time performance, and interoperability goals and requirements. structural units and different structural relationships Bass, L., Clements, P., and Kazman, R . Software Architecture in Practice . Reading, Mass.: Addison Wesley, 1998.

7. Reference Architecture A reference architecture is the generalized architecture of several end systems that share one or more common domains. The reference architecture defines the infrastructure common to the end systems and the interfaces of components that will be included in the end systems. The reference architecture is then instantiated to create a software architecture of a specific system. The definition of the reference architecture facilitates deriving and extending new software architectures for classes of systems. A reference architecture, therefore, plays a dual role with regard to specific target software architectures. First, it generalizes and extracts common functions and configurations. Second, it provides a base for instantiating target systems that use that common base more reliably and cost effectively.

10. Simple Architectures Data + Logic Presentation Data Presentation Logic 3 Tier 2 Tier monolithic Source 1 Source n Logical Step 1 Logical Step 2 EndUser Mgr Conversion(s)

12. Scott's Layered Diagram

17. Web Services Architecture Stack http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#discovery_service

21. Reference Architecture CRUD Operators DBMS DB Vendor free Design for change capture all the info Transaction Services Relationship Constraint Managers Bus. Logic Workflow Objects Presentation Mediators Display Agents Composite Entity Transformations Selectors Rules/Filters Routing Agent Rich Semi/Structured Information Units Protocol Agents Proxy services change the manner in which information is presented without impact change the DB Schema without impact reroute/recombine processing elements, creating new workflows Provide information in any format as required using transforms and filters New display devices can be introduced

22. OpenTrade – FMCP -- Gary Clients Servlets AccountServlet FactorServlet TransxServlet PositionServlet SecMasterServlet AccountEngine FactorEngine TransactionEngine AssetEngine AssetService TransactionService Clients http J2EE FixService EJBs txml dbml

25. SOA works – OT is not vaporware TransactionSink FixGwyAgent ConsolidationService Source FixGwy T Direct transformation does not exist Kernel finds a transformation path Fills txml fix fix fix txml Intermediate format

26. Earned Value! TransactionSink post FixGwyAgent Source FixService Sink FixGwy T This configuration would work Just as fine by reconfiguring the service definition. Architectural Stability. Independently developed systems interact and exchange information as needed when needed. The integration is facilitated by the catalinatech Kernel. Enterprise System capabilities are reconfigurable/adaptive /reusable and very stable. fix txml fix txml

27. We done it! FixFillService TransactionSink post FixService ConsolidationService Sink Source FixGwy T T Fills fix FixGwyAgent Sink Source Fills sql txml fix fix txml