techshristi.com€¦ · web viewas c# developers, we now understand that our c# code will be...

.Net IEEE Project

ABSTRACT

Project Title: A Survey on Cryptography Algorithms in Security of Voting System Approaches J ournal: IEEE Computer Science ISBN: 978-0-7695-3243-1

I ntroduction: There are three general classes of cryptographic voting protocols: those based on blind signatures, those based on mix-nets, and using homomorphism encryption. Historically, cryptographic research has focused on proving that the tally is the sum of all the ballots, and that the contents of individual ballots remain secret.

Cryptographic voting research considered the voter and the polling booth to be one entity. Voter’s final ballot must be secret and she cannot prove the contents of her final ballot to anyone. In the other way, voter needs ability to verify that their votes are cast and counted as intended. Survey on kinds of cryptography methods and voter verified in voting systems for better comprehension and different of them are goals of this article.

Survey of cryptography variety methods on security of Voting, beside of

voter-verified helps to find new ways in selecting models. And with these models except of increasing of voting safety assure to voter about system honesty.

ENVIRONMENT: Servers: Operating System Server: Windows XP or later Tools: Microsoft Visual Studio .Net-2005 (2.0) Code Behind: C#.Net Hardware Specification:

Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB

.Net IEEE Project

ABSTRACT








ABSTRACT

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








A LAN communicator application is developed that will

facilitate secure chatting and file sharing over the network. This Secure LAN

.Net IEEE Project

ABSTRACT








Communicator consists of two Modules, Server Module and Client Module. Server

module will keep record of all the users, their login name, passwords. It will listen

to Clients requests. Client module from other computer will first connect to the

Server by providing user name and password. If client is authenticated the Server

will send back list of all of the users that are online or offline. Client will select any

.Net IEEE Project

ABSTRACT








of the online users to chat with or any of the offline users to send him/her an

offline messages. All message sent will first go to the Server and then server will

send that message to the destination client.

The LAN Chat creates only one chat room that is why it has very clear

interface. The LAN Chat's interface is one window with list of chat participants,

.Net IEEE Project

ABSTRACT








chat messages and outgoing message. And you can also set to your status online,

away or disconnected in this window.

After the user type’s text into the input region and hits Return,

the text is transmitted to the server. The server echoes back everything that is sent

.Net IEEE Project

ABSTRACT








by the client. The client displays everything received from the server in the output

region. When multiple clients connect to one server, we have a simple chat system.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Preface

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Table of Contents

S.NO TOPIC PAGE NO

1 INTRODUCTION

1.1 INTRODUCTION TO PROJECT

.Net IEEE Project

ABSTRACT








2

1.2 ORGANIZATION PROFILE

SYSTEM STUDY

2.1 PROBLEM IDENTIFICATION

2.2 EXISTING SYSTEM

.Net IEEE Project

ABSTRACT








3

2.3 PROPOSED SYSTEM

2.4 FEATURES OF PROPOSED SYSTEM

SYSTEM SPECIFICATION

3.1 HARDWARE SPECIFICATION

.Net IEEE Project

ABSTRACT








4

3.2 SOFTWARE SPECIFICATION

3.3 ABOUT SOFTWARE

SYSTEM ANALYSIS AND DESIGN

4.1 FEASIBILITY ANALYSIS

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB 4.2 E-R DIAGRAM

4.3 DATA FLOW DIAGRAM

4.4 MODULE DESCRIPTION

4.5 DATABASE DESIGN

.Net IEEE Project

ABSTRACT








5

6

4.6 INPUT DESIGN

4.7 OUTPUT DESIGN

SYSTEM TESTING

SYSTEM IMPLEMENTATION

.Net IEEE Project

ABSTRACT








7

8

SYSTEM SECURITY

7.1 INTRODUCTION

7.2 SECURITY IN SOFTWARE

CONCLUSION

.Net IEEE Project

ABSTRACT








9

10

11

FUTURE ENHANCEMENT

BIBLIOGRAPHY

ANNEXURES

SCREEN PROTOTYPES & REPORTS

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








1.1 INTRODUCTION TO PROJECT

.Net IEEE Project

ABSTRACT








Secure LAN communicator is an easy-to-use LAN messaging application

for effective intra-office communication. It does not require a server and is

very easy to install. Secure LAN communicator correctly identifies and works

under Windows NT/2000/XP/Vista limited user accounts (without

administrative privileges). Secure LAN communicator comes with a variety of

.Net IEEE Project

ABSTRACT








handy features such as message notification alarms, personal or group

messaging, file transfer and an intuitive interface. Our LAN chat utility offers

strong encryption options for all incoming and outgoing messages,

guaranteeing no unauthorized person ever reads personal correspondence. The

program is very stable when running under any Windows operating system and

.Net IEEE Project

ABSTRACT








on large or small TCP/IP networks. This application can be used for contacting

individual users or for group notifications. All chat messages are logged, so

there is no risk of losing a message. All correspondence can be looked up at

any time. There are convenient sound alarms for incoming messages. The

program is very straightforward and requires no special training. It is ready to

.Net IEEE Project

ABSTRACT








be used right after installation is completed. Configuring the program can be

done by individual users without requesting any assistance from the IT staff or

system administrators. All settings can be saved and easily transferred to

another computer if necessary.

.Net IEEE Project

ABSTRACT








ORGANIZATION PROFILE

Software Solutions is an IT solution provider for a dynamic environment where

business and technology strategies converge. Their approach focuses on new ways

of business combining IT innovation and adoption while also leveraging an

organization’s current IT assets. Their work with large global corporations and

.Net IEEE Project

ABSTRACT








new products or services and to implement prudent business and technology

strategies in today’s environment.

Xxxxxxx’s RANGE OF EXPERTISE INCLUDES:

Software Development Services

.Net IEEE Project

ABSTRACT








Engineering Services

Systems Integration

Customer Relationship Management

Product Development

Electronic Commerce

.Net IEEE Project

ABSTRACT








Consulting

IT Outsourcing

We apply technology with innovation and responsibility to achieve two broad

objectives:

Effectively address the business issues our customers face today.

.Net IEEE Project

ABSTRACT








Generate new opportunities that will help them stay ahead in the future.

THIS APPROACH RESTS ON:

A strategy where we architect, integrate and manage technology services and solutions - we call it AIM for success.

.Net IEEE Project

ABSTRACT








A robust offshore development methodology and reduced demand on customer resources.

A focus on the use of reusable frameworks to provide cost and times benefits.They combine the best people, processes and technology to achieve excellent results - consistency. We offer customers the advantages of:

.Net IEEE Project

ABSTRACT








SPEED:

They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule.

.Net IEEE Project

ABSTRACT








EXPERTISE:

Our teams combine cutting edge technology skills with rich domain expertise. What’s equally important - they share a strong customer orientation that means they actually start by listening to the customer. They’re focused on coming

.Net IEEE Project

ABSTRACT








up with solutions that serve customer requirements today and anticipate future needs.

A FULL SERVICE PORTFOLIO:

They offer customers the advantage of being able to Architect, integrate and manage technology services. This means that they can rely on one, fully accountable source instead of trying to integrate disparate multi vendor solutions.

.Net IEEE Project

ABSTRACT








SERVICES:

Xxx is providing its services to companies which are in the field of production, quality control etc with their rich expertise and experience and information technology they are in best position to provide software solutions to distinct business requirements.

.Net IEEE Project

ABSTRACT








SYSTEM STUDY

2.1Problem Identification

.Net IEEE Project

ABSTRACT








A LAN communicator application is developed that will facilitate secure chatting and file sharing over the network. This Secure LAN Communicator consists of two Modules, Server Module and Client Module. Server module will keep record of all the users, their login name, passwords. It will listen to Clients requests. Client module from other computer will first connect to the Server by providing user name and password. If client is authenticated the Server will send back list of all of the users that are online or offline. Client will select any of the online users to chat

.Net IEEE Project

ABSTRACT








with or any of the offline users to send him/her an offline messages. All message sent will first go to the Server and then server will send that message to the destination client.

The LAN Chat creates only one chat room that is why it has very clear interface. The LAN Chat's interface is one window with list of chat participants,

.Net IEEE Project

ABSTRACT








chat messages and outgoing message. And you can also set to your status online, away or disconnected in this window.

2.2 Existing System

.Net IEEE Project

ABSTRACT








The existing system has been maintained manually. The system, which has been maintained manually, had been complex and complicated.

In the existing system client is not authenticated.

The existing system we can use browser means, global connection secure Data will be loss.

.Net IEEE Project

ABSTRACT








The existing system chat with any one we can chat the available in chat room.

2.3 Proposed System

Considering the anomalies in the existing system computerization of the whole activity is being suggested after initial analysis by the organization.

.Net IEEE Project

ABSTRACT








The proposed system keeps the Username and password of the application server that is in running and stopped status.

The user who wants to use the system should have login and password. Each activity carried out by him can be tracked later by using log files. Hence this helps out in error detection and correction.

.Net IEEE Project

ABSTRACT








The proposed system Chat creates only one chat room that is why it has very clear interface and seared.

2.4 Features of Proposed System

Instant messaging with LAN chat abilityCreate chat rooms with multiple users’ conversation.

.Net IEEE Project

ABSTRACT








Secure LAN messaging - Save your privacy

All message exchanges are protected by the encryption algorithm Group

Broadcast messagesnotify all users or specified user groups about an event.

Offline messaging

.Net IEEE Project

ABSTRACT








Send messages to users even when they are offline. No server or dedicated storage required.

File transmissionExchange documents with your colleagues with ease.

User groupingArrange your colleagues in groups by business departments or titles.

.Net IEEE Project

ABSTRACT








Does not require an Internet connection

Very easy installation

Import and export your LAN settingsConfigure network settings on one computer, export it to a file, and then import it to any other computer on your network.

.Net IEEE Project

ABSTRACT








Multilanguage user interface

3.SYSTEM SPECIFICATION

3.1 Hardware Specification

.Net IEEE Project

ABSTRACT








Hardware Requirements:

PIV 2.8 GHz Processor and Above

RAM 1 GB and Above

HDD 40 GB Hard Disk Space and Above

.Net IEEE Project

ABSTRACT








3.2 Software Specification

Software Requirements:

WINDOWS OS (XP)

Visual Studio .Net 2008 Enterprise Edition

Internet Information Server 6.0 (IIS)

.Net IEEE Project

ABSTRACT








Visual Studio .Net Framework (Minimal for Deployment) version3.5

Microsoft Visual C# .Net

3.3 About Software

INTRODUCTION TO .NET FRAMEWORK

.Net IEEE Project

ABSTRACT








The Microsoft .NET Framework is a software technology that is available with several Microsoft Windows operating systems. It includes a large library of pre-coded solutions to common programming problems and a virtual machine that manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform.

http://en.wikipedia.org/wiki/Virtual_machine

.Net IEEE Project

ABSTRACT








The pre-coded solutions that form the framework's Base Class Library cover a large range of programming needs in a number of areas, including user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications.

Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET

http://en.wikipedia.org/wiki/Runtime

http://en.wikipedia.org/wiki/Software

http://en.wikipedia.org/wiki/Source_code

http://en.wikipedia.org/wiki/Computer_networking

http://en.wikipedia.org/wiki/Algorithm

http://en.wikipedia.org/wiki/Web_application

http://en.wikipedia.org/wiki/Cryptography

http://en.wikipedia.org/wiki/Programming

.Net IEEE Project

ABSTRACT








Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together compose the .NET Framework.

http://en.wikipedia.org/wiki/Exception_handling

http://en.wikipedia.org/wiki/Memory_management

http://en.wikipedia.org/wiki/Central_Processing_Unit

http://en.wikipedia.org/wiki/Virtual_machine#Application_virtual_machine

http://en.wikipedia.org/wiki/Virtual_machine#Application_virtual_machine

http://en.wikipedia.org/wiki/Common_Language_Runtime

http://en.wikipedia.org/wiki/Common_Language_Runtime

.Net IEEE Project

ABSTRACT








Principal design features

Interoperability

Because interaction between new and older applications is commonly required, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment.

.Net IEEE Project

ABSTRACT








Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; access to other functionality is provided using the P/Invoke feature.

Common Runtime Engine

http://en.wikipedia.org/wiki/Platform_Invocation_Services

http://en.wikipedia.org/wiki/Component_Object_Model

.Net IEEE Project

ABSTRACT








The Common Language Runtime (CLR) is the virtual machine component of the .NET framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling.

Base Class Library

.Net IEEE Project

ABSTRACT








The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction and XML document manipulation.

Simplified Deployment

.Net IEEE Project

ABSTRACT








Installation of computer software must be carefully managed to ensure that it does not interfere with previously installed software, and that it conforms to security requirements. The .NET framework includes design features and tools that help address these requirements.

Security

.Net IEEE Project

ABSTRACT








The design is meant to address some of the vulnerabilities, such as buffer overflows, that have been exploited by malicious software. Additionally, .NET provides a common security model for all applications.

Portability

.Net IEEE Project

ABSTRACT








The design of the .NET Framework allows it to theoretically be platform agnostic, and thus cross-platform compatible. That is, a program written to use the framework should run without change on any type of system for which the framework is implemented. Microsoft's commercial implementations of the framework cover Windows, Windows CE, and the Xbox 360. In addition, Microsoft submits the specifications for the Common

.Net IEEE Project

ABSTRACT








Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language), the C# language, and the C++/CLI language to both ECMA and the ISO, making them available as open standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.

.Net IEEE Project

ABSTRACT








Architecture

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Visual overview of the Common Language Infrastructure (CLI)

Common Language Infrastructure

.Net IEEE Project

ABSTRACT








The core aspects of the .NET framework lie within the Common Language Infrastructure, or CLI. The purpose of the CLI is to provide a language-neutral platform for application development and execution, including functions for exception handling, garbage collection, security, and interoperability. Microsoft's implementation of the CLI is called the Common Language Runtime or CLR.

Assemblies

.Net IEEE Project

ABSTRACT








The intermediate CIL code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files. The assembly consists of one or more files, one of which must contain the manifest, which has the metadata for the assembly. The complete name of an assembly (not to be confused with the filename on disk) contains its simple text name, version number, culture, and public key token. The public key token is a unique hash generated when the assembly is compiled, thus two assemblies with the same public key

.Net IEEE Project

ABSTRACT








token are guaranteed to be identical from the point of view of the framework. A private key can also be specified known only to the creator of the assembly and can be used for strong naming and to guarantee that the assembly is from the same author when a new version of the assembly is compiled (required to add an assembly to the Global Assembly Cache).

Metadata

.Net IEEE Project

ABSTRACT








All CLI is self-describing through .NET metadata. The CLR checks the metadata to ensure that the correct method is called. Metadata is usually generated by language compilers but developers can create their own metadata through custom attributes. Metadata contains information about the assembly, and is also used to implement the reflective programming capabilities of .NET Framework.

Security

.Net IEEE Project

ABSTRACT








.NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a

.Net IEEE Project

ABSTRACT








call stack walk: every assembly of each method in the call stack is checked for the required permission; if any assembly is not granted the permission a security exception is thrown.

When an assembly is loaded the CLR performs various tests. Two such tests are validation and verification. During validation the CLR checks that the assembly contains valid metadata and CIL, and whether the internal tables are correct. Verification is not so exact. The verification mechanism checks to see if the code

.Net IEEE Project

ABSTRACT








does anything that is 'unsafe'. The algorithm used is quite conservative; hence occasionally code that is 'safe' does not pass. Unsafe code will only be executed if the assembly has the 'skip verification' permission, which generally means code that is installed on the local machine.

.NET Framework uses appdomains as a mechanism for isolating code running in a process. Appdomains can be created and code loaded into or unloaded from them independent of other appdomains. This helps increase the fault tolerance of the

.Net IEEE Project

ABSTRACT








application, as faults or crashes in one appdomain do not affect rest of the application. Appdomains can also be configured independently with different security privileges. This can help increase the security of the application by isolating potentially unsafe code. The developer, however, has to split the application into sub domains; it is not done by the CLR.

Class library

.Net IEEE Project

ABSTRACT








Namespaces in the BCLSystemSystem. CodeDomSystem. CollectionsSystem. DiagnosticsSystem. Globalization

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB System. IOSystem. ResourcesSystem. TextSystem.Text.RegularExpressions

Microsoft .NET Framework includes a set of standard class libraries. The class library is organized in a hierarchy of namespaces. Most of the built in APIs are part

.Net IEEE Project

ABSTRACT








of either System.* or Microsoft.* namespaces. It encapsulates a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. The .NET class libraries are available to all .NET languages. The .NET Framework class library is divided into two parts: the Base Class Library and the Framework Class Library.

.Net IEEE Project

ABSTRACT








The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime. The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono.

.Net IEEE Project

ABSTRACT








The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework. It includes an expanded set of libraries, including WinForms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others. The FCL is much larger in scope than standard libraries for languages like C++, and comparable in scope to the standard libraries of Java.

http://en.wikipedia.org/wiki/Java_Class_Library

http://en.wikipedia.org/wiki/C%2B%2B

http://en.wikipedia.org/wiki/Windows_Communication_Foundation

