View the software test specification here in PDF format

Introduction

This document contains testing information for the Trinity Project

Revision History

• September 21st, 2001 - Merged with hardware test specification and added PDA limitations, discovery, and delivery mechanisms. Usage, range, LED signalling, and product delivery information updated.
• September 12th, 2001 - First version of the document typed up.

Software

• Protocol level - At the protocol level, the Palm OS application will talk to the prototype system using the IrComm protocol which is one of the upper layers of the IrDA protocol stack. This functionality will be tested both with a PC with an infrared port, and the prototype unit itself once a IrDA stack has been implemented for it. The IrDA protocol handles addressing of multiple units via addressing at the transport layer of the protocol.
• Communications Module - This is a module of code that will handle the infrared communications at a level that abstracts the details of setting up and maintaining the connection from the remainder of the Palm OS application. The purpose of this is to easily add support for other communications protocols (Bluetooth, TCP/IP, Serial, etc.) in the future. This module will be tested both using debug output to dump data coming into it, and debug input to make sure it's being processed correctly. Also, it will be tested with a PC running a terminal over infrared, as well as finally, the prototype unit.
• Terminal Emulation - This will emulate a terminal on the Palm OS in such a way that commands can be composed and sent to the prototype and feedback received in an interactive manner. We will test using debug code to make sure commands are being composed in a proper manner, as well as verify the connection is being handled properly with the communications module.
• Text File Transfer - Transfer of text files from the Palm OS device to the prototype device and back will be tested with files of various sizes and ranges of characters, with both a PC and the prototype device.
• Ethernet Configuration Application - This is the graphical configuration tool for configuring ethernet information through the Palm OS device. This module will be tested on its ability to communicate with the communications module, and its ability to compose the proper commands to send to the prototype device
• Compatibiility - Currently only Palm OS compatibility planned for the software, however all steps are to be taken to abstract any API specific code from the functional algorithms and procedures. This will facilitate future ports to platforms such as Pocket PC.
• Performance - Total time for setting up an infrared connection and configuring ethernet, transferring a file, and executing a command should be less than the time for setting up a hard-wired serial connection to do the same. Transfer speeds suitable for terminal configuration (9600 bps and above) will be tested, as well as a comparison of the form factor of the Palm OS device compared to that of a laptop with serial cable.

• CPU time taken by the software is not a concern, as the Palm OS only executes one process at a time, and any extra battery drain through CPU usage will be negligible compared to that of the IR port being activated during use (which, as mentioned below is to be minimized).
• Most Palm OS devices have anywhere from 2 to 8 megabytes of memory, shared between primary and secondary storage. Linkage to C++ libraries, in compliance with Adtran's request that development be done in an object oriented manner, will be tested to see how it effects the size of the compiled program. Ideally, the program will take up less than 200 kilobytes of the Palm's memory in secondary storage.

• IR Port Battery Drain - When not communicating, the software will disable the IR port to conserve power. Observations will be made to see how fast the Palm OS battery power drains with the IR port on, off, and in normal configuration of the prototype.

• Intelligence - Device should make it simpler to configure the communications device compared to using a laptop with a serial cable, but is still targeted as a convenience towards customers who have enough intelligence to know the traditional methods.
• Visual acuity - LCD Screen on the Palm OS device is approximately 160x160 pixels. Standard font sizes for applications will be used so that any modifications made to the PDAs to facilitate usage by the vision impared will work as well with this program as any.

• Software Licensing - Free development tools and libraries are being used, to avoid licensing fees and renewal issues.

• Style - a consistent and modular structure for the software, and clearly written code, spaced and formatted in a consistent manner, will be used to ease readability and facilitate integration of this software into a production environment
• Portability - Program logic should be easily portable from the Palm OS to other platforms, although differences in memory management between Palm OS and other systems may require some porting efforts. All attempts will be made to minimize any troubles in this area, so far as the Palm architecture will allow. The software will also likely be easily modified to work with other communcations media besides infrared. All medium specific code for communications will be regulated to a central location in the code base (the communications module), in order to easily add and change different ways of communicating in the future(such as a serial port connection, or TCP/IP). (from Software Design Document , August 29th)

• The software will be initially delivered on CD, to be installed either by the windows HotSync utility, or by command line/GUI utilities available for Unix users.
• The manual for the software will be supplied in print, and on disk in PDF format, explaining the operation of every part of the software, with screenshots.
• Software updates will be supplied to users by internet access likely, due to the small file sizes involved.

Prototype System

• Use IrDA protocol up to IR COMM
• Use serial protocol
• Communication speeds up to 56Kbps

• IRDA (Prototype)
• Serial (Prototype)
• Sleep / Listen
• Active Mode

• Decode IRDA to IR COMM
• Transfer data to data communication product
• Beam Angle / Range - Adapter should be capable of communicating with the Palm OS device anywhere within three feet and approximately 30 degrees from normal. Tests will be run to determine the actual characteristics once Palm OS devices are available.

• Capable of communicating with any IrDA device

• Communication speed up to 56kbps (stated earlier)

• Adapter dimensions - Less than 3" x 3" x 1"
• Weight - Less than 10 oz.

• TL16C550C UART - 5V, 4mA, 20mW power consumed
• Tranceiver - 5V, 55uA, .275 mW power consumed
• TIR1000 IrDA encoder/decoder - 5V, 3uA, .015mW power consumed
• Total consumption - 20.290 mW

• Product should work in any environment capable of supporting Adtran Data Communication products
• IrDA protocol handles unpredictable interference from other IR beams

• Minimum Power - Typically less than 5V, 30 mW energy consumption
• Cost/Production Cost - Hopefully under $25.00 ($10.00 goal). Retail cost $75.00 maximum, hopefully closer to $40.00. Prototype cost approximately $125.00. Should have no maintenance or service cost.

• FCC Regulations - All parts are off the shelf and should fall under all existing FCC Regulations at this time

• Mobility - Usage of this device requires nothing above what is normally required of the sort of people who are to work in a machine room configuring devices with a laptop and a serial cable. Mobility requirements may even be less in most situations, due to less equipment to have to carry around.
• Visual Acuity - User must be able to discern that LED's are being lit on the front panel of the prototype, in the same way that the user would be expected to on the Adtran products before.

Technology Transfer

All code and documentation on usage and development for the Palm OS software will be handed over. The code for the prototype system is a slightly more difficult case, and it is important that we use as high level code as possible to facilitate porting of the prototype code to whatever systems Adtran might need to use it on in the present and in the future. Again, all code and documentation on the code's development and usage will be handed over upon completion and testing.

Access to the prototype system is possible, however with portable coding practices for the prototype system, and usage of tools developed to test and debug the Palm software, it is hoped that porting the prototype code to the platform of their choice will be simple and rapid.