A PROJECT REPORT

ON
NETWORK MONITORING & CONTROL SYSTEM
BACHELOR’S OF SCIENCE

IN

INFORMATION TECHNOLOG

SUBMITTED

BY

KARAN LAWAND

S.K COLLEGE OF SCIENCE AND COMMERCE ,

PLOT NO.31, Sector-25, Seawoods Navi Mumbai-400706,

2018-2019

1
 A PROJECT REPORT
ON
NETWORK MONITORING & CONTROL SYSTEM
BACHELOR’S OF SCIENCE

IN

INFORMATION TECHNOLOGY

SUBMITTED

BY

KARAN LAWAND

Seat No -2016010082

PROJECT GUIDE

Mrs.shwetakhubchandani

S.K COLLEGE OF SCIENCE AND COMMERCE ,

PLOT NO.31, Sector-25, Seawoods Navi Mumbai-400706,

2018-2019

2
 Abstract

The Aim of this project is to develop software that monitors,control and analyzes
the status and behavior of the systems that make up and automates much of the
regular tasks of the system administer who is responsible for managing the entire
network

3
 ACKNOWLEDGEMENT
I take this opportunity to express my profound gratitude and indebtedness to
our project guide Mrs. Shweta khubchandani for giving me this opportunity to
accomplish this project.
I am very much thankful to our Principal Dr. Ajit Kurup and our vice-
principal Dr. Srividya Murali for their kind co-operation in the completion of my
project.
I am also grateful to Mrs. Harman Preet Kaur, Head of Department for
being very much resourceful, kind and helpful. Their positive attitude, unassailable
optimism and unwavering faith in me assured that I come out of the words
whenever I encountered difficult.
Finally, I wish to thank our lab assistant and all my friends and the entire
Computer department who directly or indirectly helped me in the computer of this
project. Last but not the least I would thank my family without those support,
motivation and encouragement this would not have been possible.

4
 DECLARATION
I the undersigned Master Karan Sudhakar Lawand hereby, declare that the
work embodied in this project work titled Network Monitoring & Control System
forms my own contribution to the research work carried out under the guidance of
Ms.Shweta khubchandani is a result of my own research work and has not been
previously submitted to any other University for any other Degree/ Diploma to this
or any other University.
Wherever reference has been made to previous works of others, it has been
clearly indicated as such and included in the bibliography.
I will abide and take all responsibility of all issues related to plagiarism/self-
plagiarism mentioned under UNIVERSITY GRANTS COMMISSION
(PROMOTION OF ACADEMIC INTEGRITY AND PREVENTION OF
PLAGIARISM IN HIGHER EDUCATIONAL INSTITUTIONS) REGULATIONS,
2018.
I, here by further declare that all information of this document has been
obtained and presented in accordance with academic rules and ethical conduct.

Certified by Submitted by

(Ms Shweta Khubchandani) Mr Karan Sudhakar Lawand

5
Plagirism Reports

6
7
8
9
 INDEX

Sr. No. Title Page No.

1 Introduction 7
1.1 background 8
1.2 scope 9
1.3 object 10
1.4 Appalicability 11
2 Survey of technology 12
14
2.1 proposed system
15
2.2 requirement Hardware
15
2.3 Software requirement
2.4 justification 16
3 System Analysis & Design 18
3.1 Module 19
3.2 User interface 22
3.2transition diagram 29
3.3DFD diagram 33
3.4 Activity diagram 35
3.5 Gant chart 38

5 Implementation and design 39

5.1 implementation Approaches 40
5.2 coding Efficiency 41
5.3 TestingApproaches 45
5.3.1-unit Testing 50
5.4 Beta Testing 51
5.5 Modification and improvement 52
5.6 Testing Cases 53
6 Result and Discussion 55
7 Testing Report 63

10
 References 67
8

11
 1.INTRODUCTION

Networks are of growing importance and indeed have become

critical in the business world. As networks grow in size more and
more things can go wrong, disabling the network or a portion of
the network or degrading its performance to an unacceptable level.
As network installations become larger, more complex and more
heterogeneous, the importance of Network monitoringincreases.
Increase in the number and categories of clients and their
specific needs leads to a scope for a lot of exploits of the network
resource. In a scenario with limited network resource it is
becoming very important to monitor the activity of each client.
With the increased usage of client server based network, the
administrator needs to ensure efficient management of resources.
Especially in case of Educational institutes where bandwidth is
limited and users are numerous, it becomes imperative for
administrators to ensure proper utilization of availablebandwidth.
Network Monitoring & Controlling Software provides a tool
that helps the administrator in monitoring a network by keeping
track of user activities, bandwidth usage, sending warning
messages to client, locking input devices like keyboard, mouse at
client side, analyzing network traffic etc. The software automates
much of the regular tasks of the system administrator who is
responsible for monitoring the entire network thus reducing the
cost of network management.

12
 1.1BACKGROUND

One of the most widely used approaches to network monitoring

and management is the Simple Network Management Protocol (SNMP).
This convention was initially figured in 1988 through RFC 1067Since
then it has undergone many changes and is currently in version three of
the protocol (as defined by RFC 1157). SNMP has two distinct parts, a
format for describing data about computers and a protocol for
transmitting that data over network.
The format of SNMP data takes the form of a tree structure, with
each node in the tree being identified by a numerical Object IDentifier
(OID). For example, .1.3.6.1.2.1.1.1.0 contains a string that describes the
system being queried. The idea of OIDs significantly predates the
introduction of SNMP, and was standardized by the ISO. The OIDs used
by SNMP are a subset of this ISO standard, which means that all SNMP
OIDs are prefixed by .1.3.6.1.2.Like Internet Protocol addresses, these
OIDs are difficult to remember. For this reason, a method of assigning
more human-readable names to these OIDs has been defined.
This method uses a Management Information Base (MIB) to
convert the numeric OIDs into strings, much like DNS domain names.
Using this system, the example OID given above would become
.iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0. To a large extent,
the information in these MIBs is standardized — but not always in a
useful way. The MIB used by SNMP is known as MIB-II and is defined
in RFC 1213.
The SNMP network protocol itself is fairly simple; it provides
several operations to allow a monitoring station to read and write data to
a remote host. Operations to read data include get- request (to retrieve a
specific OID), get-next-request(to retrieve the next OID in sequence),
and get-bulk-request (to retrieve a block of related OIDs). Data can be
written using a set-request. In addition, SNMP defines a way for the
remote host to notify a monitoring station of an extraordinary event that
has occurred (OSI fault management). These events are sent as a trap,
and are a one-way communication between the two hosts.

13
 1.2OBJECTIVE

Objective

The main objectives of the project are:

 Monitoring the clientactivities.

 Capturing IP address of logged one users.

 Alerting.

 Snapshot Pictures Built-in Slide Show forScreen.

 Locking Inputdevices.

 Turning-off the clientmachine.

 Sending files to the desired clientmachine.

14
 1.3 Scope of the Project

The domains of the software are the firms or organizations that

are using computer networks as a source of information exchange and
communication preferably the networks in educational institutes and
other similar networks. In such organizations the performance of the
computer networks that they use plays a crucial role in their efficient
functionality. Such organizations extend from a small one having 15-20
computers to a large one employing large number of computers
including various peripheral devices.

To use a architectural decision that will make the application be as

much as possible: modular, well-managed, fair, simple, easy to
understand, user-friendly.

15
 1.3 Applicability
This paper implementation that which is the outcome, would be used at the
frontdesk, other serves terminals and for administrative, and is also applicable to
lower and higher premiums facilities. Further development of this project is opened
to more research for scalable entities.

16
2. Survey of technology

We used Java as the programming language for implementing our

monitoring system.
The following features of Java prompted us in choosing it as the programming
language:

Object Oriented:
Object-oriented programming (OOP) is a powerful way of organizing and
developing software. The short-form description of OOP is that it organizes a
program as a set of components called objects. objects exist independently of
each other, and they have rules for communicating with other object and for
telling those objects to do things. The Java language includes
setofclasslibrariesthatprovidebasicvariabletypes,systeminputandoutput
capabilities, and other functions. It also includes classes to support
networking, Internet protocols, and graphical user interface functions.

17
 Platform Independence

Stage freedom is the ability of a similar program to take a shot at

various working frameworks; Java is totally stage autonomous. A Java
class document of bytecode guidelines can execute on any stage without
adjustment.Java follows the principle of ―Write once; run anywhere,
any time, forever”.

Java is intended for the circulated condition of the Internet,

since it handles TCP/IP conventions. The feature of inter-address-
space messaging is done with the help of the
package―RemoteMethodInvocation‖.Thisfeaturebringsanunparallel
edlevelofabstractionto the client/server programming. Java
programs convey with them considerable measures of run-time
type data that is utilized to check and resolve gets to objects at run-
time. This makes it conceivable to progressively connect code in a
safe and expedient manner.

Security:
Java provides security on several different levels. Initially, the
language was intended to make it incredibly hard to execute harming
code. By killing all pointers with the exception of a restricted type of
references to objects, Java is a significantly more secure language.
Another dimension of security is the bytecode verifier. Before a Java
program is run, a verifier checks each bytecode to ensure that
nothingsuspiciousisgoingon.

18
 2.1 Proposed Approach:

We have proposed a new monitoring approach – NMoCS

(Network Monitoring& controlling System). Amongst the broad
categories of monitoring system- active and passive monitoring, NMoS
falls under active monitoring approach. Our approach includes running a
program at the server that is constantly listening to the various clients. A
separate program runs at the client machine. As soon as the client
program starts running, images are sent from the client end to the server
end. The images are sent in compressed format to speed up the transfer
of images and also to get very quick responses from the client machine.
This client data, which is in the form of compressed images, is send to
the server program continuously. If the user is found to be using the
network resources in an inappropriate manner then this can be easily
visualized at the server. Corresponding actions then may be taken to
restrict the activities of theuser.

The administrator can send a warning message to the client that he should
stop using the network resources in an incorrect manner. Steps can also be
taken to prevent the user from changing the contents of the machine. If after several
warning messages the user continues to use the network in an incorrect manner then
the administrator can take some corrective measures such as lock the input devices
or turn off the client machine
. The administrator can also use the software for transferring some files to the
desired machines. The software also helps to locate the IP address of the
machine, operating system and its version used by the client.
 2.2REQUIREMENT HARDWARE

