Master's Thesis - Computer Graphics and Visualization - TU Delft

loop in which users only need to specify the time of this loop.
7. The Culgi library is still in development. It is possible that some of the existing commands will be
replaced or deleted in future.
2.1.3 Product functions
From the general description of this product, the users’ characteristics and the interface analysis, the
Culgi GPE should have following functionalities:
1) To load Tcl interpreter into the system and be able to access the Culgi Library.
2) To represent the commands in the Culgi Library in a visual way. Each presentation unit is called a
module. A module should have properties, contents and interface. The contents of a module should be a
Tcl script which includes one or more Culgi commands. The interface should be an API that users
could manipulate. Modules will be the primary building blocks of a program.
3) To have a module library to manage modules. Modules are used to represent the commands in the
Culgi Library. But there will be several hundreds of commands in the Culgi Library. So the number of
modules will be big as well. In this case, a module library to manage these modules is necessary.
4) To provide interaction between users and modules. Users should be able to create or delete the
instance of the module, should be able to communicate with the module.
5) To run the program composed of modules.
6) Debug users’ programs.
7) To export the source code of the users’ programs automatically with the end user GUIs. We call
the export program an end user application.
8) To have an easy-to-use user interface that should wait for users’ commands and then execute the
corresponding actions.
9) To provide Enough help information on not only the function of modules and parameters, but also
on the interface itself.
In this section, we give out the overall description of the Culgi GPE. Basing on these general
requirements to the system, the section 2.2 explains the particular requirements.
2.2 Specific requirements
This section describes the functional and non functional requirements in detail. In section 2.1.1 , a
scenario is described to show how a user uses the Culgi GPE to achieve the goal successfully. Based on
this scenario, a Use Case Model 1 is defined to specify the features of the system. Then in section 2.2.2,
a detailed function list is presented. This list is concluded from the use case model.
1 The UP (Unified Process) defines the Use-Case Model within the Requirements discipline. Primarily,
this is the set of all written use cases; it is a model of the system's functionality and environment [1]. A
use case describes a sequence of actions that provide something of measurable value to an actor. An
actor here refers to a user in the system.
- 7 -