http://en.wikipedia.org/wiki/Windows_Presentation_Foundation

http://en.wikipedia.org/wiki/Language_Integrated_Query

http://en.wikipedia.org/wiki/Language_Integrated_Query

http://en.wikipedia.org/wiki/ASP.NET

.Net IEEE Project

ABSTRACT








Memory management

The .NET Framework CLR frees the developer from the burden of managing memory (allocating and freeing up when done); instead it does the memory management itself. To this end, the memory allocated to instantiations of .NET types (objects) is done contiguously from the managed heap, a pool of memory managed by the CLR. As long as there exists a reference to an object, which might be either a direct reference to an object or via a graph of objects, the object is

.Net IEEE Project

ABSTRACT








considered to be in use by the CLR. When there is no reference to an object, and it cannot be reached or used, it becomes garbage. However, it still holds on to the memory allocated to it. .NET Framework includes a garbage collector which runs periodically, on a separate thread from the application's thread, that enumerates all the unusable objects and reclaims the memory allocated to them.

The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage collector. The GC runs only when a certain amount of memory has

.Net IEEE Project

ABSTRACT








been used or there is enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim memory are reached, the GC runs are non-deterministic. Each .NET application has a set of roots, which are pointers to objects on the managed heap (managed objects). These include references to static objects and objects defined as local variables or method parameters currently in scope, as well as objects referred to by CPU registers. When the GC runs, it pauses the application, and for each object referred to in the root, it recursively enumerates all the objects reachable from the root objects and marks them as

.Net IEEE Project

ABSTRACT








reachable. It uses .NET metadata and reflection to discover the objects encapsulated by an object, and then recursively walk them. It then enumerates all the objects on the heap (which were initially allocated contiguously) using reflection. All objects not marked as reachable are garbage. This is the mark phase. Since the memory held by garbage is not of any consequence, it is considered free space. However, this leaves chunks of free space between objects which were initially contiguous. The objects are then compacted together, by using memcpy to copy them over to the free space to make them contiguous again. Any reference to

.Net IEEE Project

ABSTRACT








an object invalidated by moving the object is updated to reflect the new location by the GC. The application is resumed after the garbage collection is over.

The GC used by .NET Framework is actually generational. Objects are assigned a generation; newly created objects belong to Generation 0. The objects that survive a garbage collection are tagged as Generation 1, and the Generation 1 objects that survive another collection are Generation 2 objects. The .NET Framework uses up to Generation 2 objects. Higher generation objects are garbage collected less

.Net IEEE Project

ABSTRACT








frequently than lower generation objects. This helps increase the efficiency of garbage collection, as older objects tend to have a larger lifetime than newer objects. Thus, by removing older (and thus more likely to survive a collection) objects from the scope of a collection run, fewer objects need to be checked and compacted.

Versions

.Net IEEE Project

ABSTRACT








Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of .NET 1.0 were released.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








The .NET Framework stack.

Version Version Number Release Date1.0 1.0.3705.0 2002-01-05

.Net IEEE Project

ABSTRACT








1.1 1.1.4322.573 2003-04-012.0 2.0.50727.42 2005-11-073.0 3.0.4506.30 2006-11-063.5 3.5.21022.8 2007-11-094.0 4.0.30319.1 2010-04-12

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Client Application Development

Client applications are the closest to a traditional style of

application in Windows-based programming. These are the types of applications

that display windows or forms on the desktop, enabling a user to perform a task.

Client applications include applications such as word processors and spreadsheets,

.Net IEEE Project

ABSTRACT








as well as custom business applications such as data-entry tools, reporting tools,

and so on. Client applications usually employ windows, menus, buttons, and other

GUI elements, and they likely access local resources such as the file system and

peripherals such as printers. Another kind of client application is the traditional

ActiveX control (now replaced by the managed Windows Forms control) deployed

.Net IEEE Project

ABSTRACT








over the Internet as a Web page. This application is much like other client

applications: it is executed natively, has access to local resources, and includes

graphical elements.

In the past, developers created such applications using C/C++ in

conjunction with the Microsoft Foundation Classes (MFC) or with a rapid

.Net IEEE Project

ABSTRACT








application development (RAD) environment such as Microsoft® Visual Basic®.

The .NET Framework incorporates aspects of these existing products into a single,

consistent development environment that drastically simplifies the development of

client applications.

.Net IEEE Project

ABSTRACT








The Windows Forms classes contained in the .NET Framework are

designed to be used for GUI development. You can easily create command

windows, buttons, menus, toolbars, and other screen elements with the flexibility

necessary to accommodate shifting business needs.

.Net IEEE Project

ABSTRACT








For example, the .NET Framework provides simple properties to

adjust visual attributes associated with forms. In some cases the underlying

operating system does not support changing these attributes directly, and in these

cases the .NET Framework automatically recreates the forms. This is one of many

.Net IEEE Project

ABSTRACT








ways in which the .NET Framework integrates the developer interface, making

coding simpler and more consistent.

.Net IEEE Project

ABSTRACT








Server Application Development

Server-side applications in the managed world are implemented

through runtime hosts. Unmanaged applications host the common language

runtime, which allows your custom managed code to control the behavior of the

server.

.Net IEEE Project

ABSTRACT








This model provides you with all the features of the common

language runtime and class library while gaining the performance and scalability of

the host server.

The following illustration shows a basic network schema with

managed code running in different server environments. Servers such as IIS and

.Net IEEE Project

ABSTRACT








SQL Server can perform standard operations while your application logic executes

through the managed code.

C#.NET

The Relationship of C# to .NET

.Net IEEE Project

ABSTRACT








C# is a new programming language, and is significant in two respects:

It is specifically designed and targeted for use with Microsoft's .NET Framework (a feature rich platform for the development, deployment, and execution of distributed applications).

It is a language based upon the modern object-oriented design methodology, and when designing it Microsoft has been able to learn from the experience

.Net IEEE Project

ABSTRACT








of all the other similar languages that have been around over the 20 years or so since object-oriented principles came to prominence

One important thing to make clear is that C# is a language in its own right. Although it is designed to generate code that targets the .NET environment, it is not itself part of .NET. There are some features that are supported by .NET but not by C#, and you might be surprised to learn that there are actually features of the C# language that are not supported by .NET like Operator Overloading.

.Net IEEE Project

ABSTRACT








However, since the C# language is intended for use with .NET, it is important for us to have an understanding of this Framework if we wish to develop applications in C# effectively. So, in this chapter

The Common Language Runtime:

.Net IEEE Project

ABSTRACT








Central to the .NET framework is its run-time execution environment, known as the Common Language Runtime (CLR) or the .NET runtime. Code running under the control of the CLR is often termed managed code.

