IG1220 Closed Loop Management UMLs and State Models v2.0.0

This introductory guide defines the data models supporting closedloop management. 

An effective data model completely and accurately represents the data requirements of the end users, and It is simple enough to be understood by the end user, yet detailed enough to be used by an Interface designer (API) and /or Database designer in building the information systems database. This information model eliminates redundant data, and is independent of any hardware and software constraints, thus can be adapted to changing requirements with a minimum of effort.

The approach adopted is both a top-down and a bottom-up approach, where the basic model, represented entities and relationships are developed based on the information model, and the details related to the represented entities, such as attributes and business rules added in phases. Through an iterative approach, requirements from the information model on the data model will enable establish and continually optimize the classification of data objects as either entities or attributes, identify and define relationships between entities, enable improve naming and definition of identified attributes and relationships and effectively ensure consistent documentation. 

The users for this data model include API developers, Database designers, Protocol engineers, and the gamut of software engineers and systems engineers.