AMS G U ’ I APPENDIX D

(1)

211

APPENDIX D

AMS G ^RAPHICAL U ^SER ’ ^S I ^NTERFACE

A prototype of AMS has been implemented using the latest techniques in software engineering such as : graphics, windowing, pop-up menus and the object-oriented programming paradigm. It is based on four existing and proven packages. QNAP2 (Queueing Network Analysis Package 2) [14] for modeling and simulation, GSS (Graphical Support System) [16] for the graphical editor, S-PLUS [17] for the post-simulation, and MODLINE [18] mainly for the graphical user’s interface. The prototype is developed on a SUN machine running SunOs operating system. It is coded in C language. At present time, about 15 000 lines has been coded.

The aim of this appendix is to present, through a few samples of created screen dumps, the graphical user’s interface of the AMS. We remind that in chapter II, other screen dumps are reported, mainly for editing a satellite based communication network. More details can be found in [41] and [42].

Figure D.1 shows the initial window which appears when the AMS is asked to run. It also shows the task menu associated with an AMS model (for example

“Test.ams”). At this level, the end-user can ask for editing a model (“edit” entry), running simulations (“run” entry), displaying simulation results (“display” entry), creating experiments (“create plan” entry), or generating documents (“generate_docs” entry for an extended document or “generate_summary_docs”

entry for a short document). At this level, the end-user can also employ the AMS

(2)

workbench as a file manager. He can change for example the current directory, copy or delete files, etc.

Figure D.1 : AMS workbench

At the editing phase, the end-user has at his disposal a library of models symbolized by a set of icons (Figure D.2). There are nine simple icons, each one represents a model : Ethernet Bus, FDDI ring, Satellite repeater, MAC Ethernet, MAC FDDI, TCP, Telnet Server, Telnet Client, IP, and FTP. The icon representing a bridge can be used to interconnect Ethernet LANs, FDDI LANs and Satellite backbones. In fact, it designates five bridge models: Ethernet- Ethernet, Ethernet-FDDI, Ethernet-Satellite, FDDI-FDDI, FDDI-Satellite.

Finally, there are two special icons which can be used to edit hierarchically a

communication network: stack icon and net icon.

(3)

icon. Inside the stack window, only the icons from which a stack can be built are available.

Figure D.2 : The iconic library of AMS

213

(4)

Figure D.3 : Net and stack submodels

(5)

Each edited object (graph, node, or link) is associated with a menu. Figure D.4 shows the menu associated with a graph, where a graph represents a communication network. With this menu, the end-user can create nodes (“Create node” entry), or generate the QNAP2 code modeling the edited communication network (“Generate Code” entry), or set the model attributes (Figure D.5 shows the list of model attributes).

Figure D.6 depicts the menu associated with each node where a node is represented by an icon. The end-user can set the node attributes, duplicate or delete an existing node. Necessarily, a node is an extremity of a link. Figure D.6 shows also the link types. For example, “Lien_bus” is used to link an Ethernet Bus to a MAC Ethernet or to a bridge; “Lien3_4” is used to link IP to TCP.

Finally, figure D.7 shows the menu associated with a link. The end-user can set a link attributes which are mainly measurements.

AMS G U ’ I APPENDIX D

211

APPENDIX D

AMS G ^RAPHICAL U ^SER ’ ^S I ^NTERFACE

The aim of this appendix is to present, through a few samples of created screen dumps, the graphical user’s interface of the AMS. We remind that in chapter II, other screen dumps are reported, mainly for editing a satellite based communication network. More details can be found in [41] and [42].

Figure D.1 shows the initial window which appears when the AMS is asked to run. It also shows the task menu associated with an AMS model (for example

entry for a short document). At this level, the end-user can also employ the AMS

workbench as a file manager. He can change for example the current directory, copy or delete files, etc.

Figure D.1 : AMS workbench

Finally, there are two special icons which can be used to edit hierarchically a

communication network: stack icon and net icon.

icon. Inside the stack window, only the icons from which a stack can be built are available.

Figure D.2 : The iconic library of AMS

213

Figure D.3 : Net and stack submodels

Finally, figure D.7 shows the menu associated with a link. The end-user can set a link attributes which are mainly measurements.

Figure D.4 : Graph menu

215

Figure D.5 : Form for controlling the simulation runs

Figure D.6 : Node menu

Figure D.7 : Link menu

AMS G U ’ I APPENDIX D

211

APPENDIX D

AMS G RAPHICAL U SER ’ S I NTERFACE

The aim of this appendix is to present, through a few samples of created screen dumps, the graphical user’s interface of the AMS. We remind that in chapter II, other screen dumps are reported, mainly for editing a satellite based communication network. More details can be found in [41] and [42].

Figure D.1 shows the initial window which appears when the AMS is asked to run. It also shows the task menu associated with an AMS model (for example

entry for a short document). At this level, the end-user can also employ the AMS

workbench as a file manager. He can change for example the current directory, copy or delete files, etc.

Figure D.1 : AMS workbench

Finally, there are two special icons which can be used to edit hierarchically a

communication network: stack icon and net icon.

icon. Inside the stack window, only the icons from which a stack can be built are available.

Figure D.2 : The iconic library of AMS

213

Figure D.3 : Net and stack submodels

Finally, figure D.7 shows the menu associated with a link. The end-user can set a link attributes which are mainly measurements.

Figure D.4 : Graph menu

215

Figure D.5 : Form for controlling the simulation runs

Figure D.6 : Node menu

Figure D.7 : Link menu

AMS G ^RAPHICAL U ^SER ’ ^S I ^NTERFACE