Development
Overview
Background
The MPS History (MpsHist) is a software system for storing MPS History Messages in an RDB.
Thesaurus
- LP: link processor
Requirements
Use Cases
- User must figure out what's going on with MPS (performance statistics).
- Author: snorum
- Reason: Our mission.
- User must search and do analysis on messages.
- Author: snorum
- Reason: For diagnostics.
- User must be able to register with LP over UDP at 0.2 Hz.
- Author: snorum
- Reason: Zero configuration, dynamic change.
- User must be notified when MpsHist fails.
- Author: snorum
- Reason: Mission-critical.
- User must find out about internal state of MpsHist.
- Author: snorum
- Reason: Prevent failure.
Functional Specification
- MpsHS must capture all messages.
- Origin: Use Case #1
- How to test: All accepted messages must be in the database.
- MpsHS must write all messages to RDB.
- Origin: Use Case #2
- How to test: All accepted messages must be in the database.
- MpsHs must send notification messages to LP
- Origin: Use Case #3
- How to test: Get messages from LP.
Constraints
- Messages are streamed at up to 1MB/sec.
- MpsHS must support Oracle RDB.
- LP is a time-critical VME IOC (2.8 msecs).
- LP might not be busy for a while, so no timeouts must be introduced.
- Connect only to 1 MpsHist at a time.
Design
Comments
- Open to possibility of sending messages directly from LP to RDB.
User's Guide
Programmer's Guide
References
Administration
Task lists and schedules, spreadsheets etc.