Laserfiche WebLink
The basic framework of the CRDSS is that of an integrated system in which all of the components <br />can be run separately. An integrated design is facilitated through the use of the CRDSS <br />configuration file (see Task Memorandum 1.05-23) and allows the end-user to run CRDSS <br />applications without having to understand in detail the underlying workings of the CRDSS <br />component applications. It is necessary that components can run separately so that they can be <br />developed and supported independently. <br />In order to provide a flexible environment for development and to avoid channeling all access to the <br />CRDSS through a single GUI that may be incomplete (and therefore lack functionality that is <br />required during Year 1), a UNIX shell script will be used as the main interface to the CRDSS. This <br />shell script will set the necessary CRDSS variables and will coordinate execution of CRDSS <br />applications. Such a configuration will allow the functionality of the system to be developed and <br />debugged. The GUI version of the main CRDSS interface will be developed parallel to the UNIX <br />script and will generally have less functionality than the script (i.e., the number of applications that <br />run from the GUI will be less than the number that run from the script). <br />There may be many components of the CRDSS that the user does not have access to from the main <br />CRDSS interface (e.g., data processing routines and analysis programs). However, these <br />applications will be available from a UNIX shell and will be fully documented. More applications <br />will be incorporated into the main shell as time allows and as the value of these applications to users <br />is identified. Incorporating applications into the main CRDSS GUI will be done by providing <br />?hooks? into the main GUI such that the user's button press results in making system call to the <br />appropriate applications. The application then runs as if it were executed independently of the main <br />shell. The major components of the CRDSS will be represented as menu selections in the main <br />CRDSS shell. <br />GUI Development Plan <br />Workplans for each programming effort will depend on the specific features of each program to be <br />developed. The plan presented below concentrates on defining the guidelines to be used for the <br />major components of the CRDSS. <br />In general, the consultant recommends that the development of GUIs be given a lower priority than <br />developing functional analytical models and utilities. The consultant is wary of concentrating too <br />much effort on GUI development such that resources are used developing GUIs rather than in <br />developing working models and good data sets. <br />In order to guide GUI development so that it is most cost-effective, the consultant will interact with <br />the System Integration Team to discuss GUI options for current development efforts and will <br />coordinate development where duplicate efforts are likely. For example, tasks which rely on a time <br />series plotting tool (see Task Memorandum 1.05-18) will both use the same GUI display <br />components, rather than developing separate tools or implementing existing tools twice. Public <br />domain software will be used if possible. <br />The general procedure for new GUI development will be as shown in the following procedure and <br />applies to stand-alone model interfaces and DMI utilities: <br />Prepare mockups of screens proposed for the GUI. If the development is new, then the GUI <br />? <br />builder can be used for this task. Hand-drawn sketches are also appropriate. Initial <br />2 <br />A275 07.28.94 1.05-31 Malers <br />