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

More documents

Recommendations

Info

3a. If the content or the format of a module is not recognizable by the system, this module cannot be put on the canvas. 1. The user changes the contents of the module by module editor or by other editors and save the change. 2. This time the user can put the module onto the canvas without restarting the system. 3b. The user puts the module to a place where a module exists. 1. The system adjusts the position automatically or doesn’t allow this operation. 3c. The user finds out that the module on the canvas is not the right one, he or she should be able to delete it. Or the user wants to copy the existed module. 1. The basic edit functionality like copy, cut, move and delete is necessary. 4a. There are a lot of parameters in one module. Only a few are useful in general situation. 1. Be able to show the most common used parameters in general. 2. Show all the parameters if the user wants to. 3. Set default values to some parameters. 4b. The user wants to know clearly about the contents of this module 1. Be able to show the source code of the module. 4c. The user inputs the wrong parameters. 1. Check the valid type of the parameter. 2. Check the valid range of the parameter. 6a. The user runs the program with some necessary parameters missing. 1. Check the parameters in each module. If some parameters are missing, stop running and remind the users to set these parameters. 6b. The source code of the module is not correct. 1. Show the error message 8a. User doesn’t choose any parameters before exporting. 1. Only Tcl scripts are generated without an interface. 2.2.3 Functionality list Figure 2-1 The use case model According to the features of the Culgi GPE specified in the use case model, a particular functional requirement list is shown in Table 2-2. Table 2-2 A functionality list of the Culgi GPE No Requirement Description Req01 Module Category -Divided modules into categories. Req02 Load the Module -Load the Module Library into the interface. Library -Show the name of the module and the category this module belongs to. Req03 Module Editor -Supply a GUI of Module Editor. -Be able to show an existing module in this GUI. - 10 -
Req04 Select a module in the library -User can just type in or change some the necessary properties of the new module like parameters and source code of the module. -To help the users when typing in the source code, some basic functionality of text editor are supplied, like syntax highlighting. -Get the name and the category of the selected module. Req05 Create an instance of -Create an instance of the module according to the name and module category of this module. -Draw the icon of the module in the canvas. Req06 Interaction between -Receive the commands from users module and users -Show the parameters to the users according to desired information level. -Receive the arguments typed by users. -Check whether the value of a parameter is valid. - Check the type - Check the range of the parameter Req07 Specify the -Be able to specify which module should be run before other relationship between modules modules. Req08 Run the program -Be able to run Tcl scripts because the source code of modules is written in Tcl. -Run the module in the right order. Req09 Generate the Tcl -Generate the correct Tcl Scripts which can run without The Culgi Scripts GPE. -Allow the users to choose the parameters that will be shown in the End User GUI. -Be able to change the name of the parameters. 2.2.4 Nonfunctional requirements Ease of Use: Almost from the beginning to the end of the requirement analysis, we mainly focus on ease of use. But it is hard to define what ease of use is. A non-programmer would like an interface in which he can program just by clicking, dragging and typing some simple parameters; a user who does not know Culgi would expect an interface which can show him the basic functions of Culgi and the basic steps to make a simulation program; while a user who has some programming background and is familiar with Culgi would like to have more flexibility in programming. So ease of use has different meanings in various situations. To maintain a wide range of users, we need to provide multi views on programming to show different information in different situation. Extensible: Culgi Library is still in development. Changing in the internal structure or adding more functionality is still possible in the Culgi Library. Thus the Culgi GPE should keep independent from the Culgi Library. - 11 -
Page 1: A Graphical Programming Environment
Page 5 and 6: Preface This project started in Sep
Page 7 and 8: Abstract Culgi stands for Chemistry
Page 9 and 10: Contents Abstract..................
Page 11 and 12: Chapter 1 Introduction Culgi stands
Page 13 and 14: elationship model (see Figure 1-3).
Page 15 and 16: Chapter 2 Requirement Analysis This
Page 17 and 18: loop in which users only need to sp
Page 19: Primary actor: -Simulation Program
Page 23 and 24: Chapter 3 Design Models In chapter
Page 25 and 26: also generates the same result as (
Page 27 and 28: 3.3 The Concept Editor 3.3.1 Descri
Page 29 and 30: (a) Step1 Build Box Step2 Create Vi
Page 31 and 32: 3.5.1 Multi view of modules In the
Page 33 and 34: 3.5.2 Various widgets to display a
Page 35 and 36: a correct order. These source codes
Page 37 and 38: Chapter 4 Implementation of the Cul
Page 39 and 40: library. Meanwhile, the interface p
Page 41 and 42: For example, in Figure 3-5(b), the
Page 43 and 44: The Module Editor is a tool for cre
Page 45 and 46: corresponding operations. Figure 4-
Page 47 and 48: The second problem is about how to
Page 49 and 50: sequence. From these approaches, we
Page 51 and 52: Chapter 5 Results and Test The prev
Page 53 and 54: (a) Before click. (b) After an item
Page 55 and 56: instance of the module setDPDEnviro
Page 57 and 58: (a) Make only “Oil” visible (b)
Page 59 and 60: Feedbacks from the novices of Culgi
Page 61 and 62: Chapter 6 Conclusion The goal of th
Page 63 and 64: Chapter 7 Bibliography [1] Craig La
Page 65 and 66: Appendix A. Class Diagrams Figure A
Page 67 and 68: Figure A-4 Class Diagram of “Sequ
Page 69 and 70: Appendix B. Tables Table B-1 Functi
Page 71 and 72:
Table B-3 Functionalities of Class
Page 73 and 74:
Table B-5 Functionalities of class
Page 75 and 76:
Table B-7 Properties of input param
Page 77 and 78:
Appendix C. DPD Simulation # DPD Si
Page 79:
$plot SetSize 400 400 $plot Load My
show all

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

Create successful ePaper yourself

Delete template?

Save as template?