Kĩ thuật lập trình - Chapter 18: A framework for integrating business applications

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.

ppt28 trang | Chia sẻ: huyhoang44 | Lượt xem: 597 | Lượt tải: 0download
Bạn đang xem trước 20 trang tài liệu Kĩ thuật lập trình - Chapter 18: A framework for integrating business applications, để xem tài liệu hoàn chỉnh bạn click vào nút DOWNLOAD ở trên
Chapter 18A Framework for Integrating Business Applications Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications OverviewMotivationInformation Organizer Practical Experiences Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications MotivationAll 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, ObjectsPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Information OrganizerA product for integration of systemsFocuses on information systemsIntroduces new conceptsObjectsAspectsReuse!Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Introduction, cont.Reuse of legacy systemsDataApplicationsApplication patternsAnother possibility of reusePage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Technical detailsBuilds on Microsoft technologiesWindows 2000COMActive DirectorySecurityReuse again!Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications ConceptsBusiness Object ModelThe conceptual modelContains definitions of conceptsInformation OrganizerThe applicationBusiness Object FrameworkThe implementation of Business Object Model in Information OrganizerPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Business Object ModelThe conceptual modelIntroduces new conceptsObjectsAspectsRelationsRolesViewsPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications ObjectsThe most central type of entity in the modelObjects model physical or logical objectsRepresent entities in the applications to be integratedE.g. “valve”, “pump”, “issue”, “workflow step”.Little functionality in itself - related data is carried by its AspectsObjectAspectAspectAspectAspectPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications AspectsContains part of the functionality of an objectOften contain documents of some kindAre often associated with (legacy) applicationsCan be added and removed dynamicallyNew types of aspects can be added when the system is ready to handle themObjectAspectAspectAspectAspectPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications RelationsObjects exist in relation to other objectsTyped or generic relationsAllow connection of objects with certain aspectsNew types can be definedUsed to structure the objectsTreesArbitrary structuresCan be interpreted by a user or the system itselfObjectObjectPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications RolesA certain function offered by an objectImplemented by aspectsNot very clear descriptionPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications ViewsLimits the visibilityObjects, aspects, and relationsDifferent categories of usersDifferent information interesting depending on contextPossibility to switch viewsThe selected item still in focusE.g. locate an issue in a personal view, then switch to workflow viewCan be added dynamicallyPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Integration layerIssue manage-ment systemDocument manage-ment systemCAD systemPresentation layerData/application layerBusiness ExplorerSystem-wide information modelApplication specificuser inter-facePage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Business Object FrameworkThe implementation of Business Object ModelThe “core” of Information OrganizerExamples of tools and functionsGeneric implementation of Aspects, Objects etc.Configuration environmentDevelopment environmentRuntime environmentMechanisms for defining object and aspect typesImplement certain COM interfacesPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Information OrganizerConventional three-layered architectureUser interface layer (three types)Business Logic layer (Business Object Framework)Data layerApplicationsDocumentsDatabasesThree types of user interfaces available“Thin” client – standard browser“Fat” client – installed code on client machines“Ultra-thin” client – WAP clientPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Information Organizer, cont.Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Application PatternsGeneric implementations of commonly occurring patternsNon-domain specific patternsThree patterns are describedBusiness Process Support, “workflow”Document Management SupportRelational Database ConnectorApplied on Information Organizer levelNo support needed from participating applicationsPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Business Process SupportAdding “workflow” concept to systemsConfigurationRuntime supportNew object, aspect, and relation typesProcessorProcessProcess FlowTarget“Above” original application levelPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Business Process Support, cont.Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Document Management SupportCreates documents “on the fly”Uses templatesInserts data from objectsDesigned for InternetIntegrated with archive systemPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Relational Database ConnectorA means of retrieving data from a standard databaseGeneric implementationBuilds on XMLSeparates data from presentationEach data row is represented by an object in BOFData still resides in the databaseSecurity on row levelPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Relational Database Connector, cont.DataDescription of data recordsInformation whether some data items are writeablePresentationPresentation formatPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Practical ExperiencesComponent 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. Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications DSBOUIUIAspectUIBusinessDataFileWordUIFileWeb-CamUIRelationsPropertiesCameraHelpChangeServicesDeleteDBFileDSBOUIUIAspectUIUIBusinessDataFileNote-padUIdllRelationsPropertiesMyServiceNotepadChangeServicesDeleteDS = Data StorageUI = User InterfaceBO = Business ObjectDll = Dynamic linked libraryA three layered implementation architecture Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications AAAStep 1Personal ViewATemplateActionsStep 2BOAStep 3BOABOAAIssue AIssue BABOProcess ViewABOBOBOUser 2ABOTemplateActionsTemplateActionsPerformedActionsPerformedActionsUser 1BO - instances of different business object typesA - instances of different aspect typesA workflow application Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Practical Experiences – cont.Integrating modern, well-componentized applications is easy and straightforwardIntegrating monolithic applications is difficult and cumbersome. A Generic front-end “connector”to database provide 60 to 80 percent of the original application functionality.Page Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications SummaryComponent-based approachReuseIntegrationReuse of components not originally designed as reusable componentsReuse of application patternsLevel of integration can be chosenBasic integration reusing the applications “as is”Data level (using Relational Database Connector)Implementation in COMPage Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications

Các file đính kèm theo tài liệu này:

  • ppt18_chapterwc_7598.ppt