..

A
PROJECT REPORT ON

KNOWLEDGE BASED COMMUNITY SHARING

SUBMITTED TO:-

UTTAR PRADESH TECHNICAL UNIVERSITY

FOR THE PARTIAL FULFILMENT
FOR AWARDING THE DEGREE OF

MASTERS OF COMPUTER APPLICATION

SESSION (2011-2014)
BY:
Priyanka dixit
1103014042
Under The Guidance of
Mr. DEEPAK CHOUDHARY

SUBMITTED AT:-

INDERPRASTHA ENGINEERING COLLEGE ,GHAZIABAD (UP)

(MAY, 2014)

CERTIFICATE FOR EXTERNAL GUIDE

CERTIFICATE FROM INTERNAL GUIDE

Certified that PRIYANKA DIXIT has carried out the project

work presented in this report entitled KNOWLEDGE BASED
COMMUNITY SHARING the award of Master of
Computer

Application

from

Uttar

Pradesh

Technical

University, Lucknow under my supervision. The report

embodies result of work and studies carried out by Student
himself/herself (strike out whichever is not applicable) and the
contents of the report do not form the basis for the award of any
other degree to the candidate or to anybody else.

Date:

Mr. Deepak Choudhary

Designation: .Net Supervisor

ACKNOWLEDGEMENT

Nothing concrete can be achieved without an optimal of inspiration

and perspiration. No work can be accomplished without taking the
guidance of the experts. It is only the views and advice from
ingenious intellectual that help in the transformation of a product
into a quality product.
We owe my sincere gratitude to Mr. Deepak Choudhary , our
honorable project guide.

Last but not the least, no acknowledgement will be complete

without mentioning our parents. They have also supported us
throughout the development project.

Date
Place
PRIYANKA DIXIT

TABLE OF CONTENT

TITLE

PAGE NO.

1. Introduction /Objectives
1.1 Objectives
1.2 Purpose
1.3 Scope
1.4 Project Category
1.5 Tools to be used
1.6 Hardware & Software requirements
1.7 Existing System
1.8 Proposed System
1.9 Problems

2. System analysis
2.1 System Analysis
2.2 Identification of Need
2.3 Preliminary Investigation
2.4 Feasibility Study

3. Overall Description
3.1 Product Perspective
3.2 Communication Interface
3.3 Product Function
3.4 User Characteristics

4. Software Requirements Specification

4.1 Functional Requirement
4.2 Purpose of this document
4.3 Overview of document
4.4 Performance Requirement

5. Design
5.1 System Design

5.2 Software Design

5.3 Architectural Diagram
5.4 Use Case Diagram
5.5 Process Design
5.5.1 Class Diagram
5.5.2 E-R Diagram
5.5.3 DFD Diagram
5.6 Database Design

6. Screenshot
7. Coding
8. Testing & Implementation
9. Future Enhancement
10. Conclusion

11. Bibliography

1. INTRODUCTION:1.1

Objective

 It also aims to provide a platform for mutual cooperation

between different kinds of users.
Knowledge based system provides a platform for
bidirectional communication between
users/experts/faculty.
Knowledge based system also supports a platform for
discussions about various topics.
This site saves the time of students to be wasted on
searching; instead it directly gives the accurate results
from various experts.
This Knowledge based system will help for building and
maintains of other projects.
It provides a link to industry value, to remove gap
between students and industry.
It will provide standard, flexible knowledge structure,
knowledge-friendly culture.
System will help in decision making by confirming their
thoughts from experts advice.
KBS will help to reduce training time of employees by
giving direct communication between trainee and trainer.
KBS is a repository of database gives a fast access of
queries.

1.2 Purpose

The knowledge based management system (KBMS) provides a central point

to share ideas of user and experts on a common platform.

It also aims to provide a platform for mutual cooperation between different

kinds of users/ researchers/industrial experts
This gives a bidirectional communication between faculty and students,
where each can share their articles and blogs over site.
Discussions can be made over site. This system will provide a environment
to students/staff to enhance their technical skill and knowledge .Knowledge
based system also helpful to solve complex problems.

It incorporates a database of knowledge in response to specific queries.

1.2 SCOPE

Website will provide a secure registration and profile

management facilities.
System will give a centralization of database and will store
Experts conclusion, Ideas, Thoughts.
This will be treated as social networking site in future as
connecting peoples over web.

 This site can be used in no. of universities by students and

staffs for better education system.
This site can be treated as an educational hub.
This site will also be treated as advertisement of various
jobs.
We can add database for specific fields in future.
This site can be used in no. of universities by students and
staffs for better education system.
This site will also be treated as advertisement of various
jobs.
We can add online payment facility.

1.4

Project Category : Client Server Technology

1.5 Tools:Front End

Back End
Operating System

: .Net
: My SQL
: Windows 7/8

1.6 Hardware & software requirement :

Software Requirements:
Operating System

Windows 7

User Interface

HTML, CSS

Client-side Scripting

JavaScript

Programming Language

C#.Net

Technologies

ASP.Net, ADO.Net

IDE/Workbench

Visual Studio 2010

Database

SQL Server 2008

Server Deployment

Internet Information Services

Minimum Hardware Requirements:

Processor

Pentium IV

Hard Disk

40GB

RAM

1GB

10

1.7 Existing System : This existing system is not providing secure registration and profile
management of all the users properly.
This manual system gives us very less security for saving data and
some data may be lost due to mismanagement.
The system is giving only less memory usage for the users.
The system doesnt provide facility to track all the activities of
Agency-Chief and under working agents.
The system doesnt provide any facility to maintain any tips &
suggestion for Citizen.
The system doesnt provide any functionality to upload evidences in
encrypted format.
This system doesnt provide recruitment of agents through online.
The

system

doesnt

provide

any

functionality

to

Defense

Minister/Secrete Agency-Chief/Agents for online chatting.

11

1.8 Proposed System:The development of this new system contains the following activities, which
try to automate the entire process keeping in the view of database integration
approach.
This system maintains users personal, address, and contact details.
User friendliness is provided in the application with various controls
provided by system rich user interface.
This system makes the overall project management much easier and
flexible.
Various classes have been used for maintain the details of all the users
and catalog.
Authentication is provided for this application only registered users
can access.
Report generation features is provided using to generate different kind
of reports.

The system provides facilities to track the all activities of AgencyChief and Agents.

System also tracks the tips and suggestion online.

System provides facility to recruit Agents in online.

12

 System also provides facility to upload evidences in encrypted format

and view cases, related resources.
This system is providing more memory for the users to maintain data.
This system is providing accessibility control to data with respect to
users.
This system provides citizens to view success Stories

This system provides the functionality to Defense Minister/Secrete

Agency-Chief/Agents for online chatting.

13

1.9 Problems:1. Communication Interruption / Breakage.

2. No Proper communication channel.
3. Low Efficiency secrecy.
4. There is no Security.
5. Wastage of lot of valuable time in the preparation of work progress
reports.

14

SYSTEM
ANALYSIS

15

2.1 System analysis:Systems analysis is conducted with the following objectives in mind:
1. Identify the customers 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 subsequent
engineering

2.2 Identification of Need:The analyst meets the customer and the end user. The customer may
Be a representative of the company for which the software is being
Developed, or the marketing department of the developing company
Etc. here the intent is to understand the product objectives and to
Define the goals to fulfill the requirements.

2.3 Preliminary Investigation:-

16

The purpose of the preliminary investigation is to evaluate project

Request. It is not a design study nor does it include the collection of
details to describe the business system in all respects.
Analyst working on the preliminary investigations should accomplish
the following objectives:
1. Clarify and understand the project request.
2. Determine the size of the project.
3. Assess costs and benefits of alternative approaches.
4. Determine the technical and operational feasibility of alternative
approaches.
5. Report the findings to Management, with recommendations
outlining the acceptance or rejection of the proposal.

2.4 Feasibility Study:The concept of feasibility is to determine whether or not a project is

worth doing. The process followed in making this determination is
called feasibility study. Once it has been determine that a project is
feasible, the system analyst can go ahead and prepare the project
Specification which finalizes project requirements.
Types of feasibility:
1. Technical feasibility
2. Operational feasibility

17

3.
4.
5.
6.
7.

Economic feasibility
Social feasibility
Management feasibility
Legal feasibility
Time feasibility
Here we describe only few of these in detail:

2.4.1 TECHNICAL FEASIBILITY:This is concerned with specifying equipment and software that will
successfully satisfy the user requirement. Technical needs of the
system include: Facility to produce outputs in a given time
Response time under certain conditions
Ability to process a certain a volume of transaction at a
particular period
Facility to communicate data to distant location

2.4.2 OPERATIONAL FEASIBILTY:This is mainly related to human organization and political aspects. The
points to be considered are: What changes will be brought with the system?
What organizational structures are disturbed?
What new skills will be required? Do the existing staff
members have these skills? If not, can they be trained in due
course of time?

2.4.3 ECONOMIC FEASIBILITY:-

18

It looks at the financial aspects of the project. It determines whether the

management has enough resources and budget to invest in the proposed
system and the estimated time for the recovery of cost incurred. It also
determines whether it is worthwhile to invest the money in the proposed
project. Economic feasibility is determines by the means of cost benefit
analysis. The proposed system is economically feasible because the cost
involved in purchasing the hardware and the software are within
approachable. The personal cost like salaries of employees hired are also
nominal, because working in this system need not required a highly qualified
professional. The operating-environment costs are marginal. The less time
involved also helped in its economical feasibility. It was observed that the
organization has already using computers for other purpose, so that there is
no additional cost to be incurred for adding this system to its computers.
The backend required for storing other details is also the same database that
is DB2. The computers in the organization are highly sophisticated and dont
needs extra components to load the software. Hence the organization can
implement the new system without any additional expenditure. Hence, it is
economically feasible.

19

OVERALL
DESCRIPTION

20

3.1 Product Perspective: The web pages (XHTML/JSP) are present to provide the user
interface of Client side.
Communication between client and server provided through
HTTP/ HTTPS Protocols
The Client Software is providing the user interface on system user
client Side and for this TCP/ IP protocols are used.
On the server side web server is for EJB and Database server is for
storing the information.

21

3.2 Communication Interface: Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.

3.3 Product Function:Administrator:

i.

The Administrator is the super user and has complete

control over all the activities that can be performed.

ii.

Administrator checks the work of all users/editors.

iii.

Administrator checks the content to update I valid to

update or not.

Editor:
i.

Editors will check the content to be updated by user is valid

or not.

ii.

Editors will check that does the content follows of

copyrights or not.

iii.

Editors can update users Blogs.

Users:
i.

Users can ask and answer queries, Blogs, Articles

questions.

22

ii.

Access database.

3.4 User Characteristics:Every user should be comfortable of working with computer and net
browsing.
He must have basic knowledge of English too.

23

SOFTWARE
REQUIREMENTS
SPECIFICATION

24

4.1 Functional Requirement:Functional Requirement specifies which outputs should be produced from
the given inputs. They describe the relationship between the input and output
of the system. For each functional requirement, a detailed description of all
the data inputs and their source, the units of measure, and the range of valid
inputs must be specified.
All the operations to be performed on the input data to obtain the output
should be specified. This includes specifying the validation checks on the
input and output data.

4.2 Purpose of This Document:The Purpose Of this document is to convey the requirements of the project
to the programmers to ensure that the programmers understand and fulfill the
requirements to the expectation of the client.
Secondly, this document is used to ensure that the development team
understands the requirement specified by the client. This document will act
as the contract for all future development; all development spawns from and
adheres to the detail in the requirement. The SRS also outline the
performance requirements that may be set and required by the client/ user.

4.3 Overview of Document:The remainder of this document describes the intended users that would be
expected to interact with the system frequently, and a simple profile of each
user type is provided as a sample. This document now will go into more
detail on the expected users their interface and interaction with the product
and more on the technical approach and consideration to be implemented.

25

26

4.4 Performance Requirements:The Software is inherently designed to handle multiple users accessing the
same database system. Multiple user session will concurrently exist. Each
session will receive its own thread of execution which is invisible to all
other components of the system, but will provide reliability, efficiency, and
excellent response time. The actual capacity of users that the system can
handle is out of the scope of this document.

27

DESIGN

5.1 SYSTEM DESIGN:Introduction

28

System design provides the understandings and procedural details necessary

for implementing the system recommended in the system study. Emphasis is
on the translating the performance requirements into design specifications.
The design phase is a transition from a user-oriented document (System
proposal) to a document oriented to the programmers or database personnel.
System design goes through two phases of development:
1)

Logical Design

2)

Physical Design

A data flow diagram shows the logical flow of the system. For a system it
describes the input (source), output (destination), database (data stores) and
procedures (data flows) all in a format that meets the users requirement.
When analysis prepares the logical system design, they specify the user
needs at a level of detail that virtually determines the information flow into
and out of the system and the required data resources. The logical design
also specifies input forms and screen layouts.
The activities following logical design are the procedure followed in the
physical design e.g., producing programs, software, file and a working
system. Design specifications instruct the user about what the system should
do.
Logical and Output Design:
The logical design of an information system is analogous to an engineering
blue print of an automobile. It shows the major features and how they are
related to one another. The detailed specification for the new system was
drawn on the bases of users requirement data. The outputs inputs and
databases are designed in this phase.

29

Output design is one of the most important features of the information

system. When the outputs are not of good quality the users will be averse to
use the newly designed system and may not

Use the system. There are many types of output, all of which can be either
highly useful or can be critical to the users, depending on the manner and
degree to which they are used.
Outputs from computer system are required primarily to communicate the
results of processing to users; they are also used to provide a permanent hard
copy of these results for later consultation. Various types of outputs required
can be listed as below:

External Outputs, whose destination is outside the organization,.

Internal outputs, whose destination is with the organization.

Operational outputs, whose use is purely within the computer

department e.g., program-listing etc.

Interactive outputs, which involve the user is communicating

directly with the computer. It is particularly important to consider
human factor when designing computer outputs. End user must
find outputs easy to use and useful to their jobs, without quality
output, user may find the entire system unnecessary and avoid
using it. The term Output in any information system may apply
to either printer or displayed information. During the designing
the output for this system, it was taken into consideration,

30

whether the information to be presented in the form of query of

report or to create documents etc.

Other important factors that were taken into consideration are:

The End user, who will use the output.

The actual usage of the planned information

The information that is necessary for presentation

When and how often output and their format are needed.

While designing output for project based Attendance Compilation System,

the following aspects of outputs designing were taken into consideration.

The outputs (i.e., well formatted table outputs in the screen itself)
designed are simple to read and interpret.

Format of each output was another important point taken into

consideration. Output media, for each output appropriate media is
decided whether it will be displayed on screen or will be taken to
printer or both.

Other output design related specifications, i.e., how frequently the

outputs will be generated, how many pages or sheets
approximately it will keep up, what is its planned use and output
distribution to users are also taken into account.

These were a few major designing issues, which were taken into
consideration, while deciding the output specifications for the system. As

31

direct beneficiary of reports is the user community, they were consulted

constantly at every level. Formats and screen design for various reports were
identified, taking into account the user requirements. Before finalizing these
were given to users for any improvement and suggestions. End users issues
taken into consideration were Readability, Relevance and Acceptability.
Once all the output reports to be generated by ACS system were identified,
they were given to users for their acceptance. For prototyping various
outputs, final outputs models were created with dummy data, before they
were finalized.

Output Sources:
Output contents originate from these sources:

Retrieval from a data source.

Transmission from a process or system activity.

Directly from an input source.

The information produced in an output can be presented as

Tabular contents

Graphic format

Using Icons

Output Definition:

32

The output should be defined in terms of:

Types of outputs

Content-headings, numeric, alphanumeric, etc.,

Format-hardcopy, screen, microfilm, etc.,

Location-local, remote, transmitted, etc.,

Frequency-daily, weekly, hourly, etc.,

Response-immediate within a period, etc.,

Data items
The name given to each data item should be recorded and its characteristics
described clearly in a standard form:

Whether alphanumeric or numeric

Legitimate and specific range of characteristics

Number of characters

Positions of decimal point, arithmetic design, etc.,

Input Design:
The input design is the link that ties the information system into the users
world. Input specifications describe the manner in which data enters the
system for processing. Input design features can ensure the reliability of the
system and produce results from accurate data, or they can result in the
production of erroneous information.

33

Input Design consists of

developing specifications and procedures for data preparation

Steps necessary to put data into a usable form for processing.

Data entry, the activity of putting data into the computer

processing.

Objectives of Input design

Five objectives of design input focus on

Controlling the amount of input required

Avoid delay

Avoiding errors in data

Avoiding extra steps.

Keeping the process simple.

Input stages several activities have to be carried out as part of the overall
input process. They include some or all of the following.
Data recording (i.e., collection of data)
Data encapsulation (i.e., transfer of data)
Data conversion (i.e., controlling the flow of data)
Data transmission (i.e., transporting the data)
Data validation (i.e., checking the input data)
Data correction (i.e., correcting the errors)

34

Input Performa were designed, after a careful discussion with users. It was
attempted to cover all user requirements. Designed Performa were given to
user for any suggestion and final approval.
Input designs are aimed at reducing the chances of mistakes of errors. As the
human beings are prone to errors there is always a possibility of occurrence
of chance of errors. Adequate validation checks are incorporated to ensure
error free data storage. Some of the data validation checks applied are as
following:

Redundancy of data is checked. It means the records of primary

key do not occur twice.

Primary key field of any table must not be left blank.

Wherever items are coded, input code is checked for its validly
with respect to several checks.

Utmost care has been taken to incorporate the validation at each

stage of the system. E.g. when entering records into employee
information table for employee, it is checked that whether the
corresponding employee exists in the employee information table
etc.,

Enough messages and dialogue boxes are provided while design screen,
which does guide user at the time of any errors, or at time of entry. This
feature provides a user-friendly interface to native users. It can be
emphasized that input deigns of HRRP is so designed that it ensures easy
and error free data entry mechanism. Once one is sure of input data the
output formatting becomes a routine work.

