CyTerm software development risks
The Java 1.2 platform may not be available on Linux. This will be managed
by using jdk1.1.7 instead. Some 1.2 collection classes can be ported to
1.1.7 if needed. The jigsaw web server has been proved to work on 1.1.7
and 1.2. Another fallback is to install solaris for intel on the server.
The jigsaw server or java VM may not be stable. This will be managed by
using apache as a face with jigsaw only used when needed. A monitor process
can restart jigsaw if it fails. Some apache cgi scripts can be created
to start and stop the jigsaw servers.
Input models and unicode fonts may not work on all platforms. Testing all
combinations of platform and language may be difficult. This will be managed
by testing (by Cycom) on real client machines during the installation and
early use of the system.
Security code (encryption) may be difficult to licence and develop and
deploy because of API inadequacies and political barriers to the release
of implementations by Sun.
Source code version control may be inadequate. See the configuration
management strategy. The risk is managed by only having one developer
to minimise conflicts.
Insufficient software tools are available. The developer has JDK1.2 beta
4, emacs with cc-mode, a homegrown project builder "jmake" and a homegrown
java launcher "ja". The jigsaw server and java servlet toolkits have been
tested OK. The risk is managed by equipping with command line tools (uxwin32,
jdk) and unix utilities. Graphics layout can be achieved linguistically
rather than graphically. Design tools for UML diagrams are lacking. A demo
version of rational rose will be used with gif exports or Together-J may
be considered for purchase. MS-Word vector graphics may also be used.
Insufficient time/money may be available. This risk is managed by planning
for phased delivery where each delivery is standalone and can operate indefinitely
without development resource. Future phases can be postponed pending acquisition
of more time/money.