The purpose of this Requirements Document is to lay down, for both Motorola and the NAU Design Team to agree upon, a formal description of the product to be built and to enumerate the standards it must meet to be acceptable. It is not the intent of the document to specify an approach or imply any design details other than those required by the needs of Motorola. Simply, it describes "what" is to be built, but it says very little about "how" this is to be accomplished. This document begins with a brief overview of the product, its major components, and their relationship to one another to be built by the NAU Team. The section following, Functional Requirements, specifies exactly what will be required of the software package's three major sections. A section titled Nonfunctional Requirements outlines other non-software requirements made by Motorola. A final section, Feasibility Issues, briefly addresses the resources which the NAU Team will be drawing on throughout the development cycle. This document is attached to a Software Development Plan which more clearly outlines the process to be implemented by the NAU Team to guarantee the delivery of the product described in this document.

The software we are to create is an expansion of the functionality included in the Java Developer's Kit (JDK). The JDK contains classes that are provided as elements in a Graphical User Interface (GUI) (e.g. buttons, dialog boxes, text windows). The software package that we will develop will include an inherited subset of these classes which are the Reusable Component Class Library. This will be our initial element of design. The classes contain properties that can be adjusted to respond to the preferences of a user. The user will select theses preferences, such as Fonts, Sizes, and Colors through a GUI Control Panel, which is our 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 a preferred language environment that he/she chooses to work in. The changes to the workspace must be made dynamically, or during the run-time of an application. The third portion of our software package is a Translator that will convert GUI elements written using the original classes within the JDK to the modified classes that can be manipulated 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.