Analysis

In the analysis phase, the requirements are used to identify the interacting entities, their properties and the relationships among them. This allows the interfaces offered by the entities to be defined. In the UML notation, these entities become classes. The class descriptions along with the interfaces exposed should be traceable to the requirements. This phase should take into account the needs of human-computer interface data (i.e., the information model must contain sufficient information so that designs can be developed based on the analysis results). This Recommendation gives high-level guidance on the use of UML notation to support management interface specification. The analysis phase should be independent of design constraints. 1. The analysis may be documented using OO principles. 2. The design may use a non object-oriented technology. The information specified in the analysis phase includes: a. Class descriptions. b. Data definitions. c. Class relationships. d. Interaction diagrams (sequence diagrams and/or collaboration diagrams). e. State transition diagrams. f. Activity diagrams. The class definitions include: a. Specification of operations. b. Notifications. c. Attributes and behavior.

Analysis example
The following example is based on alarm management, but is used for illustrative purposes only and not intended to be a complete or correct set of requirements for alarm management. 1. Concepts and background: Any evaluation of the NEs' and the overall network health status requires the detection of faults in the network and, consequently, the notification of alarms to the operating Systems. 2. I nformation object classes 2.1. I nformation entities imported and local label

2.2. Class Diagram. This clause introduces the set of information object classes (IOCs) that encapsulate information within the agent. The intent is to identify the information required for the Alarm Agent implementation of its operations and notification emission. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes.