GUI Based Real Time Monitoring and Controlling Approach on Networking
A Technical Project report Submitted in the partial fulfillment of the requirement
For the award of the degree of
BACHELOR OF TECHNOLOGY
IN
COMPUTER SCIENCE AND ENGINEERING Submitted By K.BHARGAVI CH.KOMALI
(Regd. no: 11981A0528) (Regd. no: 11981A0537) K.L.V.S.SANKAR ANDE BINDU YATHISHA
(Regd. no: 11981A0541) (Regd. no: 11981A0543)

Under the esteemed guidance of
Mr. B. SATHISH KUMAR
Assistant Professor
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
[pic]
RAGHU ENGINEERING COLLEGE
(Affiliated to JNTU-KAKINADA)
Dakamari, Bheemunipatnam Mandal,Visakhapatnam-531162
2014-2015

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
RAGHU ENGINEERING COLLEGE
(AFFILIATED TO JNTUK)
BHEEMUNIPATNAM MANDAL
VISAKHAPATNAM

[pic]
CERTIFICATE
This is to certify that this Project Report Entitled “ GUI Based Real Time Monitoring and Controlling Approach on Networking” is the bonafide work carried out by K.Bhargavi(11981A0528),CH.Komli(11981A0537),K.L.V.S.Sankar(11981A0541),Ande Bindu Yathisha(11981A0543)of final year B.Tech, Computer Science Engineering, submitted in the partial fulfillment of the requirements for award of Degree of Bachelor of Technology during the Year 2011-2015.

Mr. B. SATHISH KUMAR Mr. B. VENKATESWARLU
Assistant professor Associate professor

Internal Guide Project coordinator

Head of Department External Examiner

DECLARATION

We K.Bhargavi(11981A0528),CH.Komali(11981A0537), K.L.V.S.Sankar(11981A0541) , Ande Bindu Yathisha(11981A0543) hereby declarethat the project work which is presented in this report entitled “GUI Based Real Time Monitoring and Controlling Approach on Networking” is the work done by us in partial fulfillment of requirements for the award of B.Tech in Computer Science & Engineering submitted to the department of Computer Science & Engineering of Raghu Engineering College under Jawaharlal Nehru Technological University, Kakinada is authentic of my own work carried out under the supervision of Mr. B. Sathish Kumar,M.Tech(Ph.d)(Assistant professor), Department of Computer Science Engineering, Raghu Engineering College, Dakamarri, Visakhapatnam. The work done in this report has not been submitted to any other university/institute for the award of B.Tech degree.

Date:
Place: Visakhapatnam

ACKNOWLEDGEMENT

We take this opportunity, with great pleasure, to put on record our ineffable personal indebtedness to our Chairman, Sri Kalidindi Raghu garu and our Principal Dr.M.Kameswara Rao, for providing us all the necessary departmental facilities.
We specially thank our honorable Head and Coordinator Mr.B.Venkateswarlu Associate professor, CSE, Raghu Engineering College for giving great support and for providing us all the required information regarding the project and valuable guidance, patience throughout the project.
We are quite thankful to our beloved guide Mr.B.Sathish Kumar M.TECH ph.d, (Assistant Professor), department of CSE, Raghu Engineering College for his great guidance throughout our project and gave us an urge to take up this project.
We would like to express our profound sense of gratitude to, Raghu Engineering College for giving us the opportunity of doing the thesis and for providing us all the required facilities.
Successful completion of a project undertaken, gives every individual invaluable amount of happiness and confidence. All this is possibly happened only because of our co-operative work an auxiliary support from many people.
Finally, we thank all the faculty of our department for always encouraging us. We also thank lab assistants who have helped us all time for the completion of our project. We are thankful to our college for providing us all the required facilities. We also wish to express our sincere thanks to some of our classmates who helped us in solving our logic complexities.

K.Bhargavi(11981A0528) CH.Komali(11981A0537) K.L.V.S.Sankar(11981A0541) A. Bindu Yathisha(11981A0543)
CONTENTS

Cover Page Certificate i Declaration ii Acknowledgement iii Contents iv Abstract 8 1. INTRODUCTION ...………………………………………………..10 1.1 About the project …..............................................................12 2. LITERATURE SURVEY .................................................................14 3. SYSTEM ANALYSIS …………………………………………….... 20 3.1Existing system …………………………………….……….21 3.1.1 Disadvantages 3.2 Proposed system ………………………………………….....21 3.2.1 Advantages 3.3 S/W Requirement Specification …………………………...23 3.3.1Functional Requirements ………………………23 3.3.2 Non-functional Requirements …………………23 3.3.3 S/W & H/W Requirements ……………………..24 3.4 Feasibility study ……………………………………………..25 4. SYSTEM DESIGN …………………………………………………..29 4.1 Architecture / Algorithm Design …………………………..30 4.2 Introduction to UML ……………………………………......30 4.3 UML Diagrams ……………………………………………....31 4.3.1Relationships In UML ..…………………...……..….32 4.3.2Use case diagram ..………………………………...…33 4.3.3Class Diagram ………………………………..……..34 4.3.4 Sequences Diagram………………………………….36 4.3.5 Collaboration Diagram…………………………...…37 4.3.6 Activity Diagram …………………………………...38 4.3.7 State chart Diagram ………………………………..39 4.3.8 Component Diagram….……………………………..40 4.3.9 Deployment Diagram ………………………….….....40 5. SYSTEM IMPLEMENTATION……………………………………..42 5.1 Introduction to .NET framework…...……………………….43 5.2 Introduction to WPF………...………………………………..44 5.3 Introduction to XAML……………..…………………..…….47 5.4 Implementation………………………………………………...52 5.4.1 Algorithm………………………………………...……53 5.5 Coding………………………………………………………….54 6 . SYSTEM TESTING…………………………………………………..64 6.1 Testing objectives………………………………………………65 6.2 Test Case Design 6.2.1 White box and Black box……………………………66 6.3 Testing Strategy………………………………………………..68 6.3.2 Integration Testing…………………………………..68 6.3.3 System testing………………………………………...69 6.3.4 Acceptance Testing 6.3.4.1 Alpha and beta testing……………………..71 6.4 Test Cases and Results…………….…………………………..72 7. SCREEN SHOTS……………………………………….……………..74 8. CONCLUSION………………………………………….……………..82 9. FURTHER SCOPE OF DEVELOPMENT………………………….84 11. BIBLOGRAPHY……………………………………………………….86

ABSTRACT
ABSTRACT

A GUI based architecture for monitoring the operations and controlling the activities of the client machines placed in a network by an approach named RMC (Real-time Monitoring and Controlling) system. A client – server approach of the net spy allows the administrator to view those client systems connected to the LAN. The network administrator chooses needed clients with the help of their IP address for the monitoring process that enhances various events as system information, memory usage, desktop capturing and the tasks that are currently running under those clients. It captures the resources and each operation made in the client secretly. Here we enroll another process of controlling those monitored resources. The control utility includes locking the screen of the client system. It performs shutdown operations on the clients from the server. Combination of the controlling aspect along the monitoring process includes a cost efficient approach in maintaining a reliable network.

INTRODUCTION

1. INTRODUCTION Real-time Monitoring System software for monitoring the clients in a network. Client Systems are monitored through their IP address. While a client enters a network, it is enhanced with a port number and an IP address to be given in the server. Monitoring is efficient in all organizations for maintaining records about the clients entering and exiting their network. Various events are monitored such as capturing desktop activities and tasks running under clients. Monitoring a client can be a security operation prevailed over a network to keep a reliable flow of information between client and server. Clients may enroll their IP with the server for communication purpose but administrator takes rights on clients to make a security service. RM ensures a current state monitoring system which provides a facility of maintaining actions of the clients within the network circle. Clients may work against the organization and make them to collapse the goal they fixed for the yearly needs. But RM systems are used in their organization to make them secure by monitoring those clients and make their motto to be diminished. Most of the monitoring systems ensure traffic monitoring by the use of packet analyzer . Operations can be monitored only through the IP addresses that are provided by the clients.

Real-time Controlling system is an approach engaged only on controlling the clients from the server. The server or network administrator in the network controls each activity of their clients enrolled in their network. Controlling system is also made using the IP address of the clients. An organization controlled by a head, controls all the operations of their employees or clients by giving different rights for each clients. This is organized also in networks by enabling some rights for each client . Controlling software enables the network administrator to take control of their clients from their server monitor. Administrator enhances several rights along the clients for security purposes and maintains the network by provided commands over the clients to be performed by the clients to be constant in the network circle. Real-time controlling includes the control utility such as controlling hardware support of for the clients and locking their screens if not needed. It also performs shut operations on the clients from the server. Enabling this controlling system can make a cost efficient process for the server to work through their network. RC enabled networks can be a profitable approach for the organizations to work consistently. Servers enable their operation by commanding their clients to proceed with their work along server’s interaction on them . Networking enables those clients that are engaged along the server to process a schematic referenced structure of data transferring options. Controlling state of a system is the value added process of the system with an augmented security over a network environment.

Bottom of Form vv1.1 About the project

Most organizations need an eye on their employees work to fulfill their goals. Thus RMC approach is used here for making a real-time monitoring of their employees and makes them work properly by controlling them without any physical access. RMC plays the main role in capturing the employee’s screen and displaying it in the administrator’s system. Administrator also allows the employees present in the list to be logged into their network. RMC helps in terminating the programs that are running improperly in their client system. Organizations goals are to be succeeded with a necessary procedural works by the employees but if it is out of service in monitor and controlled by the administrator acting as a server. Employee’s system could be turned on only when it is registered in the employee’s list at the time of connection orientation. Without the presence of the administrator in an organization, systems are not allowed to be accessed by the clients. They work on their organization and make a disciplined way of communication between their employees.

Nowadays various educational institutions works with RMC approach to favor an excellent education to the students they handle. Education is organized through a network where movements of every student are watched periodically. Students are allowed to make their listening and writing works through the network based education system that are monitored then and there to show a good result in their performance in examinations. Monitoring each and every student to make them study well and construct their future with a disciplined environmental state of operations within them . Teachers in the institutions acts as the administrator and takes charge of their students activities and make a perfect atmosphere over the institution. RMC approach is also used in many applications for favoring a reliable state of networking state. RMC approach has secured a reliable and cost efficient software approach over the networking field.

LITERATURE SURVEY

2. LITERATURE SURVEY

Network socket:

A network socket is an endpoint of an inter-process communication flow across a computer network. Today, most communication between computers is based on the Internet Protocol; therefore most network sockets are Internet sockets.A socket API is an application programming interface (API), usually provided by the operating system, that allows application programs to control and use network sockets. Internet socket

A socket address is the combination of an IP address and a port number, much like one end of a telephone connection is the combination of a phone number and a particular extension. Based on this address, internet sockets deliver incoming data packets to the appropriate application process or thread.

Socket ()

Socket () creates an endpoint for communication and returns a file descriptor for the socket. Socket () takes three arguments:

