Documentation

Overview

Proposed System

The objective of our project is to develop the Interactive Module(IM) system for netDeFlect^TM. netDeFlect^TM is a solution developed by Esphion for defensing DDos(Denial of Service) attacks. Esphion's website has more details on netDeFlect^TM. Esphion's customers have expressed concerns about netDeFlect^TMmaking automatic changes to their router's configuration, therefore IM is required. It allows the systems administrator to view any suggested changes to the router's configuration and approve or reject these changes.

Project Scope

This project is run as a short-release-cycle project. I.e. instead of working within one release cycle, we are required to deliver multiple releases, each of them small in scope. This strategy reduces risk for us as well as for Esphion. Because of this strategy, the project cannot be specified in detail beyond the first release at this point. While we can document a se of requirements, which at this point we see as necessary, it has to be emphasized that the first release is very much an exploratory release to test customer acceptance and gather market feedback. Accordingly, subsequent releases may divert significantly from any project plan we are outlining now, beyond the first release.

System Platform

Development Machines:

We have been provided with three desktop PC’s for the purposes of designing and developing the system. The machine specifications are as follows:

	Processor	Operating System	Memory	Hard Disk	Software
Student PC	Various	RedHat Linux 7.1	Various	Various	Apache/Tomcat MySQL

Deployment Environment:

	Processor	Operating System	Memory	Hard Disk	Software
Server	Dual Pentium III 1GHz	RedHat Linux 7.1	1GB	30GB	Apache Tomcat Java 1.4VM MySQL

Contigencies

Throughout our project we have had to allow planning time for unforeseen circumstances. The contingencies that we have allowed for are as follows:

	Team Cohesion. There also runs the risk of our team not operating fluidly together and information not being shared and other co-operation anomalies that slows up our development process. To prevent this, we decided to have a weekly meeting to discuss our progress.
	Workload underestimation. As we are only at the start of our project it is very hard to correctly estimate the workload involved future activities. For this reason estimates at present are very conservative.
	Limited resources. We have to share the development machines with other team, hence time management is critical.
	Steep learning curve. Since we have no previous experience in C/C++ programming and JSP and our first release date is 7^th July 2002, we have to learn new stuff very fast.
	Unforeseen issues. Throughout the project many problems will arise for which we have not accounted for.

Documentation

project schedule presentation slides

project schedule documentation

project brief documentation

Monthly Report

Copyright or other proprietary statement goes here.
For problems or questions regarding this web contact [ProjectEmail].
Last updated: 04/18/02.