2.1.1Hardware requirements:
Hardware for implementing TCP/IP Networking.
CPU equivalent or above Intel Celeron 800 MHz.
RAM 128 MB or higher.

2.3 Software requirements:

JDK 1.7: for Java Class Libraries and Java Runtime Environment.
Any OS that supports Java for development and testing of Software
JCreatorPro (Integrated Development Environment) for Coding and Debugging.
Microsoft Word for Documentation
 SYSTEM MAINTENANCE & EVALUATION

Update your content and presentation based on our User’s feedback. When we are
evaluating user feedback, look for trends rather than individual aberrations, such as
one person’s vehement dislike of our color scheme. Pay particular attention to the
ease of access to our information. Clients ought to have the capacity to discover
what they need rapidly.
As this application is for software development purpose we can set up the program
which is beneficial for the developers and which will help them to update their
knowledge in all terms.
For that we have to plan for on-going maintenance of our Web site. This is an area
often neglected in the initial design and budgeting of the application, but it is vital
to the success of the application. Plan to add new links, information, and featured
content continually. The Web is a live, immediately by keeping it fresh. Try to
provide new Updated links or Web pages.
 COST AND BENEFITANALYSIS

Cost Benefit Analysis is an economic tool to aid social decision-

making, and is typically used by governments to evaluate the
desirability of a given intervention in markets. The point is to check the
proficiency of the mediation in respect to the present state of affairs.
The expenses and advantages of the effects of an intercession are
assessed as far as the open's eagerness to pay for them (advantages) or
ability to pay to maintain a strategic distance from them (costs). Data
sources are regularly estimated as far as happenstance costs - the
incentive in their best elective use. The core value is to list the majority
of the gatherings influenced by an intercession, and spot a fiscal
estimation of the impact it has on their welfare as it would be
esteemed by them.

The procedure includes fiscal estimation of beginning and on-going costs versus
anticipated return. Building conceivable proportions of the expenses and
advantages of explicit activities is frequently extremely troublesome. Practically
speaking, examiners attempt to assess expenses and advantages either by utilizing
review techniques or by illustration surmisings from market conduct. Money saving
advantage examination endeavors to put every important expense and advantages
on a typical worldly balance. A rebate rate is picked, which is then used to figure all
significant future expenses and advantages in present-esteem terms.
 3. SYSTEM ANALYSIS AND DESIGN

3.1.1 Introduction to Design

The plan approach that was appropriate for the venture ended up
being object-arranged structure. It makes a portrayal of this present
reality issue space and maps it into an answer area that is programming.
In contrast to different strategies, object-arranged plan results in a
structure that interconnects information objects(data things) and
preparing activities in a manner that modularizes data and handling , as
opposed to handling alone.

3.1.2 Architectural Design

The architectural design represents the data structure and program
components that are required to build the system. It takes into account
the style of construction that the structure will take, the structure and
properties of the parts that establish the structure, and the connections
that occur between each engineering segment of a structure.Because this
is client-server model based on Component-based development model
so the main components of this system are classes which are used to
build whole system and reused later. Architectural design represents
what are the classes used and how they interact with each other to
provide full functionality.
3.1 MODULE AT CLIENT
 Steps involved in the Waterfall Model:

1. Requirement:
It involves studying different algorithms, deciding on a platform (OS) to work on
and looking for different technologies to work with.

2. Analysis: in this phase, the appropriate algorithm and technology are selected,
the functions are defined and a feasibility study is carried out.

4. Design: the architecture, software flow rate, algorithm and user interface are
all designed here.

Each period of advancement continues in demanding demand, without covering or

iterative progress.
While this process does not handle change well, it is a simple template for design
software continues to be very popular, and it is easy to understand and easy to
follow. In addition, the steps in the process are attractive to management as they
can be easily monitored and used as milestones for the project.
 The modified waterfall model works better in most cases than the classic waterfall model. It has
the same breakdown of development tasks; consequently, this approach can handle more dynami

Requirement Specification

Verification & Validation

Modified
Analysis of System
Waterfall

Verification & Validation Model

Design of System

Verification & Validation

Coding

Verification & Validation

Code &

Fix Model
Code Testing & Maintenance

& Verification & Validation

Fix Model
 User Interface Design

UI configuration makes a successful correspondence medium between a human and

a PC. Following a lot of interface plan standards, structure characters interface items
and activities and after that make a screen format that shapes the reason for a client
interface design.

Steps: User interface configuration starts with the distinguishing proof of client, task,
and ecological prerequisites.
Users: Network Administrators of the Organization will use utilities
provided by Remote Desktop Monitor for performing various
Operations over Remote Clients.

Tasks:The user shall be able to view graphically all the client systems
connected to the Remote Desktop Monitor Server program.The user
shall be able to select any number of systems and accordingly perform
any of the operations available and applicable to that client.

The Remote Desktop Monitor provide efficient mechanism to

