Document

ASSET MANAGEMENT SYSTEM

INTRODUCTION

1



INTRODUCTION & OBJECTIVE

Asset Management system plays a typical role and acts like a

link between Units of an Organization usually a corporate company.

The main objective of “Asset Management system” is to introduce

computerized system in a widely spread organization which can be used

as a resource for private network, in order to fulfill the basic needs of an

Organization like Information sharing, Communication, Document

Viewing as well as sharing.

This Asset Management System helps in creating and managing a

data repository of the inventory pertaining to the hardware of IT

resources in organization. The IT inventory list basically consists of

computers, monitors, software, network devices, printers. Plotters

scanners, cartridges, etc…..

PURPOSE OF THE PROJECT

Asset Management System is a web based application, which has two major components , an application for automatically capturing the inventory data pertaining to the installed hardware and software of a computer and its associated peripherals, and second component named which helps in the management of these inventories The second module makes use of the data captured by the first and the financial and commercial data pertaining to the inventory. The financial details include data on purchase order, invoice, warranty , AMC and the commercial details include data on suppliers, contacts , contracts etc , The financial and commercial data have to be entered manually into the second Module . The data

2


captured could be imported into the second Module; also manual entry of inventory data is possible in the software.

PROBLEM IN EXISTING SYSTEM

The problem definition for the system is to launching the online system for the inventory of Technical store. The objective of the project is to setting up of an on-line enquiry system about the status of the availability of the hardware items (printer /laptop /scanner) along with the facility to apply online and also to automate the issuing procedure.

• Time Delay: It is inefficient to deal with voluminous data

manually in the existing system, record stored in different

files. It takes lot of time to search different files.

• Redundancy: As the branches are located in different

locations, same files have to be stored at all branches which

involve lot of complications and duplication works thus

causes redundancy.

• Accuracy: Since same data is compiled at different

branches the possibility of tabulating data wrong increases

also data is more, validation becomes difficult. It may result

in loss of accuracy of data.

. SOLUTION OF THESE PROBLEMS

Computerizing of an organization whose branches are

situated at different locations and connecting them through

3


Intranet. This provides easy accessing of shared data and

provides communication channel between employees

• Reliability: The project performs intended function with

required precision; hence this project is very reliable.

• Feasibility: The project maintenance is very easy and

modifications can be made in the existing system in future.

The project can interconnect to other groups within the

organization and also to all other branches under integrated

network.

• Online Processing: The online processing of the project is

very simple following the existing manual method without

changes and suitable validation is provided for the easy and

correct access of users.

• Security: Security measures are taken to avoid mishandling

of database. Password restrictions are provided to enter

into database. A correct password only will access to the

database

4


The features of Asset Management System are:

Inventory of the computers with management of the devices connections and TCO management.

Inventory of the monitors with management of the connections to the computers Inventory of the network hardware with management of the connections to the devices (Ip,Mac addresses, VLANs)

Inventory of printers with management o connections to the computers and management of consumable associated Inventory of the external devices (Scanners, graphical tables) with management of the connections to the computers

Inventory if the software with license and expiration dates management

Assignment of the hardware by geographic area (room, floor) Commercial and financial information management (purchase, guarantee and extension, damping)

History of the modifications on the elements of the inventory

5


STUDY OF THE SYSTEM

GUI’S

In the flexibility of the uses the interface has been developed a graphics

concept in mind, associated through a browses interface. The GUI’S at

the top level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent

information that is practically, part of the organizational activities and

which needs proper authentication for the data collection. The

interfaces help the administrations with all the transactional states like

Data insertion, Data deletion and Date updation along with the

extensive data search capabilities.

The operational or generic user interface helps the users upon the

system in transactions through the existing data and required services.

The operational user interface also helps the ordinary users in

managing their own information helps the ordinary users in managing

their own information in a customized manner as per the assisted

flexibilities.

NUMBER OF MODULES

Current system is differentiated into the following modules which are closely integrated with one another.

6


Administrator

• The activities that are carried out in this module are related to the maintenance of master records such as Managers, Department master and Employee master for the entire organization. This module provides for performing addition, deletion, updating and viewing the records in the master tables. This module also provides viewing profiles of branches, departments and user’s.

• The master entries can only be accessed by the administrator of the organization. this module Also provides Viewing The software And hardware. Of it resources in Organization

Features of administrator module: Login system Add,delete user’s Profiles Response for organizations View system peripherals Viewing software installations Solving repairs in Organization View reports logout

Users

• The activities that are carried out in this module are related to software’s installation viewing in their systems, Repairs forwarding to Administrator, and updating, their profiles.. User’s can also view his profile to know the details. He can join the conference to communicate with people in the Organization.

• User can get organization Information and also communicate with Administrator Those activities that are carried out in this module are related viewing The Installed Hardware and Software's of a computers and its Associated Peripherals

Features of USER’S module: Login to system Updating User’s Profiles Response to administrator Viewing installed software’s Sending repairs and problems to the administrator

7


Submit Reports Logout

Assets:

This Module for automatically capturing the inventory data pertaining to the installed hardware and software of a computer and its associated peripherals, and second component named which helps in the management of these inventories The second module makes use of the data captured by the first and the financial and commercial data pertaining to the inventory.

This module Managing A data Repository Of The Hardware of Assets such as Computers ,Monitors, Keyboards, Printers ,Scanners, plotters, etc…..

This Product's Management consisting The Software's Information Such As Software Details With license And Expiration Dates Management Assignment Of The Hardware By Geographic Area

Features of Assets module: Suppliers Details Store software’s Information’s Store Hardware information’s Store Financial Information Legal Restrictions Submit reports

8


. INPUT AND OUTPUT

INPUT DESIGN

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.

INPUT STAGES:

The main input stages before the information gets stored in the

database media:

Data recording

Data transcription

Data conversion

Data verification

Data control

Data transmission

Data validation

Data correction

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate

the results of processing to users. They are also used to provide 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 with in organization and

they are the

9


User’s main interface with the computer.

Operational outputs whose use is purely with in the computer

department.

