III. Translator
A. The translator will convert applets written using the original
classes of the JDK to classes which make use of the new RCCL.
- The translator will be a command line application which will
take a .java script and produce a translated .java script.
- The translated script will accommodate all the functionality
of the old script along with the new functionality created with
the RCCL.
- The translator will be able to accommodate changes in the
RCCL without requiring alteration to the translator itself.
NONFUNCTIONAL REQUIREMENTS
I. Documentation
A. Design Documentation
- A set of Design Documentation produced with Software Through
Pictures using OMT will be presented to detail the design.
- Entity Relationship Modeling will be used to present the data
encapsulation of the system.
- Data Flow Diagrams will show data flow through the system.
- State Transition Diagrams will outline the flow of control
through the system.
B. User Documentation
- A User Guide constructed in Javadocs will explain usage, maintenance,
and extension of the system including:
- How to add and delete from the RCCL
- How to add and delete from the characteristics of the control
panel
- How to use the control panel
- How to extend the functionality of the translator for an altered
RCCL
- How to use the translator
- Examples of the RCCL addition and test procedures will be
provided.
II. Protection of Intellectual Property
A. The teams presentation homepage, used as a communication tool
with Motorola, will be password protected.
B. Coding and Design Documentation will not be shared with those
outside the design group.
C. All products, documents, and ideas created by the NAU team
will be considered the Intellectual Property of Motorola.
III. Miscellaneous Non-Functional Requirements
A. All code must be written in Java.
B. All applets must be executable through appletviewer or some
web browser.
C. All applets/applications must be supported on the Solaris
operating system.
D. No outside code will be used in the project, except that of
JDK.
FEASIBILITY ISSUES
I. Technical
A. Required development resources which will be used in this
project are:
- Object Modeling Tool ( OMT )
- Java Developer's Kit ( JDK )
- Revision Control System ( RCS )
II. Risk Analysis
A. See Software Development Plan.
III. Resource Availability
A. Required expertise
- The Project Manager, Dr. Ken Collier, will provide control
for the development process.
- Project advisor, Dr. John Placer, will give expert advise
and design assistance concerning compilers and adaptive systems.
- Motorola, the customer, provides conformation of product fitness
at various stages of development.