show Messages, Images, view clearly and quickly changes occurred on
client machine when user controlling that client machine from server
end on various Clients Machines.
Process modelused:
The object-oriented paradigm emphasizes the creation of classes
that encapsulate both data and the algorithms that are used to manipulate
the data. The object-oriented classes are reusable across different
applications and computer-based system architectures.
The process model used in the project is Component Assembly
Model. It demands an iterative approach to the creation of software and
composes applications from prepackaged software components.
The engineering activity begins with the identification of candidate
classes by examining the data that are to be manipulated by the
application and the algorithms that will be applied to the accomplish the
manipulation. Comparing information and calculations are bundled into
a class. Classes made in past programming designing tasks are put away
in a class library or store.
When hopeful classes are recognized, the class library is sought to
decide whether these classes as of now exist. In the event that they do,
they are separated from the library and reused.If a candidate class
doesn’t reside in the library, it is engineered using object-oriented
methods. The principal emphasis of the application to be constructed is
then created ,utilizing classes removed from the library and any new
classes worked to meet the novel needs of the application.
 Identify candidate
components.

Look up components
Construct nth
in library
iteration of system

Put new
Extract components
components in
if available
library

Build components if
unavailable
Functional Description

The main functions which are used to logically build the whole system given
below:

Read Input:
This function reads the input commands from user on the server
side by entering some data using Keyboard or through mouse click on
the menu

Establish Session:
This is the centralized and general server function which makes the
connection between client and server and create a separate session for
every connection. This stores information regarding each client
connection and sends it to appropriate handler.

Grab Image:
GrabImage is client-side function which continuously captures the
desktop screen image and sends it to the server.
BehavioralModel Description

Systemstates:

Server:
 Always waiting for new clients
 Showing data/images
 Sending instructions or message to clients
 Waiting for next event by the user or from a number of Clients
connected.
 Controlling the selected client using mouse click.
 Communicating with any no. of clients

Client:
 Waiting for connection with the server
 Waiting for next command
 Performing actions according to the instructions sent by theserver
 Sending reply to the server for an instruction.
 State TransitionDiagram
State transition diagram represents the switch between various states of system and
depicts the condition for switching.

Invoke chat/controller

Request event
Capture event
Invoke connect process
Invoke image grabber

Server Establishing Capturing image

Start/stop waiting session

Display event
Close client event
Invoke customizedisplay
Go for waiting
Customizing Processing
display image Image process event
Invoke image compressor
Modify event
Invoke customize display

Chatting

Remote Control

Chat/Control event
Page26
Packages used in project

 Java.netpackage:
This package provide a class to create a socket where the server listens
for client request.

 Java.io package:
This package is used to handle the input/output error.

 Javax.swingpackage:
This package consist the entire swing components like JTextField, JPanel
etc.

 Java.awt.eventpackage:
This package used to encapsulate the information with the application.

 com.sun.ima
 3. Server Process – FlowChart

Start

Various
constants are
initialized here

Monitor a client or
The Server continuously
stop monitoring an
listens at the corresponding
existing client if one
exists port and the server side GUI is

A new Thread is created to If any error occurs in

handle the client. The client Error handling the client request it
count is incremented by one is dealt with here and the
thread is not created.

If the connection is established

then steps are taken to display the
client activity at the server side
continuously.

Actions are taken to carry out the desired

administrator tasks

All the thread

are stopped

Stop
3 Client Process – Flow Chart

Start

Connection established
between the client and the

Client program is in a wait state. On

receiving the request from the server it
performs the desired action

Yes If
Administrat
or or
detects
Shutdown request or stop illegal
sending the images

No
Connection is lost and the
monitoring is stopped
The client keeps on running and
transferring the images of its desktop all
the time

Stop

Monitoring process can be restarted

DFD diagram:
“1”level:
3. Activity Diagram

Administrator Login

VALID INVALID

Read password as Prompt for re

input entry.
Stop
Read
command

Establish
session Close client
event

Select client

Take app.
action
Select
operation

Customize
Chat Remote Grab
display
Control Image

Process

Image

Chat contoller Image

invoked grabber
invoked
Image compressor
Continuous Capture image invoked
comm.. with
client
Controlling

& monitoring

3.11 Class Diagram

 Server-Side

Server Main

Server object

JDesktopPane object
1
1 MonitorWindow[ ] object

Chat Window [ ] object

N N

Chat Window 1 MonitorWindow

Socket object Input

Stream object Server Frame object

N
Output Stream

object Server

Client Address[ ] object

Socket [ ] Object

int client Count

Fig.Class Diagram of server side

31
Client-Side

ClientChatWindow

Input Stream

Output Stream

Image Grabber

1
Buffered Image
1
Output Stream
Control Command

Input Stream

String Comdata

32
3.3 Planning and Scheduling
GANTT CHART

SR NO. PHASE TITLE START TIME FINISH TIME DUARTION

1. Introduction 12-8-18 14-8-18 2 Days
2. Survey of 15-8-18 18-8-18 3 Days
Technologies
3. Requirement and
Analysis
3.1 Problem Definition 19-8-18 20-8-18 1 Day
3.2 Requirements 21-8-18 23-8-18 2 Days
Specification
3.3 Planning and 24-8-18 26-8-18 2 Days
Scheduling
3.4 Software and 27-8-18 30-8-18 3 Days
Hardware
Requirements
3.5 Preliminary Product 31-8-18 2-9-18 3 Days
Description
3.6 Conceptual Models
3.6.1 E-R Diagram 3-9-18 5-9-18 2 Days
3.6.2 DFD Diagram 6-9-18 8-9-18 2 Days
3.6.3 System Flow Diagram 9-9-18 12-9-18 3 Days
4. System Design
4.1 Basic Module 13-9-18 15-9-18 2 Days
4.2 Data Design
4.2.1 Class Diagrams 16-9-18 18-9-18 2 Days
4.2.2 Data Integrity and 19-9-18 22-9-18 3 Days
Constraints
4.3 Procedural Design
4.3.1 Sequence Diagram 23-9-18 26-9-18 3 Days
4.3.2 Use Case Diagram 27-9-18 28-9-18 1 Day
4.3.3 Activity Diagram 29-9-18 1-10-18 3 Days
4.4 User Interface Design
4.5 Security Issues 11-10-18 14-10-18 3 Days
4.6 Test Cases Design

33
4.Test Cases Design
Programming testing is an examination directed to furnish partners with data about
the nature of the item or administration under test.
The essence of testing is to:

Track the errors to understand their causes and any patterns that may exist.
Revalidate the stability of solutions, including ensuring that the correction of
one error does not lead to introduction of another error somewhere else.

A primary purpose for this testing is to detect software failures so that defects
may be uncovered and corrected. Programming testing is an examination
directed to furnish partners with data about the nature of the item or
administration under test. of code: does it do what it is supposed to do and
what it needs to do.

34
35
36
37
38
39
40
 5. Implementation And design
Presently, I'm not here to disclose to you that arrange observing programming can
understand the majority of your security needs, needs, and issues.That’s not what it’s built
for, and that that’s not what it does. What I can say, is that when appropriately designed, a
great system observing arrangement can be an incredible help to your standard security
regiment. And, for organizations without the resources for a full-fledged SIEM and SOC,
the tips below can be a good stop-gap solution for alerting on some critical issues.

Network discovery is the first step in configuring a network monitoring system. It is also an
essential tool for getting a security value from your configuration.

This is because having an inventory of devices on your Network,

and their typical profiles, is an integral part of any security program. Not
only does Network Discovery and inventory give you the ability to
recover after a disaster, it can also help you understand where data has
been compromised and will provide you with a higher understanding of
sensitive areas, such as servers where regulated information is stored or
transmitted.
A capable network observation tool can have the power to
implement scheduled SNMP-based or system-specific discoveries on a
daily basis, which is able to assist you continue track for changes in your
surroundings and realize new devices on your Network. You can also
make ad hoc discoveries when things don't look good. With WhatsUp
Gold, you can even set up notifications and alerts via e-mail or Slack
when a discovery finds unexpected devices.
As in dance room music, a decent baseline is important. To know
when things go wrong with your network, you first need to know what
things look like when they're right.
The best practice is to establish baselines for as many parameters
as possible. With performance monitors, you can track measures like
CPU, memory, disk use or interface, set benchmarks, and set alerts for
when these basic thresholds are exceeded. This can alert you to many
security issues.

Page 41
 Design
The architectural design represents the data structure and program components
that are required to build the system. It takes into account the architectural style
that the system will take, the structure and properties of the components that
make up the system, and the interrelationships that occur between all the
architectural components of a system.
Because it is a client-server model based on a component-based development
model, the main components of this system are classes that are used to build the
entire system and reused later. The architectural design represents the classes used
and how they interact with each other to provide a complete functionality.
N 5.1 Implementing Arrangements
SNMP stands for easy Network Management Protocol and consists of 3 key
components: managed devices, agents and network management systems (NMSS).
The protocol is a set of standards for communication with devices on a TCP/IP
network. The SNMP monitoring is useful for all those who are responsible for
servers and network devices such as hosts, routers, hubs and switches. It allows you
to keep track of network and bandwidth usage, and track important issues such as
uptime and traffic levels.
SNMP versions (SNMP V1, V2C or V3) may vary from device to device. If you
encounter problems when configuring your Windows SNMP tools, the Paessler
Support team will be happy to offer you its advice and support. In general, our
support team responds to inquiries within 24 hours. With SNMP tools just like the
SNMP tester, you'll sight and right issues. Just send your log files to our support
team for analysis
All in one, at no extra cost: this is our philosophy. With PRTG, the full range of
functions is included. There are no hidden fees or upgrades to pay. This is also true
if you want to use your monitoring for SNMP traps. Using PRTG as a trap receiver is
simple! We have created a sensor that is also available in the free version - to help
you get started.
SNMP traps: with SNMP monitoring, the monitoring software usually sends small
packets of data to the target devices to ask for various information. This in turn
triggers the response packets of the monitored devices for SNMP manager. The

Page 42
advantage of SNMP traps is that devices automatically send messages to the SNMP
server monitoring software in the event of critical incidents, without having to do
so first.

Page 43
 5.2.1 Coding Efficiency