domain, which specifies the protocol family of the created socket. For example: • AF_INET for network protocol IPv4 or • AF_INET6 for IPv6. • AF_UNIX for local socket (using a file). • SOCK_STREAM (reliable stream-oriented service or Stream Sockets) • SOCK_DGRAM (datagram service or Datagram Sockets) • SOCK_SEQPACKET (reliable sequenced packet service), or • SOCK_RAW (raw protocols atop the network layer • protocol specifying the actual transport protocol to use. The most common are IPPROTO_TCP, IPPROTO_SCTP, IPPROTO_UDP, IPPROTO_DCCP. These protocols are specified in . The value 0may be used to select a default protocol from the selected domain and type.

The function returns -1 if an error occurred. Otherwise, it returns an integer representing the newly assigned descriptor.

Prototype int socket(int domain, int type, int protocol); bind() bind() assigns a socket to an address. When a socket is created using socket(), it is only given a protocol family, but not assigned an address. This association with an address must be performed with the bind() system call before the socket can accept connections to other hosts. bind() takes three arguments:

• sockfd, a descriptor representing the socket to perform the bind on. • my_addr, a pointer to a sockaddr structure representing the address to bind to. • addrlen, a socklen_t field specifying the size of the sockaddr structure.

Bind() returns 0 on success and -1 if an error occurs.

Prototype int bind(int sockfd, const struct sockaddr *my_addr, socklen_t addrlen); listen() After a socket has been associated with an address, listen() prepares it for incoming connections. However, this is only necessary for the stream-oriented (connection-oriented) data modes, i.e., for socket types (SOCK_STREAM, SOCK_SEQPACKET). listen() requires two arguments:

• sockfd, a valid socket descriptor. • backlog, an integer representing the number of pending connections that can be queued up at any one time. The operating system usually places a cap on this value.

Once a connection is accepted, it is dequeued. On success, 0 is returned. If an error occurs, -1 is returned.

Prototype int listen(int sockfd, int backlog); accept() When an application is listening for stream-oriented connections from other hosts, it is notified of such events (cf. select() function) and must initialize the connection using the accept() function. The accept() function creates a new socket for each connection and removes the connection from the listen queue. It takes the following arguments:

• sockfd, the descriptor of the listening socket that has the connection queued. • cliaddr, a pointer to a sockaddr structure to receive the client's address information. • addrlen, a pointer to a socklen_t location that specifies the size of the client address structure passed to accept(). When accept() returns, this location indicates how many bytes of the structure were actually used.

The accept() function returns the new socket descriptor for the accepted connection, or -1 if an error occurs. All further communication with the remote host now occurs via this new socket.

Datagram sockets do not require processing by accept() since the receiver may immediately respond to the request using the listening socket.

Prototype int accept(int sockfd, struct sockaddr *cliaddr, socklen_t *addrlen); connect() The connect() system call connects a socket, identified by its file descriptor, to a remote host specified by that host's address in the argument list.

Certain types of sockets are connectionless, most commonly user datagram protocol sockets. For these sockets, connect takes on a special meaning: the default target for sending and receiving data gets set to the given address, allowing the use of functions such as send() and recv() on connectionless sockets.

connect() returns an integer representing the error code: 0 represents success, while -1 represents an error. Historically, in the BSD-derived systems, the state of a socket descriptor is undefined if the call to connect() fails (as it is specified in the Single Unix Specification), thus, portable applications should close the socket descriptor immediately and obtain a new descriptor with socket(), in the case the call to connect() fails.

Prototype int connect(int sockfd, const struct sockaddr *serv_addr, socklen_t addrlen);

Asynchronous Transfer Mode (ATM):

Asynchronous Transfer Mode (ATM) is, according to the ATM Forum, "a telecommunications concept defined by ANSI and ITU (formerly CCITT) standards for carriage of a complete range of user traffic, including voice, data, and video signals". ATM was developed to meet the needs of the Broadband Integrated Services Digital Network, as defined in the late 1980s, and designed to unify telecommunication and computer networks. It was designed for a network that must handle both traditional high-throughput data traffic (e.g., file transfers), and real-time, low-latency content such as voice and video. The reference model for ATM approximately maps to the three lowest layers of the ISO-OSI reference model: network layer, data link layer, and physical layer. ATM is a core protocol used over the SONET/SDH backbone of the public switched telephone network (PSTN) and Integrated Services Digital Network (ISDN), but its use is declining in favor of all IP.

ATM provides functionality that is similar to both circuit switching and packet switching networks: ATM uses asynchronous time-division multiplexing, and encodes data into small, fixed-sized packets (ISO-OSI frames) called cells. This differs from approaches such as the Internet Protocol or Ethernet that use variable sized packets and frames. ATM uses a connection-oriented model in which a virtual circuit must be established between two endpoints before the actual data exchange begins. These virtual circuits may be “permanent”, i.e. dedicated connections that are usually preconfigured by the service provider, or “switched”, i.e. set up on a per-call basis using signaling and disconnected when the call is terminated. ATM eventually became dominated by Internet Protocol (IP) only technology (and Wireless or Mobile ATM never got any foothold).

BITMAP IMAGE:

In computing, a bitmap is a mapping from some domain (for example, a range of integers) to bits, that is, values which are zero or one. It is also called a bit array or bitmap index.

In computer graphics, when the domain is a rectangle (indexed by two coordinates) a bitmap gives a way to store a binary image, that is, an image in which each pixel is either black or white (or any two colors).

The more general term pixmap refers to a map of pixels, where each one may store more than two colors, thus using more than one bit per pixel. Often bitmap is used for this as well. In some contexts, the term implies one bit per pixel, while pixmap is used for images with multiple bits per pixel.

A bitmap is a type of memory organization or image file format used to store digital images. The term bitmap comes from the computer programming terminology, meaning just a map of bits, a spatially mapped array of bits. Now, along with pixmap, it commonly refers to the similar concept of a spatially mapped array of pixels. Raster images in general may be referred to as bitmaps or pixmaps, whether synthetic or photographic, in files or memory.

Many graphical user interfaces use bitmaps in their built-in graphics subsystems; for

example, the Microsoft Windows and OS/2 platforms' GDI subsystem, where the specific format used is the Windows and OS/2 bitmap file format, usually named with the file extension of .BMP (or .DIB for device-independent bitmap). Besides BMP, other file formats that store literal bitmaps include Inter Leaved Bitmap (ILBM), Portable Bitmap (PBM), X Bitmap (XBM), and Wireless Application Protocol Bitmap (WBMP). Similarly, most other image file formats, such as JPEG, TIFF, PNG, and GIF, also store bitmap images (as opposed to vector graphics), but they are not usually referred to as bitmaps, since they use compressed formats internally.

3. SYSTEM ANALYSIS
3. SYSTEM ANALYSIS

Introduction

After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution. Analysis model The model that is basically being followed is the SOFTWARE DEVELOPMENT LIFE CYCLE MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. If system exists one then modification and addition of new module is needed, analysis of present system can be used as basic model .The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: - Project Planning
Requirements Definition
Design
Development
Integration & Test
Installation & Acceptance The relationship of each stage to the others can be roughly described as aWaterfall, where the outputs from a specific stage serve as the initial inputs for the following stage.

3.1 EXISTING SYSTEM In present scenarios, there are softwares performing monitoring options on the network. Softwares that can perform both monitoring and controlling operations are no more present in this existing environment. It is difficult to control the system only with the monitoring phase. the present software’s which are organized only for monitoring but not present their ideas in controlling the unwanted actions of the clients in the network.

Servers or network administrators are enhanced only with monitoring the operations made by the clients and if needed to control them, they need to make a separate manual process that means reaching them to control their activities. It requires more efforts and also its cost expensive. It may need several softwares in engaging both the operations in a network. Manual procedures may lead to several failures in control.

3.1.1 Disadvantages in Existing system

← It requires more efforts ← It is also cost expensive ← More infrastructure. ← It may need several softwares in engaging both the operations in a network. ← Manual procedures may lead to several failures in control.

3.2 Proposed system Most organizations need an eye on their employees work to fulfill their goals. Thus RMC approach is used here for making a real-time monitoring of their employees and makes them work properly by controlling them without any physical access. RMC plays the main role in capturing the employee’s screen and displaying it in the administrator’s system. Administrator also allows the employees present in the list to be logged into their network. RMC helps in terminating the programs that are running improperly in their client system. Organizations goals are to be succeeded with a necessary procedural works by the employees but if it is out of service in monitor and controlled by the administrator acting as a server. Employee’s system could be turned on only when it is registered in the employee’s list at the time of connection orientation. Without the presence of the administrator in an organization, systems are not allowed to be accessed by the clients. Client Systems are monitored through their IP address. While a client enters a network, it is enhanced with a name and an IP address to be registered in the server. Monitoring is efficient in all organizations for maintaining records about the clients entering and exiting their network. Various events are monitored such as system information, usage of memory, capturing desktop activities and tasks running under clients. Monitoring a client can be a security operation prevailed over a network to keep a reliable flow of information between client and server. Clients may enroll their IP with the server for communication purpose but administrator takes rights on clients to make a security service. RM ensures a current state monitoring system which provides a facility of maintaining actions of the clients within the network circle. Clients may work against the organization and make them to collapse the goal they fixed for the yearly needs. But RM systems are used in their organization to make them secure by monitoring those clients and make their motto to be diminished.

3.2.1 Advantages ← Net view: Get on your screen, the list of entire client’s in LAN. Keep pinging every time to check the latest status of the PC’s. ← Process view: Get the details of all processes running on the client’s machine, by viewing the static image of the client’s desktop. ← Cost efficient. ← Less infrastructure. ← Organisations working with RMC can be familiar in securing a constant network connection.. ← A network administrator can work easily with this approach by organising the network connection in a single software approach proposed ← Enabling RMC reduces extra burden of purchasing two or more softwares for monitoring and controlling the network. ← Here server can identify a network traffic easily by monitoring each clients working in a network and can control them with some system commands. ← GUI based architecture is also used to enhance a live stream of capturing the activities done in the desktops of the clients present in a network

3.3 SOFTWARE REQUIREMENT SPECIFICATION:

3.3.1 FUNCTIONAL REQUIREMENTS:

The functional requirement is describing the behavior of the system as it relates to the system's functionality. The Functional Requirements Specification describes what the system must do; how the system does it is described in the Design Specification. This system provides

➢ Authentication: It provides higher security to the user by having thier IP address and port number.

➢ Security: It provides the security mechanism by validating the IP address and port number

3.3.2 NON-FUNCTIONAL REQUIREMENTS:

The non- functional requirements elaborates the performance characteristic of the system. This system provides

➢ Efficiency: It is efficient because both monitoring and controlling can be done at same time.

➢ Reliability: It performs consistently according to its specifications.

➢ Scalability: It is able to handle a growing amount of work and to accommodate that growth.

➢ Extensibility: It also supports for the future growth. We can also add additional modules if required in future.

3.3.3 Software and Hardware requirements:

Requirement Specification plays an important role to create quality software solution; Requirements are refined and analyzed to assess the clarity.

Requirements are represented in a manner that ultimately leads to successful software implementation. Each requirement must be consistent with the overall objective. The development of this project deals with the following requirements:

• Hardware Requirements • Software Requirements

Software requirements: The software requirements specification is produces at the culmination of the analysis tasks. One of the most difficult tasks is that, the selection of the software, once system requirement is known by determining whether a particular software package fits the requirements.
Software Requirements for present project:
|Operating system |Windows 7,Windows 8,Windows XP |
|Technologies |WPF with C#.NET, XAML |
|IDE |MS-Visual Studio.Net |

Hardware requirements: The selection of hardware is very important in the existence and proper working of any software. In the selection of hardware, the size and the capacity requirements are also important.
Hardware Requirements:
|Hard Disk |20 GB(Min) |
|RAM |1 GB(Min) |

3.4 Feasibility Study

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

• Technical Feasibility • Operation Feasibility • Economical Feasibility

3.4.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the following:

• Does the necessary technology exist to do what is suggested? • Do the proposed equipments have the technical capacity to hold the data required to use the new system? • Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? • Can the system be upgraded if developed? • Are there technical guarantees of accuracy, reliability, ease of access and data security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.

3.4.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -

• Is there sufficient support for the management from the users? • Will the system be used and work properly if it is being developed and implemented? • Will there be any resistance from the user that will undermine the possible application benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

3.4.3. Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain.

SYSTEM DESIGN

4. SYSTEM DESIGN

System design is the process or art of defining the architecture, components, modules, interfaces, and data for a system to satisfy specified requirements. One could see it as the application of system theory to product development. There is some overlap with the disciplines of the system analysis, system architecture and system engineering if the broader topic of product development “Blends the perspective of marketing, design and manufacturing into a single approach to product development, then design is the act of taking marketing information and creating the design of the product to be manufactured. System design is therefore the process of defining and developing systems to satisfies specified requirements of the user. Until the 1990’s system design had a crucial and respected role in the data processing industry. In the 1990’s standardization of hardware and software resulted in the ability to build modular systems. The increasing importance of software running on generic platforms has enhanced the discipline of software engineering. Object oriented analysis and design methods are becoming the most widely used methods for computer system design. The UML has become the standard language used in object oriented analysis and design. It is widely used for modeling software systems and is increasing used for high designing non software systems and organizations.
Architectural design: The architectural design of a system emphasizes on the design of the systems architecture which describes the structure, behavior, and more views of that system and analysis. Logical design : The logical design of a system pertains to an abstract representation of the data flows, inputs and outputs of the system. This is often conducted via modeling, using an overabstract (and sometimes graphical) model of the actual system. In the context of systems design are included. Logical design includes ER Diagrams i.e. Entity Relationship Diagrams.
Physical design: The physical design relates to the actual input and output processes of the system. This is laid down in terms of how data is input into a system, how it is verified, authenticated, how it is processed, and how it is displayed as in Physical desig
4.1 ARCHITECTURAL FLOW:

[pic]

4.2 UML DIAGRAMS:

INTRODUCTION TO UML:

The Unified Modeling Language (UML) is a standard language for writing software blueprints. The UML is a language for - Visualizing - Specifying - Constructing - Documenting the artifacts of a software-intensive system. The UML is appropriate for modeling systems ranging from enterprise information systems to distributed Web-based applications and even to hard real time embedded systems.

IMPORTANCE OF MODELING: 1) If we want to build a dog house, with a little planning, we’ll likely end up with a dog house that’s reasonably functional and we can do it with no one’s help. 2) If we want to build a house for a family, it’s going to take a lot longer. In this case we need some detailed planning; we’ll need to draw some blueprints, before we lay the foundation. 3) If we want to build a high-rise office building, we’ll have to do extensive planning; and we need all sorts of blueprints and models to communicate with one another.

