1. October 30, 2008 Extensible Workflow Management for Simmod ESUG32, Frankfurt, Oct 30, 2008 Alexander Scharnweber (DLR) October 30, 2008 Slide 1 > Extensible Workflow Management for Simmod > Alexander Scharnweber

2. October 30, 2008 Background and Motivation Simmod GUI applications do not cover the complete workflow Manual tasks cost time: backing up documenting changes Working in a team requires copying complete application No Undo functionality available Backup copies take up a lot of space October 30, 2008 Slide 2 > Extensible Workflow Management for Simmod > Alexander Scharnweber

3. October 30, 2008 Background and Motivation Numerous different analysis tools in use Excel Access Stand-alone tools written in different programming languages No documentation No structured software development for tools No peer review for algorithms Slide 3 > Extensible Workflow Management for Simmod > Alexander Scharnweber

4. October 30, 2008 Extensible Workflow Management for Simmod (EWMS) Workflow Wrapper for Simmod Engine and GUI applications Prototype developed as diploma thesis Ongoing further development within DLR Will cover as much of the simulation workflow as possible Versioning and Backup Teamwork Simulation Execution Simulation Documentation as required by QMS Analysis and Reporting Slide 4 > Extensible Workflow Management for Simmod > Alexander Scharnweber

5. October 30, 2008 Versioning Complete Application stored in a Subversion repository After each simulation run, modified files are committed to the repository Metadata available: User Name Date and Time Simmod version Comment All previous versions available at any time Slide 5 > Extensible Workflow Management for Simmod > Alexander Scharnweber

6. October 30, 2008 Backup and Teamwork Daily backup for repository server Backup copies take up no space on workstation No manual backup necessary Subversion only stores modified files, not entire applications All Simmod users can access repository to retrieve applications Access Control available for individual applications Slide 6 > Extensible Workflow Management for Simmod > Alexander Scharnweber

7. October 30, 2008 Analysis and Reporting Built-in database stores relevant input and output files API Framework provides access to: application files database Analysis and Reporting Modules access information via API Modules implemented in Java File System access Individual User Interface Slide 7 > Extensible Workflow Management for Simmod > Alexander Scharnweber

8. October 30, 2008 EWMS Design Slide 8 > Extensible Workflow Management for Simmod > Alexander Scharnweber

9. October 30, 2008 Database Built-in SQL database (HSQLDB) Memory-based tables for speed Import parsers for DBF files and SIMU26 Configurable SIMU26 import to allow for future extensions Data access via SQL queries Supports several concurrent application revisions Slide 9 > Extensible Workflow Management for Simmod > Alexander Scharnweber

10. October 30, 2008 Extensibility Modules can be activated at runtime Each module is essentially an independent Java program presented as a Tab in the main interface Common filter panel provides detailed filtering of simulation output Documentation and Source Code available Peer Review of underlying algorithms Slide 10 > Extensible Workflow Management for Simmod > Alexander Scharnweber

11. October 30, 2008 Planned Extensions Performance Indicators Separations Comparative Analyses compare different revisions of an application Direct connection to real-time simulation... Export to Excel Diagram Generation Slide 11 > Extensible Workflow Management for Simmod > Alexander Scharnweber

12. October 30, 2008 Live Demonstration Slide 12 > Extensible Workflow Management for Simmod > Alexander Scharnweber

13. October 30, 2008 Questions? Slide 13 > Extensible Workflow Management for Simmod > Alexander Scharnweber