project-info/plan.xml

<?xml version="1.0"  encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan name="Agent Modeling Platform (Incubation)" plan-format="1.0"
	xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml">
	<release projectid="modeling.amp" version="1.0" />
	<introduction>
		<html:div>This plan is quite preliminary and will change. Also note
			that this plan somewhat ambitiously carries the project through to
			the initial 1.0 (non-incubation) release. Please note that as with
			all Eclipse Incubation projects, version numbers are 0.n. This does
			not necessarily reflect overall code completion or quality. For
			example 0.7.0 is planned to have a reasonably stable API and 0.8.+
			should (hopefully) be nearly production ready.</html:div>
	</introduction>
	<release_deliverables>
		<html:div xmlns="http://www.w3.org/1999/xhtml">
			Each release will include:
			<ul>
				<li>Update site including runtime, SDK, documentation and source.
				</li>
				<li>Features and plugins packaged (download).</li>
				<li>Examples (download)</li>
			</ul>
		</html:div>
	</release_deliverables>
	<release_milestones>
		<preamble />
		<milestone date="05/15/09" milestone="0.0.0">
			<html:div>Initial Commit</html:div>
		</milestone>
		<milestone date="06/15/09" milestone="M0">
			<html:div xmlns="http://www.w3.org/1999/xhtml">Basic repackaging / renaming. Move dependencies from oAW to
				M2T. Automated build and tests, update site. AMF API and meta-model
				Provisional. AGF/AXF API Experimental. Escape Modeling API Frozen.
			</html:div>
		</milestone>
		<milestone date="09/01/09" milestone="M1">
			<html:div xmlns="http://www.w3.org/1999/xhtml">Improvements (generalization, features) to meta-model from
				MetaABM. Builds to Modeling project standards. Meets general eclipse
				quality standards.
				All APIs and meta-models Provisional.</html:div>
		</milestone>
		<milestone date="12/31/09" milestone="M2">
			<html:div xmlns="http://www.w3.org/1999/xhtml">Improvements to meta-model based on community feedback. UI
				Polish. Meta-Model Extensions.
				AMF core Platform, API meta-model
				Provisional, AXF/AGF API Provisional.</html:div>
		</milestone>
		<milestone date="02/15/10" milestone="M3">
			<html:div xmlns="http://www.w3.org/1999/xhtml">Join 3.6 release train. QA, bug fixes, internals and
				runtime improvements.
				All API and meta-models Platform.</html:div>
		</milestone>
		<milestone date="04/01/09" milestone="M4">
			<html:div xmlns="http://www.w3.org/1999/xhtml">Features frozen. Bug fixes, minor internals.</html:div>
		</milestone>
		<milestone date="05/01/2009" milestone="RC1"></milestone>
		<milestone date="05/15/2009" milestone="RC2"></milestone>
		<milestone date="06/01/2009" milestone="RC3"></milestone>
		<milestone date="06/15/2009" milestone="RC4"></milestone>
		<milestone date="06/28/2010" milestone="3.6"></milestone>
		<postamble />
	</release_milestones>
	<target_environments>
		<internationalization>
			<html:div xmlns="http://www.w3.org/1999/xhtml">Unknown. Help?</html:div>
		</internationalization>
	</target_environments>
	<compatibility_with_previous_releases>
		<html:div xmlns="http://www.w3.org/1999/xhtml">Not applicable.</html:div>
	</compatibility_with_previous_releases>
	<themes_and_priorities>
		<preamble>
			<html:div xmlns="http://www.w3.org/1999/xhtml">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.</html:div>
		</preamble>
		<theme name="Innovative">
			<description>
				<html:div xmlns="http://www.w3.org/1999/xhtml">
					<ul>
						Provide disruptive tools that support new ways of doing modeling
						and general science.
					</ul>
					<ul>
						Capture emerging best practices.
					</ul>
				</html:div>
			</description>
		</theme>
		<theme name="Complete">
			<description>
				<html:div xmlns="http://www.w3.org/1999/xhtml">
					<ul>
						Support all canonical ABM modeling capabilities.
					</ul>
					<ul>
						Provide an API capable of supporting a full user experience.
					</ul>
					<ul>
						Provide comprehensive documentation, examples and exemplar usages.
					</ul>
				</html:div>
			</description>
		</theme>
		<theme name="High Quality">
			<description>
				<html:div xmlns="http://www.w3.org/1999/xhtml">
					<ul>
						Conform to all Eclipse and modeling project conventions and
						processes, including builds, testing and internal documentation.
					</ul>
					<ul>
						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.
					</ul>
					<ul>
						Within components, provide a high-level of cohesion so that
						minimal additional coding is required to adapt AMP infrastructure
						to specific needs.
					</ul>
					<ul>
						Provide attractive, consistent and responsive Look and Feel and
						branding consistent with overall Eclipse platform.
					</ul>
					<ul>
						Guide user through all exceptional conditions.
					</ul>
					<ul>
						Whenever possible, remove sources of cognitive dissonance for
						users and API developers.
					</ul>
				</html:div>
			</description>
		</theme>
		<theme name="Community Building">
			<description>
				<html:div xmlns="http://www.w3.org/1999/xhtml">
					<ul>
						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.
					</ul>
					<ul>
						Build an open, welcoming and inclusive community of collaborators
						and committers by involving other projects, organizations, and
						scientific disciplines.
					</ul>
					<ul>
						Preserve a strong architectural vision, but be open to new ideas
						and approaches.
					</ul>
				</html:div>
			</description>
		</theme>
	</themes_and_priorities>
	<appendix name="token" />
</plan>