The Second Rule Change “Architecture”
20 July 2010 Leave a comment
An architecture defines the functionality to be implemented meet the specific needs of business users.
Typically, an architecture is designed to meet the specific needs of who makes the request to the IT industry, this approach can lead to duplication functionality within the same architecture, such as a registry of
The role of architecture change radically with the introduction of a Service-oriented architecture, SOA precisely, which makes use of SOA architectures is to align IT to business demands by pushing the parties to definition of architecture not only to think about functionality but in fact develop an entire business enterprise in order to identify functionality required in the company and to extend them to use in their
The change of this view is defined by certain characteristics that SOA introduces to drive change, an architecture for SOA must be:
- Service Based
- Standards Based
- Enterprise Focus
- Business Focus
- Introducing the “Reference Architecture”
Let us now explain how this would help reduce the distance between IT and Business
A service-based architecture, allows sharing between different applications,as already developed, this is
because the identification of a service and future use are written into the WSDL, Web Service Definition
Language,which presents all the methods exposed by the service and how to use these methods In this way, before developing a new service can detect whether another area already offers a similar service to use that service without develop a new one.
Obvious even to do that you can combine multiple services to get what that the business functions require.
The SOA is based on precise standards, particularly on a standard now widely used XML. Virtually all popular programming languages provide support for XML, so you can achieve the solution without having the required need for personnel with specific skills.
Development and implementation of a SOA provides the vision of the changes are not occurs only at the business unit level but at a higher level. Unlike traditional SOA technologies requires the involvement of all stak-holder and support of the company to be applied. The technical group will go from being localized to an area of business particular, to be centralized in this way the technical choices are not more driven by line of business making the request but are guided entire business. This is reflected in the design of a service is having in mind what is the whole business.
In many architectures the execution of a request requires the Business dozens of applications, each specialized in a specific area of belonging.
There are applications ERP, CRM, and perhaps all have a customized database customer often contains information simply organized differently.
Implementing SOA requires a sharing of what are the common components, such as a registry, thus avoiding duplication components.
The Reference Architecture
The “Reference Architecture” is a descriptive document based SOA.The purpose this document is to provide a comprehensive document of all architecture which will then form the SOA.
The reference architecture is designed to break those applications are those legacy applications that are business presentation.
In this document it is good to introduce what will be at the heart of SOA hardware and software level.
Here ends the description of the second level of change, our next discuss your appointment of the Reference Architecture, particularly explain how I designed my way to do that is as common good and possible.