1 / 8

Modelling Management Components for Reuse using UML

Modelling Management Components for Reuse using UML. David Lewis (FlowThru Technical Co-ordinator) Chris Malbon Alina DaCruz University College London. standards. service providers. other service providers. customers. Business Context. frameworks & interface definitions.

adamma
Télécharger la présentation

Modelling Management Components for Reuse using UML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modelling Management Components for Reuse using UML David Lewis (FlowThru Technical Co-ordinator) Chris Malbon Alina DaCruz University College London

  2. standards service providers other service providers customers Business Context frameworks & interface definitions component vendors business needs requirements business needs frameworks & interface definitions component & frameworks system developers Development system requirements working software Operation

  3. Management Components Requirements • Ease of inter- and intra-domain access to component descriptions • Ease selection of component for reuse • Common component description at different levels of abstraction • Traceability from requirements to operational interfaces • Traceability for component maintenance

  4. requirements capture requirements statement requirements analysis uses? framework analysis model part of component uses design exports uses design model design model i/f implementation exports uses i/f software software testing Conventional Component Reuse

  5. requirements capture requirements statement requirements analysis component analysis model uses analysis model i/f design trace uses design model design model i/f implementation trace uses i/f software software facade testing Reuse with Facades

  6. Analysis Model

  7. Web Navigation MS Word (text) Paradigm Plus (UML) • Use case • pre/post conditions • description • Analysis Model • analysis object diagrams • collaboration diagrams • Design Model • CO component diagrams • IDL i/f class diagrams Analysis Model HTML Use Case HTML Design Model HTML CO component diagram Analysis object diagram Use case IDL object diagram Analysis object summary IDL object summary IDL object definition HTML

  8. Conclusions • Façade offer restricted view of component model for re-users • Traceability between modelling constructs at different façade levels is important • OOSE Analysis Model is key to mapping component requirements (use cases) to interface design (IDL) • HTML generation is limited, need more flexible XML-based approach • Mapping to CORBA Components/EJBs needed http://www.cs.ucl.ac.uk/research/flowthru/ models/fulfilment/subscription/

More Related