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

More documents

Recommendations

Info

2.2.1 The use case model In this part, a scenario in which a user uses the Culgi GPE to achieve the goal successfully is proposed. And then based on this scenario, we will analyze the detailed requirements of The Culgi GPE in the next part. A user wants to build a Tcl scipt to do chemistry simulation with the Culgi Library. He starts the Culgi GPE and opens a new file. Then he sees that there are three parts in the interface, they are menus, module library and canvas. He first chooses the right module he wants in the library, and then he needs to create the instance of the module in the canvas. Suppose he just does drag and drop, a new instance of the module is appeared in the canvas. Then he would set some values to the module according to his target. After repeating these steps several times, he has already collected enough modules to do the simulation. Then he needs to make sure that the system will run these modules in the right order. After defining the running order, he runs the program. Finally he exports Tcl script of this program. 2.2.2 Use case model Based on the scenario, we will define the use case model. The use case model treats the Culgi GPE as a black box and describes the interaction between external actors (users) and the Culgi GPE. It is about how a user uses the Culgi GPE and what the Culgi GPE will do in response to the user’s request, without assuming how the system works internally. - 8 -
Primary actor: -Simulation Program Authors Stakeholders and Interests: -Simulation Program Authors: wants to find the right modules in the module library, wants to use these modules to build a simulation program, test this simulation program and export a source code of this program. Preconditions: -The simulation problem can be solved by the Culgi Library. -The module library contains the right modules. Success Guarantee: -A Simulation program is built in the Culgi GPE and produces a correct simulation result. -A corresponding Tcl script of the simulation program is generated and runs properly. Main Success Scenario (Basic Flow): 1. A user (a simulation program author) runs the Culgi GPE, and wants to create a new simulation program. 2. The user selects a module in the modules library according to the module name. 3. The user puts this module in the canvas. The Culgi GPE shows the module on the canvas 4. The user sets the parameters of the module. 5. The user specifies the logical relationships among modules. The user repeats the steps from 3 to 7 until the he or she thinks that the program is finished 6. The user runs the program. The Culgi GPE will show the running result or a graphics window. 7. The user chooses some parameters of modules show on the canvas, and exports the program into Tcl script. 8. A Tcl program is created by the system with an end-user GUIS, in which the parameters checked in last step are open to be set. Extensions (Alternative Flows): a Whenever users want to save the current program that can be used later, the system should supply the functionality like “Save” or “Save as”. 1a. The user wants to build a simulation program continuing previous work. 1. He will open a file in Culgi GPE, then the modules and corresponding arguments are loaded to the current file. 2a. There are too many modules in the library. It is hard to find the right one. 1. Divide the modules into category according to the functionality. 2b. The user doesn’t find a proper module. He wants to make a new module himself. 1. The system supplies a module editor in which creating a new module or changing an existed module should be easy. 2. The new module should be loaded into the module library without restarting the system. - 9 -
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: loop in which users only need to sp
Page 21 and 22: Req04 Select a module in the librar
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?