However, before it can be executed by the CLR, any source code that we develop (in C# or some other language) needs to be compiled. Compilation occurs in two steps in .NET:

.Net IEEE Project

ABSTRACT








1. Compilation of source code to Microsoft Intermediate Language (MS-IL)

2. Compilation of IL to platform-specific code by the CLR

At first sight this might seem a rather long-winded compilation process. Actually, this two-stage compilation process is very important, because the

.Net IEEE Project

ABSTRACT








existence of the Microsoft Intermediate Language (managed code) is the key to providing many of the benefits of .NET. Let's see why.

Advantages of Managed Code

.Net IEEE Project

ABSTRACT








Microsoft Intermediate Language (often shortened to "Intermediate Language", or "IL") shares with Java byte code the idea that it is a low-level language with a simple syntax (based on numeric codes rather than text), which can be very quickly translated into native machine code. Having this well-definedUniversal syntax for code has significant advantages.

Platform Independence

.Net IEEE Project

ABSTRACT








First, it means that the same file containing byte code instructions can be placed on any platform; at runtime the final stage of compilation can then be easily accomplished so that the code will run on that particular platform. In other words, by compiling to Intermediate Language we obtain platform independence for .NET, in much the same way as compiling to Java byte code gives Java platform independence.

.Net IEEE Project

ABSTRACT








You should note that the platform independence of .NET is only theoretical at present because, at the time of writing, .NET is only available for Windows. However, porting .NET to other platforms is being explored (see for example the Mono project, an effort to create an open source implementation of .NET, at http://www.go-mono.com/).

Performance Improvement

.Net IEEE Project

ABSTRACT








Although we previously made comparisons with Java, IL is actually a bit more ambitious than Java byte code. Significantly, IL is always Just-In-Time compiled, whereas Java byte code was often interpreted. One of the disadvantages of Java was that, on execution, the process of translating from Java byte code to native executable resulted in a loss of performance (apart from in more recent cases, here Java is JIT-compiled on certain platforms).

.Net IEEE Project

ABSTRACT








Instead of compiling the entire application in one go (which could lead to a slow start-up time), the JIT compiler simply compiles each portion of code as it is called (just-in-time). When code has been compiled once, the resultant native executable is stored until the application exits, so that it does not need to be recompiled the next time that portion of code is run. Microsoft argues that this process is more efficient than compiling the entire application code at the start, because of the likelihood those large portions of any application code will not

.Net IEEE Project

ABSTRACT








actually be executed in any given run. Using the JIT compiler, such code will never get compiled.

This explains why we can expect that execution of managed IL code will be almost as fast as executing native machine code. What it doesn't explain is why Microsoft expects that we will get a performance improvement. The reason given for this is that, since the final stage of compilation takes place at run time, the JIT compiler will know exactly what processor type the program will run on. This

.Net IEEE Project

ABSTRACT








means that it can optimize the final executable code to take advantage of any features or particular machine code instructions offered by that particular processor.

Traditional compilers will optimize the code, but they can only perform optimizations that will be independent of the particular processor that the code will run on. This is because traditional compilers compile to native executable before the software is shipped. This means that the compiler doesn't know what type of

.Net IEEE Project

ABSTRACT








processor the code will run on beyond basic generalities, such as that it will be an x86-compatible processor or an Alpha processor. Visual Studio 6, for example, optimizes for a generic Pentium machine, so the code that it generates cannot take advantages of hardware features of Pentium III processors. On the other hand, the JIT compiler can do all the optimizations that Visual Studio 6 can, and in addition to that it will optimize for the particular processor the code is running on.

.Net IEEE Project

ABSTRACT








Language Interoperability

How the use of IL enables platform independence, and how JIT compilation should improve performance. However, IL also facilitates language interoperability. Simply put, you can compile to IL from one language, and this compiled code should then be interoperable with code that has been compiled to IL from another language.

.Net IEEE Project

ABSTRACT








Intermediate Language

From what we learned in the previous section, Intermediate Language obviously plays a fundamental role in the .NET Framework. As C# developers, we now understand that our C# code will be compiled into Intermediate Language before it is executed (indeed, the C# compiler only compiles to managed code). It makes sense, then, that we should now take a closer look at the main

.Net IEEE Project

ABSTRACT








characteristics of IL, since any language that targets .NET would logically need to support the main characteristics of IL too.

Here are the important features of the Intermediate Language:

Object-orientation and use of interfaces Strong distinction between value and reference types

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB Strong data typing Error handling through the use of exceptions Use of attributes

Support of Object Orientation and Interfaces

.Net IEEE Project

ABSTRACT








The language independence of .NET does have some practical limits. In particular, IL, however it is designed, is inevitably going to implement some particular programming methodology, which means that languages targeting it are going to have to be compatible with that methodology. The particular route that Microsoft has chosen to follow for IL is that of classic object-oriented programming, with single implementation inheritance of classes.

.Net IEEE Project

ABSTRACT








Besides classic object-oriented programming, Intermediate Language also brings in the idea of interfaces, which saw their first implementation under Windows with COM. .NET interfaces are not the same as COM interfaces; they do not need to support any of the COM infrastructure (for example, they are not derived from I Unknown, and they do not have associated GUIDs). However, they do share with

.Net IEEE Project

ABSTRACT








COM interfaces the idea that they provide a contract, and classes that implement a given interface must provide implementations of the methods and properties specified by that interface.

Object Orientation and Language Interoperability

.Net IEEE Project

ABSTRACT








Working with .NET means compiling to the Intermediate Language, and that in turn means that you will need to be programming using traditional object-oriented methodologies. That alone is not, however, sufficient to give us language interoperability. After all, C++ and Java both use the same object-oriented paradigms, but they are still not regarded as interoperable. We need to look a little more closely at the concept of language interoperability.

.Net IEEE Project

ABSTRACT








An associated problem was that, when debugging, you would still have to independently debug components written in different languages. It was not possible to step between languages in the debugger. So what we really mean by language interoperability is that classes written in one language should be able to talk directly to classes written in another language. In particular:

A class written in one language can inherit from a class written in another language

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB The class can contain an instance of another class, no matter what the

languages of the two classes are An object can directly call methods against another object written in

another language Objects (or references to objects) can be passed around between

methods When calling methods between languages we can step between the

method calls in the

.Net IEEE Project

ABSTRACT








Debugger, even where this means stepping between source code written in different languages

This is all quite an ambitious aim, but amazingly, .NET and the Intermediate Language have achieved it. For the case of stepping between methods in the

.Net IEEE Project

ABSTRACT








debugger, this facility is really offered by the Visual Studio .NET IDE rather than from the CLR itself.

Strong Data Type

One very important aspect of IL is that it is based on exceptionally strong data typing. What we mean by that is that all variables are clearly marked as being

.Net IEEE Project

ABSTRACT








of a particular, specific data type (there is no room in IL, for example, for the Variant data type recognized by Visual Basic and scripting languages). In particular, IL does not normally permit any operations that result in ambiguous data types.

For instance, VB developers will be used to being able to pass variables around without worrying too much about their types, because VB automatically performs type conversion. C++ developers will be used to routinely casting

.Net IEEE Project

ABSTRACT








pointers between different types. Being able to perform this kind of operation can be great for performance, but it breaks type safety. Hence, it is permitted only in very specific circumstances in some of the languages that compile to managed code. Indeed, pointers (as opposed to references) are only permitted in marked blocks of code in C#, and not at all in VB (although they are allowed as normal in managed C++). Using pointers in your code will immediately cause it to fail the memory type safety checks performed by the CLR.

.Net IEEE Project

ABSTRACT








You should note that some languages compatible with .NET, such as VB.NET, still allow some laxity in typing, but that is only possible because the compilers behind the scenes ensure the type safety is enforced in the emitted IL.

Although enforcing type safety might initially appear to hurt performance, in many cases this is far outweighed by the benefits gained from the services provided by .NET that rely on type safety. Such services include:

.Net IEEE Project

ABSTRACT








Language Interoperability

Garbage Collection

Security

Application Domains

Common Type System (CTS)

.Net IEEE Project

ABSTRACT








This data type problem is solved in .NET through the use of the Common Type System (CTS). The CTS defines the predefined data types that are available in IL, so that all languages that target the .NET framework will produce compiled code that is ultimately based on these types.

The CTS doesn't merely specify primitive data types, but a rich hierarchy of types, which includes well-defined points in the hierarchy at which code is permitted to define its own types. The hierarchical structure of the Common Type

.Net IEEE Project

ABSTRACT








System reflects the single-inheritance object-oriented methodology of IL, and looks like this:

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Common Language Specification (CLS)

The Common Language Specification works with the Common Type System to ensure language interoperability. The CLS is a set of minimum standards that all compilers targeting .NET must support. Since IL is a very rich language, writers of most compilers will prefer to restrict the capabilities of a given

.Net IEEE Project

ABSTRACT








compiler to only support a subset of the facilities offered by IL and the CTS. That is fine, as long as the compiler supports everything that is defined in the CLS.

Garbage Collection

.Net IEEE Project

ABSTRACT








The garbage collector is .NET's answer to memory management, and in particular to the question of what to do about reclaiming memory that running applications ask for. Up until now there have been two techniques used on Windows platform for deal locating memory that processes have dynamically requested from the system:

Make the application code do it all manually

.Net IEEE Project

ABSTRACT








Make objects maintain reference counts

The .NET runtime relies on the garbage collector instead. This is a program whose purpose is to clean up memory. The idea is that all dynamically requested memory is allocated on the heap (that is true for all languages, although in the case of .NET, the CLR maintains its own managed heap for .NET applications to use). Every so often, when .NET detects that the managed heap for a given process is becoming full and therefore needs tidying up, it calls the garbage collector. The

.Net IEEE Project

ABSTRACT








garbage collector runs through variables currently in scope in your code, examining references to objects stored on the heap to identify which ones are accessible from your code – that is to say which objects have references that refer to them. Any objects that are not referred to are deemed to be no longer accessible from your code and can therefore be removed. Java uses a similar system of garbage collection to this.

.Net IEEE Project

ABSTRACT








Security

.NET can really excel in terms of complementing the security mechanisms provided by Windows because it can offer code-based security, whereas Windows only really offers role-based security.

Role-based security is based on the identity of the account under which the process is running, in other words, who owns and is running the process. Code-

.Net IEEE Project

ABSTRACT








based security on the other hand is based on what the code actually does and on how much the code is trusted. Thanks to the strong type safety of IL, the CLR is able to inspect code before running it in order to determine required security permissions. .NET also offers a mechanism by which code can indicate in advance what security permissions it will require to run.

The importance of code-based security is that it reduces the risks associated with running code of dubious origin (such as code that you've downloaded from

.Net IEEE Project

ABSTRACT








the Internet). For example, even if code is running under the administrator account, it is possible to use code-based security to indicate that that code should still not be permitted to perform certain types of operation that the administrator account would normally be allowed to do, such as read or write to environment variables, read or write to the registry, or to access the .NET reflection features.

.Net Framework Classes

.Net IEEE Project

ABSTRACT








The .NET base classes are a massive collection of managed code classes that have been written by Microsoft, and which allow you to do almost any of the tasks that were previously available through the Windows API. These classes follow the same object model as used by IL, based on single inheritance. This means that you can either instantiate objects of whichever .NET base class is appropriate, or you can derive your own classes from them.

.Net IEEE Project

ABSTRACT








The great thing about the .NET base classes is that they have been designed to be very intuitive and easy to use. For example, to start a thread, you call the Start () method of the Thread class. To disable a Textbox, you set the Enabled property of a Textbox object to false. This approach will be familiar to Visual Basic and Java developers, whose respective libraries are just as easy to use. It may however come as a great relief to C++ developers, who for years have had to cope with such API functions as GetDIBits (), RegisterWndClassEx (), and IsEqualIID

.Net IEEE Project

ABSTRACT








(), as well as a whole plethora of functions that required Windows handles to be passed around.

Name Spaces

Namespaces are the way that .NET avoids name clashes between classes. They are designed, for example, to avoid the situation in which you define a class

.Net IEEE Project

ABSTRACT








to represent a customer, name your class Customer, and then someone else does the same thing (quite a likely scenario – the proportion of businesses that have customers seems to be quite high).

A namespace is no more than a grouping of data types, but it has the effect that the names of all data types within a namespace automatically get prefixed with the name of the namespace. It is also possible to nest namespaces within each other. For example, most of the general-purpose .NET base classes are in a

.Net IEEE Project

ABSTRACT








namespace called System. The base class Array is in this namespace, so its full name is System. Array.

If a namespace is explicitly supplied, then the type will be added to a nameless global namespace.Creating .Net Application using C#

.Net IEEE Project

ABSTRACT








C# can be used to create console applications: text-only applications that run in a DOS window. You'll probably use console applications when unit testing class libraries, and for creating Unix/Linux daemon processes. However, more often you'll use C# to create applications that use many of the technologies associated with .NET. In this section, we'll give you an overview of the different types of application that you can write in C#.

Creating Windows Forms

.Net IEEE Project

ABSTRACT








Although C# and .NET are particularly suited to web development, they still offer splendid support for so-called "fat client" apps, applications that have to be installed on the end-user's machine where most of the processing takes place. This support is from Windows Forms.

A Windows Form is the .NET answer to a VB 6 Form. To design a graphical window interface, you just drag controls from a toolbox onto a Windows Form. To

.Net IEEE Project

ABSTRACT








determine the window's behavior, you write event-handling routines for the form's controls. A Windows Form project compiles to an EXE that must be installed alongside the .NET runtime on the end user's computer. Like other .NET project types, Windows Form projects are supported by both VB.NET and C#.

Windows Control

.Net IEEE Project

ABSTRACT








Although Web Forms and Windows Forms are developed in much the same way, you use different kinds of controls to populate them. Web Forms use Web Controls, and Windows Forms use Windows Controls.

A Windows Control is a lot like an ActiveX control. After a Window control is implemented, it compiles to a DLL that must be installed on the client's machine. In fact, the .NET SDK provides a utility that creates a wrapper for ActiveX controls, so that they can be placed on Windows Forms. As is the case with Web

.Net IEEE Project

ABSTRACT








Controls, Windows Control creation involves deriving from a particular class, System.Windows.Forms.Control.

Windows Services

.Net IEEE Project

ABSTRACT








A Windows Service (originally called an NT Service) is a program that is designed to run in the background in Windows NT/2000/XP (but not Windows 9x). Services are useful where you want a program to be running continuously and ready to respond to events without having been explicitly started by the user. A good example would be the World Wide Web Service on web servers, whichListens out for web requests from clients.

.Net IEEE Project

ABSTRACT








It is very easy to write services in C#. There are .NET Framework base classes available in the System.ServiceProcess namespace that handle many of the boilerplate tasks associated with services, and in addition, Visual Studio .NET allows you to create a C# Windows Service project, which starts you out with the Framework C# source code for a basic Windows service.

The Role of C# In .Net Enterprise Architecture

.Net IEEE Project

ABSTRACT








C# requires the presence of the .NET runtime, and it will probably be a few years before most clients – particularly most home machines – have .NET installed. In the meantime, installing a C# application is likely to mean also installing the .NET redistributable components. Because of that, it is likely that the first place we will see many C# applications is in the enterprise environment. Indeed, C# arguably presents an outstanding opportunity for organizations that are interested in building robust, n-tiered client-server applications.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








SYSTEM ANALYSIS AND DESIGN

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Service Oriented Architecture

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Web services can also be used to implement architecture according to Service-oriented architecture (SOA) concepts, where the basic unit of communication is a message, rather than an operation. This is often referred to as "message-oriented" services. SOA Web services are supported by most major software vendors and industry analysts. Unlike RPC Web services, loose coupling is more likely,

.Net IEEE Project

ABSTRACT








because the focus is on the "contract" that WSDL provides, rather than the underlying implementation details.

A Web Service is programmable application logic accessible via standard Web protocols. One of these Web protocols is the Simple Object Access Protocol (SOAP). SOAP is a W3C submitted note (as of May 2000) that uses standards

.Net IEEE Project

ABSTRACT








based technologies (XML for data description and HTTP for transport) to encode and transmit application data. Consumers of a Web Service do not need to know anything about the platform, object model, or programming language used to implement the service; they only need to understand how to send and receive SOAP messages (HTTP and XML).

.Net IEEE Project

ABSTRACT








The Web services architecture places into relationship various components and technologies that comprise a Web services "stack" or completely functional implementation. Valid implementations include subsets or parts of the stack, but must at least provide the components within the basic architecture. Components and technologies that extend the basic architecture are represented within the extended architecture.

.Net IEEE Project

ABSTRACT








The basic architecture includes Web services technologies capable of:

Exchanging messages

Describing Web services

Publishing and discovering Web service descriptions

.Net IEEE Project

ABSTRACT








The basic Web services architecture defines an interaction between software agents as an exchange of messages between service requesters and service providers. Requesters are software agents that request the execution of a service. Providers are software agents that provide a service. Agents can be both service requesters and providers. Providers are responsible for publishing a description of the service(s) they provide. Requesters must be able to find the description(s) of the services.

.Net IEEE Project

ABSTRACT








The basic Web service architecture models the interactions between three roles: the service provider, service discovery agency, and service requestor. The interactions involve the publish, find, and bind operations. These roles and operations act upon the web service artifacts: the web service software module and its description. In a typical scenario a service provider hosts a network accessible software module (an implementation of a web service). The service provider defines a service description for the web service and publishes it to a requestor or service discovery

.Net IEEE Project

ABSTRACT








agency. The service requestor uses a find operation to retrieve the service description locally or from the discovery agency (i.e. a registry or repository) and uses the service description to bind with the service provider and invoke or interact with the web service implementation. Service provider and service requestor roles are logical constructs and a service may exhibit characteristics of both.

.Net IEEE Project

ABSTRACT








Requesters and providers interact using one or more message exchange patterns (MEPs) that define the sequence of one or more messages exchanged between them. A service description is hosted by a discovery service, to which a provider publishes the description, and from which the requester discovers the description. The description includes data type and structure information, identifies the MEP, and contains the address of the service provider.

.Net IEEE Project

ABSTRACT








The extended architecture describes Web services support for MEPs that group basic messages into higher-level interactions, details how support for features such as security, transactions, orchestration, privacy and others may be represented in messages (SOAP modules), and describes how additional features can be added to support business level interactions. The extended architecture builds on the basic architecture using the extensibility mechanisms inherent in the basic technologies.

.Net IEEE Project

ABSTRACT








Software agents in the basic architecture can take on one or all of the following roles:

Service requester -- requests the execution of a Web service

Service provider -- processes a Web service request

.Net IEEE Project

ABSTRACT








Discovery agency -- agency through which a Web service description is published and made discoverable

A software agent in the Web services architecture can act in one or multiple roles, acting as requester or provider only, both requester and provider, or as requester, provider, and discovery agency. A service is invoked after the description is found, since the service description is required to establish a binding.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








ASP.NET Web Services

Web Services are simple and easy to understand. It is possible, in fact, to author a simple application that surfaces data as XML conforming to the SOAP specification. It would also be relatively straightforward to build an application capable of receiving SOAP messages over HTTP and deriving meaningful value out of it. However, just as we use frameworks such as ASP and ASP.NET to build

.Net IEEE Project

ABSTRACT








Web applications, we would much rather use a framework for building Web Services. The reasoning is quite logical. We don't need to reinvent the plumbing—that is, at a high level, the capability to serialize our data as XML, transport the data using HTTP, and de-serialize the XML back to meaningful data. Instead, we want a framework that makes building Web Services easy, allowing us to focus on the application logic not the plumbing. ASP.NET provides this framework for us.

.Net IEEE Project

ABSTRACT








Web services can convert your applications into web-applications. Web services are published, found, and used through the web. For using the web service we must know the basic understanding of the following technologies

HTML

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB XML

Advantages of Web Services

Interoperability has Highest Priority

.Net IEEE Project

ABSTRACT








When all major platforms could access the web using web browsers, different platforms could interact. For these platforms to work together, web applications were developed. Web applications are simple applications run on web. These are built around the web browser standards and can mostly be used by any browser on any platform.

.Net IEEE Project

ABSTRACT








Next Level Web Applications

.Net IEEE Project

ABSTRACT








Using web services our applications can publish its function or message to the rest of the world. Web services user XML to code and to decode data, and SOAP to transport it (it’s a open protocol).

Web services are applications components

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB Web services communicate using open Protocols

Web services are self-contained and self-described

Web services can be discovered using UDDI

Web services can be used by other applications

XML is the basis for the web services

.Net IEEE Project

ABSTRACT








Web services platform elements

SOAP (Simple Object Access Protocol)

UDDI (Universal Description, Discovery and Integration)

.Net IEEE Project

ABSTRACT







Processor: Intel Pentium or More RAM: 1 GB Ram Hard Disk: PC with 20GB WSDL (Web Services Description Language)

Simple Object Access Protocol

.Net IEEE Project

ABSTRACT








SOAP is a simple XML-based protocol to let applications exchange information over HTTP. SOAP is a protocol for accessing a web service.

SOAP stands for Simple Object Access Protocol

SOAP is a communication protocol

SOAP is a format for sending messages

.Net IEEE Project

ABSTRACT








SOAP is designed to communicate via Internet

SOAP is platform independent

SOAP is language independent

SOAP is based on XML

SOAP is simple and extensible

.Net IEEE Project

ABSTRACT








SOAP allows you to get around firewalls

SOAP is a W3C standard

Web Services Description Language

WSDL is an XML-based language for describing web services and how to access them.

.Net IEEE Project

ABSTRACT








WSDL stands for Web Services Description Language

WSDL is based on XML

WSDL is used to describe Web services

WSDL is also used to locate Web services

WSDL is a W3C standard

.Net IEEE Project

ABSTRACT








UDDI

UDDI is a directory service where businesses can register and search for web services.

UDDI stands for Universal Description, Discovery and Integration

UDDI is a directory for storing information about web services

.Net IEEE Project

ABSTRACT








UDDI is a directory of web service interfaces described by WSDL

UDDI communicates via SOAP

UDDI is built into the Microsoft .NET platform

Process Flow of Web services

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








4.1 Feasibility Analysis

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

.Net IEEE Project

ABSTRACT








unlimited resources and infinite time. There are aspects in the feasibility study

portion of the preliminary investigation:

Technical Feasibility

Operational Feasibility

Economical Feasibility

.Net IEEE Project

ABSTRACT








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?

.Net IEEE Project

ABSTRACT








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?

.Net IEEE Project

ABSTRACT








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

.Net IEEE Project

ABSTRACT








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

.Net IEEE Project

ABSTRACT








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.

.Net IEEE Project

ABSTRACT








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

.Net IEEE Project

ABSTRACT








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?

.Net IEEE Project

ABSTRACT








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

.Net IEEE Project

ABSTRACT








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.

.Net IEEE Project

ABSTRACT








ECONOMICAL 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.

.Net IEEE Project

ABSTRACT








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.

4.2 E-R Diagram

.Net IEEE Project

ABSTRACT








4.3 Data Flow Diagram

.Net IEEE Project

ABSTRACT








4.4 Module Description

Number of Modules

The system after careful analysis has been identified to be presented with the following modules:

.Net IEEE Project

ABSTRACT








Number of Modules

The system after careful analysis has been identified to be presented with the following modules:

The modules involved are:

.Net IEEE Project

ABSTRACT








1. Admin2. Registration3. Server4. Client5. Chatting6. Authentication

.Net IEEE Project

ABSTRACT








Administration

Administration is the owner of the System. He can have all the privileges to do anything in this system. Administrator can register new users into the system. Admin can keep track team users and their activities. He can able to know what types of activities are done by the user.

.Net IEEE Project

ABSTRACT








Admin can categorize by the Text and update on the text size. Admin categorize the text into three types short and medium and large.

Registration

.Net IEEE Project

ABSTRACT








The system has a process of registration. Every user need to submit his complete details in the form of registration. Whenever a user registration completed automatically user can get a user id and password. By using that user id and password user can log into the system.

Server

.Net IEEE Project

ABSTRACT








Server module will keep record of all the users, their login name, passwords. Server will send back list of all of the users that are online or offline. All message sent will first go to the Server. The server echoes back everything that is sent by the client.

Client

.Net IEEE Project

ABSTRACT








Client module from other computer will first connect to the Server by providing user name and password. Client will select any of the online users to chat with or any of the offline users to send him/her an offline messages. The client displays everything received from the server in the output region

Chatting

.Net IEEE Project

ABSTRACT








The LAN Chat creates only one chat room that is why it has very clear interface. The LAN Chat's interface is one window with list of chat participants, chat messages and outgoing message. And you can also set to your status online, away or disconnected in this window.

Authentication

.Net IEEE Project

ABSTRACT








Authentication is nothing but providing security to the system. Here every must enter into the system throw login page. The login page will restrict the UN authorized users. A user must provide his credential like user Id and password for log into the system. For that the system maintains data for all users. Whenever a user enters his user id and password, it checks in the database for user existence. If the user is exists he can be treated as a valid user. Otherwise the request will throw back.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








STEM DESIGN

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








INTRODUCTION

Software design sits at the technical kernel of the software engineering

process and is applied regardless of the development paradigm and area of

.Net IEEE Project

ABSTRACT








application. Design is the first step in the development phase for any engineered

product or system. The designer’s goal is to produce a model or representation of

an entity that will later be built. Beginning, once system requirement have been

specified and analyzed, system design is the first of the three technical activities -

design, code and test that is required to build and verify software.

.Net IEEE Project

ABSTRACT








The importance can be stated with a single word “Quality”. Design is the

place where quality is fostered in software development. Design provides us with

representations of software that can assess for quality. Design is the only way that

we can accurately translate a customer’s view into a finished software product or

system. Software design serves as a foundation for all the software engineering

.Net IEEE Project

ABSTRACT








steps that follow. Without a strong design we risk building an unstable system –

one that will be difficult to test, one whose quality cannot be assessed until the last

stage.

During design, progressive refinement of data structure, program structure,

and procedural details are developed reviewed and documented. System design can

.Net IEEE Project

ABSTRACT








be viewed from either technical or project management perspective. From the

technical point of view, design is comprised of four activities – architectural

design, data structure design, interface design and procedural design.

Systems design is the process or art of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements. One

.Net IEEE Project

ABSTRACT








could see it as the application of systems theory to product development. There is

some overlap and synergy with the disciplines of systems analysis, systems

architecture and systems engineering.

Software Development Life Cycle:-

.Net IEEE Project

ABSTRACT








There is various software development approaches defined and designed which are used/employed during development process of software, these approaches are also referred as "Software Development Process Models". Each process model follows a particular life cycle in order to ensure success in process of software development.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Requirements

Business requirements are gathered in this phase. This phase is the main focus of the project managers and stake holders. Meetings with managers, stake holders and users are held in order to determine the requirements. Who is going to use the system? How will they use the system? What data should be input into the

.Net IEEE Project

ABSTRACT








system? What data should be output by the system? These are general questions that get answered during a requirements gathering phase. This produces a nice big list of functionality that the system should provide, which describes functions the system should perform, business logic that processes data, what data is stored and used by the system, and how the user interface should work. The overall result is the system as a whole and how it performs, not how it is actually going to do it.

.Net IEEE Project

ABSTRACT








Design

The software system design is produced from the results of the requirements phase. Architects have the ball in their court during this phase and this is the phase in which their focus lies. This is where the details on how the system will work is produced. Architecture, including hardware and software, communication,

.Net IEEE Project

ABSTRACT








software design (UML is produced here) are all part of the deliverables of a design phase.

Implementation

Code is produced from the deliverables of the design phase during implementation, and this is the longest phase of the software development life cycle. For a developer, this is the main focus of the life cycle because this is where the code is

.Net IEEE Project

ABSTRACT








produced. Implementation my overlap with both the design and testing phases. Many tools exists (CASE tools) to actually automate the production of code using information gathered and produced during the design phase.

Testing

During testing, the implementation is tested against the requirements to make sure that the product is actually solving the needs addressed and gathered during the

.Net IEEE Project

ABSTRACT








requirements phase. Unit tests and system/acceptance tests are done during this phase. Unit tests act on a specific component of the system, while system tests act on the system as a whole.

So in a nutshell, that is a very basic overview of the general software development life cycle model. Now lets delve into some of the traditional and widely used variations.

.Net IEEE Project

ABSTRACT








V-Model

An SDLC (System Development Life Cycle) approach that is sometimes referred to as the ‘V-Model’. Here all levels of requirements and specifications, be they the development of core software, customized software or implementation of configurable items, follow the model shown in the following illustration.

.Net IEEE Project

ABSTRACT








This approach associates various levels of requirements, specifications and development items to be properly documented and the response to each specification level is an equivalent testing (validation) and documentation of testing to ensure the quality of the software that is either developed or implemented.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Verification Phases1. Requirements analysis:In this phase, the requirements of the proposed system are collected by analyzing the needs of the user(s). This phase is concerned about establishing what the ideal system has to perform.. The user requirements document will typically describe the system’s functional, physical, interface, performance, data, security requirements etc as expected by the user. It is one which the business analysts use to communicate their understanding of the system back to the users. The users

.Net IEEE Project

ABSTRACT








carefully review this document as this document would serve as the guideline for the system.

2. System Design:System engineers analyze and understand the business of the proposed systemBy studying the user requirements document. They figure out possibilities andTechniques by which the user requirements can be implemented. If any of the requirements are not feasible, the user is informed of the issue. A resolution is

.Net IEEE Project

ABSTRACT








found and the user requirement document is edited accordingly. The software specification document which serves as a blueprint for the development phase is generated. This document contains the general system organization, menu structures, data structures etc. It may also hold example business scenarios, sample windows, reports for the better understanding.Other technical documentation like entity diagrams, data dictionary will alsoBe produced in this phase. The document for system testing is prepared inThis phase.

.Net IEEE Project

ABSTRACT








3. Architecture Design:This phase can also be called as high-level design. The baseline in selecting the architecture is that it should realize all which typically consists of the list of modules, brief functionality of each module, their interface relationships, dependencies, database tables, architecture diagrams, technology details etc.The integration testing design is carried out in this phase.

.Net IEEE Project

ABSTRACT








4. Module Design:This phase can also be called as low-level design. The designed system is broken up in to smaller units or modules and each of them is explained so that the programmer can start coding directly. The low level design document or program specifications will contain a detailed functional logic of the module, in pseudo code - database tables, with all elements, including their type and size - all interface details with complete API references- all dependency issues- error

.Net IEEE Project

ABSTRACT








message listings- complete input and outputs for a module. The unit test design is developed in this stage.

4.6 Input Design

.Net IEEE Project

ABSTRACT








Input design is a part of overall system design. The main objective during the

input design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

.Net IEEE Project

ABSTRACT








INPUT STAGES:

The main input stages can be listed as below:

Data recording

.Net IEEE Project

ABSTRACT








Data transcription

Data conversion

Data verification

Data control

Data transmission

.Net IEEE Project

ABSTRACT








Data validation

Data correction

INPUT TYPES:

.Net IEEE Project

ABSTRACT








It is necessary to determine the various types of inputs. Inputs can be categorized

as follows:

External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.

Operational, which are computer department’s communications to the system?

.Net IEEE Project

ABSTRACT








Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude

about the input media consideration has to be given to;

Type of input

.Net IEEE Project

ABSTRACT








Flexibility of format

Speed

Accuracy

Verification methods

Rejection rates

.Net IEEE Project

ABSTRACT








Ease of correction

Storage and handling requirements

Security

Easy to use

Portability

.Net IEEE Project

ABSTRACT








Keeping in view the above description of the input types and input media, it

can be said that most of the inputs are of the form of internal and interactive. As

Input data is to be the directly keyed in by the user, the keyboard can be considered

to be the most suitable input device.

ERROR AVOIDANCE

.Net IEEE Project

ABSTRACT








At this stage care is to be taken to ensure that input data remains accurate

form the stage at which it is recorded up to the stage in which the data is accepted

by the system. This can be achieved only by means of careful control each time

the data is handled.

ERROR DETECTION

.Net IEEE Project

ABSTRACT








Even though every effort is make to avoid the occurrence of errors, still a

small proportion of errors is always likely to occur, these types of errors can be

discovered by using validations to check the input data.

DATA VALIDATION

.Net IEEE Project

ABSTRACT








Procedures are designed to detect errors in data at a lower level of detail.

Data validations have been included in the system in almost every area where there

is a possibility for the user to commit errors. The system will not accept invalid

data. Whenever an invalid data is keyed in, the system immediately prompts the

.Net IEEE Project

ABSTRACT








user and the user has to again key in the data and the system will accept the data

only if the data is correct. Validations have been included where necessary.

The system is designed to be a user friendly one. In other words the system

has been designed to communicate effectively with the user. The system has been

designed with popup menus.

.Net IEEE Project

ABSTRACT








USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while

designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

.Net IEEE Project

ABSTRACT








1. User initiated interface the user is in charge, controlling the progress of the

user/computer dialogue. In the computer-initiated interface, the computer

selects the next stage in the interaction.

2. Computer initiated interfaces

.Net IEEE Project

ABSTRACT








In the computer initiated interfaces the computer guides the progress of the

user/computer dialogue. Information is displayed and the user response of the

computer takes action or displays further information.

USER_INITIATED INTERGFACES

User initiated interfaces fall into tow approximate classes:

.Net IEEE Project

ABSTRACT








1. Command driven interfaces: In this type of interface the user inputs commands

or queries which are interpreted by the computer.

2. Forms oriented interface: The user calls up an image of the form to his/her

screen and fills in the form. The forms oriented interface is chosen because it is

the best choice.

.Net IEEE Project

ABSTRACT








COMPUTER-INITIATED INTERFACES

The following computer – initiated interfaces were used:

1. The menu system for the user is presented with a list of alternatives and the user

chooses one; of alternatives.

.Net IEEE Project

ABSTRACT








2. Questions – answer type dialog system where the computer asks question and

takes action based on the basis of the users reply.

Right from the start the system is going to be menu driven, the opening

menu displays the available options. Choosing one option gives another popup

.Net IEEE Project

ABSTRACT








menu with more options. In this way every option leads the users to data entry

form where the user can key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface

design. As user is bound to commit some errors or other while designing a system

.Net IEEE Project

ABSTRACT








the system should be designed to be helpful by providing the user with information

regarding the error he/she has committed.

This application must be able to produce output at different modules for different inputs.

5.7 OUTPUTDESIGN

.Net IEEE Project

ABSTRACT








Outputs from computer systems are required primarily to communicate the results

of processing to users. They are also used to provides a permanent copy of the

results for later consultation. The various types of outputs in general are:

External Outputs, whose destination is outside the organization

Internal Outputs whose destination is within organization and they are the

.Net IEEE Project

ABSTRACT








User’s main interface with the computer.

Operational outputs whose use is purely within the computer department.

Interface outputs, which involve the user in communicating directly.

OUTPUT DEFINITION

.Net IEEE Project

ABSTRACT








The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

.Net IEEE Project

ABSTRACT








Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer.

It should be decided as which form of the output is the most suitable.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








OUTPUT SCREENS

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Screen Shots

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








Sample Code

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








SYSTEM TESTING AND IMPLEMENTATION

1.1 INTRODUCTION

.Net IEEE Project

ABSTRACT








Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. In fact, testing is

the one step in the software engineering process that could be viewed as

destructive rather than constructive.

.Net IEEE Project

ABSTRACT








A strategy for software testing integrates software test case design methods

into a well-planned series of steps that result in the successful construction of

software. Testing is the set of activities that can be planned in advance and

conducted systematically. The underlying motivation of program testing is to

.Net IEEE Project

ABSTRACT








affirm software quality with methods that can economically and effectively apply

to both strategic to both large and small-scale systems.

8.2. STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system

engineering defines the role of software and leads to software requirement analysis

.Net IEEE Project

ABSTRACT








where the information domain, functions, behavior, performance, constraints and

validation criteria for software are established. Moving inward along the spiral, we

come to design and finally to coding. To develop computer software we spiral in

along streamlines that decrease the level of abstraction on each turn.

.Net IEEE Project

ABSTRACT








A strategy for software testing may also be viewed in the context of the

spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit

of the software as implemented in source code. Testing progress by moving

outward along the spiral to integration testing, where the focus is on the design and

the construction of the software architecture. Talking another turn on outward on

.Net IEEE Project

ABSTRACT








the spiral we encounter validation testing where requirements established as part of

software requirements analysis are validated against the software that has been

constructed. Finally we arrive at system testing, where the software and other

system elements are tested as a whole.

UNIT TESTING

MODULE TESTING

SUB-SYSTEM TESING

SYSTEM TESTING

ACCEPTANCE TESTING

Component Testing

Integration Testing

User Testing

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








8.3. UNIT TESTING

.Net IEEE Project

ABSTRACT








Unit testing focuses verification effort on the smallest unit of software

design, the module. The unit testing we have is white box oriented and some

modules the steps are conducted in parallel.

1. WHITE BOX TESTINGThis type of testing ensures that

.Net IEEE Project

ABSTRACT








All independent paths have been exercised at least once

All logical decisions have been exercised on their true and false sides

All loops are executed at their boundaries and within their operational bounds

All internal data structures have been exercised to assure their validity.

.Net IEEE Project

ABSTRACT








To follow the concept of white box testing we have tested each form .we

have created independently to verify that Data flow is correct, All conditions are

exercised to check their validity, All loops are executed on their boundaries.

2. BASIC PATH TESTING

.Net IEEE Project

ABSTRACT








Established technique of flow graph with Cyclomatic complexity was used to

derive test cases for all the functions. The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graph.

Determine the Cyclomatic complexity of resultant flow graph, using formula:

.Net IEEE Project

ABSTRACT








V(G)=E-N+2 or

V(G)=P+1 or

V (G) =Number of Regions

Where V (G) is Cyclomatic complexity,

.Net IEEE Project

ABSTRACT








E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

.Net IEEE Project

ABSTRACT








3. CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and

false aspects. And all the resulting paths were tested. So that each path that may be

generate on particular condition is traced to uncover any possible errors.

4. DATA FLOW TESTING

.Net IEEE Project

ABSTRACT








This type of testing selects the path of the program according to the location

of definition and use of variables. This kind of testing was used only when some

local variable were declared. The definition-use chain method was used in this type

of testing. These were particularly useful in nested statements.

5. LOOP TESTING

.Net IEEE Project

ABSTRACT








In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for all loops:

All the loops were tested at their limits, just above them and just below them.

All the loops were skipped at least once.

For nested loops test the inner most loop first and then work outwards.

.Net IEEE Project

ABSTRACT








For concatenated loops the values of dependent loops were set with the help of

connected loop.

Unstructured loops were resolved into nested loops or concatenated loops and

tested as above.

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








SYSTEM SECURITY

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








9.1 INTRODUCTION

The protection of computer based resources that includes hardware,

software, data, procedures and people against unauthorized use or natural

Disaster is known as System Security.

.Net IEEE Project

ABSTRACT








System Security can be divided into four related issues:

Security

Integrity

Privacy

Confidentiality

.Net IEEE Project

ABSTRACT








SYSTEM SECURITY refers to the technical innovations and procedures applied

to the hardware and operation systems to protect against deliberate or accidental

damage from a defined threat.

.Net IEEE Project

ABSTRACT








DATA SECURITY is the protection of data from loss, disclosure, modification

and destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and

programs, appropriate physical security and safety against external threats such as

eavesdropping and wiretapping.

.Net IEEE Project

ABSTRACT








PRIVACY defines the rights of the user or organizations to determine what

information they are willing to share with or accept from others and how the

organization can be protected against unwelcome, unfair or excessive

dissemination of information about it.

.Net IEEE Project

ABSTRACT








CONFIDENTIALITY is a special status given to sensitive information in a

database to minimize the possible invasion of privacy. It is an attribute of

information that characterizes its need for protection.

9.3 SECURITY SOFTWARE

.Net IEEE Project

ABSTRACT








It is the technique used for the purpose of converting communication. It transfers message secretly by embedding it into a cover medium with the use of information hiding techniques. It is one of the conventional techniques capable of hiding large secret message in a cover image without introducing many perceptible distortions.

NET has two kinds of security:

.Net IEEE Project

ABSTRACT








Role Based Security Code Access Security

The Common Language Runtime (CLR) allows code to perform only those operations that the code has permission to perform. So CAS is the CLR's security system that enforces security policies by preventing unauthorized access to protected resources and operations. Using the Code Access Security, you can do the following:

.Net IEEE Project

ABSTRACT








Restrict what your code can do Restrict which code can call your code

Identify code

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








CONCLUSION

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








It has been a great pleasure for me to work on this exciting and challenging

project. This project proved good for me as it provided practical knowledge of not

only programming in windows forms and C#.NET Network based application and

no some extent Windows Application, but also about all chatting procedure

.Net IEEE Project

ABSTRACT








related with “Secure LAN Communicator with Chat Application Using Windows”.

It also provides knowledge about the latest technology used in developing

Network enabled application and client server technology that will be great

demand in future. This will provide better opportunities and guidance in future in

developing projects independently.

.Net IEEE Project

ABSTRACT








BENEFITS:

The project is identified by the merits of the system offered to the user. The

merits of this project are as follows: -

It’s a Network-enabled project.

.Net IEEE Project

ABSTRACT








This project offers user to enter the data through simple and interactive forms.

This is very helpful for the client to enter the desired information through so

much simplicity.

The user is mainly more concerned about the validity of the data, whatever he

is entering. There are checks on every stages of any new creation, data entry

.Net IEEE Project

ABSTRACT








or updation so that the user cannot enter the invalid data, which can create

problems at later date.

Sometimes the user finds in the later stages of using project that he needs to

update some of the information that he entered earlier. There are options for

him by which he can update the records. Moreover there is restriction for his

.Net IEEE Project

ABSTRACT








that he cannot change the primary data field. This keeps the validity of the

data to longer extent.

User is provided the option of monitoring the records he entered earlier. He

can see the desired records with the variety of options provided by him.

.Net IEEE Project

ABSTRACT








From every part of the project the user is provided with the links through

framing so that he can go from one option of the project to other as per the

requirement. This is bound to be simple and very friendly as per the user is

concerned. That is, we can say that the project is user friendly which is one of

the primary concerns of any good project.

.Net IEEE Project

ABSTRACT








Decision making process would be greatly enhanced because of faster

processing of information since data collection from information available on

computer takes much less time then manual system.

Allocating of sample results becomes much faster because at a time the user

can see the records of last years.

.Net IEEE Project

ABSTRACT








Easier and faster data transfer through latest technology associated with the

computer and communication.

Through these features it will increase the efficiency, accuracy and

transparency,

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








FUTURE IMPROVEMENT

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








This System being Network-based and an undertaking of Cyber Security

Division, needs to be thoroughly tested to find out any security gaps.

.Net IEEE Project

ABSTRACT








A console for the data centre may be made available to allow the personnel

to monitor on the sites which were cleared for hosting during a particular

period.

This System need to maintain login and logout history in database.

.Net IEEE Project

ABSTRACT








Moreover, it is just a beginning; further the system may be utilized in various other types of auditing operation viz. Network auditing or similar process/workflow based applications

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








BIBLIOGRAPHY

.Net IEEE Project

ABSTRACT








.Net IEEE Project

ABSTRACT








FOR .NET INSTALLATIONwww.support.mircosoft.com

FOR DEPLOYMENT AND PACKING ON SERVERwww.developer.com

http://www.developer.com/

http://www.support.mircosoft.com/

.Net IEEE Project

ABSTRACT








www.15seconds.com

FOR SQLwww.msdn.microsoft.com

FOR ASP.NETwww.msdn.microsoft.com/net/quickstart/aspplus/default.com

http://www.msdn.microsoft.com/net/quickstart/aspplus/default.com

http://www.msdn.microsoft.com/

http://www.15seconds.com/

.Net IEEE Project

ABSTRACT








www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

http://www.4guysfromrolla.com/index.aspx

http://www.aspfree.com/

http://www.asptoday.com/

http://www.fmexpense.com/quickstart/aspplus/default.com

http://www.asp.net/

.Net IEEE Project

ABSTRACT








System Analysis and Design

Senn

Database System Design

Elmasree

.Net IEEE Project

ABSTRACT








Korth

Software Engineering Concepts

Robert Pressman

.Net IEEE Project

ABSTRACT








techshristi.com€¦ · web viewas c# developers, we now understand that our c# code will be...

Documents