What is Architecture?

IEEE 1471-2000 Software architecture is the fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution

What is Software Architecture? collection of the fundamental decisions about a software product/solution designed to meet the projects quality attributes Includes the main components, their main attributes, and their collaboration expressed in several levels of a bstraction (depending on the project's size). Architecture is communicated from multiple viewpoints

What is a Service? A facility supplying some public demand the work performed by one that serves HELP, USE, BENEFIT

What is Service and system? A service is a program you interact with via message e xchanges . A service is a function that is well -defined, self -contained, and does not depend on the context or state of other services. A system is a set of deployed services cooperating in a given task

What is SOA?

A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each othe r is needed.

SOA is a framework for designing software systems using a software architecture hat views all components as services

Benefits of SOA? Based on open standards. Supports vendor diversit y. Fosters intrinsic interoperabilit y. Promotes discovery. Promotes federation. Fosters inherent reusabilit y. Emphasizes extensibilit y. Promotes organizational agilit y. Supports incremental implementation.

What is real SOA? Changed mindset: service -oriented context for business logic. Changed automation logic: service -oriented applications. Changed infrastructure: service -oriented technologies.

A top-down organization transformation requiring real commitment.

Characteristics of SOA? Loosel y coupled: minimizes dependencies between services. Contractual: adhere to agreement on service descriptions. Autonomous: control the business logic they encapsulate. Abstract: hide the business logic from the service consumers. Reusable: divide business logic into reusable services. Composable: facilitate t he assembl y of composite services. Stateless: minimize retained information specific to an activity. Discoverable: self-described so that they can be found and assessed.

How do we encapsulat e process/business logic in a SO A? Note we translate both business logic and application logic into services

We first translate business processes into business logic and define services associated with the logic Likewise, we separate the application logic from implementation and define services

Business Logic: documented implementation of the business requirement typicall y structured into processes expressing the requirements, constraints, dependencies and external factors Application Logic: implementation of business logic organized into various technology solutions . business processes through purchased or designed systems within the confines of the IT infrastructure, securit y constrains, technical capabilities and vendor dependencies

Components of Lo gic in Service Orientation Message (units of communi cation) Operations (units of work) Services (units of processing logic -- collection of units of work) Processes (units of logic -- coordinated aggregation of services)