network log managment

8/11/2019 Network Log Managment

1/31

A

Project Report

On

Network Log Management

1


2/31

CHAPTER 1

INTRODUCTION

A network log is a text file containing detailed information about network related events.

Most of the organization they connect more numbers of systems to form a network to

make their work easier to share their files and folders. While connecting we want to

monitor the network system activities for secure purpose. This ro!ect deals with

monitoring the "etwork #creen Activities. $t has two methodologies one for %lient and

another for #erver. $n the proposed system we introduce current session option to monitor

the network systems at the same time and in the accesses folder option shows the

username and user accessed folders. While client logins to the server& the %lient $

Address and #ystem names are added to the server. #erver will display all the user names&

from server we can monitor the particular %lient #creen Activities like that currently

opened screens& what are all the files created& modified and deleted.

'emote (esktop #ervices is one of Microsoft Windows components to access a

remote computer through the network. )nly the user interface of the application is

presented at the client. Any input is redirected over to the remote computer over thenetwork. At work& we use 'emote (esktop a great deal. $t allows us to login to a remote

server to perform health checks& deploy applications& troubleshoot problems& etc. We also

use remote desktop often when we do W*+ ,work from home-.

This pro!ect is an effort in to develop a simple $ #ubnet %alculator tool only for

class % $. The $ #ubnet %alculator was to give the user a uick and interactive method

to calculate available subnet and hosts. (ue to the repetitiveness of such calculates& tools

such as an $ #ubnet %alculator were developed to eliminate common mathematical

mistakes. *urthermore& these tools also provide a means for the user to do such

calculations without actually understanding the details behind calculating $ subnets.

/ou have several choices for your email client application& including a range of

web email services. +owever& many people prefer to use a stand0alone application


3/31

designed specifically for email since they sometimes have a better focus and features.

#ome people avoid the Microsoft )utlook application because of its historic vulnerability

to viruses.

11 O!ject"on o# t$e project

$n )rder to be able to define our system architecture& we must first dearly state what

our ob!ective that will driver system behavior at the same one of our ob!ective is to create

an experience& which is not only uniue to the ,user- client& but also makes him feel that

he has loyal attachment to the system and approaches us whenever he she needs.

To achieve better results and success by implement computerize

ed process instead of manual process.

1% Mo&'(e an& t$e"r De)cr"pt"on

This pro!ect having *ive Modules

1. Admin1. 2iew& delete all 'emote screens and user logs

. 3ser 1. 3ser )nly view log

1A&m"nThe 4ogin module consists of username and password. This process is for

authentication.$f the hard drives of an employee5s computer and a system administrator5s

computer are connected& a system administrator can view the log files remote(*. The

administrator has to have access to the drive to check files remotely. )therwise& a system

administrator can check the computer before an employee comes in or after the employee

leaves for the day.

% Network Mon"tor"ng +*)tem,The most of the organization they connect more numbers of systems to form a

network to make their work easier to share their files and folders. While connecting we

6


4/31

want to monitor the network system activities for secure purpose. This ro!ect deals with

monitoring the "etwork #creen Activities. $t has two methodologies one for %lient and

another for #erver. $n the proposed system we introduce current session option to monitor

the network systems at the same time and in the accesses folder option shows the

username and user accessed folders. While client logins to the server& the %lient $

Address and #ystem names are added to the server. #erver will display all the user names&

from server we can monitor the particular %lient #creen Activities like that currently

opened screens& what are all the files created& modified and deleted

- Remote De)ktop Mon"tor"ng'emote (esktop #ervices is one of Microsoft Windows components to access a

remote computer through the network. )nly the user interface of the application is

presented at the client. Any input is redirected over to the remote computer over the

network. At work& we use 'emote (esktop a great deal. $t allows us to login to a remote

server to perform health checks& deploy applications& troubleshoot problems& etc. We also

use remote desktop often when we do W*+ ,work from home-.

.U)er Log

The user log contains events logged by user . *or example& a database program

may record a file error in the application log. 7vents that are written to the

