CSCI 211:
OBJECT-ORIENTED ANALYSIS AND DESIGN
by
Chandrasekhar Maddipatla
Contents: page
number
1.Background 03
2.Requirements Specification 06
3.Use Case 10
4.CRC Cards 13
5.Class Model 16
Network Management System
1. Background:
1.1 Definition:
Network Management Tool is a service that helps human network managers to monitor and maintain networks by employing various tools, applications, and devices. This project is based on the five major areas in the ISO Network Management Model. The following are the five areas:
1. Performance Management
2. Configuration Management
3. Accounting Management
4. Fault Management
5. Security Management
1.1.1 Performance Management:
The primary goal of Performance Management is to make sure that the performance of the network is maintained at an acceptable level by measuring and making various aspects of performance available. The three steps involved in Performance Management are:
· gather performance data on variables of interest
· analyze the data collected to determine baseline levels
· appropriate performance thresholds are determined for each important variable so that exceeding these thresholds indicates a network problem worthy of attention.
An alert is issued to the network management system when the performance threshold is exceeded. Proactive methods such as network simulation can be used to project the effects on performance metrics by the growth of the network.
1.1.2
Configuration Management:
There will always be a chance of different versions of hardware and software elements on the network. All of them need to be tracked and monitored for better performance of the network. Configuration Management accomplishes this. The configuration Management system tracks and manages the network by basically monitoring network and system configuration information and the effects on network operation of various versions of hardware and software components. Configuration Management subsystems store the version information in a database for access. This database is searched for clues when a problem arises in the network. These clues, if appropriate can be used to solve the problem.
1.1.3 Accounting Management:
Individual or group uses on the network need to be regulated. Measuring the network-utilization parameters can do this. This is the task of Accounting Management of the ISO Network Management Model. This regulation minimizes the network problems and the access to the network is fair to all the users. The following are the steps involved in Accounting Management:
· measuring the utilization of all important network resources
· analyze the results to get insight into current usage patterns, and set usage quotas at this point
· correction is needed to reach optimal access practices
· ongoing measurement of resource use yields billing information, as well as information used to access continued fair and optimal resource utilization
1.1.4 Fault Management:
The primary goals of
Fault Management is to detect, log, notify users of, and automatically fix
network problems to keep the network running. Faults in the network cause
downtime, unacceptable network degradation. For this reason Fault Management in
the ISO Network Management Model is the most widely implemented element. It
involves:
·
determining
symptoms first and isolating the problem
·
fixing the
problem and then the solution is tested on all-important subsystems
·
detection and
resolution of the problem is recorded
1.1.5 Security Management:
The primary goal of Security Management is to protect the network from illegal access so that sensitive information on the network is safe. Security Management subsystems
·
monitor users
logging on to network resources, and refusing access to those who enter
inappropriate access codes.
·
partition
network resources into authorized and unauthorized areas. For users who are
company outsiders access to any network resource is inappropriate. For
internals access to information originating from a particular department is
inappropriate.
·
try to identify
sensitive network resources and determine mappings between sensitive network
resources and user sets.
·
monitor access
points to sensitive resources and keep track of inappropriate access to
sensitive network resources.
The main aim of this project is to design a network management tool, which keeps track of the status of the various systems in the network, provide automatic solutions to any problems that arise, keep track of the traffic in the network, authorization of valid users and maintain record of resources. This project is developed with Object-Oriented Analysis and Design technique using UML.
2. Requirements
Specification:
2.1 Overview Statement:
The purpose of this project is to create a reliable Network Management System with least possibility of breakdowns and strong security features. This tool has many options, which can be used by the human administrator for better overall management of the network. This tool will be designed to deal with vast array of technologies, applications, and equipment used to manage networks of today and the networks of the future.
2.2 Customers:
The possible customers for this system may range from a small work group to organizations with a large network.
2.3 Goals:
The goals of the this project are as follows:
1. To provide automatic network management with minimal human interference.
2. To keep the performance of the network at very high levels.
3. To control the network traffic.
4. Network Security.
5.Network resource management.
6.Detection and correction of network malfunctions (both hardware and software)
7.Develop and Implement the system using Object-Oriented Analysis and design Technique.
2.4 System functions:
The following are the five main functions of this Network Management System:
1. Performance Management
2. Configuration Management
3. Accounting Management
4. Fault Management
5. Security Management
2.4.1 Performance Management
Functions:
|
Ref# |
Function |
Category |
|
R 1.1 |
Calculation of bytes/packets transferred |
Hidden/Evident |
|
R 1.2 |
Calculation of performance threshold |
Hidden/Evident |
|
R 1.3 |
Calculation of response time |
Hidden/Evident |
|
R 1.4 |
Calculation of delay |
Hidden/Evident |
Note: Evident for the network administrator and Hidden for the network user.
2.4.2 Configuration Management
Functions:
|
Ref# |
Function |
Category |
|
R 2.1 |
Keeping track of software version and name |
Hidden/Evident |
|
R 2.2 |
Keeping track of hardware version and name |
Hidden/Evident |
Note: Evident for the network administrator and Hidden for the network user.
2.4.3 Account Management Functions:
|
Ref# |
Function |
Category |
|
R 3.1 |
Computation of resource usage time |
Hidden/Evident |
|
R 3.2 |
Keeping track of the user of a particular resource |
Hidden/Evident |
Note: Evident for the network administrator and Hidden for the network user.
2.4.4 Fault Management Functions:
|
Ref# |
Function |
Category |
|
R 4.1 |
Servicing of software error |
Hidden/Evident |
|
R 4.2 |
Servicing of hardware error |
Hidden/Evident |
Note: Evident for the network administrator and Hidden for the network user.
2.4.5 Security Management Functions:
|
Ref# |
Function |
Category |
|
R 5.1 |
Authorization of user onto the network |
Hidden/Evident |
|
R 5.2 |
Authorization of Network Administrator |
Hidden |
|
R 5.3 |
Authorization of users to special areas of network |
Hidden/Evident |
Note: 1. R 5.1 & R 5.3: Evident for the network administrator and Hidden for the network user.
2. R 5.2: Hidden for both user and network administrator.
2.5 System Attributes:
The following are the five types of attributes of this Network Management System:
1.
Performance Management Attributes
2.
Configuration
Management Attributes
3. Accounting Management Attributes
4. Fault Management Attributes
5. Security Management Attributes
2.5.1 Performance Management Attributes:
|
Attribute |
Details |
|
bytes/packets transferred |
Number of bytes/packets transferred across the network in a given period of time or at a point of time |
|
Delay |
Time delay in transfer of information between two nodes of the network |
|
response time |
Time between sending and reception of a request between two nodes of the network |
|
performance threshold |
Limit set on network performance over which the network becomes unstable |
2.5.2 Configuration Management Attributes:
|
Attribute |
Details |
|
software version number |
Version number of different software elements in the network |
|
hardware version number |
Version number of different
hardware elements in the network |
|
software name |
Names of different software
elements in the network |
|
hardware name |
Names of different software
elements in the network |
2.5.3 Accounting Management
Attributes:
|
Attribute |
Details |
|
resource name |
Type of resource being used by a user |
|
resource usage time |
Usage time of the particular resource by a user |
|
User |
User who is using the resource |
2.5.4 Fault Management Attributes:
|
Attribute |
Details |
|
hardware error |
To isolate the hardware error and the type of hardware error |
|
software error |
To isolate the software error and the type of software error |
2.5.5 Security Management Attributes:
|
Attribute |
Details |
|
User login name |
Login name of the user used to log on to the network |
|
Admin login name |
Login name of the administrator used to logon to network |
|
User password |
Password o the user |
|
Admin password |
Password of the administrator |
|
Special access permission |
Attribute to check whether or not a user is authorized to access special resources of the network |

3.2 Login/Authorization:
Use case: Login/Authorization
Actors: User, Administrator
Type: Primary and essential
Description:
A user logs on to the network by supplying his login name and password. The network administrator also logs on to the system by supplying a login name and password. If login is successful the user or the administrator works on the network. Access of special resource on the network is given only to a few privileged users.
3.3 Resource Management:
Use case: Resource Management
Actors: User, Administrator
Type: Primary
Description:
A user uses a network resource. The usage time is calculated and if the user is blocking other users from using the network resources, he is alerted and the administrator takes necessary action so that other users are not deprived of the network resources.
3.4 Performance Management:
Use case: Performance Management
Actors: Administrator
Type: Primary
Description:
Performance metrics of the network such as throughput are calculated using many attributes of the network. If the performance threshold exceeds a set limit, the network becomes unstable. The Administrator takes necessary steps to bring back the threshold to normal level.
3.5 Configuration Management:
Use case: Configuration Management
Actors: Administrator
Type: secondary
Description:
When new software or a hardware component is added to the network, it’s name and version number need to be stored to distinguish it from its predecessors. These details are used to isolate any problem that arises in the network.
3.6 Fault Management:
Use case: Fault Management
Actors: Administrator
Type: Primary
Description:
When the network is malfunctions, the administrator corrects the identified software or hardware error. After this the network works as it used to before the occurrence of the malfunction.
3.7 Database Control:
Use case: Database Control
Actors: Database
Type: Primary
Description:
The database returns the requested data to the appropriate class. The database has all the data needed for a network to run smoothly. Database stores login names and corresponding passwords of users and administrators. It also stores configuration details, fault management details, account management details and performance management details.
4.Class Responsibility and
Collaboration Cards:
4.1 “performMgmt” class:
|
performMgmt |
|
|
Responsibilities |
Collaborators |
|
Calculation of bytes/packets transferred |
databaseControl |
|
Calculation of performance threshold |
accountMgmt |
|
Calculation of response time |
|
|
Calculation of delay |
|
4.2 “faultMgmt” class:
|
faultMgmt |
|
|
Responsibilities |
Collaborators |
|
Servicing of software error |
configMgmt |
|
Servicing of hardware error |
accountMgmt |
|
|
databaseControl |
4.3 “databaseControl” class:
|
databaseControl |
|
|
Responsibilities |
Collaborators |
|
Service various requests from other classes by returning the requested data |
configMgmt |
|
|
performMgmt |
|
|
securityMgmt |
|
|
faultMgmt |
|
|
accountMgmt |
4.4 “accountMgmt” class:
|
accountMgmt |
|
|
Responsibilities |
Collaborators |
|
Computation of resource usage time |
databaseControl |
|
Keeping track of a user of a particular resource |
performMgmt |
|
|
faultMgmt |
|
|
securityMgmt |
4.5 “securityMgmt” class:
|
securityMgmt |
|
|
Responsibilities |
Collaborators |
|
Authorization of user onto the network |
databaseControl |
|
Authorization of Network Administrator |
accountMgmt |
|
Authorization of users to special areas of network |
|
4.6 “configMgmt” class:
|
configMgmt |
|
|
Responsibilities |
Collaborators |
|
Keeping track of software version and name |
databaseMgmt |
|
Keeping track of hardware version and name |
faultMgmt |
