Dynamics
Requirements table $Revision: 1.4 $ State approved
Date 02-Nov-1998 Author Tom Weckström
Review date 04-Nov-1998 Reviewed by Jouni Malinen
Approval date 04-Nov-1998 Approved by Jouni Malinen
$Id: reqtable.html,v 1.4 1998/11/04 18:50:11 jkmaline Exp $
 
The following table presents the requirements of the Dynamic IP-tunnel project.
The requirements stated by the project team are also listed.

Requirement types:
F    Functional
P    Product
C    Process
E    External
O    Other
T    Team requirement
 
Type
Requirement
Priority
F Tunneling shall be hierarchical. 1
F The system shall update only those elements that need to be updated.  1
F The length of the tunnel shall not be explicitly restricted by the system architecture. 1
F The tunnel configuration information updates shall be dynamic.  1
F Further development and inter operability shall be supported. 1
E The IP-protocol version shall be 4. 1
E The mobility of the mobile node shall be transparent to an external observer. 1
T The end product shall be good enough for further development. 1
T The scheduling shall be proactive. 1
T Important documents and the code shall be reviewed. 1
T CVS version control shall be used. All the deliverables shall be versioned. 1
F The functionality should be transparent to the mobile user. 2
F The lowest foreign agents should use broadcasting to advertise availability. 2
F The mobile node shall select the lowest foreign agent. 2
F The home elements shall handle several concurrent users. 2
P The product maturity level shall be a working prototype. 2
P The software shall have an installation mechanism. 2
E The platform should be Linux.  2
O Tunneling should be possible with minimum firewall openings. 2
F Mobility management information updates shall be secure.  3
F The system should support logging.  3
F Resource allocation should be optimized.  3
P The mobility management security design should be modular.  3
P Each piece of the software should be configurable. 3
P There should be monitoring tools for the software.  3
P There should be a programming API for the software. 3
O The software should not be a clear bottleneck. 3
T Communication with the customer shall be continuous. 3
O The portability should be taken into account. 4
T The code shall be written according to Linux kernel programming guidelines. 4
F There may be multiple modes for tunneling. 5