Interface outputs, which involve the user in communicating

directly with

The outputs were needed to be generated as a hard copy and as

well as queries to be viewed on the screen. Keeping in view these

outputs, the format for the output is taken from the outputs, which are

currently being obtained after manual processing. The standard

printer is to be used as output media for hard copies.

PROCESS MODELS USED WITH JUSTIFICATION

SDLC MODEL:

Waterfall Model

Software products are oriented towards customers like any other

engineering products. It is either driver by market or it drives the

market. Customer Satisfaction was the main aim in the 1980's.

Customer Delight is today's logo and Customer Ecstasy is the new

buzzword of the new millennium. Products which are not customer

oriented have no place in the market although they are designed using

the best technology. The front end of the product is as crucial as the

internal technology of the product.

A market study is necessary to identify a potential customer's

need. This process is also called as market research. The already

existing need and the possible future needs that are combined together

for study. A lot of assumptions are made during market study.

10


Assumptions are the very important factors in the development or start

of a product's development. The assumptions which are not realistic can

cause a nosedive in the entire venture. Although assumptions are

conceptual, there should be a move to develop tangible assumptions to

move towards a successful product.

Once the Market study is done, the customer's need is given to the

Research and Development Department to develop a cost-effective

system that could potentially solve customer's needs better than the

competitors. Once the system is developed and tested in a hypothetical

environment, the development team takes control of it. The

development team adopts one of the software development models to

develop the proposed system and gives it to the customers.

The basic popular models used by many software development

firms are as follows:

A) System Development Life Cycle (SDLC) Model

B) Prototyping Model

C) Rapid Application Development Model

D) Component Assembly Model

A) System Development Life Cycle Model (SDLC Model):

11


This is also called as Classic Life Cycle Model (or) Linear Sequential

Model (or) Waterfall Method. This model has the following activities.

1. System/Information Engineering and Modeling

2. Software Requirements Analysis

3. Systems Analysis and Design

4. Code Generation

5. Testing

6. Maintenance

1) System/Information Engineering and Modeling

As software development is large process so work begins by

establishing requirements for all system elements and then allocating

some subset of these requirements to software. The view of this system is

necessary when software must interface with other elements such as

hardware, people and other resources. System is the very essential

requirement for the existence of software in any entity. In some cases

for maximum output, the system should be re-engineered and spruced

up. Once the ideal system is designed according to requirement, the

development team studies the software requirement for the system.

2) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study.

In this requirement analysis phase, the development team visits the

customer and studies their system requirement. They examine the need

for possible software automation in the given software system. After

12


feasibility study, the development team provides a document that holds

the different specific recommendations for the candidate system. It also

consists of personnel assignments, costs of the system, project schedule

and target dates.

The requirements analysis and information gathering process is

intensified and focused specially on software. To understand what type

of the programs to be built, the system analyst must study the

information domain for the software as well as understand required

function, behavior, performance and interfacing. The main purpose of

requirement analysis phase is to find the need and to define the problem

that needs to be solved.

3) System Analysis and Design

In System Analysis and Design phase, the whole software

development process, the overall software structure and its outlay are

defined. In case of the client/server processing technology, the number

of tiers required for the package architecture, the database design, the

data structure design etc are all defined in this phase. After designing

part a software development model is created. Analysis and Design are

very important in the whole development cycle process. Any fault in the

design phase could be very expensive to solve in the software

development process. In this phase, the logical system of the product is

developed.

4) Code Generation

13


In Code Generation phase, the design must be decoded into a

machine-readable form. If the design of software product is done in a

detailed manner, code generation can be achieved without much

complication. For generation of code, Programming tools like

Compilers, Interpreters, and Debuggers are used. For coding purpose

different high level programming languages like C, C++, Pascal and

Java are used. The right programming language is chosen according to

application.

5)Testing

After code generation phase the software program testing begins.

Different testing methods are available to detect the bugs that were

committed during the previous phases. A number of testing tools and

methods are already available for testing purpose.

6) Maintenance

Software will definitely go through change once when it is

delivered to the customer. There are large numbers of reasons for the

change. Change could happen due to some unpredicted input values

into the system. In addition to this the changes in the system directly

have an effect on the software operations. The software should be

implemented to accommodate changes that could be happen during the

post development period.

14


15


DESIGN PRINCIPLES & METHODOLOGY:

Object Oriented Analysis And Design

When Object orientation is used in analysis as well as design, the

boundary between OOA and OOD is blurred. This is particularly true

in methods that combine analysis and design. One reason for this

blurring is the similarity of basic constructs (i.e.,objects and classes)

that are used in OOA and OOD. Through there is no agreement about

what parts of the object-oriented development process belongs to

analysis and what parts to design, there is some general agreement

about the domains of the two activities.

The fundamental difference between OOA and OOD is that the

former models the problem domain, leading to an understanding and

specification of the problem, while the latter models the solution to the

problem. That is, analysis deals with the problem domain, while design

deals with the solution domain. However, in OOAD subsumed in the

solution domain representation. That is, the solution domain

representation, created by OOD, generally contains much of the

representation created by OOA. The separating line is matter of

perception, and different people have different views on it. The lack of

clear separation between analysis and design can also be considered one

of the strong points of the object-oriented approach the transition from

analysis to design is “seamless”. This is also the main reason OOAD

methods-where analysis and designs are both performed.

The main difference between OOA and OOD, due to the different

domains of modeling, is in the type of objects that come out of the

analysis and design process.

16


Features of OOAD:

It users Objects as building blocks of the application rather

functions

All objects can be represented graphically including the

relation between them.

All Key Participants in the system will be represented as actors

and the actions done by them will be represented as use cases.

A typical use case is nothing bug a systematic flow of series of

events which can be well described using sequence diagrams

and each event can be described diagrammatically by Activity

as well as state chart diagrams.

So the entire system can be well described using OOAD model,

hence this model is chosen as SDLC model.

. SYSTEM ARCHITECTURE

The current application is being developed by taking the 3-tier architecture as a prototype. The 3-tier architecture is the most common approach used for web applications today. In the typical example of this model, the web browser acts as the client, IIS handles the business logic, and a separate tier MS-SQL Server handles database functions.

Although the 3-tier approach increases scalability and introduces a separation of business logic from the display and database layers, it does not truly separate the application into specialized, functional layers. For prototype or simple web applications, the 3-tier architecture may be sufficient. However, with complex demands placed on web applications, a 3-tiered approach falls short in several key areas, including flexibility and scalability. These shortcomings occur mainly because the business logic tier is still too broad- it has too many

17


functions grouped into one tier that could be separated out into a finer grained model.

18


SYSTEM DESIGN

19


DESIGN

Software Requirement Specification:

Software Requirement Specification (SRS) is the starting point of

the software developing activity. As system grew more complex it

became evident that the goal of the entire system cannot be easily

comprehended. Hence the need for the requirement phase arose. The

software project is initiated by the client needs. The SRS is the means

of translating the ideas of the minds of clients (the input) into a formal

document (the output of the requirement phase.)

The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis: The process is order and more

nebulous of the two, deals with understand the problem, the goal and

constraints.

2) Requirement Specification: Here, the focus is on specifying what

has been found giving analysis such as representation, specification

languages and tools, and checking the specifications are addressed

during this activity.

The Requirement phase terminates with the production of the

validate SRS document. Producing the SRS document is the basic goal

of this phase.

20


Role of SRS:

The purpose of the Software Requirement Specification is to

reduce the communication gap between the clients and the developers.

Software Requirement Specification is the medium though which the

client and user needs are accurately specified. It forms the basis of

software development. A good SRS should satisfy all the parties

involved in the system.

Software Requirements

Operating System : Windows-XP with SP2 orWindows Vista

Technologies : ASP.NET with C#.NET

Database : MS-SQL server2005

IDE : Ms Visual Studio .Net 2008

Browser : Internet Explorer

21


Hardware RequirementsHardware Requirements

Pentium IV System with 2.8 Pentium IV System with 2.8 GHZ Processor.GHZ Processor.

HDD 20 GB Min 40 GB Recommended

RAM 1 GB Min 2 GB Recommended

22


DATA DICTIONARY

23


24


LOGIN TABLE

25


USERTABLE

26


HARDWRE DEATAILS

27


SOFTWARE DEATAILS

28


VENDOR DEATAILS

29


ORDERDEATAILS

30


SHIPPING DEATAILS

31


BILLING ADDRESS

32


UML

33


Diagrams:

UML DIAGRAMS

UML stands for UNIFIED MODELING LANGUAGE The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic,semantic and pragmatic rules.A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

1. User Model ViewThis view represents the system from the users perspective.The analysis representation describes a usage scenario from the end-users perspective.

2. Structural Model viewIn this model the data and functionality are arrived from inside the system.This model view models the static structures.

3. Behavioral Model ViewIt represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

4. Implementation Model ViewIn this the structural and behavioral as parts of the system are represented as they are to be built.

5. Environmental Model ViewIn this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.

UML is specifically constructed through two different domains they are:

34


UML Analysis modeling, which focuses on the user model and structural model views of the system.

UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

35


AssetManagement

System

Asset’s

ADMINISTRATOR

USER’S

loginResponse

Add, Delete User’sView User’s Profiles

View Software's information'sView Systems Peripherals

Solve repairsSubmit Reports

Logout

Logout

loginResponse

Update, cancel user’s

View Reports

Sending repairs

Change PasswordView Installed Software's

Supp

liers

Detail

s

Fina

ncial

Inform

ation

Gene

ratin

g Re

ports

Stores

Softw

are’s

inform

ation

Lega

l Res

trictions

Stor

es H

ardw

are I

nfor

mati

on's

36


Level:1 Diagrams :

Admin LoginAdd delete

User’s Profiles

LoginDB

View’s S/w

Assets

User’s DB

ReportsDBH/W Assets DB

Viewing User’s Profiles

s/w Assets

Reportsgeneration

Login DB

logout

1

1

Viewsh/w

Assets

Admin

Administrator:-

37


User’s LoginUpdateUser’s Profiles

LoginDB User's DB

Manage Assets services

Orders DB

CustomerReceiving

Orders

Suppliers DB User's

Suppliersinformation

1

1

User’s

38


Asset's SuppliersLookup

Suppliersservices

Suppliers DB H/W Assets DB

StoringH/w

Assets

S/W Asset DB

Restrictions DB

StoringS/W

Assets

1

1 LegalInformation's Asset's

Assets

39


Login

Reportgeneration

Register, DeleteUser’sAdministrator

Views User’s Profiles

View Software's information's

View Systems Peripherals

USECASE DIAGRAMS

40


Login

Response

Views installedSoftware's

Sending Repairs

SubmitReports

Logout

Updating UsersProfilesUser’s

41


Login

Start

Add ,DeleteUser’s

information

View Software'sinformation's Solve repairs View Reports

Logout

Stop

Administrator

Yes

No

ACTIVITY DIAGRAMS

View User’s Profiles

42


Login

Start

UpdateUser's

View Installed

Software's

Sending Repairs

Logout

Stop

Register

Admin

No

Yes

User’s

Register

Submit Reports

ResponseTo

administrator

43


Login

Start

Suppliers Details

StoreS/W ,H/W

Details

Logout

Stop

Assets

YesNo

MaintainFinanancial

Information

44


Login

Login

Add,Delete

software'sInformation

ComputerPeripheralsInformation

SolveRepairs

(Customer)

Administrator

(Users)

Reports generation

ReportsUsers

SEQUENCE DIAGRAMS

RepairsH/W Assets

S/WAssets

45


Login

Login

User’s

UpdateUser’s View

InstalledSoftware's

SubmitReports

Users ReportsS/WAssets repairs

Sending Repairs toAdmin

46


Login

Login

SuppliersDeatails Stores

FinancialInformation

Submit Reports To Administrator

Assets SuppliersFinancialInformation

Submit Reports

47


Class DiagramsAdministrator

User’s Assets

1…1

Register, Delete User Profiles

Update User Profiles

+view S/ w Information+view H/w Information+Solve Repairs+View Reports

+User id+Sending repairs+Submit Reports

+Asset id(s/ w&h/ w)

+Suppliers Details+Store s/ w,H/ w Information's+Legal Information's+Generating Reports

48


User’s login

Admin

log in

Software deatails

Hardware Deatails

Logout

Vendor deatails

Shipping address

User deatails

Er-diagram

Can s/w deatails

Use full information

Users information

vid Name Address

city

phone

email

emailName

Name

phone

Address

uid

Address

phoneemail

regionBranch name

Price

Asset id

license

warranty

Price

Asset id

category

49


50


SCREENS

51


SCREENS:

52


53


54


55


56


57


58


59


60


61


62


63


64


65


66


67


68


69


70


Introduction to .NET

71


Overview of .Net frame work:

The .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment.

The .NET Framework is designed to fulfill the following objectives:-

1. To provide a consistent object oriented programming

environment.

2. To provide a code execution environment that minimizes software

deployment and versioning conflicts.

3. To provide code execution environment that guarantees safe

execution of code, including code created by an unknown or semi

trusted third party.

4. To provide code execution environment that eliminates the

performance problems of scripted or interpreted environments.

5. To make the developer experience consistent across widely

varying types of applications such as window based applications

and web based applications.

6. To build all communication on industry standards to ensure that

code based on the .NET Framework can integrate with any other

code.

The .NET framework has two main components:

1. Common Language Runtime (CLR)

2. .NET Framework Class Library (FCL)

The CLR is a foundation of .NET Framework. It is like agents that

manages the code at execution time, providing core services such as

memory management, thread management and also enforces strict type

72


safety and other forms of code accuracy that ensures security and

robustness. In fact the concept of code management is a fundamental

principle of the runtime.

Code that targets runtime is known as managed code, while the code

doesn’t target the runtime is known as unmanaged code. The class

library, the other main component of the .NET Framework, is a

comprehensive, object oriented collection of reusable types that u can

use to develop applications ranging from graphical user interface

applications to applications based on the latest innovations provided by

VB.NET.

The .NET Framework can be hosted by unmanaged components

that load the CLR their processes and initiate the execution of managed

code there by creating a software environment that can exploit both

managed and unmanaged features. The .NET Framework not only

provides several runtime hosts but also supports the development of

third party runtime hosts.

Features of Common Language Runtime (CLR):

The CLR manages memory, thread execution, code execution,

code safety verification, compilation and other system services. These

features are intrinsic to managed code that runs on the CLR.

With regard to security, managed components are awarded

varying degrees of trust, depending on the number of factors that

include their origin.

73


This means that managed component may or may not be able to

perform file access operations, registry access operations and other

sensitive operations even if it is being used in same active application.

The runtime enforces code access security. The runtime also

enforces code robustness by implementing a strict type and code

verification infrastructure called the Common Type System (CTS). The

CTS ensures that all managed code is self describing. The various

Microsoft and other language compilers generate managed code that

conforms to the CTS.

The runtime also accelerates the developer productivity. For

example, programmers can write applications in their development

language of choice, yet take full advantage of runtime, the class library

and components written in other languages by other developers.

Language compilers that target the .net framework make the features

available to the existing code written in that language, easing the

migration process for existing applications. Interoperability between

managed and unmanaged code enables developers to continue to use

necessary components.

The runtime is designed to enhance performance. Although the

CLR provides standard runtime services, code is never interpreted. A

feature called Just in Time compiling (JIT) enables all managed code to

run in the native machine language of the systems on which it is

executing.

\

74


.Net frame work class library:

The .NET Framework class library is a collection of reusable

types that tightly integrates with the CLR. The class library is object-

oriented, providing types from which the managed code can derive

functionality. This not only makes the .NET Framework types easy to

use but also reduces the time associated with learning new features

of .NET Framework. In addition, third party components can integrate

successfully with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of

interfaces that you can use to develop your own collection classes.

1. The .NET Framework types enable you to accomplish a range of a

common programming task, including tasks such as string

management, data collection; data base connectivity and file

access. In addition to these common tasks, the class library

includes types that support a variety of specialized development

scenarios.

75


.NET Framework Architecture

76


Introduction To ADO.NET

77


ADO.NET (ActiveX Data Objects) MODEL:

ADO.NET is the primary relational data access model. It may be

used to access data sources for which there is a specific .NET Provider,

or, via a .NET Bridge Provider, for which there is a specific OLE DB

Provider, ODBC Driver, or JDBC Driver.

ADO.net is the overall name for set of the classes (spread across a

number of namespaces including System.Data, System.Data.Common,

System.Data.SqlTypes, System.Data.SqlClient and System.Data.OleDb)

that the .Net framework provides for working with data in relational

databases.

The ADO object model is broken up into two distinct sets of

objects – Data provider objects and Dataset objects.

The dataset objects provide a memory-resident, disconnected set of

objects that you can load with data.

The data provider objects handle the task of working directly with data

sources. The Data Adapter object, serves as a conduit between the two

sets of objects. By using a Data Adapter we can load data from a

database into a Dataset and later save changes back to original data

source. In generic terms, the data provider objects manage the database

for the application and the Dataset objects manage the data model for

the application.

78


Data providers and their objectives:

The main five data objects are:

Connection

Command

Parameter

DataReader

DataAdapter

A data provider is a namespace that implements these five classes for

use with a particular database. For example, SQL data provider has

been used, which is implemented in the System.Data.SqlClient

namespace. In this namespace the object names are as follows:

SqlConnection

SqlCommand

SqlParameter

SqlDataReader

SqlDataAdapter

But the Sql server data provider is not the only alternative for

retrieving data in ADO.NET. The .NET Framework also ships with the

Oracle provider implemented in the System.Data.OracleClient

namespace. In this namespace the object names are as follows:

OracleConnection

OracleCommand

OracleParameter

OracleDataReader

OracleDataAdapter

79


The data set objects:The second set of ADO.NET objects are the Dataset objects, which

