Phase: Elaboration

See ProcessOverview for a description of the process I'm going to be following as I develop this project.

Management

• Phase goal: Plan development.
• Iteration goal: Further refine the vision and architecture. There will probably be at least 1 more iteration in the elaboration phase, because this is going to be a fairly large framework.
• Artifacts: Business Case | Software Development Plan | Vision | Work Breakdown Structure | Status

By the end of this iteration, I'd like to be using peppy to edit my own source code, so this will iteration be focused on usability.

Environment

• Phase goal: Install development environment and change management database.

The Trac process is documented in Software Development Plan, and I've used it successfully in Iteration 5. Further enhancements to the environment are likely, as I've found svn enhancements that can link svn checkins to trac ticket tracking.

Requirements

• Phase goal: Define architecture objectives.
• Artifacts: Use Cases | Release Specifications | Vision

The primary goal of this release is to increase the usability of the editor, as I would like to be using the editor as the primary editor for my own code by the end of the release.

Since I've announced the project to a wider audience, I hope to get feedback from other people about the quality of my documentation. I'm sure that it will need lots of improvement, but it will be interesting to see where. I feel that it isn't laid out that logically, so I'm definitely hoping for some suggestions in that area.

See the roadmap for a complete list of current requirements, or the individual milestones for requirements for each release:

• release 0.6.0 requirements
• release 0.6.1 requirements
• release 0.6.2 requirements
• release 0.6.3 requirements
• release 0.6.4 requirements
• release 0.6.5 requirements
• release 0.6.6 requirements

Design

• Phase goal: Describe architecture baseline.
• Artifacts: Design Models | Test Models | Architecture Description

As this iteration has progressed, I discovered that I needed some hyperspectral image analysis capabilities earlier than I had planned. So, I've integrated the hyperspectral image analysis capabilities of peppy earlier than I expected to.

I've had a large break due to my wedding and a move across country, and am getting back into peppy. I've actually had a chance to think about the architecture some more and want to refactor it a bit. I'm working on a Music Player Daemon control mode as a way to generalize the architecture some more.

The plugin system needs some work as well, so that's in line for a refactoring as well.

Implementation

• Phase goal: Produce architecture baseline.

See the roadmap for the current status of the implementation.

Assessment

• Phase goal: Assess architecture.
• Artifacts: Release Specifications | User Manual

Quite a lot has happened in the 0.6 series of releases. Several architectural refinements have made the code cleaner and more logical, although there's still work to do in that area. It is still inconsistent in places with respect to message passing or looping through a series of listeners.

The major architectural change was in the transition to Yapsy plugins which allow me to version plugins and activate/deactivate them in the running program.

Deployment

• Phase goal: Define user manual.
• Artifacts: Executables | User Manual | Developer's Guide

Milestone

Milestones are available at the roadmap.