application log are determined by the developers of the software program. #ecurity

log & The security log records events such as valid and invalid logon attempts& as

well as events related to resource use& such as the creating& opening& or deleting of

files. *or example& when logon auditing is enabled& an event is recorded in the

security log each time a user attempts to log on to the computer. /ou must be

logged on as Administrator or as a member of the Administrators group in order to

turn on& use& and specify which events are recorded in the security log. #ystem log &

The system log contains events logged by Windows 8 system components. *or

example& if a driver fails to load during startup& an event is recorded in the system

log. Windows 8 predetermines the events that are logged by system components.

9


5/31

CHAPTER -

CU+TOMER RE/UIREMENT+ DETERMINATION

-1E0")t"ng )*)tem

The existing system has been maintained manually. The system& which has

been maintained manually& had been complex and complicated. There were many

chances to loss the data and the work wouldn:t be an effective and efficient one.

Manual operation is always been complicated to the organizations for maintaining the

records. $n the existing system

$n this system we can:t monitor who all are accessing the files at the same time.

$t:s difficult to find which are the files are updated and renamed.

Draw!ack) o# t$e e0")t"ng )*)tem

Maintenance of the system is very difficult.

7mployee:s attentions are needed for maintaining the system.

There is a possibility for getting inaccurate results.

3ser friendliness is very less.

;


6/31

$t consumes more time for processing the activities.

-%Propo)e& )*)tem

%onsidering the anomalies in the existing system computerization of the whole

activity is being suggested after initial analysis by the organization.

$n this system we can monitor who all are accessing the files in the network at the

same time. When monitoring the connected systems& we can easily found what are the files

updated and renamed.

ADANTA2E+ O3 THE PROPO+ED +4+TEM

*ully #ecured

'ole based access

7ase in maintenance

"otification about the modification


7/31

CHAPTER .

+O3T5ARE RE/UIREMENT+ +PECI3ICATION

#oftware 'euirements #pecification ,#'#- is the starting point of the software

development activity. 4ittle importance was given to this phases in the early days of

software development. The emphasis was first on coding and then shifted to design.

As systems grew more complex& it become evident that the goal of the entire

system cannot be easily comprehended. +ence need for the reuirements analysis phase

arose. "ow& for large software systems& reuirements analysis is perhaps the most

difficult activity and also the most error prone.

#ome of the difficulty is due to the scope of this phase. The software pro!ect is

imitated by the client needs. $n the beginning these needs are in the minds of various

people in the client organization. The reuirement analyst has to identify the reuirements

by tacking to these people and understanding their needs. $n situations where the software

is to automated a currently manuals process& most of the needs can be understood byobserving the current practice.

The #'# is a means of translating the ideas in the minds of the clients ,the output-

into formal document ,the output of the reuirements phase-. Thus the output of the

phase is a set of formally specified reuirements& which hopefully are complete and

consistent& while the input has none of these properties.

=


8/31

.% Per#ormance Re6'"rement)The pro!ect must the end user reuirements. Accuracy and fast must be imposed

in the ro!ect.The pro!ect is development as easy as possible for the sake of end user. The

pro!ect has to be developed with view of satisfying the future reuirements and future

enhancement.The tool has been finally implemented satisfying the needs specified by the company. As

per the performance is concerned this system said is performing

This processing as well as tine taken to generate well reports where also even when large

amount of data was used. The system is designed in such a way that even when large

amount of data used for processing there would less performance degradation.

.- Inter#ace re6'"rement)

.-1 Har&ware Inter#ace

The stranded input device like keyboard and mouse are to get input. The output

will be generated and display in the monitor. The reports can also be exported to a #>40

server document are text file. The stranded printer in used to take outputs.

?


9/31

.-% +o#tware Inter#ace

The design part and interface id done the front end A#."et and #>4 server as a

backend of the pro!ect.

.. Operat"ona( re6'"rement)

The database or databases that are being failed over to the stand by server cannot

be used for anything else. @ut databases on the standby server not being used for failover

can still be used normally.

When it comes time for actual failover& you much one of two things to make your

application work either rename the standby server the same name as the failed production

server,and the $ address-&or re0point your user:s applications to new standby server in

some cases& neither of this option is practical.

.7 Re)o'rce Re6'"rement)

.71 Har&ware Re6'"rement)

')%7##)' 7"T$3M $$$ ?4 #7'27' DD;

.8 +ec'r"t* Re6'"rement)

G


10/31

Web application are available via network access& it is a difficult. $f not possible&

to limit the population of the end0user who may access the applicationsH $n order to

product sensitive connect and provide secure mode be implemented throughout the

infrastructure that the supports web application and within the application itself.

Web Application have become heavy integrated with critical corporate and

database.70commerce application extracts and then store sensitive customer information.

.9 De)"gn Re6'"rement)To create pro!ect& add base masters and masters to the pro!ect& assign

behaviors to the master& create and assign behavior sets& and then apply& test and validate

those behaviors. $t also shows how to create and build a stencil to hold the shapes.

.: /'a("t* an& Re("a!"("t* Re6'"rement)A software component that is developed for reuse would be correct and would

contain no defects. $n reality& formal verification is not carried out routinely& and defects

can add to occur.+owever&with each reuse&&defects are found eliminated& and a

components ualify improve as a result. )ver time the components virtually defect free.#oftware reliability is defined in statical term asB the probability of faultier0free

operation of a computer program in a specified environment for specified tineB. The

software uality and reliability& failure is nonconformance to software reuirements.

*ailure can be only anything or catastrophic. one failure can be corrected within seconds

while another reuirements week even mouths to correct. %omplicating the issue even

further& the correction of the one failure may in fact result in the introduction of the errors

that ultimately result in other failure.

Web %orrect link processing

Application 'eliability 7rror recovery

>uality $nput validation and recovery

1D


11/31

CHAPTER 7

+4+TEM ANAL4+I+

$n this section discussed about data flow diagram& 7ntity relationship diagram. these

things are represented as diagrams with proper notation.

71 Data 3(ow D"agram

The data flow diagram is one of the most improvement tools used by the system

analyst (eMacro ,1G=?- "ad Eand #arson ,1G=G- popularized the use if the data flow

diagram as modeling tools through their structured system analysis methodologies.

A data flow diagram should be the first tool used by system analyst to model

system components. These components are the system processesI the data used by this

processes and external entities that interact with the system and the information flows in

the system.

There are four kinds of system components

711 Proce))

rocess show what system does. 7ach process has one or more data inputs and

produce one or more data output& %ircles in a data flow diagram represent process. 7achprocess has uniue name and number. This name and number appear inside the circle

that represents the processes in a data flow diagram.

This process is represented as circle

11


12/31

71% Data +tore)

*ile or data store is depositary of data. They contain data that is retained

in the system. rocesses can enter the data into a data store or retrieve data from the data

store. 7ach data store is represented by thin line in the data flow diagram and each data

store has a uniue name.

The data store is represented in form of a line

71- E0terna( Ent"t"e)

7xternal entities are outside the system but they either supply input data

into the system or use the system output& they are entities which the designer has no

control. #uare or rectangle may represent external entities that supply data into a system

or some times called sources. 7xternal entities that use the system data are sometimes

called sinks.

71. Data 3(ow)

(ataflow model the passage of data in the system and are represented lines

!oining system components. An arrow indicates the direction of the flow and the line

labeled by the name of the data flow.

1


13/31

16


14/31

CHAPTER 8

+4+TEM DE+I2N

(esign is multi0step process that focuses on data structure software architecture&

procedural details& ,algorithms etc.- and interface between modules. The design process

also translates the reuirements into the presentation of software that can be accessed for

uality before coding begins.

%omputer software design changes continuously as new methodsI better analysis

and broader understanding evolved. #oftware (esign is at relatively early stage in its

revolution.

Therefore& #oftware (esign methodology lacks the depth& flexibility and

uantitative nature that are normally associated with more classical engineering

disciplines. +owever techniues for software designs do exist& criteria for design ualities

are available and design notation can be applied.

81 INPUT DE+I2N

$nput design is the process of converting user0originated inputs to a computer0

based format. $nput design is one of the most expensive phases of the operation ofcomputerized system and is often the ma!or problem of a system.

$n the pro!ect& the input design is made in various web forms with various

methods. *or example& in the Admin form& the empty username and password is not

allowed. The username if exists in the database& the input is considered to be invalid and

is not accepted.

8% OUTPUT DE+I2N

)utput design generally refers to the results and information that are generated by

the system for many end0usersI output is the main reason for developing the system and

the basis on which they evaluate the usefulness of the application.

19


15/31

$n the pro!ect& if the employee has to communicate with other employees they can

communicate through send and receive message.

8- INTER3ACE DE+I2N

The )(@% ,)pen (atabase %onnectivity- interface is a pure ."7T to execute

#>4 statement. The )(@% provides a set classes and interfaces that can be used by

developers to write database applications. @asic )(@% interactions in its simplest form&

can be broken down into four steps

1. )pen a connection to the database.

. 7xecute a #>4 statement

6. rocess the result

9. %lose the connection to the database

8. TA;LE AND DATA;A+E DE+I2N,

8.1 Norma("


16/31

8.1- THIRD NORMAL 3ORM,

A table is said to be in third normal form and every non key attribute is

functionality dependent only on the primary key. This normalization process is applied to

this system and the normalized tables are given in the above section.

TA;LE DE+I2N

A&m"n Log"n Ta!(e

8.% Data!a)e De)"gn,

The database design is a must for any application developed especially more for

the data store pro!ects. #ince the chatting method involves storing the message in the

table and produced to the sender and receiver& proper handling of the table is a must.

$n the pro!ect& login table is designed to be uniue in accepting the username and

the length of the username and password should be greater than zero

The complete listing of the tables and their fields are provided in the annexure

under the title JTable #tructure:.

87 3RONT END DE+I2N

A high0level programming language developed by #un Microsystems. Kava was

originally called OAK,and was designed for handheld devices and set0top boxes. )ak

1


17/31

was unsuccessful so in 1GG; #un changed the name to Kava and modified the language to

take advantage of the burgeoning World Wide Web.

Kava is an ob!ect0oriented language similar to %LL& but simplified to eliminate language

features that cause common programming errors. Kava source code files ,files with

a .javaextension- are compiled into a format calledbytecode ,files with

a .classextension-& which can then be executed by a Kava interpreter. %ompiled Kava code

can run on most computers because Kava interpreters and runtime environments& known

asJava Virtual Machines (VMs),exist for most operating systems& including 3"$8&

the Macintosh )#& and Windows. @yte code can also be converted directly into machine

language instructions by a !ust0in0time compiler ,K$T-.

Kava is a general purpose programming language with a number of features that make the

language well suited for use on the World Wide Web. #mall Kava applications are called

Kava applets and can be downloaded from a Web server and run on your computer by a

Kava0compatible Web browser& such as "etscape or Microsoft $nternet 7xplorer.

=a>ais a programming language originally developed by Kames Eosling at #un

Microsystems ,which is now a subsidiary of )racle %orporation- and released in 1GG; as

a core component of #un Microsystems5 Kava platform. The language derives much of

its syntax from %and %LL but has a simpler ob!ect model and fewer low0level facilities.

Kava applications are typically compiled tobytecode,class file- that can run on any Kava

2irtual Machine ,K2M- regardless of computer architecture. Kava is a general0purpose&

concurrent& class0based& ob!ect0oriented language that is specifically designed to have as

few implementation dependencies as possible. $t is intended to let application developers

write once& run anywhere. Kava is currently one of the most popular programming

languages in use& and is widely used from application software to web applications.

The original and reference implementation Kava compilers& virtual machines& and class

libraries were developed by #un from 1GG;. As of May DD=& in compliance with the

specifications of the Kava %ommunity rocess& #un relicensed most of its Kava

technologies under the E"3 Eeneral ublic 4icense. )thers have also developed

1=
http://en.wikipedia.org/wiki/C_(programming_language)http://en.wikipedia.org/wiki/Java_bytecodehttp://en.wikipedia.org/wiki/Java_bytecodehttp://en.wikipedia.org/wiki/C_(programming_language)


18/31

alternative implementations of these #un technologies& such as the E"3 %ompiler for

Kava& E"3 %lasspath& and (alvik.

Pr"nc"p(e) o# =a>a

There were five primary goals in the creation of the Kava language

1. $t should be simple& ob!ect oriented& and familiar.

. $t should be robust and secure.

6. $t should be architecture neutral and portable.

9. $t should execute with high performance.

;. $t should be interpreted& threaded& and dynamic.

Java Platform

)ne characteristic of Kava is portability& which means that computer programs written in

the Kava language must run similarly on any supported hardwareNoperating0system

platform. This is achieved by compiling the Kava language code to an intermediate

representation calledKava bytecode& instead of directly to platform0specific machine

code. Kava bytecode instructions are analogous to machine code& but are intended to

be interpreted by a virtual machine ,2M- written specifically for the host hardware. 7nd0

userscommonly use aKava 'untime 7nvironment,K'7- installed on their own machine

for standalone Kava applications& or in a Web browser for Kava applets.

#tandardized libraries provide a generic way to access host0specific features such as

graphics& threading& and networking.

A ma!or benefit of using bytecode is porting. +owever& the overhead of interpretation

means that interpreted programs almost always run more slowly than programs compiled

to native executables would. Kust0in0Time compilers were introduced from an early stage

1?
http://en.wikipedia.org/wiki/Dalvik_(software)http://en.wikipedia.org/wiki/Java_bytecodehttp://en.wikipedia.org/wiki/Java_bytecodehttp://en.wikipedia.org/wiki/End-userhttp://en.wikipedia.org/wiki/End-userhttp://en.wikipedia.org/wiki/Java_Virtual_Machinehttp://en.wikipedia.org/wiki/Java_Virtual_Machinehttp://en.wikipedia.org/wiki/Applethttp://en.wikipedia.org/wiki/Thread_(computer_science)http://en.wikipedia.org/wiki/Computer_networkhttp://en.wikipedia.org/wiki/Dalvik_(software)http://en.wikipedia.org/wiki/Java_bytecodehttp://en.wikipedia.org/wiki/End-userhttp://en.wikipedia.org/wiki/End-userhttp://en.wikipedia.org/wiki/Java_Virtual_Machinehttp://en.wikipedia.org/wiki/Applethttp://en.wikipedia.org/wiki/Thread_(computer_science)http://en.wikipedia.org/wiki/Computer_network


19/31

that compile bytecodes to machine code during runtime. )ver the years& this K2M built0in

feature has been optimized to a point where the K2M5s performance competes with

natively compiled % code.

Implementations

#un Microsystems officially licenses the Kava #tandard 7dition platform for 4inux& Mac

)# 8&and #olaris. Although in the past #un has licensed Kava to Microsoft& the license

has expired and has not been renewed. Through a network of third0party vendors and

licensees&O9Palternative Kava environments are available for these and other platforms.

#un5s trademark license for usage of the Kava brand insists that all implementations be

compatible. This resulted in a legal dispute with Microsoft after #un claimed that the

Microsoft implementation did not support 'M$ or K"$ and had added platform0specific

features of their own. #un sued in 1GG=& and in DD1 won a settlement of 3#QD million&

as well as a court order enforcing the terms of the license from #un.As a result& Microsoft

no longer ships Kava with Windows& and in recent versions of Windows& $nternet

7xplorer cannot support Kava applets without a third0party plugin. #un& and others& have

made available free Kava run0time systems for those and other versions of Windows.

latform0independent Kava is essential to the Kava 77 strategy& and an even more rigorous

validation is reuired to certify an implementation. This environment enables portable

server0side applications& such as Web services& Kava #ervlets& and 7nterprise Kava@eans&

