Performance, structure and output requirements

As the project is a prototype, there weren't any strict performance requirements. Still since the presented project was going to turn into a tool for the engineers, a decent speed and light resource consumption were expected. The resource consumption requirement was more dominant.

The structure requirements were even more deliberate. We were expected to build a function-module oriented mechanism, easy for understanding. Since the project was being written in an interpreted script-like language - PERL, we were expected to allow the engineers working with the project to insert minor inner changes into program if needed.

We must remember, that LAN is a very unique thing to any campus, and SNMP requests may vary on types of equipments. Therefore we had to produce separate database and queries configuration files for an easy representation of LAN structure as a collection of neccessary arguments and flags, specific to these types of equipment and software. For those needs also an installation utility was supplied.

Of course, very important was the tracking of real-time errors and troubleshooting, therefore log files for any data collections were implemented, where all actions are being written and the error messages are indented properly.

Again, as a prototype, the output requirements were simplified. Still, we tried to output our data in an easily understandable way. For any type of interface we tried to create a fine looking table containing all the requested data.


romm@empire.tau.ac.il
Last modified: Thu Jun 5 04:25:39 1997