namespace Networks
{
publicpartialclassLogin : DevComponents.DotNetBar.Office2007Form
{
public Login()
{
Initialize Component();
}

privatevoidLogin Load(object sender, Eventers e)

{
this.Office2007ColorTable = DevComponents.DotNetBar.Rendering.eOffice2007ColorScheme.Black;

privatevoid BtnLogin_Click(object sender, Eventers e)

{
if (TxtUserName.Text=="admin"&& TxtPassword.Text=="admin")
{
Main mn = new Main();
MN. Show();
Hide();
}
else
{
MessageBox.Show("Please Enter valid Username or
Password","Login",MessageBoxButtons.OK,MessageBoxIcon.Information);
}
}

privatevoid BtnClose_LinkClicked(object sender, LinkLabelLinkClickedEventArgs e)

{
this. Dispose();
}
}
}

Page 44
namespace Networks
{
partialclassLogin
{
///<summary>
/// Required designer variable.
///</summary>
private System.ComponentModel.IContainer components = null;

///<summary>
/// Clean up any resources being used.
///</summary>
///<param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
protectedoverridevoid Dispose(bool disposing)
{
if (disposing && (components != null))
{
components. Dispose();
}
base. Dispose(disposing);
}

#region Windows Form Designer generated code

///<summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
///</summary>
privatevoidInitialize Component()
{
this.GroupPanel1 = new DevComponents.DotNetBar.Controls.GroupPanel();
this.BtnClose = new System.Windows.Forms.LinkLabel();
this.LabelX3 = new DevComponents.DotNetBar.LabelX();
this.PictureBox1 = new System.Windows.Forms.PictureBox();
this.LabelX2 = new DevComponents.DotNetBar.LabelX();
this.LabelX1 = new DevComponents.DotNetBar.LabelX();
this.TxtPassword = new DevComponents.DotNetBar.Controls.TextBoxX();
this.BtnLogin = new DevComponents.DotNetBar.ButtonX();
this.TxtUserName = new DevComponents.DotNetBar.Controls.TextBoxX();
this.GroupPanel1.SuspendLayout();
((System.ComponentModel.ISupportInitialize)(this.PictureBox1)).BeginInit();
this.SuspendLayout();
//
// GroupPanel1
//
this.GroupPanel1.CanvasColor = System.Drawing.SystemColors.Control;
this.GroupPanel1.ColorSchemeStyle = DevComponents.DotNetBar.eDotNetBarStyle.Office2007;
this.GroupPanel1.Controls.Add(this.BtnClose);
this.GroupPanel1.Controls.Add(this.LabelX3);
this.GroupPanel1.Controls.Add(this.PictureBox1);
this.GroupPanel1.Controls.Add(this.LabelX2);
this.GroupPanel1.Controls.Add(this.LabelX1);
this.GroupPanel1.Controls.Add(this.TxtPassword);
this.GroupPanel1.Controls.Add(this.BtnLogin);
this.GroupPanel1.Controls.Add(this.TxtUserName);
this.GroupPanel1.Location = new System.Drawing.Point(12, 10);
this.GroupPanel1.Name = "GroupPanel1";
this.GroupPanel1.Size = new System.Drawing.Size(352, 192);
//
Page 45
//
//
this.GroupPanel1.Style.BackColor2SchemePart = DevComponents.DotNetBar.eColorSchemePart.PanelBackground2;
this.GroupPanel1.Style.BackColorGradientAngle = 90;
this.GroupPanel1.Style.BackColorSchemePart = DevComponents.DotNetBar.eColorSchemePart.PanelBackground;
this.GroupPanel1.Style.BorderBottom = DevComponents.DotNetBar.eStyleBorderType.Solid;
this.GroupPanel1.Style.BorderBottomWidth = 1;
this.GroupPanel1.Style.BorderColorSchemePart = DevComponents.DotNetBar.eColorSchemePart.PanelBorder;
this.GroupPanel1.Style.BorderLeft = DevComponents.DotNetBar.eStyleBorderType.Solid;
this.GroupPanel1.Style.BorderLeftWidth = 1;
this.GroupPanel1.Style.BorderRight = DevComponents.DotNetBar.eStyleBorderType.Solid;
this.GroupPanel1.Style.BorderRightWidth = 1;
this.GroupPanel1.Style.BorderTop = DevComponents.DotNetBar.eStyleBorderType.Solid;
this.GroupPanel1.Style.BorderTopWidth = 1;
this.GroupPanel1.Style.CornerDiameter = 4;
this.GroupPanel1.Style.CornerType = DevComponents.DotNetBar.eCornerType.Rounded;
this.GroupPanel1.Style.TextAlignment = DevComponents.DotNetBar.eStyleTextAlignment.Center;
this.GroupPanel1.Style.TextColorSchemePart = DevComponents.DotNetBar.eColorSchemePart.PanelText;
this.GroupPanel1.Style.TextLineAlignment = DevComponents.DotNetBar.eStyleTextAlignment.Near;
this.GroupPanel1.TabIndex = 1;
this.GroupPanel1.TitleImagePosition = DevComponents.DotNetBar.eTitleImagePosition.Center;
//
// Buncos
//
this.BtnClose.AutoSize = true;
this.BtnClose.BackColor = System.Drawing.Color.Transparent;
this.BtnClose.Location = new System.Drawing.Point(319, 173);
this.BtnClose. Name = "Buncos";
this.BtnClose.Size = new System.Drawing.Size(24, 13);
this.BtnClose.TabIndex = 7;
this.BtnClose.TabStop = true;
this.BtnClose.Text = "Exit";
this.BtnClose.LinkClicked += new
System.Windows.Forms.LinkLabelLinkClickedEventHandler(this.BtnClose_LinkClicked);
//
// LabelX3
//
this.LabelX3.AutoSize = true;
this.LabelX3.BackColor = System.Drawing.Color.Transparent;
this.LabelX3.Location = new System.Drawing.Point(79, 21);
this.LabelX3.Name = "LabelX3";
this.LabelX3.Size = new System.Drawing.Size(248, 15);
this.LabelX3.TabIndex = 6;
this.LabelX3.Text = "Please Enter User Name and Password Pres login";
//
// PictureBox1
//
this.PictureBox1.BackColor = System.Drawing.Color.Transparent;
this.PictureBox1.Image = global::Networks.Properties.Resources.login;
this.PictureBox1.Location = new System.Drawing.Point(3, 0);
this.PictureBox1.Name = "PictureBox1";
this.PictureBox1.Size = new System.Drawing.Size(61, 59);
this.PictureBox1.SizeMode = System.Windows.Forms.PictureBoxSizeMode.StretchImage;
this.PictureBox1.TabIndex = 5;
this.PictureBox1.TabStop = false;
//
// LabelX2
//
this.LabelX2.AutoSize = true;
Page 46
this.LabelX2.BackColor = System.Drawing.Color.Transparent;
this.LabelX2.Location = new System.Drawing.Point(80, 108);
this.LabelX2.Name = "LabelX2";
this.LabelX2.Size = new System.Drawing.Size(67, 15);
this.LabelX2.TabIndex = 4;
this.LabelX2.Text = "PASSWORD";
//
// LabelX1
//
this.LabelX1.AutoSize = true;
this.LabelX1.BackColor = System.Drawing.Color.Transparent;
this.LabelX1.Location = new System.Drawing.Point(79, 59);
this.LabelX1.Name = "LabelX1";
this.LabelX1.Size = new System.Drawing.Size(68, 15);
this.LabelX1.TabIndex = 3;
this.LabelX1.Text = "USER NAME";
//
// TxtPassword
//
//
//
//
this.TxtPassword.Border.Class = "Textbox Border";
this.TxtPassword.Border.CornerType = DevComponents.DotNetBar.eCornerType.Rounded;
this.TxtPassword. Font = new System.Drawing.Font("Microsoft Sans Serif", 11.25F,
System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, ((byte)(0)));
this.TxtPassword. Location = new System.Drawing.Point(174, 104);
this.TxtPassword. Name = "Tx Password";
this.TxtPassword.PasswordChar = '*';
this.TxtPassword. Size = new System.Drawing.Size(151, 32);
this.TxtPassword.TabIndex = 1;
//
// BtnLogin
//
this.BtnLogin.AccessibleRole = System.Windows.Forms.AccessibleRole.PushButton;
this.BtnLogin. Location = new System.Drawing.Point(207, 151);
this.BtnLogin. Name = "Benogin";
this.BtnLogin. Size = new System.Drawing.Size(75, 23);
this.BtnLogin.TabIndex = 2;
this.BtnLogin. Text = "Login";
this.BtnLogin. Click += new System.EventHandler(this. BtnLogin_Click);
//
// TX Username
//
//
//
//
this.TxtUserName.Border.Class = "Textbox Border";
this.TxtUserName.Border.CornerType = DevComponents.DotNetBar.eCornerType.Rounded;
this.TxtUserName. Font = new System.Drawing.Font("Microsoft Sans Serif", 11.25F,
System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, ((byte)(0)));
this.TxtUserName. Location = new System.Drawing.Point(174, 58);
this.TxtUserName. Name = "TX Username";
this.TxtUserName. Size = new System.Drawing.Size(151, 32);
this.TxtUserName.TabIndex = 0;
//
// Login
//
this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
Page 47
this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
this.ClientSize = new System.Drawing.Size(377, 213);
this.Controls.Add(this.GroupPanel1);
this.DoubleBuffered = true;
this.FormBorderStyle = System.Windows.Forms.FormBorderStyle.FixedDialog;
this.MaximizeBox = false;
this.MinimizeBox = false;
this. Name = "Login";
this.StartPosition = System.Windows.Forms.FormStartPosition.CenterScreen;
this. Text = "Login";
this. Load += new System.EventHandler(this.Login_Load);
this.GroupPanel1.ResumeLayout(false);
this.GroupPanel1.PerformLayout();
((System.ComponentModel.ISupportInitialize)(this.PictureBox1)).EndInit();
this.ResumeLayout(false);

#end region

internal DevComponents.DotNetBar.Controls.GroupPanel GroupPanel1;

internal System.Windows.Forms.LinkLabel Buncos;
internal DevComponents.DotNetBar.LabelX LabelX3;
internal System.Windows.Forms.PictureBox PictureBox1;
internal DevComponents.DotNetBar.LabelX LabelX2;
internal DevComponents.DotNetBar.LabelX LabelX1;
internal DevComponents.DotNetBar.Controls.TextBoxX Tx Password;
internal DevComponents.DotNetBar.ButtonX Benogin;
internal DevComponents.DotNetBar.Controls.TextBoxX TX Username;
}
}

Page 48
5.3 Testing apparoches
The use of tools in Agile projects should complement, but not replace, the interaction of people.
In Agile software development projects, there are many tools that are used in various situations.
Some examples of tools are: developers use tools like SONAR for static analysis and code
coverage, JUnit for code coverage. Developers also use configuration management tools like
SVN, where they can check source code, unit tests. The configuration management tool will
compile and build the code with test frames.
Unit tests
minimum software components (modules) are tested.
Each unit (basic component) of the software is tested to verify that the detailed design of the
device has been correctly implemented.
The tests shall be carried out at Class level, and the minimum unit tests shall include
manufacturers and destructors.
In Back Box Testing, tests based on specifications are performed to find that each module
provides a specific output for particular input integration tests.
Interfaces and interaction between integrated components are tested.
A growing group of tested software components corresponding to elements of architectural
design are integrated and tested until the software functions as a system.
Beta Test
* A beta test is the second phase of the software test in which a sample of the target audience
tests the product. (Beta is that the second letter of the Greek alphabet. The term alpha testing
originally meant the first phase of testing in a software development process. The first phase
involves testing units, components and systems. Beta tests can be considered as “pre-release
tests".
* The purpose of beta testing is to put your application in the hands of actual users outside your
own engineering team to discover faults or problems from the user's point of view that you
would not want to have in your final, published version of the application. Example: Microsoft
and many other organizations release beta versions of their products for user testing.
5.4 Modification and improvement
The network monitoring and control system in the Modification of the so easily catch the data as
well as the switch to the data
In this system are required to the ip address and after the calculated process
Sender sends data to recipient accept data
This project is the improvement of all the information showing are easily
Only we have the address inserted to automatically display all information on
Test Case
Regression Tests:
The regression test focuses on the discovery of flaws after a major code change has taken place
specifically, it seeks to discover the regression of software, or old bugs that have returned. Such
regression occurs when the functionality of the software that previously functioned properly
Page 49
ceases to function as expected.
Stability Testing:
Stability testing is used to verify that the software is capable of continuous operation for or
beyond an acceptable period of time. This non-functional software activity.
User-friendliness Tests:
Usability testing is necessary to verify whether the user interface is easy to use and understand.
He's getting closer to using the app.
686. result and description
The network monitoring and control system in the result of us are inserted the Ip address and
after the calculated process
And another step is starting your monitor it means that the name of the server and the username,
password
The network monitoring and control system in the sending of e-mail are easily in this project in
the mail, AOD as well as tweet are included
To use an architectural decision that will make the application be as much as possible: modular,
well managed, fair, simple, easy to understand, user-friend

Page 50
Snapshots

Page 51
Page 52
Page 53
Page 54
Page 55
Page 56
Page 57
6.1 Test Report
In this project, the ip addresses are inserted correctly . the automatic system
calculated

The subnet mask and host numbers show

The network monitoring system in the monitor name insert this means that the set as
the server name and the username are required. The regression test focuses on the
discovery of flaws after a major code change has taken place specifically, it seeks to
discover the regression of software, or old bugs that have returned. Such regression
occurs when the functionality of the software that previously functioned properly
ceases to function as expected.

Stability testing is used to verify that the software is capable of continuous

operation for or beyond an acceptable period of time. This non-functional software
activity.

Usability testing is necessary to verify whether the user interface is easy to use
and understand. He's getting closer to using the app.
Install Yandex. Translate on your mobile phone
Mobile version Developers User Agreement Help

Page 58
 6.2 User Documentation

RAGISTER

USERNAME

PASSWORD

SUBMIT

Page 59
Page 60
 7 . Conclusion
project closure issues were discussed and ways to evaluate a project were
discussed. Key elements of project closure were identified and discussed
and their importance in ensuring that project goals and objectives were
achieved was explored. You should now be able to plan for an effective
closure of the project. Problems often need to be resolved at the close-out
stage, and project managers need to be aware of potential problems.

The transfer and delivery of a project or its components, are

important steps. They require planning to ensure that the project proponent
or other beneficiaries of the project results are satisfied and able to move
forward. There are also opportunities at these races to improve the
impression the project team made.

Evaluation can take place at any time during the course of a project
and can have a significant impact on its continuation, in the direction of
golden success. Most projects end with an evaluation, and project team
leaders are generally invited to contribute. The evaluation may also take
place some time after a project has been concluded, to examine how well it
has achieved sits the long-term objective. You should now be able to
contribute with confidence to the planning and implementation of
evaluations.
Planning your personal development to improve your future
performance in project management was also discussed.

Page 61
 Limitation of the system

While flexibility is the hallmark that distinguishes Nagios from

other monitoring tools, the
the flexibility of Nagios becomes a two-edged sword. Users generally
experience this flexibility and
configurability usually translates into a long and arduous setup process.
Some limitations are
probably due to the minimalist philosophy of Nagios design concept, for
example the absence of
attractive and interactive user interface. Fortunately, the community of
Nagios has recognized these
problem. Some of the weaknesses can be filled with add-ons gold plugins
of Nagios
community. However, some limitations remain a challenge. This section
examined
these two types of limitations in Nagios from the point of view of Nagios
users and developers.

Page 62
7.3 future scope of the project

Software domains are companies ‘gold organizations that use computer

networks as a source of information exchange and
communication preferably networks of educational institutions and other
similar networks. In these organizations, the performance of the computer
networks they use-plays a crucial role in their effective functionality. Such
organizations range from a small having 15-20 computers to a large
employing a large number of computers, including various peripheral
devices.

To use year architectural decision that will make the application be as

much as possible: modular, well managed, fair, simple, easy to understand,
user-friendly.

Page 63
 References
 www.slideshare.net
 www.infoworld.com
 issuu.com
 1000projects

Page 64