35

5.2 SOFTWARE DESIGN:The purpose of this phase is to plan a solution for the problem specified by
the requirement document. This is first step in moving from the problem
domain to solution domain. Designing activity is divided into two parts.
a) System Design
It aims to identify the modules that should be in the system, the specification
of these modules and how they interact with each other to produce the
desired result.
b) Detailed Design
The internal goal of each of the modules specified in the system design is
decided.

36

5.3 Architectural Design:-

Pest asp.net artiectual disignn image from internet

37

5.4 Use Case Diagram:-

38

5.5 PROCESS DESIGN:The process can be conceptualized in such a way to keep the methodology of
main module process along with some auxiliary task, which will run
concurrently with the main program.
The top-down approach is maintained so as to keep track of the process,
which satisfies the maintenance reliability testing requirements. The
concurrency of the data is checked during data entry, by means of validation
check for data in each field.

5.5.1 Class Diagram:The class diagram is used to define the use case diagram and define a
detailed design of the system. The class diagram classifies the actors defined

39

in the use case diagram into a set of interrelated classes. The relationship or
association between the classes can be either an "is-a" or "has-a"
relationship.

40

5.5.2 E-R Diagram:ER Diagrams represent the relationship between the entities. An ER diagram
is composed of

1. Entity is shown by rectangle.

2. Attribute is shown by oval.
3. Relationships with rhombus.
4. Optional is shown by circle.
5. Compulsory with dash.
6. Primary key with underscore.
Terms used in ER DIAGRAM
Entity
An entity may be defined as a thing which is recognized as being capable of
an independent existence and which can be uniquely identified. An entity is
an abstraction from the complexities of some domain. Entities are
represented as rectangles.

Graphical Representation:

41

 Relationship
A relationship captures how two or more entities are related to one another.
Relationships are represented as diamonds, connected by lines to each of the
entities in the relationship.

Graphical Representation:

Attribute
Entities and relationships can both have attributes. Attributes are
represented as ellipses connected to their owning entity sets by a line.

Graphical Representation:

UML DIAGRAMS

42

ER DIAGRAM

Blogs
F&Q

ID

NEWS
Articles

Y/N

Login

Admin
Home

Checks
Type

GK

Blogs
F&Q

Password
N

NEWS
Articles

Editor Home

GK
Blogs

User Type

F&Q

NEWS
Articles

First Name

Last Name

Registration
(1:1)

Faculty Home

GK

Blogs
F&Q

NEWS
Articles

Confirm
Password

ID

User Home

GK

Password

43

5.5.3 Data Flow Diagram:Data Flow Diagramming is a means of representing a system at any level of
detail with a graphic network of symbols showing data flows, data stores,
data processes, and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model of
all possibilities with different detail shown on different hierarchical levels.
This processes of representing different details level is called leveling or
partitioning by some data flow diagram advocates. Like a road map, there
is no starting point or stop point, any time or timing, or steps to get
somewhere. We just know that the data path must exist because at some
point it will be needed. A road map shows all existing or planned roads
because the road is needed.
Details that is not shown on the different levels of the data flow diagram
such as volumes, timing, frequency, etc. is shown on supplementary
diagrams or in the data dictionary. For example, data store contents may be
shown in the data dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the
systems. Data Flow Diagram also known as Bubble Chart is used to clarify
system requirements and identifying the major transformations that will
become programs in system design. So it is the starting point of the design
phase that functionally decomposes the requirements specifications down to
the level of details.

44

Terms used in DFD

Process
A process transforms data values. The lowest level processes are pure
functions without side effects. An entire data flow graphics high level
process.

Graphical representation:

Graphical Representation:
Data flows
A data flow connects the output of an object or process to input of another
object or process. It represents the intermediate data value within a
computation. It is represented by an arrow and labeled with a description of
data, usually its name or type.

Graphical Representation:
Actors
An actor is active object that drives the data flow graph by producing or
consuming values.
Data store
A data store is a passive object with in a data flow diagram that stores data
for later access.

45

Graphical Representation:
External Entity
A rectangle represents an external entity such as a librarian, a library
member.

Graphical Representation:

Output Symbol
This box represented data production during human computer interaction

Graphical Representation:

46

0 level
0 Level

Data Flow Diagram

0 Level DFD is a technique that depicts information flow and the

transformations that are applied as data move from input to output.

Ask Queries

System

Solutions

Database

47

1 Level
1 Level DFD:

User

LLllad
Login
Processss
Database

Login
Home

Check User Type

Admin
Page

Editor
Page

Faculty
Page

User
Page

48

Criteria follow

