Modelling Management Components for Reuse using UML David Lewis (FlowThru Technical Co-ordinator) Chris Malbon Alina DaCruz University College London
Business Context other service providers service providers customers system developers component vendors standards Development Operation frameworks & interface definitions business needs working software component & frameworks system requirements business needs requirements frameworks & interface definitions
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
Conventional Component Reuse requirements statement requirements capture analysis model design model requirements analysis design implementation software testing component framework design model software i/f uses exports uses? part of
Reuse with Facades requirements statement requirements capture analysis model design model requirements analysis design implementation software testing component design model software i/f trace uses facade uses analysis model i/f trace
Analysis Model
Design Model HTML Analysis Model HTML Use Case HTML MS Word (text) Web Navigation Use case pre/post conditions description Paradigm Plus (UML) Analysis Model analysis object diagrams collaboration diagrams Design Model CO component diagrams IDL i/f class diagrams Use case Analysis object diagram CO component diagram Analysis object summary IDL object summary IDL object definition HTML IDL object diagram
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 models/fulfilment/subscription/