Team42 - Course Presentation EEL5881, Fall, 2003 Project:...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Course Presentation EEL5881, Fall, 2003 Project: Network Reliability Tests Team Client: Dr. Joseph Berrios Team: Gladiator Shuxin Li Victor Velez Xin Bai High Level Design Interface Diagram Use Case Diagram High Level Design Design Issues ­ Reusability Some components may be designed to be reusable Need to be taken care of Maintainability Customer may want add new functions and new services type Detailed documentation. High Level Design Design Issues ­ Portability Need to be taken care of The software needs to be run on different Operating System : Windows or Linux. Security Not important Does not contain sensitive information Only one user : Network Administrator High Level Design Design Issues ­ Robustness Need to be taken care of The format of the servers list file Detailed Design Operation Sequence Diagram Data Dictionary No.1 ­ Servers List Statement: it holds all the servers need to be monitored, including address, port, service type Source: Customer Operations: Create an empty one, load from a saved file, save to a file, edit Conflicts: When monitoring, no operation can be perform on servers list except reading Supporting Materials: Customer requirements, High­level design, Test plan Revision History: 1.0 Data Dictionary No.2 –Plug­in Notification Statement: It is method used to notify user in case of error Source: Monitoring result Operations: Enable, disable, configure, notification Conflicts: When configuring the plug­in notifications, the monitoring should be stopped and others buttons are not accessible Supporting Materials: Customer requirements, High­level design, Test plan Revision History: 1.0 Data Format Service Configuration Log message Name, Type, Timeout, Port, Check interval, Notification. Type includes http, ftp, ssh, tcp, smtp, pop3, mssql, imap, tcp­connection. "service_type on address:port up/down at occuring_time“ Number of faults at each logging time Statistical chart For example: "ftp on yahoo:21 down at 1:30 afternoon". Detail Design Monitor GUI Design Detail Design Server History GUI Design Detail Design Displaying statistical chart Detail Design Configure Plug­in Parameters Trace of Requirements to Design Functional Requirements: For Fundamental actions Allows the validity checking when loading a servers IP address list, if the format is not correct, an error message will pop­up. Finished the implementation Check use case diagram above for exact sequence of operations. Finished the implementation Finished the implementation Use JAVA ICMP packages to get required results Trace of Requirements to Design Interface Requirements: Input data items: Server IP address list (including the Ip address, the server type, the server port) ===> Implemented, see the GUIs Output data items Statistical analysis in a period of time. Finish the implementation Will be implemented in the implementation phase. Error messages in the case of invalid data input Thank you! ...
View Full Document

This note was uploaded on 08/25/2011 for the course EEL 5881 taught by Professor Staff during the Spring '09 term at University of Florida.

Ask a homework question - tutors are online