Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. User must find out about internal state of MpsHist.
    • Author: snorum
    • Reason: Prevent failure.
  1. User must swich from one MpsHist to another.
    • Author: snorum
    • Reason: Prevent loss of messages.
Functional Specification
  1. MpsHS must capture all messages.
    • Origin: Use Case #1
    • How to test: All accepted messages must be in the database.

...

  1. MpsHs must send notification messages to LP
    • Origin: Use Case #3
    • How to test: Get messages from LP.
  1. MpsHs must run several copies of itself.
    • Origin: Use Case #
    • How to test: Have 2 of them running.
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.

...