are all contained in the System.Data namespace. Unlike the data

provider objects there is only one set of Dataset objects. The Dataset

objects represent data in an abstract form that which is not tied to any

particular database implementation.

DataSet

Datatable

DataRelation

DataRow

DataColumn

DataView

The DataSet itself is a self-contained memory-resident representation

of relational data. A DataSet contains other objects such as DataTables

and DataRelations that hold the actual data and information about the

design of the data. The dataset is designed to be easy to move between

components.

The Data Table object represents a single table within a DataSet.

A single DataSet can contain many DataTable objects. The Data

Relation object stores information on the relations between data tables

within a Data Set.

The DataRow represents a single row of data when you are selecting,

inserting, updating or deleting data in a Data Set, we can normally work

with DataRow objects.

80


The Data Column represents a single column in the Data table. By

manipulating the DataColumn objects we can determine and even

change the structure of DataTable.

The Data View object represents a view of data contained in the data

table. A DataView might contain every DataRow from the DataTable or

it might be filtered to contain only specific rows.

81


Introduction To C#.NET

82


About C#.Net:-

Visual C# (pronounced C sharp) is a new programming language.

Introduced in Visual Studio .NET. An evolution of C and C++, C# is

simple, modern, type-safe, and object-oriented.

It was designed for building a wide range of enterprise

applications that run on the .NET Platform. Code that you write with

visual C# is complied as managed code, which means it benefits from

the services of the Common Language Runtime.

These services include language interoperability, garbage

collection, enhanced security, and improved versioning support.

Visual C# is fully supported within Visual Studio .NET by project

templates, designers, property pages, code assistants, an object model,

and other features of the development environment.

The library for Visual C# programming is the .NET Framework.

C# is a simple but powerful programming language intended for

writing enterprise applications.

The C# language is an evolution of C and C++. The C# language

is Component-Oriented language because it includes Properties,

Methods, Events, Attributes, XML documentation.

C# introduces considerable improvement and innovations in

areas such as type safety, versioning, events, and garbage collection.

83


C# provides access to the common API styles: .NET

Framework, COM, Automation, and C-style APIs. It also

supports unsafe mode, where you can use pointers to manipulate

memory that is not under the control of the garbage collector.

C# programs can consist of one or more files. Each file contains

one or more namespaces. A namespace can contain types such as

classes, structs, interfaces, in addition to other namespace.

C# .Net features:-

Flexible: C# programs can execute on the current machine, or they

can be transmitted over the Web and executed on some distant

computer.

Powerful: C# has essentially the same command set as C++, but with

the rough edges filed smooth.

Easier to use: C# modifies the commands responsible for most C++

errors so you spend far less time chasing down those errors.

Visually oriented: The .NET code library that C# uses for many of its

capabilities provides the help needed to readily create complicated

display frames with drop-down lists, tabbed windows, grouped

buttons, scroll bars, and background images, to name just a few.

Internet friendly: C# plays a pivotal role in the .NET Framework,

Microsoft’s current approach to programming for Windows, the

Internet, and beyond. .NET is pronounced dot net.

Secure: Any language intended for use on the Internet must include

serious security to protect against malevolent hackers.

C# is a simple but powerful programming language intended for

writing enterprise applications.

84


The C# language is an evolution of C and C++. It uses many C++

features in the areas of statements, expressions, and operators.

C# introduces considerable improvement and innovations in

areas such as type safety, versioning, events and garbage collection.

Why use C#.Net:-

C#.NET is a modern and elegant language, Lot less typing than

VB.Net, Overload Operators and it is direct access to memory.

C# .NET also gives you the capability to build durable system-

level components by virtue of the following features:

Full COM/Platform support for existing code integration.

Robustness through garbage collection and type safety.

Security provided through intrinsic code trust mechanisms.

Full support of extensible metadata concepts.

You can also interoperate with other languages, across platforms,

with legacy data, by virtue of the following features:

Framework services with tight library-based access.

XML support for web-based component interaction.

Versioning to provide ease of administration and deployment.

85


Introduction To ASP.NET

86


ASP.Net :

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

MS Access can perform standard operations while your application

logic executes through the managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to use

the .NET Framework to target Web-based applications. However,

ASP.NET is more than just a runtime host; it is a complete architecture

for developing Web sites and Internet-distributed objects using

managed code. Both Web Forms and XML Web services use IIS and

ASP.NET as the publishing mechanism for applications, and both have

a collection of supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology,

are distributed, server-side application components similar to common

Web sites. However, unlike Web-based applications, XML Web services

components have no UI and are not targeted for browsers such as

Internet Explorer and Netscape Navigator. Instead, XML Web services

87


consist of reusable software components designed to be consumed by

other applications, such as traditional client applications, Web-based

applications, or even other XML Web services. As a result, XML Web

services technology is rapidly moving application development and

deployment into the highly distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will

immediately notice the improvements that ASP.NET and Web Forms

offers. For example, you can develop Web Forms pages in any language

that supports the .NET Framework. In addition, your code no longer

needs to share the same file with your HTTP text (although it can

continue to do so if you prefer). Web Forms pages execute in native

machine language because, like any other managed application, they

take full advantage of the runtime. In contrast, unmanaged ASP pages

are always scripted and interpreted. ASP.NET pages are faster, more

functional, and easier to develop than unmanaged ASP pages because

they interact with the runtime like any managed application.

The .NET Framework also provides a collection of classes and tools to

aid in development and consumption of XML Web services

applications. XML Web services are built on standards such as SOAP (a

remote procedure-call protocol), XML (an extensible data format), and

WSDL ( the Web Services Description Language). The .NET

Framework is built on these standards to promote interoperability with

non-Microsoft solutions.

88


For example, the Web Services Description Language tool included with

the .NET Framework SDK can query an XML Web service published

on the Web, parse its WSDL description, and produce C# or Visual

Basic source code that your application can use to become a client of the

XML Web service. The source code can create classes derived from

classes in the class library that handle all the underlying communication

using SOAP and XML parsing. Although you can use the class library

to consume XML Web services directly, the Web Services Description

