Team Inventory and Standards-Includes Team members and their positions within the group.
As well as a list of standards and By-laws which we have established for ourselves.
Software Development Plan (SDP)-The SDP is a paper document that contains the
information for our development process (i.e. management, models, milestones, and etc.).
Requirements Document-The Requirements document is basically our guide to
implementing our design. Every function and expectation needed to develop our project
should be recorded within this document.
Prototypes
1. Our initial prototype will be a single MClass which will demonstrate the touch-and-feel
feature of our design
2. Our second prototype will be the Control Panel with one fully operational characteristic
3. Our third prototype will be a preliminary version of the translator
Reviews
1. Internal code reviews to assure progress
2. Reviews with client to confirm design and progress
Design Document-This will be the official documentation for our design which will include
diagrams created by the Software through pictures software using the Object Modeling
Technique.
In accordance with this document, a technical document will be produced using Javadoc.
Presentations
1. Visual presentations to inform our client of our progress will be made from the NAU-
Motorola Group Homepage on the WWW. In addition, Microsoft Powerpoint presentations
will be used when necessary.
2. Hard copies of our code will be filed with our recorder to have available upon request by our
client and team members.
DEVELOPMENT PROCESS
The NAU team has decided to use an Incremental approach for the development process. Various
prototypes will be made throughout the design/development process. For example, a single
Reusable Component will be constructed (scheduled for a 10-22-96 completion) and reviewed
before refinements are made and the library of components completed (11-7-96). The completed
library will then be submitted to Motorola for evaluation (11-13-96). The GUI Control Panel similarly
will be framed up and reviewed (12-3-96). Upon completion (1-27-97) the Control Panel will be
reviewed, refined and handed off to Motorola (2-13-97). The Translator portion will be completed (2-
17-97), reviewed, refined and then delivered to Motorola (3-6-97). The Master Schedule further
breaks down the increments of the developmental timeline.
These early deliveries to Motorola should not be viewed as finished products, but rather as material
that the NAU team believes resembles the final product. Then with interaction between the NAU
team and Motorola the package to be finally presented to Motorola on April 17, 1997 will really be the
package that Motorola is seeking. The intent is to catch requirements problems early on in the
process.
CONFIGURATION MANAGEMENT
The File Management Tool - RCS Revision Control System - will be used to maintain
software progress through cataloging successful milestones as they are developed. This tool
will allow us to keep multiple instances of a file and can be used to maintain library check-in
check-out for any versions of the software that have been developed.
Options available: