Website: Government Employment office

CHAPTER-1
INTRODUCTION

Page 1 of 32
 Website: Government Employment office

CHAPTER -1
INTRODUCTION

India is a developing country, and most of the youth power is getting waste due to
unemployment. This project is fully concern to the government employment office. The
government employment office is a department of Government of India, which is running at
the district level.

This website allows one to create account on this site, and provide the latest updates of current
vacancies and latest employment news. The registered member can also put their queries and
get quick response.

This website is easy to operate and even any common man can get up to date information and
can directly contact to the Government Employment office.

1.1 CURRENT SYSTEM:

There is not any site regarding to Government Employment office until now.

1.2 NEED OF PROPOSED SYSTEM

As the employment office is the extension of Government of India, then this site may prove
itself a better communication bridge between Government Employment office and common
man.

Page 2 of 32
 Website: Government Employment office

CHAPTER-2
LITERATURE SURVEY

Page 3 of 32
 Website: Government Employment office

CHAPTER - 2
LITERATURE SURVEY

Page 4 of 32
 Website: Government Employment office

CHAPTER-3
ANALYSIS

Page 5 of 32
 Website: Government Employment office

CHAPTER – 3
ANALYSIS

The word System is derived from the Greek word Systema, which means an organized
relationship among functioning units or components. A system exists because it is designed to
achieve one or objectives. In other words “System is an orderly grouping of interdependent
components linked together according to a plan to achieve a specific objective”.

It is a detailed study of various operations performed by a system and their relationship within
and outside of the system. One aspect of analysis is defining the boundaries of the system and
determining whether or not a candidate system should consider other related system. During
analysis, data are collected on available files, decision points and transaction handled by the
present system. Once analysis is completed, the analyst has a firm understanding of what has
to be done. The next step is to decide how the problem might be solved. Thus, in a system
design, we move from the logical to the physical aspects of the life cycle,

System analysis is an activity that encompasses most of the task before the actual software
analysis starts. It is collectively known as system engineering. System analysis is completely
different from software analysis. Before software can be engineered the ‘system’ in which it
resides must be understood. To accomplish this overall objective of the system must be
determined; the role of hardware software, people, database, procedures, and other system
elements must be identified; and operational requirements must be elicited, analyzed,
specified, modeled, validated, and managed. These activities are the foundation of system
engineering. A system engineer works to understand system requirements by working with the
customers and future users.

There’s an old saying: ‘You cannot see the forest for the trees.’ In this context the ‘forest’ is
the system and the trees are the technology elements (including software) that are required to
realize the system. If you rush to build technology elements before you understand the system,
you all undoubtedly make mistakes that will disappoint your customer. Before you worry
about the trees, understand the forest.

Eliciting information from the customer identifies objectives and more detailed operational
requirements; requirements are analyzed to assess their clarity; a specification, often
incorporating a system model, is created and then validated by administrator. Finally system
requirements are managed to ensure that changes are properly controlled.

An effective representation of the system must be produces as a consequence of system

engineering. This can be a prototype, a specification or even a symbolic model, but if must
communicate the operational, functional, and behavioral characteristics of the system to be
built and provide insight into the system architecture.

We have conducted system analysis with the following objectives in mind:

1. Identified the need of software.
2. Evaluated the system concept for feasibility.

Page 6 of 32
 Website: Government Employment office

3. Performed economical analysis.

4. Performed technical analysis.
5. Allocated functions to various system elements.
6. Created the system definition that forms the foundation for all subsequent engineering
work.

3.1 REQUIREMENT ANALYSIS

System analysis is defined as “The process of gathering and interpreting facts, diagnosing
problems and using these facts to improve the system. It is a process of examining a business
transaction processing activities with the intent of improving it with better procedure and
methods.

System analysis is an important phase in system development and focuses on its necessary
accomplishments of new design. Thus system analysis is the crucial examination of a system
with the view of promptly understanding the functionality of the system and making use of
an orderly structured process for identity and solving problem. System analysis emphasize on
what the system must do and external environment to which the system must respond.

Software actually starts from the requirement analysis. The requirement gathering process is
intensified & focused specially on software. To understand the actual nature of the program to
be built the software engineer must understand the information domain for the software. As
well as the required function behavior performance & interface. Requirement for both
software & system are documented & reviewed with customer. Software Requirement
analysis is software engineering task that bridges the gap between system level requirement
engineering & software design.
The first step of software analysis process involves the identification of needs. Identification
of the need is starting point in the evaluation of a computer-based system. We have assisted
the customer in defining the goals of the system (product), the information to be produced, the
information to be provided, the function & performance to be required. We made sure to
distinguish customer’s needs (features critical to success) & customer’s wants (features nice to
have but not essential).
We have divided the Software Requirement analysis into five areas of efforts those are
Problem recognition, evaluation & synthesis, modeling, synthesis, & review. In problem
recognition we have some regular meeting with the customer & classified the customer
requirements into three categories.
- Normal Requirements: These include the objectives & the goals that are stated for a
product. If these requirements are there the customer is satisfied.
- Expected Requirements: These requirements are implicit to the product or the system &
are so fundamental that customer does not explicitly state them but their absence may cause
considerable dissatisfaction to the customer.
- Exciting Requirements: These features go beyond the customer’s expectation & prove to
be very satisfying when present.

Page 7 of 32
 Website: Government Employment office

Then some Use-cases are created. To create a Use-case, the analyst must first identify the
different types of people that use the system or product. Then the functional & behavioral
models are prepared. The work is often partitioned in to smaller tasks. System analysts often
prepare software specifications for the practitioners so that the gap between them can be
bridged. At the end the specifications are reviewed in presence of both customer & developer.
This review is necessary in order to avoid future changes that may be costlier to the customer
& difficult for practitioner.
The analysis is then modeled into some of the analysis models. Commonly we model this
analysis into Data Flow Diagrams, Entity Relationship Diagrams, & transition diagrams. The
basic entities are defined then we have created the ER diagrams. The Long tables are difficult
to be drawn on a paper as an ER diagram.
Once overall goals are identified, we moved on to an evaluation of supplement information:
Does the technology exist to build the system? What special development & manufacturing
resources will be required? What bounds have been placed on costs & schedule? We specified
the information gathered during this step in a system concept document.

3.2 REQUIREMENT SPECIFICATION

Requirement analysis is a process of understanding the customer needs and expectations from
a proposed system or application and is a well defined stage in Software Development Life
cycle model. Requirements are a description of how a system should behave or a description
of system properties or attributes. It can alternatively be a statement of ‘what’ an application is
expected to do.

Given the multiple levels of interaction between users, business processes and devices in
global corporations today, there are simultaneous and complex requirements from a single
application, from various levels within an organization and outside it as well.

The Software Requirements Analysis Process covers the complex task of eliciting and
documenting the requirements of all these users, modeling and analyzing these requirements
and documenting them as a basis for system design. A dedicated and specialized
Requirements Analyst is best equipped to handle the job.

The Requirements analysis function may also fall under the scope of Project Manager,
Program Manager or Business Analyst, depending on the organizational hierarchy. Software
Requirements Analysis and Documentation Processes are critical to software project success.
Requirement Engineering is an emerging field which deals with the systematic handling of
requirements.

SRS is generated by the output of requirement analysis. The requirement analysis involves
Obtaining to clear and through understanding of the product to be developed. Thus, SRS
should be consistent, correct, unambiguous and complete.

Uses of SRS:-
Project managers based their plans and estimates of schedule, and resources on it.
Development team needs it to develop the product. The testing group needs to generate test

Page 8 of 32
 Website: Government Employment office

plans based on described external behavior. The maintenance and product support staff need is
to understand what the software product is supposed to do.

3.3 USE CASE ANALYSIS

The various interactions of the actors with a system are quantized into use case. A use case is a
coherent piece of functionality that a system can provide by interacting with actors Let us
consider the following figure; first any administrator can see the local representative’s list.
Similarly, a local representative can register the unemployed persons.

Each use case involves one or more actors as well as the system itself. The administrator’s user
account involves the actor admin, and the local representative’s user account involves the local
representative actor.

A use case involves a sequence of messages among the system and its actors. Some use cases
have a fixed sequence of messages. More often, however, the message sequence may have
some variations. We should define first a mainline behavior sequence, and then define optional
subsequences, repetition, and other variations.

Error conditions are also part of a use case. From the user’s point of view, some kinds of
behavior may be thought of as error. The designer, however, should plan for all possible
behavior sequences. From the system’s point of view, use errors or resource failures are just
additional kinds of behavior that a robust system can accommodate.
A use case brings together all of the behavior relevant to a slice of system functionality. This
includes normal mainline behavior, variations on normal behavior, exception conditions, error
conditions and cancellation of request.

In a complete model, the use cases partition the functionality of the system. They should be
preferably all being at a comparable level of abstraction.

USE CASE DIAGRAMS:-

A system involves a set of use cases and a set of actors. Each use case represents a slice of the
functionality the system provides. The set of use cases shows the complete functionality of the
system at some level of detail. Similarly, each actor represents one kind of object for which
the system can perform behavior. The set of actors represents the complete set of objects tat
the system can perform behavior. The set of actors represents the complete set of objects that
the system can serve. Objects accumulate behavior from all the systems with which they
interact as actors.

The UML has a graphical notation for summarizing use cases. A rectangle contains the use
cases for a system with actors listed on the outside. The name of the system may be written
near a side of the rectangle. A name within an ellipse denotes a use case. A “stick man” icon
denotes an actor, with the name being placed below or adjacent to he icon. Solid lines connect
use cases to participating actors.

Page 9 of 32
 Website: Government Employment office

CHAPTER - 4
DESIGN

Page 10 of 32
 Website: Government Employment office

CHAPTER - 4
DESIGN

Design is a meaningful representation of something that is to be built. It can be traced to a

customer’s requirements and at same time assessed for quality against a set of predefined
criteria for good design. ‘Software design is the practice of taking a specification of
externally observable behavior and adding details needed for actual computer system
implementation, including human interaction, task management and data management details.
Software design is the process of inventing and selecting programs that meet the objectives
for software systems.’

In the design phase the architecture is established. This phase starts with the requirement
document delivered by the requirement phase and maps the requirements into architecture.
The architecture defines the components, their interfaces and behaviors. The deliverable
design document is the architecture. The design document describes a plan to implement the
requirements. This phase represents the ``how'' phase. Details on computer programming
languages and environments, machines, packages, application architecture, distributed
architecture layering, memory size, platform, algorithms, data structures, global type
definitions, interfaces, and many other engineering details are established.

Design, usually considered in the context of applied arts, engineering, architecture and other
creative endeavors, is used both as a noun and a verb. As a verb, “to design” refers to the
process of originating and developing a plan for a product, structure, system, or component.
As a noun, “to design” is used for either the final plan or the result of implementing that plan.

Designing normally requires a designer to consider the aesthetic, functional and many other
aspects of an object or a process, which usually requires considerable research, thought,
modeling, interactive adjustment and re-design. The design starts with the information in
other hand created above. Throughout the design process the quality of the evolving design is
assessed with a series of formal technical or design walkthroughs. The design concepts like
abstraction, refinement, modularity, software architecture, control hierarchy, software
partitioning, data structures, software procedures, & information hiding are used to achieve
good design.

CHARACTERISTICS OF GOOD DESIGN

1. The design must implement all of the explicit requirements contained in analysis model,
and it must accommodate all of the implicit requirements desired by the customer.
2. The design must be readable, understandable guide for those who generate code and for
those who test and subsequently support the software.
3. The design should provide a complete picture of the software, addressing data, functional
and behavioral domains from an implementation perspective.

Page 11 of 32
 Website: Government Employment office

4.1.1 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system. A data flow diagram can also be used for the visualization of data
processing (structured design). It is common practice for a designer to draw a context-level
DFD first which shows the interaction between the system and outside entities. This context-
level DFD is then "exploded" to show more detail of the system being modeled. Data flow
diagrams were invented by Larry Constantine, the original developer of structured design,
based on Martin and Estrin's "data flow graph" model of computation. There are a number of
symbols that are used in DFDs for threat modeling.

Fig.4.2 0-Level Data Flow Diagram

Page 12 of 32
 Website: Government Employment office

Fig.4.3 1 level Data Flow Diagram

Page 13 of 32
 Website: Government Employment office

Fig.4.3 2-level Data Flow Diagram

4.2 MODULES IDENTIFIED

Page 14 of 32
 Website: Government Employment office

A System is considered modular if it consists of discrete components so that each component

can be implemented separately, and a change to one component has minimal impact on other
components. There are many definitions of term ‘MODULE’. They range from “a module is
a FORTRAN subroutine” to “a module is an ADA package” to “a module is a work
assignment for an individual programmer”. Modular system consists of well defined,
manageable units with well defined interfaces among the units.

Our Project has been divided into four Modules:

• Login Page/Default
• Home Page
• Forum Section
• Video Section
• Photo Gallery
• Logout Page

Login Page:
This module includes the registration form for a user who wants to be the member of this site.
If user is already a member of this site, he will directly access the site by giving his correct
username and password given text box.

Home Page:

In this module, we have included introductory part of our website. The introduction includes
a brief description of our collage events. A user can access Home page only if he can
successfully logged in.The home page module a shortcut to visit other modules of this site
such as video gallery, flash photo album etc.

Forum Section:

In this module, we have included a special feature of asking any number of questions or
queries. The other user can reply these questions. These questions and answers are viewable
to all members of website. As this website is mostly purposed for college advertising and
keeping tracks of all historical music events of college campus ,any outsider who wants to
know more information about college, can ask question related to college.

Video Section:

This module contains records of all musical and cultural events of college. We have provided
the facility to upload any video, who is the member of this site. Sharing of videos is the main
specification of our site. Our existing application supports the following formats of
videos:*.avi,*.mpeg,*.mp4,*.wmv.

Photo Gallery:

Page 15 of 32
 Website: Government Employment office

This module contains all the pictures of college events.

Logout:

It remove the user from the session.

4.3 DATABASE DESIGN

Database design is the process of producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a Data Definition Language, which can
then be used to create a database. A fully attributed data model contains detailed attributes
for each entity.

The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are the
tables and views. In an object database the entities and relationships map directly to object
classes and named relationships. However, the term database design could also be used to
apply to the overall process of designing, not just the base data structures, but also the forms
and queries used as part of the overall database application within the database management
system.

4.3.1 DATABASE TABLES

The tables described below are used in the project in the database designing. It gives an
overview of the tables used in the database. The format of tables, various fields of table, their
size, & the description is discussed.

Video Table:

Field Name Datatype Description

Id Int Primary key
Topic Char
Language Char
Member_id Int
Title Char
File_name Varchar
Uploading_time Datetime

Page 16 of 32
 Website: Government Employment office

Table 4.1

Member Table:

integer Primary Key

Id
First_name Char Unique key
Last_name Char

Username Char Unique key

Password Char
Password_key Char
Date_of_birth Date time
Sex Char
Email_address VarChar
Country Char
Reffered_email Char
Is_date_of_birth Char
Receive_email Char
Hint_question Varchar
Hint_answer(10) Char
Active_status Char
Mobile_no. Int

Table 4.2

Page 17 of 32
 Website: Government Employment office

Activation table:

Field name Datatype Description

Username Int Primary/forignkey
Activation_id Char

Table 4.3

Music Table:

Field Name Data Type Description

Id numeric Int Primary Key

Topic Char

Language Char

Member_id Char

Title Char

Category Char

Singers Varchar

Composers Varchar

File_name Varchar

Uploading_name Datetime

Page 18 of 32
 Website: Government Employment office

Table 4.4

4.3.2 ER DIAGRAM :In software engineering, an entity-relationship model (ERM) is an

abstract and conceptual representation of data. Entity-relationship modeling is a
database modeling method, used to produce a type of conceptual schema or semantic
data model of a system, often a relational database, and its requirements in a top-down
fashion. Diagrams created by this process are called entity-relationship diagrams, ER
diagrams, or ERDs.

The building blocks: entities, relationships, and attributes

Two related entitie.

An entity with an attribute

A relationship with an attribute

Primary key: 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. When we speak of an entity we normally speak of some aspect of
the real world which can be distinguished from other aspects of the real world.[3]

An entity may be a physical object such as a house or a car, an event such as a house sale or a car
service, or a concept such as a customer transaction or order. Although the term entity is the one

Page 19 of 32
 Website: Government Employment office

most commonly used, following Chen we should really distinguish between an entity and an
entity-type. An entity-type is a category. An entity, strictly speaking, is an instance of a given
entity-type. There are usually many instances of an entity-type. Because the term entity-type is
somewhat cumbersome, most people tend to use the term entity as a synonym for this
term.Entities can be thought of as nouns. Examples: a computer, an employee, a song, a
mathematical theorem.

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

interrelationships between entities in a database. ER diagrams often use symbols to represent
three different types of information. Boxes are commonly used to represent entities. Diamonds
are normally used to represent relationships and ovals are used to represent attributes. It is also
known as ER Diagram, E-R Diagram, entity-relationship model.

This document is an entity-relationship diagram, or “ERD,” for a system to manage electronic

resources. An ERD is a model that identifies the concepts or entities that exist in a system and
the relationships between those entities.

An ERD is often used as a way to visualize a relational database: each entity represents a
database table, and the relationship lines represent the keys in one table that point to specific
records in related tables. ERDs may also be more abstract, not necessarily capturing every table
needed within a database, but serving to diagram the major concepts and relationships.

Page 20 of 32
 Website: Government Employment office

Fig.4.4 E-R Diagram of Music Forum

Page 21 of 32
 Website: Government Employment office

CHAPTER – 5
IMPLEMENTATION

Page 22 of 32
 Website: Government Employment office

CHAPTER – 5
IMPLEMENTATION

Implementation is a phase of SDLC in which the information system is coded, tested, installed
and supported in the organization.

Fig 5.1 Implementation Block Diagram

The implementation system is less creative than system design. It is primarily concerned with
user training, site preparation and file conversion. When the candidate system is being installed
on the user’s site it is also included under implementation.

During the final testing, user acceptance is tested followed by the user training. Depending
upon the nature of the system, extensive user training may be required. For this we have to give
training to the staff members of the existing system.

Page 23 of 32
 Website: Government Employment office

Once the programs become available, test data are read into the computer and processed against
the files provided for testing. If successful, the programs then run with “live” data. Otherwise a
diagnostic procedure is used to locate and correct errors in the program.

5.1 PLATFORM USED

5.1.1 Hardware Platform

1. Processor – Intel Pentium III or Advanced.

2. Speed – In MHz or GHz.
3. RAM – .99GB
4. Hard Disk – 500MB.
5. Monitor – VGA or SVGA.
6. Mouse – Optical or Mechanical scroll mouse.

5.1.2 Software Requirements

1. Operating System - Ms-Windows XP Professional 2002

2. Front End - Java
3. Back End - mySQL

5.1.2.1 INTRODUCTION TO JAVA:

5.2 Software Platform: - Employment office management is using the following Softwares: -

1. Java
(a) Java Server pages
(b)Java Servlet
2. Tomcat
3. MySql

1. Java : - A high-level programming language developed by Sun Microsystems. Java is an

object-oriented language, simplified to eliminate language features that cause common
programming errors. Java source code files (files with a .java extension) are compiled into a
format called byte code (files with a .class extension), which can then be executed by a Java
interpreter. Compiled Java code can run on most computers because Java interpreters and
runtime environments, known as Java Virtual Machines (VMs), exist for most operating systems.

(a)Java Server pages :- (JSP) is a Java technology that helps software developers serve
dynamically generated web pages based on HTML, XML, or other document types. JSP was
designed to address the perception that the Java programming environment didn't provide
developers with enough support for the Web. JSPs are compiled into servlets by a JSP compiler.
The compiler either generates a servlet in Java code that is then compiled by the Java compiler,

Page 24 of 32
 Website: Government Employment office

or it may compile the servlet to byte code which is directly executable. JSPs can also be
interpreted on-the-fly, reducing the time taken to reload changes.

(b)Java Servlet :- A Servlet is a Java class which conforms to the Java Servlet API, a protocol by
which a Java class may respond to http requests. Thus, a software developer may use a servlet to
add dynamic content to a Web server using the Java platform. The generated content is
commonly HTML, but may be other data such as XML. Servlets are the Java counterpart to non-
Java dynamic Web content technologies such as CGI and ASP.NET. Servlets can maintain state
in session variables across many server transactions by using HTTP cookies, or rewriting. The
servlet API, contained in the Java package hierarchy javax.servlet, defines the expected
interactions of a Web container and a servlet. A Web container is essentially the component of a
Web server that interacts with the servlets. The Web container is responsible for managing the
lifecycle of servlets, mapping a URL to a particular servlet and ensuring that the URL requester
has the correct access rights. A Servlet is an object that receives a request and generates a
response based on that request. The basic servlet package defines Java objects to represent
servlet requests and responses, as well as objects to reflect the servlet's configuration parameters
and execution environment. The package javax.servlet.http defines HTTP-specific subclasses of
the generic servlet elements, including session management objects that track multiple requests
and responses between the Web server and a client. Servlets may be packaged in a WAR file as a
Web application.

2.Tomcat : - Apache Tomcat (or Jakarta Tomcat or simply Tomcat) is an open source servlet
container developed by the Apache Software Foundation (ASF). Tomcat implements the Java
Servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, and provides a
"pure Java" HTTP web server environment for Java code to run. Tomcat should not be
confused with the Apache web server, which is a C implementation of an HTTP web server;
these two web servers are not bundled together. Apache Tomcat includes tools for configuration
and management, but can also be configured by editing XML configuration files.

3. MySQL :- MySQL is a relational database management system (RDBMS)[1] that runs as a

server providing multi-user access to a number of databases. Free-software projects that require a
full-featured database management system often use MySQL. . MySQL is also used in many
high-profiles, large-scale World Wide Web products including Wikipedia, Google and
Facebook.

Platforms and interfaces :- MySQL works on many different system platforms, including AIX,
BSDi, FreeBSD, HP-UX, i5/OS, Linux, Mac OS X, NetBSD, Novell NetWare, OpenBSD,
OpenSolaris, eComStation, OS/2 Warp, QNX, IRIX, Solaris, Symbian, SunOS, SCO
OpenServer, SCO UnixWare, Sanos, Tru64 and Microsoft Windows.
All major programming languages with language-specific APIs include Libraries for accessing
MySQL databases. In addition, an ODBC interface called MyODBC allows additional
programming languages that support the ODBC interface to communicate with a MySQL
database.

Page 25 of 32
 Website: Government Employment office

Features :-
1. Stored procedures
2. Triggers
3. Cursors
4. Updatable Views
5. True Varchar support
6. Sub-SELECTs (i.e. nested SELECTs)
7. Partial Unicode support (UTF-8 and UCS-2 encoded strings are limited to the BMP)

5.3 TESTING

Testing is the process of exercising or evaluating a system or system component by

manual or automated means to verify that it satisfies specified requirements. Testing is a set
of activities that can be planned in advance and conducted systematically.

TESTING OBJECTIVE

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 –yet undiscovered error.

TESTING PRINCIPLES

1. All tests should be traceable to customer requirement.

2. Test should be planned long before testing begins.
3. Testing should begin “in the small” and progress toward testing “in the large”.
4. Exhaustive testing is not possible.
5. To be most effective, an independent third party should conduct testing.

TYPES OF TESTING USED

In our project, we have used both types of testing

WHITE BOX TESTING

White Box Testing is also known as structural testing. White box testing uses an internal
perspective of the system to design test cases based on internal structure. It requires
programming skills to identify all paths through the software. The tester chooses test case
inputs to exercise paths through the code and determines the appropriate outputs. In electrical
hardware testing, every node in a circuit may be probed and measured; an example is in-circuit
testing (ICT).

Since the tests are based on the actual implementation, if the implementation changes, the tests
probably will need to change, too. While white box testing is applicable at the unit, integration

Page 26 of 32
 Website: Government Employment office

and system levels of the software testing process, it is typically applied to the unit. While it
normally tests paths within a unit, it can also test paths between units during integration, and
between subsystems during a system level test. Though this method of test design can uncover
an overwhelming number of test cases, it might not detect unimplemented parts of the
specification or missing requirements, but one can be sure that all paths through the test object
are executed

Fig 6.2 Testing

Typical white box test design techniques include

1. Control flow testing

2. Data flow testing
3. Branch Testing

BLACK BOX TESTING

Black box testing takes an external perspective of the test object to derive test cases. These
tests can be functional or non-functional, though usually functional. The test designer

Page 27 of 32
 Website: Government Employment office

selects valid and invalid inputs and determines the correct output. There is no knowledge of
the test object's internal structure.

This method of test design is applicable to all levels of software testing: unit, integration,
functional testing, system and acceptance. The higher the level, and hence the bigger and
more complex the box, the more one is forced to use black box testing to simplify. While
this method can uncover unimplemented parts of the specification, one cannot be sure that
all existent paths are tested.

Fig 6.3 Black Box Testing

Black Box Testing is testing without knowledge of the internal workings of the item being
tested. For example, when black box testing is applied to software engineering, the tester
would only know the "legal" inputs and what the expected outputs should be, but not how the
program actually arrives at those outputs. It is because of this that black box testing can be
considered testing with respect to the specifications, no other knowledge of the program is
necessary. For this reason, the tester and the programmer can be independent of one another,
avoiding programmer bias toward his own work. For this testing, test groups are often used,
"Test groups are sometimes called professional idiots...people who are good at designing
incorrect data." Black Box testing is applied during the later stages of testing. It focuses on the
information domain .Tests are designed to answer the following questions.

Page 28 of 32
 Website: Government Employment office

CHAPTER – 6
CONCLUSION

Page 29 of 32
 Website: Government Employment office

CHAPTER – 6
CONCLUSION

As there are many private online job portals are available. This site will provide the reliable
and trust worthy employment updates to the user. This will help the government to reach state
to state to state and hence city to city.
In an on demand world, there is first necessity to get a suitable job. After we have completed
the project we are sure that problems in the existing system would overcome.. The
maintenance of unemployment records is made efficient, as all the records are stored in
ACCESS database, through which data can be retrieved easily. The navigation control is
provided in all forms to navigate through the large amount of records.

Our main aim of the project is to provide a reliable, authorized and common platform to the
unemployed persons to get faster and easy update and to extend the functionality and behavior
of employment office world widely.

6.1 ADVANTAGES

The site we provided is easy to maintain and

1. It Provide the fasciitis to the users to get them updated.
2. Here User can direct interact with the authorized person.
3. Here user can register himself for the better opportunities.
4. Here the government can maintain broader records of the employment status of whole
country.

6.2 LIMITATIONS

Limitations of new proposed system are:

1. GUI is only in English.

2. Login and password is used for identification of customer and there is no facility for
guest.
3. This system is working for single server.
4. Video should be limited up to 16 Mb.
5. Limited to HTTP.

Page 30 of 32
 Website: Government Employment office

REFERENCES

REFERENCES

Page 31 of 32
 Website: Government Employment office

Bibliography:

1. HTML: a beginner’s guide

2. Practical: MySQL

References

• Books

1. The complete reference of Dot Net.

2. Sql queries by Ivan Bayros.

• Sites

1. www.microsoft.com

2. www.asp.net

3. www.programmerworld.net

4. www.sourcecodesworld.com

5. www.google.com

Page 32 of 32