as well as with embedded systems based on )#Ei&using 7mbedded Kava environments.

Through the newElass*ishpro!ect& #un is working to create a fully functional&

unified open source implementation of the Kava 77 technologies.

#un also distributes a superset of the K'7 called the Kava (evelopment Cit ,commonly

known as the K(C-& which includes development tools such as the Kavacompiler& Kavadoc&Kar&and debugger.

Performance

rograms written in Kava have a reputation for being slower and reuiring more memory

than those written in %.+owever& Kava programs5 execution speed improved significantly

1G
http://en.wikipedia.org/wiki/Java_(programming_language)#cite_note-23http://en.wikipedia.org/wiki/OSGihttp://en.wikipedia.org/wiki/OSGihttp://en.wikipedia.org/wiki/GlassFishhttp://en.wikipedia.org/wiki/GlassFishhttp://en.wikipedia.org/wiki/Java_compilerhttp://en.wikipedia.org/wiki/Java_compilerhttp://en.wikipedia.org/wiki/Javadochttp://en.wikipedia.org/wiki/Javadochttp://en.wikipedia.org/wiki/JAR_(file_format)http://en.wikipedia.org/wiki/JAR_(file_format)http://en.wikipedia.org/wiki/Java_(programming_language)#cite_note-23http://en.wikipedia.org/wiki/OSGihttp://en.wikipedia.org/wiki/GlassFishhttp://en.wikipedia.org/wiki/Java_compilerhttp://en.wikipedia.org/wiki/Java_compilerhttp://en.wikipedia.org/wiki/Javadochttp://en.wikipedia.org/wiki/JAR_(file_format)


20/31

with the introduction of Kust0in0time compilation in 1GG=N1GG? for Kava 1.1&the addition

of language features supporting better code analysis ,such as inner classes& #tring@uffer

class& optional assertions& etc.-& and optimizations in the Kava 2irtual Machine itself& such

as +ot#potbecoming the default for #un5s K2M in DDD.

To boost even further the speed performances that can be achieved using the Kava

language& #ystronix made K#tik&a microcontroller based on the aKile #ystems line of

embeddedKava processors. $n addition& the widely used A'M family of %3s has

hardware support for executing Kava bytecode through itsKazelleoption.

A'tomat"c memor* management

Kava uses an automatic garbage collector to manage memory in the ob!ect lifecycle. The

programmer determines when ob!ects are created& and the Kava runtime is responsible for

recovering the memory once ob!ects are no longer in use. )nce no references to an ob!ect

remain& the unreachable memory becomes eligible to be freed automatically by the

garbage collector. #omething similar to a memory leak may still occur if a programmer5s

code holds a reference to an ob!ect that is no longer needed& typically when ob!ects that

are no longer needed are stored in containers that are still in use. $f methods for a

nonexistent ob!ect are called& a null pointer exception is thrown.

)ne of the ideas behind Kava5s automatic memory management model is that

programmers can be spared the burden of having to perform manual memory

management. $n some languages& memory for the creation of ob!ects is implicitly

allocated on the stack& or explicitly allocated and deallocated from the heap. $n the latter

case the responsibility of managing memory resides with the programmer. $f the program

does not deallocate an ob!ect& a memory leak occurs. $f the program attempts to access or

deallocate memory that has already been deallocated& the result is undefined and difficult

to predict& and the program is likely to become unstable andNor crash. This can be

partially remedied by the use ofsmart pointers& but these add overhead and complexity.

"ote that garbage collection does not prevent logical memory leaks& i.e. those where

the memory is still referenced but never used.

D
http://en.wikipedia.org/wiki/HotSpothttp://en.wikipedia.org/wiki/JStikhttp://en.wikipedia.org/wiki/JStikhttp://en.wikipedia.org/wiki/Jazellehttp://en.wikipedia.org/wiki/Jazellehttp://en.wikipedia.org/wiki/Jazellehttp://en.wikipedia.org/wiki/Dynamic_memory_allocationhttp://en.wikipedia.org/wiki/Smart_pointerhttp://en.wikipedia.org/wiki/Smart_pointerhttp://en.wikipedia.org/wiki/HotSpothttp://en.wikipedia.org/wiki/JStikhttp://en.wikipedia.org/wiki/Jazellehttp://en.wikipedia.org/wiki/Dynamic_memory_allocationhttp://en.wikipedia.org/wiki/Smart_pointer