Language tool and the other tools contained in the SDK facilitate your

development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET

Framework provides a set of classes that conform to all the underlying

communication standards, such as SOAP, WSDL, and XML. Using

those classes enables you to focus on the logic of your service, without

concerning yourself with the communications infrastructure required

by distributed software development.

Finally, like Web Forms pages in the managed environment, your XML

Web service will run with the speed of native machine language using

the scalable communication of IIS.

89


Active Server Pages.NET

ASP.NET is a programming framework built on the common language

runtime that can be used on a server to build powerful Web

applications. ASP.NET offers several important advantages over

previous Web development models:

Enhanced Performance. ASP.NET is compiled common language

runtime code running on the server. Unlike its interpreted predecessors,

ASP.NET can take advantage of early binding, just-in-time compilation,

native optimization, and caching services right out of the box. This

amounts to dramatically better performance before you ever write a

line of code.

World-Class Tool Support. The ASP.NET framework is

complemented by a rich toolbox and designer in the Visual Studio

integrated development environment. WYSIWYG editing, drag-and-

drop server controls, and automatic deployment are just a few of the

features this powerful tool provides.

Power and Flexibility. Because ASP.NET is based on the common

language runtime, the power and flexibility of that entire platform is

available to Web application developers. The .NET Framework class

library, Messaging, and Data Access solutions are all seamlessly

accessible from the Web. ASP.NET is also language-independent, so you

can choose the language that best applies to your application or

partition your application across many languages. Further, common

90


language runtime interoperability guarantees that your existing

investment in COM-based development is preserved when migrating to

ASP.NET.

Simplicity. ASP.NET makes it easy to perform common tasks, from

simple form submission and client authentication to deployment and

site configuration. For example, the ASP.NET page framework allows

you to build user interfaces that cleanly separate application logic from

presentation code and to handle events in a simple, Visual Basic - like

forms processing model. Additionally, the common language runtime

simplifies development, with managed code services such as automatic

reference counting and garbage collection.

Manageability. ASP.NET employs a text-based, hierarchical

configuration system, which simplifies applying settings to your server

environment and Web applications. Because configuration information

is stored as plain text, new settings may be applied without the aid of

local administration tools. This "zero local administration" philosophy

extends to deploying ASP.NET Framework applications as well. An

ASP.NET Framework application is deployed to a server simply by

copying the necessary files to the server. No server restart is required,

even to deploy or replace running compiled code.

Scalability and Availability. ASP.NET has been designed with

scalability in mind, with features specifically tailored to improve

performance in clustered and multiprocessor environments. Further,

91


processes are closely monitored and managed by the ASP.NET runtime,

so that if one misbehaves (leaks, deadlocks), a new process can be

created in its place, which helps keep your application constantly

available to handle requests.

Customizability and Extensibility. ASP.NET delivers a well-factored

architecture that allows developers to "plug-in" their code at the

appropriate level. In fact, it is possible to extend or replace any

subcomponent of the ASP.NET runtime with your own custom-written

component. Implementing custom authentication or state services has

never been easier.

Security. With built in Windows authentication and per-application

configuration, you can be assured that your applications are secure.

Language Support

The Microsoft .NET Platform currently offers built-in support for three

languages: C#, Visual Basic, and JScript.

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common

language runtime programming model that can be used on the server to

dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax

compatibility with existing pages), the ASP.NET Web Forms

92


framework has been specifically designed to address a number of key

deficiencies in the previous model. In particular, it provides:

The ability to create and use reusable UI controls that can

encapsulate common functionality and thus reduce the amount of code

that a page developer has to write.

The ability for developers to cleanly structure their page logic in

an orderly fashion (not "spaghetti code").

The ability for development tools to provide strong WYSIWYG

design support for pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name

extension. They can be deployed throughout an IIS virtual root

directory tree. When a browser client requests .aspx resources, the

ASP.NET runtime parses and compiles the target file into a .NET

Framework class. This class can then be used to dynamically process

incoming requests. (Note that the .aspx file is compiled only the first

time it is accessed; the compiled type instance is then reused across

multiple requests).

An ASP.NET page can be created simply by taking an existing HTML

file and changing its file name extension to .aspx (no modification of

code is required). For example, the following sample demonstrates a

simple HTML page that collects a user's name and category preference

and then performs a form postback to the originating page when a

button is clicked:

93


ASP.NET provides syntax compatibility with existing ASP pages. This

includes support for <% %> code render blocks that can be intermixed

with HTML content within an .aspx file. These code blocks execute in a

top-down manner at page render time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first

is the method shown in the preceding samples, where the page code is

physically declared within the originating .aspx file. An alternative

approach--known as the code-behind method--enables the page code to

be more cleanly separated from the HTML content into an entirely

separate file.

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program

dynamic content, ASP.NET page developers can use ASP.NET server

controls to program Web pages. Server controls are declared within

an .aspx file using custom tags or intrinsic HTML tags that contain a

runat="server" attribute value. Intrinsic HTML tags are handled by

one of the controls in the System.Web.UI.HtmlControls namespace. Any

tag that doesn't explicitly map to one of the controls is assigned the type

of System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values

between round trips to the server. This control state is not stored on the

server (it is instead stored within an <input type="hidden"> form field

94


that is round-tripped between requests). Note also that no client-side

script is required.

In addition to supporting standard HTML input controls, ASP.NET

enables developers to utilize richer custom controls on their pages. For

example, the following sample demonstrates how the <asp:adrotator>

control can be used to dynamically display rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build

dynamic Web UI.

2. ASP.NET Web Forms pages can target any browser client (there

are no script library or cookie requirements).

3. ASP.NET Web Forms pages provide syntax compatibility with

existing ASP pages.

4. ASP.NET server controls provide an easy way to encapsulate

common functionality.

5. ASP.NET ships with 45 built-in server controls. Developers can

also use controls built by third parties.

6. ASP.NET server controls can automatically project both uplevel

and downlevel HTML.

7. ASP.NET templates provide an easy way to customize the look

and feel of list server controls.

8. ASP.NET validation controls provide an easy way to do

declarative client or server data validation.

95


Introduction To SQL Server

96


SQL SERVER:-

DATA BASE:

A database management, or DBMS, gives the user access to

their data and helps them into information. Such database

management systems include dBase, paradox, IMS, SQL Server

and sql server. These systems allow user to create, update and

extract information form their database.

A database is a structured collection of data. Data refers to

the characteristics of people, things and events. SQL Server stores

each data item in its own fields. In SQL Server, the fields relating

to a particular person, things or event are bundled together to

form a single complete unit of data, called a record (it can also be

referred to as raw or an occurrence). Each record is made up of a

number of fields. No two fields in a record can have the same field

name.

During an SQL server Database design project, the analysis

of your business needs identifies all the field or attribute of

interest. If your business needs change over time, you define any

additional fields or change the definition of existing fields.

SQL Server Tables:

SQL server stores records relating to each other in a table.

Different tables are created for various group of information.

Related tables are grouped together to form a database.

97


Primary Key:

Every table in SQL server has a field or a combination of

fields that uniquely identifies each record in the table. The Unique

identifier is called the Primary Key, or simply the Key. The

primary key provides the means to distinguish one record form all

other in a table. It allows the user and the database system to

identify, locate and refer to one particular record in the database.

Relational Database:

Sometimes all the information of interest to a business

operation can be stored in one table. SQL server makes it very

easy to link the data in multiple tables. Matching an employee to

the department in which they work in one example. This is what

makes SQL server a relational database management system, or

RDBMS. It stores data in two or more tables and enables you to

define relationship between the tables.

98


Foreign Key:

When a field is one table matches the primary key of

another field is referred to as a foreign key. A foreign key is a

field or a group of fields in one table whose values match those of

the primary key of another table.

Referential Integrity:

Not only does SQL Server allow you to link multiple tables,

it also maintains consistency between them. Ensuring that the

data among related tables is correctly matched is referred to as

maintaining referential integrity.

Data Abstraction:

A major purpose of a database system is to provide users

with an abstract view of the data. This system hides certain details

of how the data is stored and maintained. Data abstraction is

divided into three levels.

Physical Level:

This is the lowest level of abstraction at which one describes

how the data are actually stored.

99


Conceptual Level:

At this level of database abstraction all the attributed and

what data are actually stored is described and entries and

relationship among them.

View Level:

This is the highest level of abstraction at which one

describes only part of the database.

Advantages of RDBMS:

Redundancy can be avoided

Inconsistency can be eliminated

Data can be shared

Standard can be enforced

Security restrictions can be applied

Integrity can be maintained

Conflicting requirements can be balanced

Data independence can be achieved.

100


Disadvantages of DBMS:

A significant disadvantage of the DBMS system is cost. In

addition to the cost of purchasing of developing the software, the

hardware has to be upgraded to allow for the extensive programs

and the workspace required for their execution and storage.

While centralization reduces duplication, the lack of duplication

requires that the database be adequately backed up to that in case

of failure the data can be recovered.

FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management

system (DBMS) because it is the only database that meets the

uncompromising requirements of today's most demanding

information systems. From complex decision support system

(DSS) to the most rigorous online transaction processing(OLTP)

application, even application that require simultaneous DSS and

OLTP access to the same critical data, SQL Server leads the

industry in both performance and capability.

SQL SERVER is a truly portable, distributed, and open

DBMS that delivers unmatched performance, continuous

operation and support for every database.

101


SQL SERVER RDBMS is high performance fault tolerant

DBMS which is specially designed for online transaction

processing and for handling large database application.

SQL SERVER with transaction processing option offers

two features which contribute to very high level of transaction

processing throughput, which are

The row level lock managers

Enterprise wide Data Sharing:

The unrivaled portability and connectivity of the SQL

SERVER DBMS enables all the

systems in the organization to be linked into a singular, integrated

computing resource.

Portability:

SQL SERVER is fully portable to more than 80 distinct

hardware and operating system platforms, including UNIX,

MSDOS, OS/2, Macintosh and dozens of proprietary platforms.

This portability gives complete freedom to choose the database

server platform that meets the system requirements.

Open System:

SQL SERVER offers a leading implementation of industry -

standard SQL. SQL Server's open architecture integrates SQL

SERVER and non-SQL SERVER DBMS with industries most

102


comprehensive collection of tools, application, and third party

software products SQL Server's open architecture provides

transparent access to data from other relational database and

even non-relational database.

Distributed data sharing:

SQL server 's networking and distributed database

capabilities to access data stored on remote server with the same

ease as if the information was stored on a single local computer. A

single SQL statement can access data at multiple sites. You can

store data where system requirements such as performance,

security or availability dictate.

Unmatched Performance:

The most advanced architecture in the industry allows the

SQL SERVER DBMS to deliver unmatched performance.

Sophisticated concurrency control:

Real world applications demand access to critical data.

With most database systems application becomes "contention

bound" -which performance is limited not by the CPU power or

by disk I/O, but user waiting on one another for data access. SQL

Server employs full, unrestricted row-level locking and contention

free queries to minimize and in many cases entirely eliminates

contention wait times.

103


No I/O Bottlenecks:

SQL Server's fast commit groups commit and deferred

write technologies dramatically reduce disk I/O bottlenecks.

While some database write whole data block to disk at commit

time, SQL Server commits transactions with at most sequential

log file on disk at commit time, On high throughput systems, one

sequential writes typically group commit multiple transactions.

Data read by the transaction remains as shared memory so that

other transactions may access that data with out reading it again

from disk. Since fast commits write all data necessary to the

recovery to the log file, modified blocks are written back to the

database independently of the transaction commit, when written

from memory to disk.

104


NORMALIZATION

105


NORMALIZATION:It is a process of converting a relation to a standard form. The process

is used to handle the problems that can arise due to data redundancy i.e.

repetition of data in the database, maintain data integrity as well as

handling problems that can arise due to insertion, updation, deletion

anomalies.

Decomposing is the process of splitting relations into multiple

relations to eliminate anomalies and maintain anomalies and maintain

