Monday, November 10, 2014

A Simple Development Plan.

    As I promised, today I will deliver an informal project plan. It will outline the activities for each week with a single development goal for each. The plan might be revised over the next few weeks.

Week   Goal
0        Project Overview and Discussion
1        Create "Hello World"-style program which serves up internally stored XHTML
2        Create "Hello World"-style program which serves up externally stored XHTML
3        Create "Hello World"-style program which serves up externally stored XHTML
          whose filename we extract from an XML file
4        Extend the prototype so a method populates the #STENCIL_REPLACEMENT_VARIABLE#s
          in the XHTML page.
5        Extract the name of the method which populates the stencil replacement from an XML file
6        Consider converting between DOM and SAX XML reader for efficiency and user control over
         data structure which hold application configuration parameters.
7       Improve exception handling. Do not simply throw exceptions upward.
8       Add contracts for enforcing "program-correctness" within controller.
9       Deploy this first iteration of the evolutionary model at java.net/projects/caboose
10     Create life-cycle documents for development of the production product based on reasoning
         from this prototype

   The secondary goal for this week is the creation of an XML Reader for parsing the application's configuration file. We will initially use a Document Object Model (DOM) parser for reading and interpreting the file. This is probably simplest since, as a DOM reader parses an XML file, the reader place all of the attributes, elements, and etc. in a data structure, the DOM, from which one can read them. If a future week, we might create a more efficient, special-purpose structure for holding the elements and attributes using a SAX reader which does not store these values in data structure while processing it. We might save this for the second full iteration of the evolutionary process model.

That is all for today, Team. La-La.

No comments:

Post a Comment