Use Case Section CommentUse Case Name Connecting a EMS to NMSScope Network Management SystemLevel Subfunction (and not user-goal)Primary Actor UserStakeholders and InterestsNetwork Engineer: Interested in monitoring the new network elements that will be added to the network.Company whose network will be managed by the NMS: Interested in knowing the frequency of faults in the network.DBA : Database interface is working properly for the client.Preconditions - User is authorized.- NMS has fully functional and has the ability to receive andforward alarms.- EMS alarm format is XML.- Structure of the XML is already present in NMS.Success Guarantee EMS is successfully added to the NMS.Main Success Scenario1. User logs in.2. User enters the API address of the EMS that needs to be connected to the NMS.3. Once connected, User is given a confirmation message of the successful addition.4. The EMS id is entered in to the NMS's database5. EMS inherits the XML structure from the NMS. 6. The EMS is configured and successfully connected to NMS.Extensions Alternate scenarios of success or failure.2a. Error connecting to NMS.3a. EMS with the API address already exists. 1.System signals error and asks user to enter again. 3b. Invalid API address.5a. XML file corrupted. 1. EMS again tries to pull out the XML format from NMS. 1a. Try pulling it out from NMS at a later point of time.Special RequirementsNoneTechnology and Data Variations ListNoneFrequency of OccurrenceOnce in a while as new network elements are addedOpen Issues 1. Does user get to customize the structure of XML?Use Case Section CommentUse Case Name Storing Alarms in DatabaseScope Network Management SystemLevel Subfunction (and not user-goal)Primary Actor Event : Alarm is already processedStakeholders and InterestsNetwork Engineer : Interested in generating reports of the alarms at a later point of time.Company whose network will be managed by the NMS : Interested in knowing the frequency of faults in the network.DBA : Database interface is working properly for the client.Database System :Preconditions Alarm has been processed.Success Guarantee Database will contain the record of the AlarmMain Success Scenario7. After an alarm is processed, it will be sent to a queue, to get stored in the database.8. Alarm present at the front of the queue (i.e. the alarm which had been processed first among the ones in the queue) will be picked and important information will be captured.9. The information obtained will be then stored in the database.Extensions Alternate scenarios of success or failure.3a.DB connection failureSystem will retry to connect to the database.Special Requirements1. The database operation of saving the data must not take more than 2 seconds 95% of the time.Technology and Data Variations ListFrequency of OccurrenceAlmost continuous.Open Issues 2. If the database is down for a long time, do we need to save a local copy of the information till then so that once the database is up and running, the information can be
View Full Document
Unlocking...