Iteration Plan - edwardkort/WWIDesigner GitHub Wiki

This is the iterations and references to the associated user stories that will be implemented for WIDesigner.

The length of each iteration is uncertain at this time.

Iteration 1

Data

Functionality for building up scales and tunings from scale symbol lists, temperaments, fingering patterns, and reference notes will be added in conjunction with UI development.

  1. Scale symbol list (see User Stories 1): define XSD, XML samples, binding framework. Validate marshal/unmarshal behavior. Developer Edward Kort Completed, 5/18/12

  2. Scale (see User Stories 2): define XSD, XML samples, binding framework. Validate marshal/unmarshal behavior. Developer Edward Kort Completed, 5/8/12

  3. Temperament (see User Stories 4): define XSD, XML samples, binding framework. Validate marshal/unmarshal behavior. Developer Edward Kort Completed, 5/8/12

  4. Fingering pattern (see User Stories 6): define XSD, XML samples, binding framework. Validate marshal/unmarshal behavior. Developer Edward Kort Completed, 5/8/12

  5. Tuning (a fingering pattern with associated notes (name and frequency): define XSD, XML samples, binding framework. Validate marshal/unmarshal behavior. Developer Edward Kort Completed, 5/8/12

  6. Flatten package hierarchy, removing redundant "impedance" package. Developer Edward Kort Completed, 5/8/12

Iteration 2

Geometry

Develop the initial data content that describes the geometry of a woodwind. Incorporate a mechanism for identifying those dimensions in the geometry that may or may not be under the control of the optimization engine.

  1. Define XSD for a general woodwind geometry. Developer Edward Kort Completed, 6/3/12

  2. Create a few representative instrument XML instance documents. Developer Edward Kort Completed, 6/3/12

  3. Generate the binding framework for the instrument schema. Developer Edward Kort Completed, 6/3/12

  4. Incorporated in the instrument schema, and/or as a separate structure, define identifiers associated with geometry elements to facilitate optimization control. Developer Edward Kort Completed, 6/3/12

  5. Write unit tests to validate the marshal/unmarshal behavior of the instrument instance documents. Developer Edward Kort