DOC PREVIEW
UT Dallas CS 6359 - Project_Part_3

This preview shows page 1 out of 2 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Primary Activities:Project Part Three: Design Model.CS 6359.001 – Fall-2014 - Team Project – Part 3Due Date: 11:55PM November 18.Project Overview:You will be designing part of a Network Management System (NMS). The NMS manages many Element Management Systems (EMS), which in turn manage network elements (like routers, switches, etc.) in different networks. See diagram below:Figure 1. Basic NMS-EMS ArchitectureThe NMS can be used for many aspects of network management: Discovery, Configuration, Fault Reporting, etc. We will concentrate a few scenarios specific to Fault Reporting (Alarm Management). Theuser of the system accesses the NMS through a terminal; it is assumed that this person is a network engineer who is familiar with the system.Primary Activities:The main activities we will be designing the system for are as follows: 1. The user should be able to add a new EMS to the NMS, meaning that the system will connect to the EMS and register to receive alarms. The user does this by entering an API address for the EMS. Once registered, the NMS will receive alarms generated by the EMS whenever a fault occurs. The alarms are formatted as XML files, and it is assumed that all EMS use the same format for the alarms. 2. The NMS will receive alarms from the EMS and present them to the user on the terminal. Alarmsthat have been identified as critical will be given top priority.3. Alarms will be stored in a database – the database is not part of our system, but our system will interface to it. Once the XML file containing the alarm has been processed, a record of the alarm (including the important information) is stored in a database.4. Each XML file will contain only one alarm for now. 5. The system should allow the user to generate a report of all alarm activity over a given time period. The report will be a PDF file.Project Part Three: Design Model.For the third part of the project, you will create a Design Model that realizes two use cases for the above system. You should have written fully dressed use cases for activities 1 and 2 above; using the SSDs and Domain Model you created in Part 2, create interaction diagrams (either sequence or communication) for each use case. Then use the interaction diagrams to create a static DCD for the system. You can createthe dynamic (interaction) and static (DCD) diagrams in any tool you wish, but you should submit your final work in PDF format so the TA can read it. Since manually drawing UML diagrams can be daunting, the use of a UML Diagramming tool such as StarUML is highly recommended. You are not limited to


View Full Document

UT Dallas CS 6359 - Project_Part_3

Documents in this Course
Lecture2

Lecture2

63 pages

Lecture3

Lecture3

49 pages

Lecture4

Lecture4

48 pages

Lecture5

Lecture5

47 pages

Lecture6

Lecture6

45 pages

Lecture7

Lecture7

63 pages

Lecture8

Lecture8

77 pages

Lecture9

Lecture9

48 pages

Lecture10

Lecture10

84 pages

Lecture11

Lecture11

45 pages

Lecture12

Lecture12

134 pages

Lecture13

Lecture13

62 pages

Lecture14

Lecture14

76 pages

Project

Project

2 pages

Chapter_1

Chapter_1

25 pages

Load more
Download Project_Part_3
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Project_Part_3 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Project_Part_3 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?