data integrity. To do this we use normal forms or rules for structuring

relation.

Insertion anomaly: Inability to add data to the database due to absence of other data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial update

Normal Forms: These are the rules for structuring relations that eliminate anomalies.

First Normal Form:

106


A relation is said to be in first normal form if the values in the

relation are atomic for every attribute in the relation. By this we mean

simply that no attribute value can be a set of values or, as it is

sometimes expressed, a repeating group.

Second Normal Form:

A relation is said to be in second Normal form is it is in first

normal form and it should satisfy any one of the following rules.

1) Primary key is a not a composite primary key

2) No non key attributes are present

3) Every non key attribute is fully functionally dependent on full set

of primary key.

Third Normal Form:

A relation is said to be in third normal form if their exits no

transitive dependencies.

Transitive Dependency: If two non key attributes depend on each other

as well as on the primary key then they are said to be transitively

dependent.

The above normalization principles were applied to decompose

the data in multiple tables thereby making the data to be maintained in

a consistent state.

107


Data Dictionary

After carefully understanding the requirements of the client the the

entire data storage requirements are divided into tables. The below

tables are normalized to avoid any anomalies during the course of data

entry.

108


TESTING

109


TESTING

The development of software systems involves of a series of

production activities where opportunities for injection of human

fallibilities are enormous. Errors may begin to occur at the very

inception of the process where the objectives may be erroneously or

imperfectly specified, as well as in later design and development stages.

Because of human inability to perform and communicate with

perfection, software development is accompanied by a quality assurance

activity.

5.1 Testing Techniques:-

Testing is the process of executing a program with the intention of

finding errors. The various test strategies used for testing the software

are as follows.

Unit Testing:-

Unit testing focuses on verification effort on the smallest unit of

the software design module. The main goal is to make sure that every

source statement and logic path has been executed correctly at least

once. The output of this stage is the source code.

Integration Testing:-

In Integration testing, we find errors that have occurred during

the integration. After testing each module, which is then integrated into

subsystems and then to form the entire system on which integration

testing is performed. The goal of testing is to detect the design errors,

while focusing on the testing the interconnection between modules.

110


System Testing:-

In this testing, the system is tested for the errors after coupling all

the modules together The system is tested against the specified

requirements to see if all the requirements are met and the system

performs as specified by the requirements.

Acceptance Testing:-

The testing is performed to demonstrate to the client, the

operations of the system. Here the entire software system is tested. The

goal is to see if the software developed meets its requirements. This is

essentially a validation exercise and in many situations this is the only

validation activity.

Alpha testing:-

A customer conducts the test at the developer’s site. The software

is used in a natural setting with the developer “looking over the

shoulder” of the use and recording errors and usage problems. Alpha

tests are conducted in a controlled environment.

Beta Testing:-

The beta test is conducted at one or more customer sites by the

end users of the software. The developer is generally not present.

Therefore, the beta test is the live application of the software in an

environment that cannot be controlled by the developer. The customer

records all the problems that are encountered during beta testing and

reports these to the developer at regular intervals. As a result of

problems reported during beta test, the software developer makes

111


modifications and then prepares for release of the software product to

the entire customer base.

\Maintenance: -

Maintenance accounts for the majority of the effort and cost spent

on the computer software. Maintenance activities involve making

enhancements to software products, adapting products to new

environments, and correcting problems. Software product

enhancements may involve providing new functional capabilities,

improving user displays and modes of interaction, upgrading external

documents and internal documents, or upgrading the performance f the

characteristic of the system. As more programs are developed, a

distributing trend has emerged the amount of effort and resources

expended on software maintenance are growing. Ultimately some of the

software organizations may end up spending time more on

maintenance, rather on developing new systems.

Three types of maintenance activities are performed on computer

software:-

Corrective Maintenance: - Adapted to correct errors that are

uncovers after the Software is used.

Adaptive Maintenance: - Applied to modify software to properly

interface with The changing environment.

Perfective Maintenance: - Incorporates enhancements that are

requested by the User community.

112


Software maintenance, like all the software- engineering activities,

requires both managerial and technical expertise. Maintaining the

quality of the software product through the successive cycles of

modification and updating is an issue of fundamental concern during

software maintenance.

Planning for maintenance, developing the product with an eye to

maintenance, organizing the maintenance activity and providing good

Maintenance tools can greatly improve the software quality,

programmer productivity and programmer morale.

113


SYSTEM SECURITY

114


SYSTEM SECURITY

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

System Security can be divided into four related issues:

Security

Integrity

Privacy

Confidentiality

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.

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.

115


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.

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.

. SECURITY IN SOFTWARE

System security refers to various validations on data in form of checks

and controls to avoid the system from failing. It is always important to

ensure that only valid data is entered and only valid operations are

performed on the system. The system employees two types of checks and

controls:

116


CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that

only valid data is entered. Client side validation saves server time and

load to handle invalid data. Some checks imposed are:

VBScript in used to ensure those required fields are filled with

suitable data only. Maximum lengths of the fields of the forms are

appropriately defined.

Forms cannot be submitted without filling up the mandatory data so

that manual mistakes of submitting empty fields that are mandatory

can be sorted out at the client side to save the server time and load.

Tab-indexes are set according to the need and taking into account

the ease of user while working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are

necessary to save the system from failing and intimating the user that

some invalid operation has been performed or the performed operation

is restricted. Some of the server side checks imposed is:

Server side constraint has been imposed to check for the validity of

primary key and foreign key. A primary key value cannot be

duplicated. Any attempt to duplicate the primary value results into a

message intimating the user about those values through the forms

using foreign key can be updated only of the existing foreign key

values.

User is intimating through appropriate messages about the successful

operations or exceptions occurring at server side.

117


Various Access Control Mechanisms have been built so that one user

may not agitate upon another. Access permissions to various types of

users are controlled according to the organizational structure. Only

permitted users can log on to the system and can have access

according to their category. User- name, passwords and permissions

are controlled o the server side.

Using server side validation, constraints on several restricted

operations are imposed.

118

Documents

Document