21/31

Earbage collection may happen at any time. $deally& it will occur when a program is idle.

$t is guaranteed to be triggered if there is insufficient free memory on the heap to allocate

a new ob!ectI this can cause a program to stall momentarily. 7xplicit memory

management is not possible in Kava.

Kava does not support %N%LL style pointer arithmetic& where ob!ect addresses and

unsigned integers ,usually long integers- can be used interchangeably. This allows the

garbage collector to relocate referenced ob!ects and ensures type safety and security.

As in %LL and some other ob!ect0oriented languages& variables of Kava5s primitive data

types are not ob!ects. 2alues of primitive types are either stored directly in fields ,for

ob!ects- or on the stack ,for methods- rather than on the heap& as commonly true for

ob!ects ,but see 7scape analysis-. This was a conscious decision by Kava5s designers for

performance reasons. @ecause of this& Kava was not considered to be a pure ob!ect0

oriented programming language. +owever& as of Kava ;.D& auto boxing enables

programmers to proceed as if primitive types were instances of their wrapper class.

88 ;AC? END DE+I2N

3EATURE+ O3 +/L@+ERER % The )4A #ervices feature available in #>4 #erver version =.D is now called

#>4 #erver DDD Analysis #ervices. The term )4A #ervices has been replaced with the

term Analysis #ervices. Analysis #ervices also includes a new data mining component.

The 'epository component available in #>4 #erver version =.D is now called Microsoft

#>4 #erver DDD Meta (ata #ervices. 'eferences to the component now use the term

Meta (ata #ervices. The term repository is used only in reference to the repository engine

within Meta (ata #ervice

#>40#7'27' database consist of six type of ob!ects&

They are&

1


22/31


23/31

A form is used to view and edit information in the database record by record .A

form displays only the information we want to see in the way we want to see it.

*orms use the familiar controls such as textboxes and checkboxes. This makes

viewing and entering data easy.

"ew) o# 3orm

We can work with forms in several primarily there are two views&

They are&

1 De)"gn "ew

% 3orm "ew

De)"gn "ew

To build or modify the structure of a form& we work in forms design view. We

can add control to the form that are bound to fields in a table or uery& includes

textboxes& option buttons& graphs and pictures.

3orm "ew

The form view which display the whole design of the form.

REPORT

A report is used to vies and print information from the database. The report can

ground records into many levels and compute totals and average by checking values

from many records at once. Also the report is attractive and distinctive because we

have control over the size and appearance of it.

MACRO

A macro is a set of actions. 7ach action in macros does something. #uch

as opening a form or printing a report .We write macros to automate the common

tasks the work easy and save the time.

