Introduction

The development of this IAML Eclipse plugin is based on an iterative approach. In particular, large iterations (minor versions) which are then broken down into smaller iterations (revisions, spikes). These iterations are also designed to be synchronised with my PhD.

I hope to also use Test Driven Development significantly in order to test and validate the majority of the plugin. Though I'm not yet sure how to test the usability of Eclipse :)

• Introduction
• Release 0.1
• Release 0.2
• Release 0.3
• Release 0.3.1
• Release 0.4
• Release 0.5
• Release 0.6+
• Release 0.9
• Release 1.0

Release 0.1

(Released November 2008)

1. Initial IAML model that can describe initial requirements
2. Usability improvements
• Display shortcut elements for referenced elements
3. Look into rule engines for element inference
4. Testing
• Initial testing of code generation
• Initial testing of element inference
• Testing of plugin structure
5. Code generation
• Basic HTML/PHP genereation
6. Set up update site

Release 0.2

(Released April 2009)

1. Publish milestones
2. Expand IAML model
• All basic model elements can be placed in a diagram
• Inference and code generation tests
3. Code generation
• Clean up structure of code generation plugin
• Operation deep chaining (r563)
• Can generate all elements of the initial requirements
4. Testing
• Test operational modelling and generation
• Test cases for code generation of all modelling elements

Release 0.3

(Released July 2009)

1. Expand IAML model
• Document existing atomic operations
• Document existing composite operations
2. Inference
• Queue-based knowledge inference - to be detailed in upcoming paper
• Infer directly-contained model elements
• Inference actions available through right-click
3. Code generation
• Session persistence within multiple remote calls (r586)
• Generated code is cleaned with the iacleaner formatter (issue 13)
4. Testing and Documentation
• Sessions
• Buttons
• Operation modelling
• Condition modelling
• Domain objects, domain object instances
• Login handlers (secret key)
• Select wires
• New instance wires
5. Editor
• Create edges from shortcut elements not directly contained (issue 34)
• Render shortcut elements and edges not directly contained (issue 47)
6. Usability improvements
• Can migrate models between different versions
• Render model diagram to PNG images (issue 9)
• Progress monitors for inference and code generation (issue 23)
• Deletion of generated elements semantics (issue 29)
7. Development
• Investigations into model-driven code coverage

Release 0.3.1

(Released July 2009)

1. Upgrade editor to Eclipse 3.5/GMF 2.2 (issue 50)
2. Usability improvements
• More icons for editor elements (issue 18)
• Model element creation tools are now rendered in groups

Release 0.4

(Released October 2009)

1. Expand IAML model
• Login Handlers (domain instance and user)
• Clear the current session DomainObjectInstance
• Set Wire: a one-way Sync Wire
• Query Parameter (url?param=bar)
• Users as first-class citizens
• Join Node, Split Node
• ...
2. Documentation
• Automatically generated documentation
• Installation guide
• "Hello, World" tutorial
• Rich suite of example models
3. Usability improvements
• Differences between primitive operations and composite operations have been clarified
• Model instances will be checked for validity before code generation occurs
• Debug information is no longer displayed by default ( issue 115 )
4. Development
• PHP and Javascript libraries moved into a separate runtime bundle ( issue 75 ,  issue 76 )
• Refactoring of code generation templates
• Diagram tests moved into separate bundle ( issue 109 )

Release 0.5

(Outstanding issues)

1. Expand IAML model
• Text element
• Resultset viewer
• InputForm which renders SyncWire contents as Text, rather than InputTextFields
• DomainObjectInstance autosave default should be false
• E-mails
• Server-side operation (e.g. written in PHP)
• Client-side operaiton (e.g. written in Javascript)
• Deleting domain objects

Release 0.6+

(Outstanding issues)

Release 0.9

1. Can implement Ticket 2.0

Release 1.0

1. Focus on Usability
2. Implement code generation in another language (JSP?)
3. Extensibility