NAME:M.

SUBHASHREE

REGNO:9908004328

BRANCH:CSE

SECTION:CSE-E

SUBJECT :SOFTWARE
QUALITY
MANAGEMENT

ASSIGNMENT NO:1

TITLE:LAN MONITORING
SYSTEM

1
:

Project Title : LAN monitoring System

Abstract: Everyone knows that the Internet can be a wonderful source for useful
information as well as an indispensable mean to communicate with friends, meet new
people, play games, go shopping and perform other tasks that may have a rather
negative effect when it comes to Internet usage during office or school hours.

Due to a hidden built-in keystroke logger, administrators can track all user activities
on the network connected computers including emails sent and received, website
history, chat and social networking conversations made, etc. You may also setup this
real-time LAN monitoring system so that it will record everything to the central log
database.

This information can be later used for the deeper analysis to find out who is not
performing tasks as expected.

Scope:-

To enable administrators to track all user activities on the network connected

computers including emails sent and received website history, chat and social
networking conversations made, etc.

Purpose:-

2
With Activity Monitor, you can monitor and control all user activities within our local
network from a single administrator’s PC. Once our professional LAN monitoring
system is installed, there is no necessity to have physical access to employee or
student computers – any computer in the network can be spied remotely. From now
on we can easily keep a watchful eye on your students having necessary control over
computer and Internet usage in your classroom

Tools & Technologies used :

Front end: - VB.Net

Back end: - Oracle
System Analysis
System Analysis refers into the process of examining a situation with the intent of improving
it through better procedures and methods. System Analysis is the process of planning a new
System to either replace or complement an existing system. But before any planning is done
the old system must be thoroughly understood and the requirements determined. System
Analysis, is therefore, the process of gathering and interpreting facts, diagnosing problems
and using the information to re-comment improvements in the System. Or in other words,
System Analysis means a detailed explanation or description. Before computerized a system
under consideration, it has to be analyzed. We need to study how it functions currently, what
are the problems, and what are the requirements that the proposed system should meet.

System Analysis is conducted with the following objectives in mind:

1. Identify the customer’s need.

2. Evaluate the system concept for feasibility.

3. Perform economic and technical analysis.

4. Allocate functions to hardware, software people, database and other system elements.

5. Establish cost and schedule constraints.

6. Create a system definition that forms the foundation for all the subsequent
engineering work.

Requirement Analysis/ SRS of the Component

Software and hardware requirements:-

Front end: - VB.Net

Back end: - Oracle

Reason for choosing VB.Net:-

1) VB.Net allows network task simpler to test and implement.

3
 2) It enables the captured image to convert into the JPEG format using inbuilt
methods rather than going for complex algorithms.
3) VB.Net provides a type safe environment and it is platform independent.

Reason for choosing Oracle 8: -

1) Server software can be installed on any system, which could be an oracle

client or oracle server.
2) It is highly secured in data access.

Oracle database conventions refer to defined groups of object ownership

(generally associated with a "username") as schemas.

Most Oracle database installations traditionally came with a default schema

called SCOTT. After the installation process has set up the sample tables, the
user can log into the database with the username scott and the
password tiger. The name of the SCOTT schema originated with Bruce Scott,
one of the first employees at Oracle (then Software Development
Laboratories), who had a cat named Tiger. Oracle Corporation has de-
emphasized the use of the SCOTT schema, as it uses few of the features of the
more recent releases of Oracle. Most recent examples supplied by Oracle
Corporation reference the default HR or OE schemas.

Software specification:-

1. There must be running VB.Net .

2. There should be access to a version of SQL server supported by

VB.Net such as SQL Plus 8.0.

The operating System must be any of the following:-

Windows XP

Hardware requirements:-

The important constraint in hardware implementation for the system comes from network
It require to have all machines in the system properly configure with no ip address conflict.

For server software RAM :- 256 MB.

For client software RAM :- 128 MB.

General requirements:-
Processor:-Pentium 2.
Network interface control:-Real-tek Ethernet 10/100 adapter.

Hardware specification:-

4
 1. An Intel Pentium 300 MHz process is the mini platform required.

2. 120 MB of RAM is the mini requirement.

3. The dot net CLR requires approximately 200 MB of disk storage space.

4. A color monitor (256 colors) is recommended.

Testing:-
1. Unit testing

2. Integration testing

3. Validation testing

