| Business DEX (UK_Defence041):— anomaly_reporting | Date: 2010/03/12 11:13:00 Revision: 1.10 |
The information requirements table for the product failure DEX is shown below:
|
Information requirement |
Business Object(s) |
|---|---|
| The information that defines the message that contains the anomaly and related information.. | Message, Record. |
| The information that defines the anomaly. | Anomaly, Status Assignment, Anomaly Effect, Faults, Failure Fault, Defect, Failure, Failure Relationship, Document, Document_association, Product |
| Other information that is closely related to the anomaly, such as the context within which it was found,
EXAMPLE the date, time and location. |
Anomaly Symptom, Symptom, Product Role, Observation |
| The information that identifies the product that the anomaly is identified against. | Anomaly, Product, Product Design, Product Specification, NATO Item of Supply Specification |
| The information that relates an event to an anomaly. | Anomaly, Anomaly Event Relationship, Event, Product Event, Product, Required PSE Constituent Usage Phase |
Table 1 — anomaly_reporting information requirements
In terms of business objects, these information requirements are modelled as shown below in Figure 1.
NOTE For clarity, not all of the dependent business objects - those that will make the model referentially complete - have been included on the diagram.
© UK MOD 2010 — All rights reserved