PRINCIPLES OF MODELING: Four basic principles of modeling are • The choice of what models to create has a profound influence on how a Problem is attacked and how a solution is shaped. • Every model may be expressed at different levels of precision. • The best models are connected to reality. • No single model is sufficient.

UML DIAGRAMS:

UML diagrams can be classified into two types: • Structural Diagrams • Behavioral Diagrams

➢ Structural Diagrams: These are of four types • Class Diagram • Object Diagram • Component Diagram • Deployment Diagram

➢ Behavioral Diagrams: These are classified into 5 types • Use Case Diagram • Sequence Diagram • Collaboration Diagram • State Chart Diagram • Activity Diagram

4.2.1 RELATIONSHIPS IN UML: There are 4 kinds of Relationships in the UML:

Dependency:

Dependency is a relationship between two things in which a change to one thing (Independent thing) may affect the other thing (Dependent thing). It is denoted by dashed line with an arrow.

➢ Association: Association is a structural relationship that describes a set of links, a link being a connection among objects. Aggregation is a special kind of association, representing a structural relationship between a whole and its parts. It is denoted by a solid line.

➢ Generalization: Generalization is a relationship in which the child will share the behavior of the parent. It is denoted by a solid line with a hollow arrow head pointing to the parent.

➢ Realization: Realization is a relationship between classifiers, where one classifier specifies a contract that another classifier guarantees to carry out. It is denoted by dashed lines with a hollow arrow head.

4.2.2 USE CASE DIAGRAM: A Use Case diagram shows a set of use cases and actors and their relationships.

• Use Case: Scenarios of the system. • Actor: Someone or something who is interacting with the system. • Relationship: Semantic link between use case and actor.

[pic] Fig 4.2.2 Use Case Diagram

4.2.3 CLASS DIAGRAM: A Class diagram shows a set of classes, interfaces, and collaborations and their relationships. A class consists of class name, attributes, operations and responsibilities. The components are: • Class • Relationships

[pic] Fig 4.2.3 Class Diagram

Object Diagram
[pic]
4.2.3.1 object diagram INTERACTION DIAGRAM: An interaction diagram models the dynamic aspects of the system by showing the relationship among the objects and messages they may dispatch. There are two types of interaction diagrams: ➢ Sequence Diagram ➢ Collaboration Diagram

4.2.4 Sequence Diagram: A Sequence diagram is an interaction diagram that emphasizes the time-ordering of messages. The components are: • Actor • Object • Messages • Lifeline • Focus of Control

