Documente Academic
Documente Profesional
Documente Cultură
good thing when an existing solution is adequate but memory, repeaters, modems, Host Bus
we claim that existing situation with practice of Adapters, multiplexers, CSU/CDU,
network diagramming is not satisfactory. So we transceivers, access points, printers,
decided to empirically collect requirements for a set scanners, cameras, satellites, antennae,
of logical symbols, a simple language for drawing ports, connectors, adapters/interfaces,
networks and to separate design of such a language taps, concentrators, sensors, amplifiers,
from possibly even harder practical problem of etc. bridges, routers, switches,
selling it. gateways, encryption devices, IDS,
firewalls, storage arrays, and
Desirable features of the intended visual language for multifunctional devices or enclosures
network diagramming, elicited from a number of for honey-pots, etc. many of which are
consulted faculty lead to the following initial list of prominent at multiple layers.
requirements:
- Symbols should be logical i.e. abstract, not The key issue to start with is which symbols to use,
overly representational, more like road signs and an answer to this question is to be based on
(for example not a picture of a brick wall in explicit set of criteria and an academic assessment of
case of a firewall) established practices, with an expectations that most
- Preferably common and non proprietary symbols can be reused as is or abstracted into
symbols well established internationally, for minimal and consistent set. As network is formally a
example a communication link and a disk graph whose arcs are communication lines (various
based storage. kinds of channels including implied as in case of a
- Appropriate for visualizing functional and broadcast) and whose nodes are functional devices
structural information for multilevel transforming content and/or regulating
networks (subnets), communication traffic, various symbols are needed
- Sharp and clear 2D (minimal number of for nodes and links.
lines, painted and exposed surfaces and no
shading) To rigorously define a formal language is a task
- Memorable that is easy to recognize, clearly to be done; we postponed formalization for
- Crisp in black and white copies, and some later time as our selection will be initially based
- Easy to draw by hand and by a common on common usage to agree with intuition of general
tools like Visio (stencil). users. Furthermore, we intent to explore possibility of
involving IEEE or similar standardization bodies in
Specifically symbols should address logical considering consensus based framework for official
network diagrams at all layers and in various standard development and adoption once a solid
domains such as: requirements become acceptable for a wider
o Traditional (analog) networks community of stakeholders (that is beyond our
o Data networks primary focus on academics and students).
o LAN/CAN/MAN/WAN
o Internet/Intranet Collecting of requirements outlined above was
o Wireless networks, incl. Satellite ones performed during two semesters in consultation with
o Optical networks a number of instructors involved in teaching
o Storage networks, SAN, NAS, CAS networking related coursework in the IS, CS and IT
arrays etc. departments and a number of very enthusiastic
o Distributed Computing networks students. A professional conference like IACIS may
o Supercomputing architecture, be a good venue to vet those requirements and
o Security Assessment (with additional evaluate an initial prototype as well as provide
overlays showing DMZ, support and momentum for eventual improvement
infestation/recovery paths, possibly and most of all early adoption.
honey pots etc. etc.).
Decision to focus our attention exclusively on logical
Components expected should be the one representation opened up a need to consider
frequently used in modern networks, for example annotations for the symbols thus providing for media
a minimal selection from a larger list such as: and performance information to be added to a
o Links- cables etc., buses, hubs, phones, diagram (still avoiding brand names etc. as
servers (computers), external memory appropriate). We think of the selection of rules for
(disk), internal memory and cache combining and connecting symbols and/or adding
annotations to symbols as a form of syntax rules or a demonstrated. Icons used in SANDS prototype are
grammar of a symbolic language whose terminal shown in Figure 2.
components are symbols – this is also the next big
question that need an answer if we are to define a <insert Figures 2 and 3 here>
reasonably general, complete and consistent standard
for logical diagramming of networks as systems. The images are clearly more visible and retain that
property even when minimized as in the print
screen example in Figure 3.
INITIAL RECOMMENDATIONS
Figure 2. An example of SANDS use by students during preliminary validation of the prototype version 0.1