Đang tải... (xem toàn văn)
In this chapter, the following content will be discussed: Component-based approach: reuse, integration, reuse of components not originally designed as reusable components, reuse of application patterns; level of integration can be chosen basic integration reusing the applications “as is”, data level (using relational database connector), implementation in COM.
Chapter 18 A Framework for Integrating Business Applications Building Reliable Componentbased Overview Motivation Information Organizer Practical Experiences Building Reliable Componentbased Motivation All information of importance is to be made available to different categories of users Containing information which must be reused Another method to access and interrelate associated information in different systems is called for Microsoft’s Active Directory: a tool for sharing information between different applications IEC1346, OMG, IT4 Aspects, Objects Building Reliable Componentbased Information Organizer A product for integration of systems Focuses on information systems Introduces new concepts Objects Aspects Reuse! Building Reliable Componentbased Introduction, cont Reuse of legacy systems Data Applications Application patterns Another possibility of reuse Building Reliable Componentbased Technical details Builds on Microsoft technologies Windows 2000 COM Active Directory Security Reuse again! Building Reliable Componentbased Concepts Business Object Model The conceptual model Contains definitions of concepts Information Organizer The application Business Object Framework The implementation of Business Object Model in Information Organizer Building Reliable Componentbased Business Object Model The conceptual model Introduces new concepts Objects Aspects Relations Roles Views Building Reliable Componentbased Objects The most central type of entity in the model Objects model physical or logical objects Represent entities in the applications to be integrated E.g “valve”, “pump”, “issue”, “workflow step” Little functionality in itself - related data is carried by its Aspects Aspect Aspect Aspect Object Aspect Building Reliable Componentbased Aspects Contains part of the functionality of an object Often contain documents of some kind Are often associated with (legacy) applications Can be added and removed dynamically New types of aspects can be added when the system is ready to handle them Aspect Aspect Object Aspect Aspect Building Reliable Componentbased Business Explorer Presentation layer System-wide information model Application specific user interface Integration layer Data/application layer Issue management system Document management system Building Reliable Componentbased CAD system Business Object Framework The implementation of Business Object Model The “core” of Information Organizer Examples of tools and functions Generic implementation of Aspects, Objects etc Configuration environment Development environment Runtime environment Mechanisms for defining object and aspect types Implement certain COM interfaces Building Reliable Componentbased Information Organizer Conventional three-layered architecture User interface layer (three types) Business Logic layer (Business Object Framework) Data layer Applications Documents Databases Three types of user interfaces available “Thin” client – standard browser “Fat” client – installed code on client machines “Ultra-thin” client – WAP client Building Reliable Componentbased Information Organizer, cont Building Reliable Componentbased Application Patterns Generic implementations of commonly occurring patterns Non-domain specific patterns Three patterns are described Business Process Support, “workflow” Document Management Support Relational Database Connector Applied on Information Organizer level No support needed from participating applications Building Reliable Componentbased Business Process Support Adding “workflow” concept to systems Configuration Runtime support New object, aspect, and relation types Processor Process Process Flow Target “Above” original application level Building Reliable Componentbased Business Process Support, cont Building Reliable Componentbased Document Management Support Creates documents “on the fly” Uses templates Inserts data from objects Designed for Internet Integrated with archive system Building Reliable Componentbased Relational Database Connector A means of retrieving data from a standard database Generic implementation Builds on XML Separates data from presentation Each data row is represented by an object in BOF Data still resides in the database Security on row level Building Reliable Componentbased Relational Database Connector, cont Data Description of data records Information whether some data items are writeable Presentation Presentation format Building Reliable Componentbased Practical Experiences Component based development can be highly profitable A significant part of the development time was spent in learning the full capabilities and impacts of existing technologies and components Development of custom functions for the framework actually occupied a smaller part of the total project time One of the main reasons why verbal commitments to component-based development often fall short in practice Building Reliable Componentbased A three layered implementation architecture UI UI Business BO Aspect DS Data UI UI UI WebCam Word File File Relations Properties Camera Help Change Services Delete DS = Data Storage UI = User Interface BO = Business Object Dll = Dynamic linked library UI UI Business BO Data UI UI Aspect DS dll DB File UI Notepad File Building Reliable Componentbased Relations Properties MyService Notepad Change Services Delete A workflow application Step Process View A BO Template Actions A User User A A A BO Step Template Actions BO A Performed Actions BO BO A A Issue A Issue B A BO BO Template Actions A BO A Personal View Step BO - instances of different business object types A - instances of different aspect types Building Reliable Componentbased Performed Actions Practical Experiences – cont Integrating modern, well-componentized applications is easy and straightforward Integrating monolithic applications is difficult and cumbersome A Generic front-end “connector”to database provide 60 to 80 percent of the original application functionality Building Reliable Componentbased Summary Component-based approach Reuse Integration Reuse of components not originally designed as reusable components Reuse of application patterns Level of integration can be chosen Basic integration reusing the applications “as is” Data level (using Relational Database Connector) Implementation in COM Building Reliable Componentbased ... Building Reliable Componentbased Relational Database Connector, cont Data Description of data records Information whether some data items are writeable Presentation Presentation format Building Reliable Componentbased ... types Building Reliable Componentbased Performed Actions Practical Experiences – cont Integrating modern, well-componentized applications is easy and straightforward Integrating monolithic applications. .. types) Business Logic layer (Business Object Framework) Data layer Applications Documents Databases Three types of user interfaces available “Thin” client – standard browser “Fat” client – installed