[pic]

Fig 4.2.4 Sequence Diagram

4.2.5 Collaboration Diagram: A Collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages. The components are: • Actor • Object • Link

[pic] Fig 4.2.5 Collaboration Diagram

4. 2.6 ACTIVITY DIAGRAM:

An activity diagram is a special kind of state chart diagram that shows the flow from activity to activity within a system, which are connected by a trigger less transition. The components are: • Start State

• End State

• Transition

• Decision Box

• Synchronization Bar

• Swim Lane

[pic] Fig 4.2.6 Activity Diagram

4.2.7 STATE CHART DIAGRAM: A State chart diagram shows a state machine, consisting of states, transitions, events, and activities. The components are: • Start State • End State • State • Transition

[pic] Fig 4.2.7 State Chart Diagram

4.2.8 COMPONENT DIAGRAM: Component is a physical replaceable part of the system. A Component diagram shows the organizations and dependencies among a set of components. The components are: • Component • Dependency • Interface

[pic] Fig 4.2.8 Component Diagram

4.2.9 DEPLOYMENT DIAGRAM: A Deployment diagram shows the configuration of run-time processing nodes and the components that are present in them.

[pic] Fig 4.2.9 Deployment Diagram

SYSTEM IMPLEMENTATION
5. SYSTEM IMPLEMENTATION

Introduction
System implementation is the development, installation and testing of system components and delivery of that system into production (Bentley et. al., 2007). The purpose of system implementation is to build a system, install it, replace and old systems, preparing system and user documentation and train users. During this phase, it’s also involved closedown the entire project.

System implementation has several major activities. There are five major tasks in this phase; coding, testing, installation, documentation and training as in Figure 12-1. The purpose of this phase is to convert the physical system specifications into working and reliable software and hardware, document the work that have been done and provide help for current and future users.

[pic] Figure 12-1: Five Activities in the System Implementation Phase

5.1 Technologies

Introduction to .NET Framework

The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

• To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. • To provide a code-execution environment that minimizes software deployment and versioning conflicts. • To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party. • To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments. • To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. • To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and Remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by WPF.NET, such as Desktop Applications and XAML Web services.
WPF (Windows Presentation Foundation)

Windows Presentation Foundation (or WPF) is a graphical subsystem for rendering user interfaces in Windows-based applications by Microsoft. WPF, previously known as "Avalon", was initially released as part of .NET Framework 3.0. Rather than relying on the older GDI subsystem, WPF uses DirectX. WPF attempts to provide a consistent programming model for building applications and separates the user interface from business logic. It resembles similar XML-oriented object models, such as those implemented in XUL and SVG.

WPF employs XAML, an XML-based language, to define and link various interface elements.[1] WPF applications can also be deployed as standalone desktop programs, or hosted as an embedded object in a website. WPF aims to unify a number of common user interface elements, such as 2D/3D rendering, fixed and adaptive documents, typography, vector graphics, runtime animation, and pre-rendered media. These elements can then be linked and manipulated based on various events, user interactions, and data bindings.

Windows Presentation Foundation (WPF) is a means for the programmer to create Windows applications possessing rich user interfaces and graphics which the classic .NET Windows applications lack.

1. Declarative Programming

WPF application paves the way for the developers to define the thick client UI in a declarative way, which was never supported by the traditional .NET windows forms. Tasks like defining a template for a control, creating a control hierarchy and similar work would be much easier if it is done in a declarative fashion. In WPF declarative programming was made possible with the introduction of Extensible Application Markup Language (XAML). It can be compared to the HTML part in a web user interface.
Below is the sample XAML code in a WPF Window.

2. Independent of Screen Resolution

This is a neat feature of WPF. What I mean by independency of screen resolution is, the WPF user interface will look better even on a screen with low resolution. It uses DirectX components where as the Windows Forms applications make use of the User 32 components of a machine. WPF framework has the Media Integration Layer (MIL) in order to talk to the DirectX components. The direct components impose a vector based graphics on the WPF user interface. The below screen shot will show you the difference between the Windows forms UI and WPF UI at lower resolutions of the screen.

3. Control inside a Control

WPF allows you to provide not only the text but it also allows you to define a control as a content of another basic control like a Button. This feature is truly astonishing fact for the developers and this lets the world know, what the power of WPF is when it comes to user interfaces.

4. Control Templates

What if the user wants to change the shape of a button, this will definitely sound weird for .NET developers. Now it can be done in WPF by defining the control template. For example you can declare a Button on your WPF window and can change its shape to elliptical.

5. Control Transforms

WPF contains a handful of 2D transforms which will enable you to change the size, position, rotation angle and also allows skewing. Control transforms can be performed in two ways Layout Transform and Render Transform.
• Layout Transform - Transform is applied before the control is laid out on the form
• Render Transform - Transform is applied after the control is laid on the form
There are 5 kinds of transforms available

1. Rotate Transform - It will rotate the controls to a specified angle 2. Scale Transform - It enlarges or shrinks the controls in x and y axis 3. Skew Transform - It slants the control 4. Translate Transform - It moves the control based on x and y values 5. Matrix Transform - It combines all the above transforms
Layouts are used in separating the controls on the UI logically and also enable you to present them neat on the window. WPF provides you a wide and powerful set of layout controls. Some of the main layouts in WPF are:

Stack Panel:

A stack panel lays the child controls inside them either horizontally or vertically based on the specified Orientation. It is very much useful for managing small scale aspects of the layout.

Wrap Panel:

A Wrap panel lays the child controls from left to right and as the name suggests it goes to the new line once it fills up the container width.

Dock Panel:

A Dock panel docks the child control either to Top, Bottom, Right or to Left based on the Dock type specified. This provides you with the docking functionality which you get in Windows Forms Applications.

Grid:

A Grid layout allows you to create a table like structure on the WPF window, it has rows and columns. It enables the user to place the controls in the desired cell of the grid layout.

Canvas:

A Canvas layout allows you to place the controls as you desire. It allows you to take complete control of the layout process.

7. 2D, 3D Graphics, animations and media

This is a vast topic in WPF, in my opinion these features make WPF a much more unique technology which mixes both controls and graphics to be tightly coupled. I will be touching some key features under this topic.

XAML (Extensible Application Markup Language) XAML is a declarative markup language. As applied to the .NET Framework programming model, XAML simplifies creating a UI for a .NET Framework application. You can create visible UI elements in the declarative XAML markup, and then separate the UI definition from the run-time logic by using code-behind files, joined to the markup through partial class definitions. XAML directly represents the instantiation of objects in a specific set of backing types defined in assemblies. This is unlike most other markup languages, which are typically an interpreted language without such a direct tie to a backing type system. XAML enables a workflow where separate parties can work on the UI and the logic of an application, using potentially different tools.

Introduction to C#

C#, pronounced c sharp, is a computer language used to give instructions that tell the computer what to do, how to do it, and when to do it. This is a universal language that is used on many operating systems, including Microsoft Windows. C# is one of the languages used in the Microsoft .NET Framework. The Microsoft .NET Framework is a library of objects that create or draw things on the computer.

