Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 1 Behavioural Models for Hierarchical Components Tomás Barros, Ludovic Henrio and Eric Madelaine

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 2 Component base programming Component = software unit, deployment unit Industrial acceptance : EJBs, CCM, COM … 3 key concepts : –1. Encapsulation Black boxes, offered and required services, configuration –2. Composition Design of complex systems Hierarchical organization into sub-systems –3. Description ADL Logical and geographical composition Tools REUSABILITY CUSTOMIZATION COMPLEXITY HANDLING HIGH ABSTRACTION LEVEL

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 3 ATTRIBUTEBINDINGLIFE CYCLECONTENT Content Fractal Components Model

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 4 Component Behaviour Temporal Phases Deployment –Definition of its content and initial binds –Usually defined in an ADL Running –Only functional operations Reconfiguration –Structural and non-structural changes

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 5 Behaviour correctness (from the user point of view) Initial Composition –Requirements expressed as temporal formulas –Respect a SPEC Reconfiguration –New properties (features) –Preservation

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 6 Synchronisation Network (pNet) > –global action alphabet pAg, –finite set of arguments, each with sort pI i and params K i, corresponding to as many actual arguments as necessary in a given instantiation, –parameterized synchronisation vectors pAg <- [*, *, a3(k3), *, a4(k4), *] Instantiation : for a finite abstraction of the parameters domains D v Formalism: Parameterized Networks Finite Network pLTS x D v  LTS pNet x D v  Net callFoo(i,x) [x>0]!B[i].foo(x) other A !B[i].foo(x) n ?A.foo(x) n+x ?A.foo(x) k B 0 T. Barros, R. Boulifa, E. Madelaine: Parameterized Models for Distributed Java Objects, Forte'2004 Conference, Madrid, Sep. 2004, LNCS 3235, © Springer-Verlag

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 7 Example System A Controller

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 8 General Controller

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 9 Deployment –The deployment is always successful –Error absence during deployment Species of temporal properties

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 10 Functional Behaviour –After deployment without reconfigurations Species of temporal properties –Systems with no reconfiguration –Non-functional transparent respect to functional (commute)

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 11 Species of temporal properties Non-Structural reconfiguration –No Abstraction Structural Transformations Steps –Controller of the new structure –Action mapping –Identify states in the original controller where transformation is possible (set T ) –“Connect” both controllers from T through the transformation  ( T’ is the image of  ) –The new controller is the reachable parts from T’ (using the action mapping)

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 12 Related Work Wright –Connectors specified using CSP –Compatibility relation Darwin –FSP specifications, CAR for construction –Only functional aspects Sofa –Frame vs. Architecture based on traces –Compliance relation and detection of unsuccessful communications Behavioural Contracts –Behavioural typing (CSP like specification) –Type compatibility (decidable) and contract compliance (non decidable) –Non compositional

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 13 Conclusions Automatic construction of behaviour for hierarchical models (including errors) Taking into account functional and no- functional aspects Reconfigurations and transformations Classification and proofs of properties Implementation of a prototype tool with CADP

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 14 Future Work Asynchronous components (calls, requests, queues) ADL integration On-the-fly construction and checking Thanks Full version at: