Project Goal: “To write a web-based ap=
that will create, solve, display, and compare performances of a 3D hidden w=
puzzle generator/solver by the middle of June, 2005.”
Project Development Methodology: This will be
iteratively driven starting NOW.
Project Cycle Point: At this point, I am
drafting plans for the under lying data structure(s), design documentation =
requirements, use cases, risks, testing, and flow of control.
At this point my number one risk would be not
finishing what I set out to do for this iteration, and having to carry some=
it over (hopefully not!).
Next Steps to move on: If everything actually
gets done listed for this iteration, the next thing to do would be the sequ=
and class (CRC) diagrams, the work break down structure, and completion of =
high-level flow of program control diagram. Then after this and in later
iterations this term, we’ll be refining most of what was done for the
first and second pass throughs that should show at a not-so-high level how =
user interface and the code will be organized.
this first iteration, I intend to do the following action items:
Rewrite this introduction to provide a more
descriptive explanation for this iteration’s action items.
Rewrite the “Requirements.xls”
document correcting certain grammatical errors, spelling errors, and items =
belong more in the pseudo code section of the project design and documentat=
such as requirement #1: “Create an automatic method…”, and
lastly add certain critically overlooked requirements such as (1) bench mar=
measurements for performance of the application, (2) collecting the benched
marked statistics for logging, and (3) help/documentation which will have t=
install and uninstall instructions.
Rewrite the “UseCases.doc” and t=
“Use Cases Diagram.vsd” to reflect the missing requirements with
the use cases, display the correct ways in which each use case in some form=
another “uses” another use case or actor on a use case (this sh=
also communicate the flow of control to some extent), and last but not least
compile together the missing preconditions and postconditions parallel to t=
“uses” head and tail arrows of the diagram in a separate docume=
This separate document will have references to the corresponding use cases.=
Rewrite the “Risk Management.doc”
file explaining which risk have been mitigated as described earlier, and wh=
ones are sill being worked on as we speak.
Write a Software Quality Assurance Plan (SQA=
document using the “CST412_SQAPLAN.doc” template document that =
talk about how I plan to go about doing my test plans and my unit tests.
Begin drafting the over all Test Plan and Un=
Test Plan in the “CST412_Unit-Test-Plan_Template.doc” document =
will supplement the Software Quality Assurance Plan content.
Begin drafting a plan for the underlining da=
structure (The Red/Black Tree) in which we’ll use for processing the
dictionary and the puzzle (This will help to perpetuate how the algorithms I
already have will be reused without truly starting from scratch and also how
the ADO.NET database connection will use it’s notion of the
Begin drafting the user interface prototype.
This will help to perpetuate the UI design ideas we can up with on the boar=
few weeks back.