1. Group 1 Remote Computer Monitoring System
Nick Conway
Doug Lother
James Haggard
Wes Reinhart

2. High Level Designs (Class Diagrams)

3. High Level Designs (Class Diagrams)

4. High Level Designs (Class Diagrams)

5. High Level Designs (Design Issues)
Reusability
Future integration with client’s master app.
Maintainability
Single library provides a-la-carte monitoring.
Portability
Minor requirement
Linux only support.

6. High Level Designs (Design Issues)
Performance & Technical difficulties
Bounded by kernel.
Generate most technical difficulties.
Safety
Minor-issue
Doesn’t write to critical system files.
Doesn’t make life threatening decisions.

7. High Level Designs (Design Issues)
Alternate Design Strategies
Could be done in one “C” program.
Could be broken down into smaller classes.
Why this architecture?
Functional modularity.
Optional monitoring choices (I.e. CPU and MEM but not Network monitoring.)
Prototypes

8. High Level Designs (Trace of Design)
Compute CPU utilization.
getCPUdata()
analyzeCPUdata()
writeCPUdata()

9. High Level Designs (Trace of Design)
Compute memory utilization.
getMEMdata()
analyzeMEMdata()
writeMEMdata()

10. High Level Designs (Trace of Design)
Compute network utilization.
getNetworkdata()
analyzeNetworkdata()
writeNetworkdata()
Anyone see a pattern?

11. Questions?
Thank you for your time.