89 A(gor"t$m U)e&

6


24/31

#tep1 The username and password is entered it redirectly to the next

page.

#tep To view the main network page& after it may be share folder to the current

session.

#tep6 The next page contsins the details of the client of sharing other systems.

#tep9 After the form contains the uset details may be view of the current session.

#tep; The next page contains the $ #ubnet calculator& you must enter the $

address and then calculate the range of netmask.

#tep


25/31

CHAPTER :

+4+TEM TE+TIN2

#ystem testing involves user training system testing and successful running of the

developed proposed system. The user tests the developed system and changes are made

according to their needs. The testing phase involves the testing of developed system using

various kinds of data.

An elaborate testing of data is prepared and the system is tested using the test

data. While testing& errors are noted and the corrections are made. The corrections are

also noted for the future use. The users are trained to operate the developed system.

TE+TIN2

#ystem testing is the stage of implementation that is aimed at ensuring that the

system works accurately and efficiently before live operation commences. Testing is vital

;


26/31

to the success of the system. #ystem testing makes logical assumption that if all the parts

of the system are correct& then the goal will be successfully achieved. A series of testing

are done for the proposed system before the system is ready for the user acceptance

testing.

The following are the types of Testing

1. 3nit Testing

2. $ntegration Testing

6. 2alidation Testing

9. 2erification testing

;. 3ser acceptance testing

B1 Un"t Te)t"ng

3nit testing focuses verification efforts on the smallest unit of the software

design& the module. This is also known as Rmodule testingB. The modules are tested

separately. This testing was carried out during programming stage itself. $n this testing

each module is found to be working satisfactorily as regards to the expected output from

the module.

B% Integrat"on Te)t"ng

(ata can be lost across an interface one module can have adverse efforts on

another. $ntegration testing is the systematic testing for construction of program structure&

while at the same time conducting tests to uncover errors associated within the interface.

+ere correction is difficult because the isolation of cause is complicated by the cast

expense of the entire program. Thus in the integration testing step& all the errors

uncovered are corrected for the next testing steps.

B- a("&at"on Te)t"ng

At the conclusion of integration testing& software is completely assembled as a

package& interfacing errors have been uncovered and corrected and a final series of

software tests begins validation test has been conducted one of the two possible


27/31

conditions exists. )ne is the function or performance characteristics confirm to

specification and are accepted and the other is deviation from specification is uncovered

and a deficiency list is created.

B. er"#"cat"on Te)t"ng

2erification is a fundamental concept in software design. This is the bridge

between customer reuirements and an implementation that satisfies those reuirements.

This is verifiable if it can be demonstrated that the testing will result in an

implementation that satisfies the customer reuirements.

B7 U)er Acceptance Te)t"ng

3ser acceptance testing of a system is the key factor of the success of any system.

The system under study is tested for the user acceptance by constantly keeping in touch

with the prospective system users at any time of developing and making changes

whenever reuired.

CHAPTER B

PRO;LEM+ 3ACED

When there is a clear goal in sight but no clear set of directions or means to attain

that goal& then it is called a problem. problems can be broken down into four aspectsI

goal& givens& means of transforming conditions& and obstacles.

2oa( the goal is the desired end state which the problem solving is being directed

toward.The hope is to reach that end state and be able to assess whether or not you achieved what

you wanted.

2">en)@these are the ob!ects & conditions &and constraints that accompany a problem &and

can be either explicit or implicit.

=


28/31

Mean) o# tran)#orm"ng con&"t"on)0 there should be a way of changing the initial stateof

the problem.this is most usually a person:s knowledge or skill level. *or instance &a

computer programmer presented with a problem would utilize his or her knowledge of

programming language to transform the state of the problem.

O!)tac(e)0 the problem should present a challenge.if there are no challenges involved

and the situation can be easily solved then it is not so a problem so much as a rountine

task.

7very problem has a pro!(em #ace&& which is the whole range of possible states

and operators.only some of these states and operators will bring the person closer to the

goal state. The problem starts at the "n"t"a( )tate and operator)are applied to change the

state& creating a series of intermediate states that should hopefully lead to the final goal

state

CHAPTER 1

3UTURE PLAN+

7very application has its own merits and demerits. The pro!ect has covered

almost all the reuirements. *urther reuirements and improvements can easily be done

since the coding is mainly structured or modular in nature. %hanging the existing

modules or adding new modules can append improvements. *urther enhancements can be

made to the application& so that the web site functions very attractive and useful manner

than the present one

?


29/31

CONCLU+ION

$t is concluded that the application works well and satisfy the admin and user .

The application is tested very well and errors are properly debugged. The application is

simultaneously accessed from more than one system. #imultaneous login from more than

one place is tested.

The application works according to the restrictions provided in their respective

browsers. *urther enhancements can be made to the application& so that the application

functions very interactive and useful to existing application .The application satisfies both

the company and students by eliminating more input. The speed of the transactions

become more enough now.

G


30/31

6D


31/31

network log managment

Documents