SourceForge.net Logo

aas course report

BERSERK was the code deliverable for a Degree Course in IST. The course was about security applications and algorithms, and the lectures included SNORT and SATAN as well as IPSEC, WEP, GPRS, GSM, DES, DH, etc, etc...

As you can see it is a very horizontal course, a global overview about network security both past and state of the art.

The course included a programmatic project, and I proposed BERSERK.

motivation

BERSERK appeared while a code and structural refactoring was taking place in Gestor de Serviços.

Although it was born in the Fénix system, it could be of use to any kind of application, especially with needs for multiple criterion types. Achieving generalization was not straightforward, as there were many hard coded Fénix concepts.

The requester was a specific Fénix class and exception handling used Fénix exceptions. Although not being a fault in the original design, it was necessary to eliminate any code dependency to increase BERSERK stability.

Some potentialities of Gestor de Serviços were not being used, because they were not available to it’s interface. For example method granularity for services has been foreseen but not made available to applications.

The analysis of the old code brought unreported potentialities to the surface, and the idea of building a business logic and security framework was born.

Refactoring included limiting all explicit references to BERSERK classes to be done via BERSERK’s library. This way BERSERK could be a deliverable artefact for course evaluation and, at the same time, an open source solution for those who have multiple criterion types needs for their applications.

BERSERK was proposed to solve Gestor de Serviços’ problems, add some new features and prepare future extensions to be easy and appellative.  

what can you find in the document ?

The document was delivered for evaluation on December the 2nd, 2003 and it may be ocasionally updated. Hence, you may not expect it to reflect BERSERK's actual state.

The document contains more detailed information about BERSERK's internal architecture and about how it really works. It includes a sequence diagram for a tipical interaction, and class diagrams for the core components (Service Manager and Filter Broker Factory).

Nevertheless many of this website's information was extracted from this document, consulting one of them does not necessarilly implies not reading the other becauase they have complementary information.

download the document

The download link is here .

Nevertheless the age of the document, I thank you for sending me comments and sugestions about it, and I may even update it if it is worth it.

© 2003, Gonçalo Luiz