Workload and performance requirement
The Engineering of Consolidation is a physical architecture effort which is driven by Enterprise business workload and performance requirment as describe in the following drawing :Enterprise Workload and perforamnce requirement analysis overview
3 Driven by workload and performance requirment
3.1 Mission workload
The enterprise infrastructure must be designed based on enterprise workload analysis rather than by each application system to eliminate the waste of redundant infrastructure. The traditional EA approach , workload and performance requirement is consider as the operational characteristic by each application system. The operational characteristics is not an engineering calculation rather, it is frequently over estimated to be on the safe side. As a result, most of enterprise infrastructure are over designed over and over by each application system. A simple calculation to add up all the users estimation by each application system, it is not difficult to find that the estimate users are far exceed the total users in the enterprise
Enterprise workload and performance analysis is essential in enterprise strategic planning , most of enterprise have established their workload and performance analysis from statistic data and future projection for their strategic planning purpose. The engineering of sharing leverage on the existing resources to establish the technology workload and performance requirement without substantial investment as it is in enterprise wide business process engineering effort. For example :
3.2 IT workload distribution
3.3 Performance requirement
3.4 Performance measurement
^ TOP
EA to define the services
The challenge of SOA is which service to provideAs SOA become the diretion of application technology evolution in the industry, the need of EA have become obvious. A major chanlenge in service oriented architecture is how to qualify the proper services for the enterprise need.
EA define the proper services
EA is the effort to identify common foundation by looking for commonality.
The services must be selected from enterprise wide consideration rather then put together in pieces. EA, which enable the agility and simplicity, provide common services via the engineering of consolidation from the enterprise wide consideration.
Many SOA projects are initiated in a stovepipe approach to catch up with technology evolution with limited consideration from the aspect of the true benefit of SOA to enable agility and simplicity.
SOA do not replace EA
SOA do not replace EA. The confussion is due the different interpretation of EA. Technical community interpret EA as the enterprise solution such as the enterprsie wide collaboration system. The enterprise wide solution can be easly interpreted as SOA.
SOA in stovepipe appraoch
Implement SOA in a stovepipe approach has totally overlook the basic of SOA to share common services. As a result, the stovepipe oriented SOA approach does not benefit from SOA in sharing resources but also pay for the overhead of SOA. To achieve the purpose of sharing common services, SOA is designed as lose coupled with wrap around, there is an overhead effort for encapuslating the services which contribute to the general concern of SOA perforamnce issue. The overhead concern can be offset via the benefit of sharing common resources in an EA environment. Howerver, It become an extraburden to the stovepipe oriencte approach.
^ TOP
The applicaiton Services
The application services
The application oriented SOA concept:
Wikipeida Service Oriented Achiecture descirb SOA in the follown diagrams.
A service-oriented architecture (SOA) is a group of services that communicate with each other. The process of communication involves either simple data-passing between a service provider and service consumers, or a more complicated system of two or more service providers. Intercommunication implies the need for some means of connecting two or more services to each other.
SOAs build applications out of software services. Services comprise intrinsically unassociated, loosely coupled units of functionality that have no calls to each other embedded in them. Each service implements one action, such as filling out an online application for an account, viewing an online bank-statement, or placing an online booking or airline ticket order. Instead of services embedding calls to each other in their source code, they use defined protocols that describe how one or more services can "talk" to each other.
A software developer, software engineer, or business process expert associates individual SOA objects by using orchestration. In the process of orchestration, a software engineer or process engineer associates relatively large chunks of software functionality (services) in a non-hierarchical arrangement (in contrast to a class hierarchy) by using a special software tool that contains an exhaustive list of all of the services, their characteristics, and a means to record the designer's choices that the designer can manage and the software system can consume and use at run-time.
^ TOP
Data Services
A service oriented enterprise architecture does not only provide application service but also provide data service.Data service provide the treateed data content to multiple application need. It is analogy to a water reservor and water treatment plant. Data service consist of the data resorvor, data treatment, data search and distribution
Without recognize the concept of enterprise data service, Industry has initiate data warehousing, knowledge management, search engine, data mining, cleaning. The services oriented Enterprsie Architecture concept tie application, data and infrastructure together and continue to evolve data service concept in an holistic approach.
The map data.
The medical data.
The identity data.
The industry data.
Data resources supply the data need by similar to water resoruces in building build water resorvor, treat water quality and distriture water. Information is the enterprsie asset, it is created once and share by every one.
Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes.[3]
This new term is intended to completely encompass the legacy problem domains that have traditionally been addressed by records management and document management. It also includes all of the additional problems involved in converting to and from digital content, to and from the traditional media of those problem domains (such as physical and computerized filing and retrieval systems, often involving paper and microforms). Finally ECM is a new problem domain in its own right, as it has employed the technologies and strategies of (digital) content management to address business process issues, such as records and auditing, knowledge sharing, personalization and standardization of content, and so on.
Knowledge Management is about systematically extracting information and knowledge from an organizations data holdings and solving business problems. It is the combination of critical information and collective database design that enables an organization to make a decision, create a solution, share an asset, allocate a resource, or change direction. This function must be supported by a foundation of good data and database management.
Knowledge Management is defined by the roles, standards, and decision-making criteria in place for the acquisition and deployment of the components that perform the systematic process of finding, selecting, organizing, sharing, and distilling information. The goal is to provide internal and external users easy access to information. Additionally, Knowledge Management defines the components that provide capabilities to store demographic metrics of the users; what they want, how they want it, and when they want it.
Knowledge Management encompasses the technology that makes data, information, and knowledge visible and accessible to others. It determines processes and protocols for systematically making use of the information within and across agencies. The rationale for pursuing the development of this discipline includes:
Extracting and combining data from multiple agencies without changing the originating systems or developing new systems.
Reducing the burden on programmers to generate reports and data queries.
Reducing the demand on mission critical operational systems.
Creating user-friendly centralized locations for information.
Providing the public with integrated, direct access to government information.
Allowing for the retention or migration of data from retired systems.
Separating transaction-processing systems from huge ad hoc queries that are required by analytical, execute decision systems.
Defining and disseminating information on the owner of data to ensure accuracy, security and privacy.
Sharing of data will minimize the collection of redundant data that will need cleansing and storage.
Reducing the volume of data to a manageable level through aggregation.
Providing consistent data between systems and agencies.
Allowing access to cleansed data.
Simplifying operational processes of consolidating data from disparate systems.
Avoiding re-keying data from one system to another
The importance of Knowledge Management to the citizenry will grow as integrated project activities increase within the state. Potential benefits of developing the Knowledge Management discipline include:
Enhancing and accelerating business decision-making that requires information beyond the traditional borders of a system or agency.
Expanding knowledge of information existence so that its value can be ^ TOP
Infrastructure services
Infrastructure services is most recognized services to support the enterprise automation need.Network
Platform
Collaboration
^ TOP