Decision support software technology demonstration plan Page: 48 of 87
90 pagesView a full description of this report.
Extracted Text
The following text was automatically extracted from the image on this page using optical character recognition software:
3.2.2 Documentation of Software
The software will be evaluated in terms of its documentation. The documentation should
include detailed instructions on how to use the code, examples of verification tests performed with
the code, a discussion of all output files generated by the code and how the output files may be used
by other programs (for example, it can be directly imported into the Surfer graphics program), and
a review of the theory behind the technical approach used in the code.
3.2.3 Training and Technical Support
The Developers will be asked to list the necessary background knowledge base necessary to
successfully operate the code (i.e., basic understanding of hydrology, geology, geostatics, etc. along
with proficiency in auxiliary software used by the code and in use of operating systems (e.g. Unix,
Windows NT, etc.). A discussion of training and technical support provided by the Developers will
also be required. Much of this information has been presented in Section 3.1.
3.2.4 Ease of Use
Ease of use is one of the most important factors to users of computer software. Ease of use
will be evaluated based on examination of the codes operation, the presence of adequate on-line help,
the availability for obtaining technical support, the flexibility to change input parameters and data
bases used by the code, and time required for an experienced user to setup the model and prepare the
analysis (that is, input preparation time, time required to run the simulation, and time required to
prepare graphical output).
In a further attempt to understand the operation of the software packages, the Developers will
be requested to provide a brief (maximum of four hours) training course to a few individuals. These
individuals will then be asked to attempt to use the code to perform a few simple tasks. These tasks
will be performed without further guidance from the Developers, however, documentation and on-line
help will be permitted. This evaluation will be focused on how easy it is to use the code, not on how
well the code evaluates environmental problems.
It is recognized that there is a wide range in the level of sophistication and modeling in these
codes, and in many cases four hours will be insufficient training to use the full range of options of the
software. The purpose of the training is not to become a proficient user of the software but rather
to understand the required training level and ease of use of the software. The Developers will focus
on a few key points which they feel can be adequately taught within the limited time frame.
3.2.5 Efficiency and Representativeness
Efficiency will be evaluated through the resource requirements used to evaluate the problems.
This will be assessed through the number of problems completed as a function of time required for
the analysis and machine capabilities.39
Upcoming Pages
Here’s what’s next.
Search Inside
This report can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Report.
Sullivan, Terry & Armstrong, Anthony. Decision support software technology demonstration plan, report, September 1, 1998; Upton, New York. (https://digital.library.unt.edu/ark:/67531/metadc712499/m1/48/: accessed July 16, 2024), University of North Texas Libraries, UNT Digital Library, https://digital.library.unt.edu; crediting UNT Libraries Government Documents Department.