Transcript Group 1 Remote Computer Monitoring System Nick Conway Doug Lother

Group 1
Remote Computer Monitoring System
Nick Conway
Doug Lother
James Haggard
Wes Reinhart
High Level Designs
(Class Diagrams)
QuickTime™ and a
TIFF (LZW) decompressor
are needed to see this picture.
High Level Designs
(Class Diagrams)
QuickTime™ and a
TIFF (LZW) decompressor
are needed to see this picture.
High Level Designs
(Class Diagrams)
High Level Designs
(Design Issues)

Reusability


Maintainability


Future integration with client’s master app.
Single library provides a-la-carte monitoring.
Portability


Minor requirement
Linux only support.
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.
High Level Designs
(Design Issues)

Alternate Design Strategies



Why this architecture?



Could be done in one “C” program.
Could be broken down into smaller classes.
Functional modularity.
Optional monitoring choices
(I.e. CPU and MEM but not Network monitoring.)
Prototypes
High Level Designs
(Trace of Design)

Compute CPU utilization.



getCPUdata()
analyzeCPUdata()
writeCPUdata()
High Level Designs
(Trace of Design)

Compute memory utilization.



getMEMdata()
analyzeMEMdata()
writeMEMdata()
High Level Designs
(Trace of Design)

Compute network utilization.




getNetworkdata()
analyzeNetworkdata()
writeNetworkdata()
Anyone see a pattern?
Questions?
Thank you for your time.