Updated
Tables

User validation
New Email

New user
A R

AdminA Admin

Update
Blogs

Articles
Content Verify

Copyright Act.

Control over All users

Accurate Content

Database

Control users
Control Faculty
Control Editor

49

5.6 Database Design:A database is a collection of inter-related data stored with a minimum of
redundancy to serve many applications. It minimizes the artificiality
embedded in using separate files. The primary objectives are fast response
time to enquires, more information at low cost, control of redundancy,
clarity and ease of use, accuracy and fast recovery. The organization of data
in a database aims to achieve three major objectives, they are data
integration, data integrity and data independence. During the design of the
database at most care has been taken to keep up the objectives of the
database design.

50

SCREENSHOTS

51

CODING

52

CODE DESIGN
The process of code is to facilitate the identification and retrieve of items of
information. The code should be simple and easy to understandable. The
codes were designed in such a way that the features such as optimum human
oriented use and machine efficiency are unaffected.
For the code to be designed effectively, the following characteristics were
also considered while designing the code.
Uniqueness
Versatility
Stability
Simplicity
Consciousness

The code should be adequate for present and anticipated data processing for
machine and human use. Care was taken to minimize the clerical effort and
computer time required to continue operation.

53

TESTING

TESTING
During system testing, the system is used experimentally to ensure that the
software does not fail. Specific test data are input for processing, and the

54

results examined. It is desirable to discover any surprises before the

organization implements the system and depends on it.

TESTING OBJECTIVES:1. Testing is a process of executing a program with the intent of finding
an error.
2. A good test case is one that has a high probability of finding an as yet
undiscovered error.
3. A successful test is one that uncovers as a yet undiscovered error.

TESTING PRINCIPLES:1. All tests should be traceable to the customers requirements.

2. Tests should be planned long before the testing begins.
3. Testing should begin in the small and progress towards in the
large.
4. Exhaustive testing is not possible.
5. To be most effective, testing should be conducted by an third
independent party.

SYSTEM TESTING

55

Here the System testing involved is the most widely used testing process
consisting of five stages as shown in the figure. In general, the sequence of
testing activities is component testing, integration testing, and then user
testing. However, as defects are discovered at any one stage, they require
program modifications to correct them and this may require other stages in
the testing process to be repeated.

Unit testing

Module
testing

Sub-system
testing

System
testing

Acceptance
testing

(Component testing)

(Integration testing)

(User

testing)

56

Testing is the process of detecting errors. Testing performs a very critical

role for quality assurance and for ensuring the reliability of the software. The
results of testing are used later on during maintenance also.
Testing is vital to the success of the system. System testing makes a logical
assumption that if the parts of the system are correct, the goal will be
successfully achieved. In adequate testing or non-testing leads to errors that
may not appear until months or even years later (Remember the New York
three day power failures due to a misplaced Break statement).
This creates two problems:
1. The time lag between the cause and the appearance of the problem.
2. The time interval effect of the system errors on files and the records
on the system.
A small error can conceivably explode into a much larger problem. Effective
testing early in the process translates directly into long term cost savings
from a reduced number of errors.
Another reason for system testing is its utility as a user oriented vehicle
before implementation. The best program is worthless if it does not meet the
user requirements. Unfortunately, the users demands are often compromised
by efforts to facilitate program or design efficiency in terms of processing
time or design efficiency.
Thus in this phase we went to test the code we wrote. We needed to know if
the code compiled with the design or not? Whether the code gave the desired
outputs on given inputs? Whether it was ready to be installed on the users
computer or some more modifications were needed?

57

Through the web applications are characteristically different from their

software counterparts but the basic approach for testing these web
applications is quite similar. These basic steps of testing have been picked
from software engineering practices. The following are the steps, we
undertook:

1. The content of the Intranet site is reviewed to uncover Content

Errors. Content Errors covers the typographical errors, grammatical
errors, errors in content consistency, graphical representation and cross
referencing errors
2. The design model of the web application is reviewed to uncover the
navigation errors. Use cases, derived as a part of the analysis activity
allows a web designer to exercise each usage scenario against the
architectural and navigational design.
3. When web applications are considered the concept of unit changes. It
is not always possible to test each of these individually. Thus is the
base of the web applications the unit to be considered is the web page.
The Assembled web application is tested for overall functionality and
content delivery. The various user cases are used that test the system
for errors and mistakes.
4. The Web application is tested for a variety of environmental settings
and is tested for various configurations and upon various platforms.
The modules are integrated and integration test are conducted.

58

