module 8 - Module 8 Technical and service integration...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Module 8: Technical and service integration architectures Preview This module explains how integration architectures are used to translate the integration strategy to a set of building codes and blueprints needed to begin the construction of integration across the enterprise and with external stakeholders. The integration architecture has a number of sub-architecture or plans, including service, technical, information, and process architectures. This is similar to the build operation of a vehicle where there are blueprints for each major category such as electrical, drive train, braking, and so forth. The construction of a building contains similar sub-plans. To a large degree, engineers have been using this technique for decades. It is referred to as systems engineering methods (SEM) . Over the last few years, the discipline of information technology is starting to adapt more basic engineering concepts and practices in the design and build of information systems. To continue with the automotive example, once the individual plans are completed: z agreed upon standards are in place z the parts are interoperable - the electrical system will function with the drive train and braking system as designed z part sourcing is in place with purchasing z costing is nearing completion It now becomes the task of a process engineer to translate the individual plans to the manufacturing operation. As you can imagine, the entire electrical system is manufactured at once. However, each system needs to be partially assembled during assembly. The integration architecture follows a similar methodology. In this module, you study a proactive approach to designing an architecture, called event-driven design. It is in this phase that accountants need to be involved. Finally, the use case diagram is introduced. This is a very powerful and easy-to-understand diagramming technique that attempts to reduce if not eliminate the technical jargon of information technology in describing what a system should do and what results can be expected once the integration environment is built. Knowledge objectives Business Process Integration Module 8 · 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
z Justify spending time and resources to complete the enterprise integration architecture. z Describe the major components of an enterprise integration architecture. z Explain the advantages of event-driven designs. z Explain how use case diagrams attempt to remove ambiguity from the expected results of an integration program. Skill competencies z Contribute and participate in the build of use case diagrams. z Assist those trained in information technology to identify the business events that need to be addressed in the enterprise integration program. z
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 06/04/2009 for the course BUSINESS AIT 803 taught by Professor Peter during the Spring '09 term at Seneca.

Page1 / 28

module 8 - Module 8 Technical and service integration...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online