The programs we will write are meant to give instructions to the computer about what to do, when to do something, and how to do it. You write these instructions in an easy to understand English format, using words we will study. This means that a regular instruction uses normal text with alphabetic characters, numbers, and non-readable symbols. Normally, you can write your instructions using any text editor such as Notepad, WordPad, WordPerfect, or Microsoft Word, etc. When writing your instructions, there are rules your must follow and suggestions you should observe..

The group of instructions used by your program is also referred to as code. To assist you with writing code, Microsoft Visual C# 2008 includes a text editor referred to as the Code Editor. This is the window that displays when you have just created a console application. Besides the Code Editor, the integrated development interface(IDE) of the Microsoft Visual C# 2008 is made of various parts, which we will review when necessary.

Features of C#

Some notable features of C# that distinguish it from C and C++ (and Java, where noted) are:

• Portability

By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or FORTRAN.

• Typing

C# supports strongly typed implicit variable declarations with the keyword var, and implicitly typed arrays with the keyword new followed by a collection initializer.

C# supports a strict Boolean data type, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the Boolean type. While C++ also has a Boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach, on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of programming mistakes common in C or C++ such as if (a = b) (use of assignment = instead of equality ==).

C# is more type safe than C++. The only implicit conversions by default are those that are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. No implicit conversions occur between Booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default.

C# has explicit support for covariance and contra variance in generic types, unlike C++ which has some degree of support for contra variance simply through the semantics of return types on virtual methods.

Enumeration members are placed in their own scope.

The C# language does not allow for global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++.

• Meta programming

Meta programming via C# attributes is part of the language. Many of these attributes duplicate the functionality of GCC's and Visual C++'s platform-dependent preprocessor directives.

• Methods and functions

Like C++, and unlike Java, C# programmers must use the keyword virtual to allow methods to be overridden by subclasses.

Extension methods in C# allow programmers to use static methods as if they were methods from a class's method table, allowing programmers to add methods to an object that they feel should exist on that object and its derivatives.

The type dynamic allows for run-time method binding, allowing for JavaScript-like method calls and run-time object composition.

C# has support for strongly-typed function pointers via the keyword delegate. Like the Qt framework's pseudo-C++ signal and slot, C# has semantics specifically surrounding publish-subscribe style events, though C# uses delegates to do so.

C# offers Java-like synchronized method calls, via the attribute and has support for mutually-exclusive locks via the keyword lock.

• Property

C# provides properties as syntactic sugar for a common pattern in which a pair of methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class. No redundant method signatures for the getter/setter implementations need be written, and the property may be accessed using attribute syntax rather than more verbose method calls.

• Namespace

A C# namespace provides the same level of code isolation as a Java package or a C++ namespace, with very similar rules and features to a package.

• Memory access

In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one that has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the System. IntPtr type, but it cannot dereference them.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory that is no longer needed.

• Exception

Checked exceptions are not present in C# (in contrast to Java). This has been a conscious decision based on the issues of scalability and version ability.

• Polymorphism

Unlike C++, multiple inheritance is not supported by C#, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI. When implementing multiple interfaces that contain a method with the same signature, C# allows the programmer to implement each method depending on which interface that method is being called through, or, like Java, allows the programmer to implement the method once and have that be the single invocation on a call through any of the class's interfaces.

However, C#, unlike Java, supports operator overloading. Only the most commonly overloaded operators in C++ may be overloaded in C#.

• Functional programming

Though primarily an imperative language, C# 2.0 offered limited support for functional programming through first-class functions and closures in the form of anonymous delegates. C# 3.0 expanded support for functional programming with the introduction of a light weight syntax for lambda expressions, extension methods (an affordance for modules), and a list comprehension syntax in the form of a "query comprehension" language.

5.2 IMPLEMENTATION:

Implementation is the carrying out, execution, or practice of a plan, a method, or any design for doing something. Implementation is the action that must follow any preliminary thinking in order for something to actually happen.

5.2.1 Algorithm

Client Algorithm

1) Create client socket with address family->Inter network, socket type.
2) Take IP address and port number and server IP from input.
3) Bind the client socket with corresponding IP address and port number.
4) To connect to the server by using server end point.
5) Wait for accept.
6) If server is accept your client connection then go to step (7) otherwise go to step (18).
7) Take a screen shot from client desktop and save to buffer.
8) To send that byte array to server.
9) Wait for acknowledgement.
10) If server gives the acknowledgement then go to step (11) otherwise (17).
11) Client socket take the buffer to byte array from server.
12) Convert the byte array to string format.
13) Checks the string contains lock coin or not.
14) If string contain lock coin go to (15) Otherwise (16).
15) Lock the system.
16) Go to step (7).
17) Wait for network time.
18) Close the server socket connection.
19)Close the client socket.

Server Algorithm

1) Create server socket with address family->inter networking, socket type->stream, protocol type->TCP.
2) Take the server IP port number from input.
3) Bind the server socket with IP address and port number.
4) Listen the server socket that is waiting for incoming connection.
5) If client connection comes go to step (6) otherwise go to (4).
6) Accept the client.
7) Begin receiving the buffer from client connection.
8) Transform the byte array to image.
9) Show the image on server application.
10) If you want to lock the client then go to (13) otherwise go to (14).
11) String lock win convert to a byte array and that byte array is transfer to the client socket.
12) Received byte array from client, that byte array is transferred to the client.
13) Repeat the steps (9) to (15).
14) Close the client socket.
15)Close the Server socket.

5.3 CODING
Client side
MainWindow.xaml