5. Thread based testing is done to monitor the regression tests so that the
site does not become very slow is a lot of users are simultaneously
logged on.
6. A controlled and monitored population of end users tests Intranet
application, this all comprises of the User Acceptance Testing.

Because web applications evolve continuously, the testing process is an

ongoing activity, conducted by web support staff in our case the
Organizations IS people who will finally update and manage the
application.

PSYCHOLOGY OF TESTING
The aim of testing is often to demonstrate that a program works by showing
that it has no errors. The basic purpose of testing phase is to detect the errors
that may be present in the program. Hence one should not start testing with
the intent of showing that a program works, but the intent should be to show
that a program doesnt work. Testing is the process of executing a program
with the intent of finding errors.

59

LEVELS OF TESTING
In order to uncover the errors present in different phases, we have the
concept of levels of testing. The basic levels of testing are

Client Needs

Acceptance Testing

Requirements

System Testing

Design

Integration Testing

Code

Unit Testing

Unit Testing
Unit testing focuses verification effort on the smallest unit of software i.e.
the module. Using the detailed design and the process specifications, testing
is done to uncover errors within the boundary of the module. All modules
must be successful in the unit test before the start of the integration testing
begins.
In this project each service can be thought of a module. There are so many
modules like Login, HR Department, Interviewer Section, etc. Each module
has been tested by giving different sets of inputs. When developing the

60

module as well as finishing the development, the module works without any
error. The inputs are validated when accepting them from the user.

Integration Testing
After unit testing, we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing
interfaces between modules. This testing activity can be considered as
testing the design and hence the emphasis on testing module interactions.
In this project the main system is formed by integrating all the modules.
When integrating all the modules I have checked whether the integration
effects working of any of the services by giving different combinations of
inputs with which the two services run perfectly before Integration.
SYSTEM TESTING
Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal is to see if software
meets its requirements.
Here entire HRRP has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.
ACCEPTANCE TESTING
Acceptance Testing is performed with realistic data of the client to
demonstrate that the software is working satisfactorily. Testing here is
focused on external behavior of the system; the internal logic of program is
not emphasized.

61

Test cases should be selected so that the largest number of attributes of an

equivalence class is exercised at once. The testing phase is an important part
of software development. It is the process of finding errors and missing
operations and also a complete verification to determine whether the
objectives are met and the user requirements are satisfied.
WHITE BOX TESTING
This is a unit testing method, where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors. I tested
step wise every piece of code, taking care that every statement in the code is
executed at least once. The white box testing is also called Glass Box
Testing. I have generated a list of test cases, sample data, which is used to
check all possible combinations of execution paths through the code at every
module level.
White-box test focuses on the program control structure. Test cases are
derived to ensure that all statement in the program control structure. Test
cases are derived to ensure that all statement in the program control
structure. Test cases are derived to ensure that all statement in the program
has been executed at least once during testing and that all logical conditions
have been exercised. Basis path testing, a white box technique, makes use of
program graphs (or graph matrices) to derive the set of linearly independent
test that will ensure coverage. Condition and data flow testing further
exercising degrees of complexity.
BLACK BOX TESTING
This testing method considers a module as a single unit and checks the unit
at interface and communication with other modules rather getting into

62

details at statement level. Here the module will be treated as a block that will
take some input and generate output. Output for a given set of input
combinations are forwarded to other modules.
Black-box test are designed to uncover errors functional requirement without
regard to the internal workings of a program. Black-box testing techniques
focus on the information domain of the software, deriving test cases by
partitioning the input and output domain of a program in manner that
provides through test coverage. The black-box test is used to demonstrate
that software functions are operational, that input is properly produced, and
that the integrity of external information are maintenance.

Integration Testing
Validation Testing

Validation testing

CHAPTER 10
SYSTEM SECURITY

63

IMPLEMENTATION

IMPLEMENTATION

64

A crucial phase in the system life cycle is the successful implementation of

the new system design. Implementation includes all those activities that take
place to convert from the old system to the new one. The new system may
be completely new, replacing an existing manual or automated system or it
may be major modification to an existing system. In either case, proper
implementation becomes necessary so that a reliable system based on the
requirements

of

the

organization

can

be

provided.

Successful

implementation may not guarantee improvement in the organization using

the new system, but improper installation will prevent it. It has been
observed that even the best system cant show good result if the analysis
managing the implementation do not attend to every important details. This
is an area where the system analyst needs to work with utmost care. The
system will be implemented using .net as front end my SQL server as back
end windows 8 as the platform.
For the successful implementation of a system, the training of the users of
the system plays an important role. Because even well designed system can
succeed or fail because of the way they are operated and used. Therefore, the
quality of the training received by the personnel involved with the system in
various capacities helps or hinders and may even prevent the successful
implementation of MIS. Those who are directly or indirectly related with the
system development work must know in detail with their roles will be, how
they can make efficient use of the system and what system will or will not
do for them. Therefore four system operators and users need trainee.

