• Xcarecrows 4 MDA definitions
• State machines hierarchical design
• Database usage through operative objects
• Simulation
• Conclusion

• Uses UML to design the structure and behaviour application
• Uses hierarchical families of elements, which cooperate in controlling logic, data is kept apart
• Interfaces itself with an UML modelling tool conformant with XMI 2
• Is an Eclipse plug-in

• Xcarecrows 4 MDA définition
• State machine hierarchical design
• Database usage through operative objects
• Simulation
• Conclusion

• Set a hierarchical view
• Use refinements to manage complete design
• Separate features
• Add or modify features easily
• Simplify a complex problem
• Bind the simulation model with a requirements tool

• Use a requirements traceability tool to prove the model completeness
• Interface Xcarecrows 4 MDA with customer requirements traceability tool

• A simulation model is made of cooperative elements family
• A family uses hierarchy model
• The family organisation is :
  • A leader to deal with messages inside the family ;
  • A set of cooperative objects like : state machine, operative object, leaders ;
  • A set of signals to mark messages managed by a leader.
• Elements follow hierarchical dependency :
  • Each cooperative element in a family knows only its leader ;
  • The leader is the only one who knows all sub-elements.

• Two populations:
  • the lice
  • the hosts
• The lice population increases or decreases.
• The hosts population increases, decreases and hosts lice.
• The model describes population evolution.

As is in the customer order

• Is defined by UML state diagrams
• Uses an error event
• Associates a behaviour for each state/event pair
• Deals with its hierarchy
• Is extracted from an UML modelling tool to be used in the Eclipse IDE

• Is defined by its interface contract as defined by Xcarecrows 4 MDA model
• The Java code is restricted to operative objects behaviour
• Deals with its hierarchy
• Is modelled by a signal source and an event hole

• The hierarchical design :
  • Is easy to understand ;
  • Uses the functionalities defined in the specifications of the simulated process.
• The modelling process is guided by the

Xcarecrows 4 MDA graphical interface

• The control design is extracted from UML
• Xcarecrows 4 MDA is plugged into Eclipse IDE

• Java code needed only for object behaviour
• The UML model defines objects interface
• The simulation model is easy to extend
• Programming rules for a Xcarecrows 4 MDA family are checked on the fly
• The documentation is automatically produced
• A requirement traceability tool is used to check extracted documentation from the model

• Keep one functionality in mind at a time
• Less code is written so less possible errors
• Remaining errors are easy to track in the state machine behaviour.

• Xcarecrows 4 MDA definition
• State machine hierarchical design
• Database usage through operative objects
• Simulation
• Conclusion

• The data base deals with :
  • the model operative data ;
  • the scenarios ;
  • the simulation results ;
  • the concurrent access to objects.

• Model specifications
• Parameterized evolution laws
• Scenarios
• Logical model
• Observation of model running

• Location
  • A set of villages with people.
• Biology
  • A set of people and parasites.
• Mobility
  • Vehicles move people and hosted parasites from village to another.

• An host could have child as soon as he is a days old *
• Disease
  • Each host have a life expectancy of b days.
  • Each parasite costs the host d days of life, less than c days old *
  • Each parasite costs the host e days of life, assuming that the host is more than c days old *
• * Numerical value are to be assigned to a to e.
• Other evolution laws can be added.

• Are a set of steps generated a priori
• Describe possible evolutions of the model
• Comply with specifications
• Are built independently of the evolution laws
• Ignore the real state of the system at simulation time
• Test uncommon set of events

• The model traduces the specifications.
• It receives orders from the scenario.
• It applies orders and checks that they do not break :
  • the specifications ;
  • the evolution laws.

• Synchronizes :
  • the a priori view from the scenario ;
  • with the observed reality and applied evolution laws.
• At each step, checks are done :
  • step feasibility through pre-condition ;
  • reality situation drift against scenarios and evolution laws with a post-condition.

• A scenario producer works :
  • in a reproducible way ;
  • from database ;
  • from pseudo-random generation number ;
  • using many combinations of scenario steps.
• The scenario is an XML document.
• Each scenario could be edited.

• Provides :
  • An observation of the simulation running in the analysis environment
  • A check of simulation model
  • A check of parameters choice
  • A coverage of the simulation model

• Xcarecrows 4 MDA definition
• State machines hierarchical design
• Database usage through operative objects
• Simulation
• Conclusion

• Multi Xcarecrows 4 MDA families
• Help the refinement and favor usage of non-regression tests.

• The database allows :
  • to enact integrity rules ;
  • to synchronize data access through native primitives ;
  • to observe, during simulation, stable reliable situation ;
  • to insulate the check of the integrity rules within the simulation.

• Xcarecrows 4 MDA definition
• State machine hierarchical design
• Database usage through operative objects
• Simulation
• Conclusion

• Xcarecrows 4 MDA leads to :
  • extract automatically a documentation for a check-in requirements tool ;
  • separate functionalities ;
  • distribute the functionalities along hierarchy ;
  • thoroughly model validation ;
  • control the model design process ;
  • split simulation into many threads.
• The simulation model :
  • is easily extendable ;
  • separates control data from operative data ;
  • interfaces itself with existing data base and applications ;
  • checks data consistency.