MainWindow.xaml.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Windows; using System.Windows.Controls; using System.Windows.Data; using System.Windows.Documents; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Imaging; using System.Windows.Navigation; using System.Windows.Shapes; using System.Net.Sockets; using System.Net; using System.Threading; using System.Drawing; using System.Drawing.Imaging; using System.Windows.Interop; using System.IO; using System.Runtime.InteropServices; namespace Clientimage
{
/// /// Interaction logic for MainWindow.xaml /// public partial class MainWindow : Window { [DllImport("user32")] public static extern void LockWorkStation(); Socket Clientsocket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); byte[] bby = new byte[1000000]; public MainWindow() { InitializeComponent(); }

private void button1_Click(object sender, RoutedEventArgs e) { // LockWorkStation(); connectserver();

startcli(); }

private void connectserver() { //throw new NotImplementedException(); try { IPAddress ip = IPAddress.Parse(clientip.Text); IPEndPoint ipend = new IPEndPoint(ip, Convert.ToInt32(Clientport.Text)); Clientsocket.Bind(ipend); IPEndPoint ipendser = new IPEndPoint(IPAddress.Parse(Serverip.Text), Convert.ToInt32(Clientport.Text)); Clientsocket.Connect(ipendser); button1.Content = "Conected"; //Thread t = new Thread(new ThreadStart(startcli)); // t.Start(); } catch (Exception ex) { MessageBox.Show("the problem having connection"); } } void startcli() {

// System.Windows.Controls.Image i = new System.Windows.Controls.Image();

BitmapSource bitmapSource = CopyScreen();

JpegBitmapEncoder encoder = new JpegBitmapEncoder(); MemoryStream memoryStream = new MemoryStream(); BitmapImage bImg = new BitmapImage();

encoder.Frames.Add(BitmapFrame.Create(bitmapSource)); encoder.Save(memoryStream);

bImg.BeginInit(); bImg.StreamSource = new MemoryStream(memoryStream.ToArray()); bImg.EndInit();

bImg.Freeze(); if (imagepic.Dispatcher.CheckAccess()) { imagepic.Source = bImg; } else { Action act = () => { imagepic.Source = bImg; }; imagepic.Dispatcher.BeginInvoke(act); } byte[] by = memoryStream.ToArray(); memoryStream.Close();

// Clientsocket.Send(by);

Clientsocket.BeginSend(by, 0, by.Length, 0, new AsyncCallback(onsend), Clientsocket); } void onsend(IAsyncResult ar) {

Clientsocket.BeginReceive(bby, 0, bby.Length, 0, new AsyncCallback(onreceive), Clientsocket); } void onreceive(IAsyncResult ar) { string ss = System.Text.ASCIIEncoding.UTF8.GetString(bby); if (ss.Contains("lockwin")) { LockWorkStation(); Clientsocket.Close(); } Thread.Sleep(500); startcli(); } private static BitmapSource CopyScreen()

{

using (Bitmap screenBmp = new Bitmap(

(int)SystemParameters.VirtualScreenWidth,

(int)SystemParameters.VirtualScreenHeight,

System.Drawing.Imaging.PixelFormat.Format32bppArgb))

{

using (var bmpGraphics = Graphics.FromImage(screenBmp))

{

bmpGraphics.CopyFromScreen(0, 0, 0, 0, screenBmp.Size);

return Imaging.CreateBitmapSourceFromHBitmap(

screenBmp.GetHbitmap(),

IntPtr.Zero,

Int32Rect.Empty,

BitmapSizeOptions.FromEmptyOptions());

}

}

}

}
}

Server side
MainWindow.xaml

MainWindow.xaml.cs using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Windows; using System.Windows.Controls; using System.Windows.Data; using System.Windows.Documents; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Imaging; using System.Windows.Navigation; using System.Windows.Shapes; using System.Net; using System.Net.Sockets; using System.Threading; using System.IO; using System.Drawing; using System.Windows.Interop;
//using System.Windows.Forms;
//using System.Drawing; namespace ServerImage
{
/// /// Interaction logic for MainWindow.xaml /// public partial class MainWindow : Window { // List clientlist = new List(); public delegate void UpdateImage(BitmapImage bg); List bilist = new List(); Socket serversocket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); Socket clintsoc,cli; int i = 0; int locki=0; byte[] bb = new byte[1000000]; BitmapImage bbbg = new BitmapImage(); public MainWindow() { InitializeComponent();

}

private void button1_Click(object sender, RoutedEventArgs e) { button1.Content = "Start server"; stariningserver();

}

private void stariningserver() { // throw new NotImplementedException(); IPAddress ip = IPAddress.Parse(Serverip.Text); IPEndPoint ipend = new IPEndPoint(ip, Convert.ToInt32(serverport.Text)); serversocket.Bind(ipend); serversocket.Listen(10); serversocket.BeginAccept(ascalback, serversocket); }

private void ascalback(IAsyncResult ar) { Socket lis = (Socket)ar.AsyncState; clintsoc = lis.EndAccept(ar);

cli = (Socket)clintsoc; cli.BeginReceive(bb, 0, bb.Length, 0, new AsyncCallback(onrecive), cli);

}

void onrecive(IAsyncResult ar) { try { if (locki == 0) { Thread.Sleep(500); BitmapImage blg = new BitmapImage(); blg.BeginInit(); blg.StreamSource = new MemoryStream(bb); blg.EndInit(); blg.Freeze(); if (image1.Dispatcher.CheckAccess()) { image1.Source = blg; } else { Action act = () => { image1.Source = blg; }; image1.Dispatcher.BeginInvoke(act); } // image1.Source = blg; //bilist.Add(blg); cli.BeginSend(bb, 0, bb.Length, 0, new AsyncCallback(onsend), cli); } else { string s = "lockwin";

byte[] bbb = Encoding.ASCII.GetBytes(s); cli.BeginSend(bbb, 0, bbb.Length, 0, new AsyncCallback(onsend), cli); } } catch (Exception ex) { MessageBox.Show("erro" + ex.ToString()); }

} void onsend(IAsyncResult ar) {

cli.BeginReceive(bb, 0, bb.Length, 0, new AsyncCallback(onrecive), cli); }

private void button2_Click(object sender, RoutedEventArgs e) { locki = 1; } }}

SYSTEM TESTING

6. SYSTEM TESTING

System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software components that have passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together or between any of the assemblages and the hardware. System testing is a more limited type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

6.1 TESTING OBJECTIVE: Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing also provides objective, independent view of the software to allow the business to appreciate and understand the risk at the implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. Software testing can also be stated as the process of validating and verifying that a software program/application/product: 1.meets the technical requirements that guided its design and development; 2. Works as excepted; and 3. Can be implemented with the same characteristics. Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development models will focus the test effort at different points in the development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team o testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed. Testing can never completely identify all the defects within software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against oracles-principles or mechanism by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts, comparable products, past versions of the same product, inferences about intended or excepted purpose, user or customer expectations, relevant standards, applicable laws, or other criteria. Every software product has a target audience, For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, Its target audience, its purchasers, and other stake holders. Software testing is the process of attempting to make this assessment. A study conducted by NIST in 2002 reports that software bugs cost the U.S economy $59.5 billion annually. More than a third of this cost could be avoided its better software testing was performed.

6.2 TEST CASE DESIGN:
The Box Approach
Software testing methods are traditionally divided into white-box and black-box testing. these two approaches are use to descried the point of view that a test engineer takes when designing test cases.

6.2.1 White Box Testing

White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these. . Types of white box testing The following types of white box testing exist:

• API testing(application programming interface)- testing of the application using public and private APIs *Code coverage-creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once)

• Fault injection methods –improving the coverage of a test by introducing faults to test code paths * Mutation testing methods

• Static testing – White box testing includes all static testing Test coverage White box testing suite that was created with the black box testing methods, this allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested.

Two common forms of code coverage are: • Function coverage, which reports on functions executed

• Statement coverage, which reports on the number of lines executed to complete the test

2. Black Box Testing

Black box testing treats the software as a “black box”-without any knowledge of internal implementation, Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing aims to test the functionality of software according to the applicable requirements. Thus, the tester inputs data into, and only sees the output from, the test object .this level of testing usually requires thorough the test cases to be provide to the tester, who then can simply verify that for a given input, the output value, either ”is” or “is not” the same as the excepted value specified to guard against certain risks. Advantages and Disadvantages: The black box tester has no “bonds” with the code, and a tester’s perception is very simple: a code must have bugs. Using the principle, “Ask and you shall receive,” black box testers find bugs where programmers do not. But, on the hand, black box testing has been said to be “like a walk in a dark labyrinth without flashlight,” because the tester doesn’t know how the software being tested was actually constructed.