SYSTEM OPERATORS TRAINEE:-

65

Running of the system successfully depend on the personnel working in the

computer center. They are responsible for providing the necessary support.
Their trainee must and sure that they are able to handle or possible
operations, both routine and extra ordinary in nature. Operators trainee
should include such fundamentals as how to turn the equipment on and use
it, how to power off and knowledge of what constitutes normal operations.
The operators should also be trained on different type mal functioning, how
to recognize them and what steps should be taken whenever they arise. As
part of their trainee, operators should be given both a trouble shooting list
that identifies possible problems and remedies for them, as well as the
names and telephone numbers of individual to contact when unexpected or
unusual problem arise. Trainee also involves familiarization with run
procedures, which involves working through sequences of activities needed
to use a new system on an ongoing basis.

USER TRAINING:User may be trained on use of equipment, particularly in the case where for
example, a micro computer is in used and the individual involved in both
operator and user. In such cases user must be given training on how to
operate the system also. Questions that may be trivial to the analyst, such as
how to turn on a terminal, how to insert a disk into a micro computer or

66

when it is safe to turn if the equipment without danger of data loss, are
significant problems to new users who are not familiar with the computers.
This is also the case with our system. In most of the cases, user training
deals with the operation of the system itself, with proper attention given to
data handling techniques. It is imperative that users way properly trained in
methods of entering transactions, editing data, formulating inquiries,
deleting and inserting of records no training is complete without
familiarizing user with simple system maintenance activities. Weakness in
any aspect of training may leave to awkward situations that cause user
frustration and errors. In our project also it is necessary to train users on how
to commit the transactions. Training of operators can be organized in several
different ways most important ways to train users are enter vendor and in
service training.
IN HOUSE TRAINING:
Often the best equipment source of training on equipment in the vendor who
supplies the. Most vendors offer extensive educational programs as part of
their services. In the case of our project two, well provide training to the
users of our project.

Conversation is also important in the implementation face. Conversation is

the process of changing from the old system to the new one.
It must be properly planned and executed four methods of conversion are
common is in use.
They are:

67

1.
2.
3.
4.

Parallel systems
Direct conversion
Pilot systems
Systems face-

Each method should be considered in the light of the opportunities that it

offers and problem that it may create. However, it may be possible that
sometimes we may be forced to apply one method over others, even though
other methods may be more beneficial. In general, systems conversion
should be accomplished in shortest possible time. Long conversion periods
create problems for all persons involved including both analyst and users.

68

FUTURE
ENHANCEMENT

FUTURE ENHANCEMENT

69

 24 x 7 Availability
If the base is now the entire world, staying open 24 hours a day becomes
critical. Because system can be an automated Process, so it can stay open for
24 hours a day. So UPS support must be on server site for at least 8 hours in
case of power failure. System will remain inaccessible to users at 2:00 to
4:00 am for backup and maintenance purpose.

Dynamic Website

Many early Web implementations consisted of static HTML pages. This

becomes very difficult to manage if the number of pages gets too large. An
effective system should be largely dynamic taking advantage of technology
that automates this process rather than relying on manual processes.
Application should serve dynamic user based customized web pages to its
clients from server.

Integration with existing enterprise systems

Any existing Web site that relies on the manual duplication of data from
another system is one that can be improved. Most of the business data in the
world today exists in enterprise servers that can be connected to the Web
servers to make this process far more effective.

Provide good performance and the ability to scale

the
Server

The Web application Server should provide good performance and the
ability to manage performance with techniques, such as support for caching,
clustering, and load balancing.

providing session management capability

Web application developers should not spend valuable time worrying about
how to maintain sessions within the application. The Web Application Server
should provide these services.

70

CONCLUSION

CONCLUSION
Now at the submission of this project, we conclude that the activities during
the project benefited us immensely in sharpening our programming and
practical skills. It also helped a lot in improving our designing skills too.

71

While working on this project we got experience of how to understand and

fulfill the requirement of a person managing cybernetics.
We have taken various considerations while creating a project. Various
environmental and technical factors have been taken care of. We have tried
to handle maximum type of information.
However the project developed is time saving and user friendly. We have
tried tested up to our best to make this project fully error free and effective
in all manners. This project CYBERNETICS PROTECTOR is a result
of teamwork and has been prepared with a great efforts and enthusiasm. We
hope a positive feedback from user side and wselcome the suggestion, if any.

72