Software testing is a critical element of the ultimate review of specification design and
coding. Testing of software leads to the uncovering of errors in the software functional and
performance requirements are met .Testing also provides a good indication of software
reliability and software quality as a whole. The result of different phases of testing are
evaluated and then compared with the expected results. If the errors are uncovered they are
debugged and corrected. A strategy approach to software testing has the generic
characteristics:
 Testing begins at the module level and works “outwards” towards the integration of
the entire computer based system.
 Different testing techniques are appropriate at different points of time.
 Testing and debugging are different activities, but debugging must be accommodated
in the testing strategy

Goals and Objectives

“Testing is a process of executing a program with the intent of finding an error”. A good test
case is one that has a probability of finding an as yet undiscovered error. A successful test is
one that uncovers an as yet undiscovered error. Our Objective is to design test processes that
systematically uncover different classes of errors and do so with minimum amount of time
and effort.

Statement of scope

A description of the scope of the software testing is developed. All the features to be tested
are noted as follows. The basic principles that guides software testing are,

 All test cases should be traceable top customer requirements. The most severe defects
from the customer’s point of view are those that cause the program to fail to meet its
requirements.

 Test case should be planned long before testing begins. Testing plan can begin as
soon as the requirement model is complete. Detailed definition of the test cases can

5
 begin as soon as the design is solidified. Therefore, the entire test can be planned
before any code has been generated.

 Testing should begin “in the small” and progress towards “in the large”. The
first test planned and executed generally focus on the individual modules. As
testing progresses testing shifts focus in an attempt to find errors in integrating
clusters of modules and ultimately in the entire system

Test Case

Before the project is released, it has to has pass through a test cases suit, so that the
required functionality is met and previous functionality of the system is also not
broken to do this, there is an existing test cases which checks for the previous
functionality. New test cases are prepared and added to this existing test suit to check
for the added functionality.
Test case describes an input description and compare the observed output with
expected output to know the outcome of the test case. If it is different, then, there is a
failure and it must be identified.

New Test Case Output

Software
Under
Existing Test Case
Testing

Comparator

Result Of Testing

Testing Process
The testing process can be shown as:

Test Test
Levels of testing
Plan Procedures

6
 Test Case
Specification

Yes
Test Case
Execution
Is Error
Uncovered Test Case
? Analysis

No

Test Report

Following types of testing are done on the System.

a) Unit Testing
The module interface is tested to ensure that information properly flows into and out of the
program unit under test. The unit testing is normally considered as an adjunct step to coding
step. Because modules are not a standalone program, drivers and/or stubs software must be
developed for each unit. A driver is nothing more than a “main program” that accepts test
cases data and passes it to the module. A stub serves to replace the modules that are
subordinate to the modules to be tested. A stub may do minimal data manipulation, prints
verification of entry and returns.

Approaches used for Unit Testing were:

Functional Test: Each part of the code was tested individually and the panels were tested
individually on all platforms to see if they are working properly.
Performance Test: These determined the amount of execution time spent on various parts of
units and the resulting throughput, response time given by the module.

Stress Test: A lot of test files were made to work at the same time in order to check how
much workloads can the unit bear.

Structure Test: These tests were made to check the internal logic of the program and
traversing particular execution paths.

b) Integration Testing
“If they all work individually, they should work when we put them together.” The
problem of course is “putting them together “. This can be done in two ways:
Top down integration: Modules are integrated by moving downwards through the control
hierarchy, beginning with main control module are incorporated into the structure in either a
depth first or breadth first manner.

Bottom up integration: It begins with construction and testing with atomic modules i.e.
modules at the lowest level of the program structure. Because modules are integrated from the

7
bottom up, processing required for the modules subordinate to a given level is always
available and the need of stubs is eliminated.

• Testing includes

 Verification and Validation

 Verification:-is a process of confirming that software meets its
specification.
 Validation:- is the process of confirming that software meets the
customer’s requirements.

c) Validation Testing

Validation succeeds when software functions in a manner that can be reasonably expected by
the customer. It covers the following :-

Validation test criteria: Performance, functional characteristics and uncovered deviation

from specification

Configuration review: Ensures that all the elements of software configuration have been
properly developed cataloged and have support for the maintenance phase of software life
cycle

Alpha Beta testing: Alpha test is conducted by developer’s site by customer. Beta test is
conducted at one or more customer site by software end user

Modular integration testing:

Modular integration testing is done to ensure that the module is working independently. The
inputs as required by the module are given as required and the output is tested as per the
specifications