Software Developement Plan

OVERVIEW OF THIS DOCUMENT

The purpose of this Software Development Plan is to outline for Motorola the approach that will be taken by the NAU team in designing, implementing and documenting the "Java Control Panel" project that has been conceived by Motorola. It contains the following sections:
Project Description A brief description of the software itself. Please note that an additional document, entitled Requirements Document is attached, which describes the product to be produced by the NAU team in depth.

Structure of the Team A list of team members and responsibilities.

Risk Analysis Risk Analysis Results of a preliminary risk analysis to illuminate possible pitfalls to be surmounted during this project.

Requirements Coverage Details of our plan to assure that requirements are not lost in any of the stages from the initial "capture" phase to delivery date.

Documentation To provide details of the design at several levels of abstraction as well as instructions as to its end-usage and maintenance.

Development Process A brief discussion of the paradigm that the NAU team is developing under. This section highlights specific milestones on the attached Master Schedule which correspond to the development paradigm.

Configuration Management Discusses the technique employed by the NAU team to ensure that stable configurations of the software are maintained for development purposes.

Testing Specifies the system by which the NAU team will both detect errors and completeness of requirements coverage.

Tools & Environments Lists the commercial tools and platforms that the NAU team will use for design, implementation, testing, documentation and presentation of its product.

Updating Project Status A plan to keep Motorola abreast with the current progress of the project.

PROJECT DESCRIPTION The software is an expansion of the functionality included in the Java Developer’s Kit (JDK). There are classes in the JDK that are provided as elements in a Graphical User Interface (GUI) (e.g. buttons, dialog boxes, text windows). The software package to be developed will include an inherited subset of these classes which are modified to respond to the preferences of a user. The user will select theses preferences, such as Fonts, Sizes, and Colors through a Control Panel, the second key element of the package. The Control Panel must also allow the user to make a selection from a given set of Languages for that users preference. The changes must be allowable dynamically, or during the run of an application. The third piece of software is a Translator that converts GUI elements written using the original classes within the JDK to the modified classes that are manipulatable by the Control Panel. Accompanying these software deliverables will be corresponding documentation covering design, use, and maintenance of the software. As the software is to be used as a basis for further work by Motorola, certain guidelines will apply to the package. All code will be written in Java. The Control Panel must be designed to accept new GUI elements along with their required preferences. The Control Panel too must be able to accept avenues of control without alteration to the code. This requirement mandates that the software be written in a totally encapsulated form so that it may be "blindly" added to or taken away from without disrupting the continuity of the system.

Page 1

Document Index

Page 3

Project Description	A brief description of the software itself. Please note that an additional document, entitled Requirements Document is attached, which describes the product to be produced by the NAU team in depth.
Structure of the Team	A list of team members and responsibilities.
Risk Analysis	Risk Analysis Results of a preliminary risk analysis to illuminate possible pitfalls to be surmounted during this project.
Requirements Coverage	Details of our plan to assure that requirements are not lost in any of the stages from the initial "capture" phase to delivery date.
Documentation	To provide details of the design at several levels of abstraction as well as instructions as to its end-usage and maintenance.
Development Process	A brief discussion of the paradigm that the NAU team is developing under. This section highlights specific milestones on the attached Master Schedule which correspond to the development paradigm.
Configuration Management	Discusses the technique employed by the NAU team to ensure that stable configurations of the software are maintained for development purposes.
Testing	Specifies the system by which the NAU team will both detect errors and completeness of requirements coverage.
Tools & Environments	Lists the commercial tools and platforms that the NAU team will use for design, implementation, testing, documentation and presentation of its product.
Updating Project Status	A plan to keep Motorola abreast with the current progress of the project.