6.3 TESTING STRATERGY:
6.3.1 Unit Testing Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and minimum unit tests include the constructors and destructors These type of tests are usually written by developers as they work on code(white –box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code . unit testing alone cannot verify the functionality of piece of software uses work independently of each other.

Unit testing is also called component testing.

6.3.2 Integration Testing Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together (“big bang”). Normally the former is considered a better practice since it allows interface issues to be localized more quickly and fixed. Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software as a system. • System testing System testing tests a completely integrated system to verify that it meets its requirements.

• System integration testing system integration testing verifies that a system is integrated to any external or third party systems defined in the system requirements.

• Regression testing Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, or old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release process and risk of the added features. They can either to complete, for changes added late in the release or deemed to be risky, to very shallow, consisting of positive tests on each feature ,if the changes are early in the release or deemed to be of low risk.

6.3.3 System Testing

System testing tests a completely integrated system to verify that it meets its requirements. System testing falls under the black box testing category of software testing. System testing involves the external workings of the software from the user's perspective.

System testing involves testing the software code for following

• Testing the fully integrated applications including external peripherals in order to check how components interact with one another and with the system as a whole. This is also called End to End scenario testing.
• Verify thorough testing of every input in the application to check for desired outputs.
• Testing of the user's experience with the application.

Types of System Testing

There are more than 50 types of System Testing. Below we have listed types of system testing a large software development company would typically use

1. Usability Testing - Usability testing mainly focuses on the user's ease to use the application, flexibility in handling controls and ability of the system to meet its objectives
2. Load Testing - Load testing is necessary to know that a software solution will perform under real life loads.
3. Regression Testing - Regression testing involves testing done to make sure none of the changes made over the course of the development process have caused new bugs. It also makes sure no old bugs appear from the addition of new software modules over time.
4. Recovery Testing - Recovery testing is done to demonstrate a software solution is reliable, trustworthy and can successfully recoup from possible crashes.
5. Migration Testing - Migration testing is done to ensure that the software can be moved from older system infrastructures to current system infrastructures without any issues.
6. Functional Testing - Also known as functional completeness testing, functional testing involves trying to think of any possible missing functions. Testers might make a list of additional functionalities that a product could have to improve it during functional testing.
7. Hardware/Software Testing - IBM refers to Hardware/Software testing as "HW/SW Testing". This is when the tester focuses his/her attention on the interactions between the hardware and software during system testing.

What Types of System Testing Should Testers Use?

There are over 50 different types of system testing. The specific types used by a tester depend on several variables. Those variables include:

• Who the tester works for - This is a major factor in determining the types of system testing a tester will use. Methods used by large companies are different than that used by medium and small companies.
• Time available for testing - Ultimately, all 50 testing types could be used. Time is often what limits us to using only the types that are most relevant for the software project.
• Resources available to the tester - Of course some testers will not have necessary resources to conduct a testing type. For example if you are a tester working for a large software development firm, you are likely to have expensive automated testing software not available to others.
• Software Tester's Education - There is a certain learning curve for each type of software testing available. To use some of the software involved, a tester has to learn how to use it.
• Testing Budget - Money becomes a factor not just for smaller companies and individual software developers but large companies as well.

6.3.4 Acceptance Testing Acceptance testing can mean one of two things: • A smoke test is used as an acceptance test prior to introducing a new build to the main testing process that is before integration or regression.

• Acceptance testing performed by the customer, often in their lab environment on their own hardware, is known as user acceptance testing .Acceptance testing may be performed as part of the hand-off process between any two phases of development.

• 6.3.4.1 Alpha testing

Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team as the developers site .Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing. Van veenendaal Erik, ”Standard glossary of terms used in software Testing”. 6.3.4.2 Beta testing

Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.

6.4 TEST CASES AND RESULTS
|Test No |Testing |Test |Input |Expected |Actual output |Result |
| | |case | |output | | |
|1 |Connecting to |Invalid clientIP|Client IP: |Error |The problem having|passed |
| |server at client |address and port|192.168.3.183 |message |the connection | |
| |side |number |Port number: | | | |
| | | |8050 | | | |
|2 |Connecting to |Invalid server |Server IP: |Error |The problem having|passed |
| |server at client |IP address |192.168.3.183 |message |the connection | |
| |side | | | | | |
|3 |Starting the server|Invalid ServerIP|Server IP: |Error |error |passed |
| |at server side |address and port|192.168.3.186 |message | | |
| | |number |Port number: | | | |
| | | |8050 | | | |
|4 |Connecting to |Valid IP address|All valid details |Connects to server |connects |passed |
| |server at client |and port number | | | | |
| |side | | | | | |
|5 |Starting the server|valid ServerIP |All valid details |Starts server |Getting screen |passed |
| |at server side |address and port| | |shots | |
| | |number | | | | |

SCREENSHOTS

[pic]
Client giving the IP address of server and client and port number for connecting to server

[pic]
Server giving IP address and port number for starting the server

[pic]Screen shots of client actions at server

[pic]

Client actions

[pic]Screen shots of client actions at server

[pic]
To control client actions Server lock the client screen

[pic]
Client screen gets locked

CONCLUSION 8. CONCLUSION

Our project “GUI Based Real Time Monitoring and Controlling Approach on Networking” has been successfully completed. The entire project has been developed and deployed as per the requirements. It is found to be bug free as per the testing standards that are implemented. The application is designed to provide security and user friendly interface.

This application will help the user to increase the security of user account as well as helps the server to monitor control the client actions.

FURTHER SCOPE OF DEVELOPMENT

9. FURTHER SCOPE OF DEVELOPMENT

We can also integrate more than one client actions when we use same ip addresss with same wi-fi connections to client&the server.server can detect every client action & takes a screen shots. we can even develop a database in this client server-model.

BIBLOGRAPHY 10.BIBLOGRAPHY
Books referred:
( C# 5.0 in a Nutshell: The Definitive Reference.
( CLR via C# by Jeffrey Richter.
( C# 5.0 Pocket Reference: Instant Help for C# 5.0 Programmers by Joseph Albahari, Ben Albahari
( Head First C#, 2E: A Learner‟s Guide to Real-World Programming with Visual C# and .NET by Andrew Stellman, Jennifer Greene.

Websites Referred:
( http://www.visualstudio.com
( http://ijcaonline.org/archives/volume12/number9/1713-2295 ( http://www.ijircce.com/upload/2013/april/41_Integration_H.pdf
( http://ijsrm.in/v1-i4/2%20ijsrm.pdf
( http://www.ijsrp.org/research-paper-0713/ijsrp-p1904.pdf
( http://www.ijcsmc.com/docs/papers/November2014/V3I11201495.pdf
( http://www.ijettjournal.org/volume-9/number-10/IJETT-V9P298.pdf ( http://www.microsoft.com
( http://www.youtube.com
( http://en.wikipedia.org/wiki

-----------------------
System
Analysis

System
Planning

√ Coding
√ Testing
√ Installation
√ Documentation
√ Training

System
Maintenance

System
Implementation

System
Design