Project Plan For Agent Modeling Platform, version 0.9.0

Introduction

We're making a major change to the schedule. Rather than focus on getting the new Acore meta-model out, we're working on getting documentation, testing and polish completed first so that we have the best possible platform for future improvements. MetaABM is not perfect, but it works very well for the majority of current use cases. The greatest priority now is to build up a good user and contributor base and that means using the current very stable meta-model target and improving surrounnding infrastructure. Please note that as with all Eclipse Incubation projects, version numbers are 0.n. This is not a reflection of overall code completion or quality. For example 0.7.0 is planned to have a reasonably stable API and 0.8.+ should be production ready, i.e. at least equivalent to 1.0. The 1.0.0 release is the new target for Acore functionality.

Release Deliverables

Each release will include:
  • Update site including runtime, SDK, documentation and source.
  • Features and plugins packaged (download).
  • Examples (download)

Table of Contents

Release Milestones

0.0.006/15/2009
Initial AXF Commit. Basic repackaging / renaming. Move dependencies from oAW to M2T. AGF/AXF API Experimental. Escape Modeling API Frozen.
M007/15/2009
AMF Commit. AMF API and meta-model Experimental (To be replaced w/ acore). AGF/AXF API Experimental. Escape Modeling API Frozen.
Public Release08/15/2009
[Slip] Automated build and tests, update site, basic documentation.
M11/1/2010
0.5.0. Builds to Modeling project standards. Meets general eclipse quality standards. User getting started documentation. New testing and parameterization functionality. All APIs and meta-models Provisional.
M26/1/2010
UI Polish. Complete parameterization, testing and data extensions. Meta-Model Extensions. AMF core Platform, API meta-model Provisional, AXF/AGF API Provisional. Extensive user documentation.
0.8.0 Release6/23/2010
0.8.0 Feature frozen. QA, bug fixes, internals and runtime improvements. Major documentation improvements. Meta-model funcitonality additions. All API and existing Meta-Models for "metaabm" model platform. Escape API platform.
0.9.0 Release6/26/2011
Integration of extensive Systems Dynamics and other features. Improvements (generalization, features) to meta-model from MetaABM. Focus on quality and community. Core AGF/AXF API platform.
1.009/01/2011

Table of Contents

Target Environments

Internationalization

Unknown. Help?

Table of Contents

Compatibility with Previous Releases

Not applicable.

Table of Contents

Themes and Priorities

Please note that the below are goals, not advertisements. We might not meet all of them, but by keeping them in mind, AMP contributors and users can focus their efforts on the important stuff.

Innovative

    Provide disruptive tools that support new ways of doing modeling and general science.
    Capture emerging best practices.

Complete

    Support all canonical ABM modeling capabilities.
    Provide an API capable of supporting a full user experience.
    Provide comprehensive documentation, examples and exemplar usages.

High Quality

    Conform to all Eclipse and modeling project conventions and processes, including builds, testing and internal documentation.
    Use Eclipse approaches (e.g. adapters, extension points, OSGi and other runtime mechanisms) to support extremely low coupling between AMP components and for toolsets utilizing AMP. For example, as an exemplar project the core Escape library and AMP will ideally share no common API.
    Within components, provide a high-level of cohesion so that minimal additional coding is required to adapt AMP infrastructure to specific needs.
    Provide attractive, consistent and responsive Look and Feel and branding consistent with overall Eclipse platform.
    Guide user through all exceptional conditions.
    Whenever possible, remove sources of cognitive dissonance for users and API developers.

Community Building

    Provide technology that is open ended enough to support unanticipated usages, yet provides easily understood and high-value components to encourage early adoption by core audience.
    Build an open, welcoming and inclusive community of collaborators and committers by involving other projects, organizations, and scientific disciplines.
    Preserve a strong architectural vision, but be open to new ideas and approaches.

Table of Contents

Appendix token

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"