1. MICheckout is a tool for making and using MIBBI Foundry modules. It allows users to select modules, view them in different formats like wiki code or XML, and download them. 2. The current interface is very simple, allowing users to pick modules in any order without guidance on required dependencies. This can lead to missing required pieces. 3. Future versions may implement a wizard interface to guide typical users through questions, or allow searching by domain-specific concepts to find equivalent recommended modules. An advanced interface would also be maintained for power users.

1. MICheckout: Status
and Next Steps
Chris Taylor, Susanna Sansone,
Dawn Field, The MIBBI Project
Project website: http://mibbi.org/

2. ‘Pedro’ tool → XML → (via XSLT) Wiki code (etc.)

3. Making and Using MIBBI Foundry modules
Stage one
• Pedro tool (Garwood et al., 2004) using the MIBBI module schema
• Highly-configurable (mostly XML Schema, partly a configuration file)
• Validates data and exports XML (also saves in a ‘native’ zipped XML)
Stage two
• Mini shell scripts for XSL transformation using Saxon
— Initially just to get the (media)wiki code for Foundry pages
— Now have MediaWiki and HTML (both as table & list), tab-
delimited text, XML Schema (for MDA) and ISA config (XML)
• Java (command line) tool (using DOM) built to combine and transform
modules using the above XSLTs (=MyMICheckout)
Stage three
• ‘MICheckout the movie’ built using Flash (catalyst/builder)
• Same functionality (same XSLTs), rather nicer UI (i.e., it has one)

4. MICheckout: Supporting Users

5. Future direction for MICheckout?
Current status
• Very simple interface
— Pick what you want, in the order you want
— Download or view in the format you want
• Issues with the current interface
— Pick what you want, in the order you want (=anarchy)
— No way to work out everything that you need (fiddly bits)
Different approaches
1. Wizard-based Q&A for normal users, plus ‘advanced’ interface
— Simple ordered (ISA) questions for users; high level concepts
— Advanced interface similar to the current one
2. Domain-specific-MI-based concepts as keys/shortcuts
— “I normally get MIxxx – please give me the equivalent”
— Similar advanced access to #1

6. Future direction for MICheckout?
Current status
• Very simple interface
— Pick what you want, in the order you want
— Download or view in the format you want
• Issues with the current interface
— Pick what you want, in the order you want (=anarchy)
— No way to work out everything that you need (fiddly bits)
Different approaches
1. Wizard-based Q&A for normal users, plus ‘advanced’ interface
— Simple ordered (ISA) questions for users; high level concepts
— Advanced interface similar to the current one
2. Domain-specific-MI-based concepts as keys/shortcuts
— “I normally get MIxxx – please give me the equivalent”
— Similar advanced access to #1