1.

INTRODUCTION

1.1 Purpose:

The main purpose for preparing this document is to give a general insight into
the analysis and requirements of the existing system or situation and for determining
the operating characteristics of the system.

1.2 Scope:

This Document plays a vital role in the development life cycle (SDLC) and it
describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirements in the future will have to go through formal change approval process.

1
 2.OVERALL DECRIPTION

2.1 EXISTING SYSTEM

 Cannot Upload and Download the latest updates.

 No use of Web Services and Remoting.

 Risk of mismanagement and of data when the project is under development.

 Less Security.

 No proper coordination between different Applications and Users.

 Fewer Users - Friendly.

2.2 PROPOSED SYSTEM

To debug the existing system, remove procedures those cause data

redundancy, make navigational sequence proper. To provide information about audits
on different level and also to reflect the current work status depending on
organization/auditor or date. To build strong password mechanism.

2.3 STUDY OF THE SYSTEM

GUI’S

In the flexibility of the uses the interface has been developed a graphics
concept in mind, associated through a browses interface. The GUI’S at the top level
have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication
for the data collection.

2
 The interfaces help the administrations with all the transactional states like Data
insertion, Data deletion and Date updation along with the extensive data search
capabilities.The operational or generic user interface helps the users upon the system
in transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information helps the
ordinary users in managing their own information in a customized manner as per the
assisted flexibilities.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the
following modules:

The modules involved are:

 Admin

 Job Seeker

 Job Provider

 Notification

 Search

 Report

 Authentication

Admin:

In this module Admin will add all the qualifications, skill, experience, city,
state, country and update and delete information about the job provider or job seeker
he can also search for the job seeker and he can send mail to offer the job to job
seeker and he can also see the jobs add by the job provider.

3
Job Seeker:

In this module Job Seeker register himself and upload his resume and fill the profile
give by admin and after login he will search for the job on various conditions and he
can change his

Profiles and resume and he can apply for the jobs based on various conditions.
He can see the response of the company and he can call the company person for the
interview.

Job provider:

In this module Job Provider register himself and his company and after login
he will add new job and he can search for the job seekers on various condition and he
can offerthe job to job seeker according to the job profile and he can also see the
response from the job seekers and send the mail.

Notification:

In this module admin and job provider send the notification to the job seeker
in the form of email.

Reports:

This module contains all the information about the reports generated by the
admin based on the particular job seeker, particular job provider, all job seeker and
job provider, all jobs generated by the job providers.

Authentication:

This module contains all the information about the authenticated user. User
without his username and password can’t enter into the login if he is only the
authenticated user then he can enter to his login.

PROJECTINSTRUCTIONS:

 Based on the given requirements, conceptualize the Solution Architecture. Choose

the domain of your interest otherwise develop the application for
ultimatedotnet.com. Depict the various architectural components, show
interactions and connectedness and show internal and external elements. Design

4
 the web services, web methods and database infrastructure needed both and client
and server

 Provide an environment for upgradation of application for newer versions that are
available in the same domain as web service target.

2.4 FEASIBILITY REPORT

Preliminary investigation examine project feasibility, the likelihood the system

will be useful to the organization.

The main objective of the feasibility study is to test the Technical, Operational
and Economical feasibility for adding new modules and debugging old running
system. All system is feasible if they are unlimited resources and infinite time. There
are aspects in the feasibility study portion of the preliminary investigation:

 Technical Feasibility

 Operation Feasibility

 Economical Feasibility

Technical Feasibility

The technical issue usually raised during the feasibility stage of the
investigation includes the following:

 Does the necessary technology exist to do what is suggested?

 Do the proposed equipment’s have the technical capacity to hold the data required
to use the new system?

 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?

 Can the system be upgraded if developed?

 Are there technical guarantees of accuracy, reliability, ease of access and data
security?

5
 Earlier no system existed to cater to the needs of ‘Secure Infrastructure
Implementation System’. The current system developed is technically feasible. It is a
web based user interface for audit workflow at NIC-CSD. Thus it provides an easy
access to the users.

The database’spurpose is to create, establish and maintain a workflow among

various entities in order to facilitate all concerned users in their various capacities or
roles. Permission to the users would be granted based on the roles specified.
Therefore, it provides the technical guarantee of accuracy, reliability and security. The
software and hard requirements for the development of this project are not many and
are already available in-house at NIC or are available as free as open source. The
work for the project is done with the current equipment and existing software
technology. Necessary bandwidth exists for providing a fast feedback to the users
irrespective of the number of users using the system.

Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organization’s operating requirements. Operational
feasibility aspects of the project are to be taken as an important part of the project
implementation. Some of the important issues raised are to test the operational
feasibility of a project includes the following:

 Is there sufficient support for the management from the users?

 Will the system be used and work properly if it is being developed and
implemented?

 Will there be any resistance from the user that will undermine the possible
application benefits?

This system is targeted to be in accordance with the above-mentioned issues.

Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine
the possible application benefits.

6
 The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.

Economic Feasibility

A system can be developed technically and that will be used if installed must
still be a good investment for the organization. In the economical feasibility, the
development cost in creating the system is evaluated against the ultimate benefit
derived from the new systems. Financial benefits must equal or exceed the costs.

7
 3. SOFTWARE REQUIREMENT SPECIFICATIONS

3.1 SOFTWARE INTERFACES

 Language: Microsoft C#.Net language

 Environment: Microsoft Visual Studio 2008 IDE

 Operating System: Windows 2000/NT/XP

 Run-time environment: Microsoft framework 3.5

 Technologies: JavaScript, ASP.NET 3.5

3.2 HARDWARE INTERFACES

 RAM: 1 GB or higher

 Processor: Pentium IV or higher

 Hard Disk: 40 GB or higher

3.3 FUNCTONAL REQUIREMENTS

 Microsoft Framework 3.0.

 ASP.Net 3.0.

 C# language.

 Microsoft Visual studio 2008 IDE.

 HTML.

 Ajax control tool kit.

 Microsoft SQL Server 2008 and above.

8
3.4 NON-FUNCTIONAL REQUIREMENTS

Hardware Requirements:
Processor : Intel Pentium or more

Ram : 256 MB or more

Hard disk : 40 GB hard disk recommended for primary partition.

9
 4. LANGUAGES OF IMPLEMENTATION

Asp.net description

Active Server Pages.NET

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

runtime that can be used on a server to build powerful Web applications. ASP.NET
offers several important advantages over previous Web development models:

 Enhanced Performance. ASP.NET is compiled common language

runtime code running on the server. Unlike its interpreted
predecessors, ASP.NET can take advantage of early binding, just-in-
time compilation, native optimization, and caching services right out of
the box. This amounts to dramatically better performance before you
ever write a line of code.

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

complemented by a rich toolbox and designer in the Visual Studio
integrated development environment. WYSIWYG editing, drag-and-
drop server controls, and automatic deployment are just a few of the
features this powerful tool provides.

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

language runtime, the power and flexibility of that entire platform is
available to Web application developers. The .NET Framework class
library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so
you can choose the language that best applies to your application or
partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to
ASP.NET.

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

simple form submission and client authentication to deployment and
site configuration.

10
 For example, the ASP.NET page framework allows you to build user
interfaces that cleanly separate application logic from presentation
code and to handle events in a simple, Visual Basic - like forms
processing model.

 Additionally, the common language runtime simplifies development, with

managed code services such as automatic reference counting and garbage
collection.

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

configuration system, which simplifies applying settings to your server
environment and Web applications. Because configuration information
is stored as plain text, new settings may be applied without the aid of
local administration tools. This "zero local administration" philosophy
extends to deploying ASP.NET Framework applications as well. An
ASP.NET Framework application is deployed to a server simply by
copying the necessary files to the server. No server restart is required,
even to deploy or replace running compiled code.

 Scalability and Availability. ASP.NET has been designed with

scalability in mind, with features specifically tailored to improve
performance in clustered and multiprocessor environments. Further,
processes are closely monitored and managed by the ASP.NET
runtime, so that if one misbehaves (leaks, deadlocks), a new process
can be created in its place, which helps keep your application
constantly available to handle requests.

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

architecture that allows developers to "plug-in" their code at the
appropriate level. In fact, it is possible to extend or replace any
subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has
never been easier.

 Security. With built in Windows authentication and per-application

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

11
Language Support

The Microsoft .NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript.

What is ASP.NET Web Forms?

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

runtime programming model that can be used on the server to dynamically generate
Web pages. Intended as a logical evolution of ASP (ASP.NET provides syntax
compatibility with existing pages), the ASP.NET Web Forms framework has been
specifically designed to address a number of key deficiencies in the previous model.
In particular, it provides:

 The ability to create and use reusable UI controls that can

encapsulate common functionality and thus reduce the amount of
code that a page developer has to write.

 The ability for developers to cleanly structure their page logic in an

orderly fashion (not "spaghetti code").

 The ability for development tools to provide strong WYSIWYG

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

ASP.NET Web Forms pages are text files with an .aspx file name extension.
They can be deployed throughout an IIS virtual root directory tree. When a browser
client requests .aspx resources, the ASP.NET runtime parses and compiles the target
file into a .NET Framework class. This class can then be used to dynamically process
incoming requests. (Note that the .aspx file is compiled only the first time it is
accessed; the compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, thefollowing sample demonstrates a simple HTML page that collects a
user's name and category preference and then performs a form post back to the
originating page when a button is clicked:

12
 ASP.NET provides syntax compatibility with existing ASP pages. This
includes support for <% %> code render blocks that can be intermixed with HTML
content within an .aspx file. These code blocks execute in a top-down manner at page
render time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is the
method shown in the preceding samples, where the page code is physically declared
within the originating .aspx file. An alternative approach--known as the code-behind
method--enables the page code to be more cleanly separated from the HTML content
into an entirely separate file.

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program dynamic
content, ASP.NET page developers can use ASP.NET server controls to program
Web pages. Server controls are declared within an .aspx file using custom tags or
intrinsic HTML tags that contain a runat="server" attribute value. Intrinsic HTML
tags are handled by one of the controls in the System.Web.UI.HtmlControls
namespace. Any tag that doesn't explicitly map to one of the controls is assigned the
type of System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between

round trips to the server. This control state is not stored on the server (it is instead
stored within an <input type="hidden"> form field that is round-tripped between
requests). Note also that no client-side script is required.

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

developers to utilize richer custom controls on their pages. For example, the following
sample demonstrates how the <asp:adrotator> control can be used to dynamically
display rotating ads on a page.

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

2) ASP.NET Web Forms pages can target any browser client (there are no script
library or cookie requirements).

13
 3) ASP.NET Web Forms pages provide syntax compatibility with existing ASP
pages.

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

functionality.

5) 5. ASP.NET ships with 45 built-in server controls. Developers can also use
controls built by third parties.

6) 6. ASP.NET server controls can automatically project both up level and down-
level HTML.

7) 7. ASP.NET templates provide an easy way to customize the look and feel of
list server controls.

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

or server data validation.

C#.net description.

C# is an object-orientedprogramminglanguage developed by Microsoft as part

of the .NET .Anders Hejlsberg leads development of the C# language, which has a
procedural, object-oriented syntax based on C++ and includes influences from aspects
of several other programming languages (most notably Delphi and Java) with a
particular emphasis on simplification.

 C# is intended to be a simple, modern, general-purpose, object-oriented

programming language.

 Because software robustness, durability and programmer productivity are

important, the language should include strong type checking, array bounds
checking, detection of attempts to use uninitialized variables, source code
portability, and automatic garbage collection.

 The language is intended for use in developing software components that can
take advantage of distributed environments.

 Programmer portability is very important, especially for those programmers

already familiar with C and C++.

14
  Support for internationalization is very important.

 C# is intended to be suitable for writing applications for both hosted and

embedded systems, ranging from the very large that use sophisticated
operating systems, down to the very small having dedicated functions.

ADO.NET

Data Access in ADO.NET relies on two components; Dataset and

DataProvider.

 Dataset:

The Dataset is a disconnected, in-memory representation of data. It can be

considered as a local copy of the relevant portions of the database. The Data Set is
persisted in memory and the data in it can be manipulated and updated independent of
the database. When the use of this Dataset is finished changes can be made back to
the central database for updating. The data in Dataset can be loaded from any valid
data source like Microsoft SQL server, an Oracle database or from a Microsoft Access
database.

 DataProvider:

The DataProvider is responsible for providing and maintaining the

connection to the database. A DataProvider is a set of related components that works
together to provide data in an efficient and performance driven manner. The .NET
framework currently comes with two Data Providers the SQL DataProvider which is
designed only to work with Microsoft’s SQL server 7.0 or later and the Oledb
DataProvider which allows us to connect to other types of databases like Access and
Oracle.

Each DataProvider consists of the following component classes:

 The Connection object which provides a connection to the database.

 The Command object which is used to execute a command.

 The DataReader object which provides a forward-only, read-only, connected

record set.

15
  The DataAdapter object which populates a disconnected Data Set with data
and performs update.

Data Access with ADO.NET can be summarized as follows:

A connection object establishes the connection for the application with the
database. The command object provides direct execution of the command to the
database. If the command returns more than a single value, the command object
returns a Data Reader provide the data. Alternatively, the DataAdapter can be used to
fill the Data Set object. The database can be updated using the command object or the
DataAdapter.

Component classes that makes up the Data Providers:

The Connection object:

The Connection object creates the connection to provide the database. Microsoft
Visual Studio .NET provides two types of Connection classes: the sqlConnection
object which is designed specifically to connect to Microsoft SQL server 7.0 or later
and the OleDbConnection object which can provide connections to a wide range of
database types like Microsoft Access and Oracle. The Connection object contains all
of the information required to open a connection to the database.

The Command object:

The Command object is represented by two corresponding classes:

SqlCommand and OleDbCommand. Command objects are used to execute

commands to a database across a data connection. The Command objects can be used
to execute stored procedures on the database, SQL commands or return complete
tables directly. Command object provide three methods that are used to execute
commands on the database.

ExecuteNonQuery:

It executes commands that have no return values such as insert, update or delete.

ExecuteScalar:

It returns a single value from a database query

16
ExecuteReader:

It returns a result set by way of a DataReader object.

The Data Reader object:

The DataReader object provides a forward-only, read-only, connected stream

record set from a database. Unlike other components of the DataProvider, DataReader
objects cannot be directly instantiated. Rather, the DataReader is returned as the result
of the Command objects ExecuteReader method. The sqlCommand method returns a
SqlDataReader object and the OleDbCommand. ExecuteReader method returns an
OleDbDataReader object. The DataReader can provide rows of data directly to
application logic when you do not keep the data cached in memory. Because only one
row is in memory at a time the DataReader provides the lowest overhead in terms of
system performance but requires the exclusive use of an open Connection object for
the lifetime of the DataReader.

The Data Adapter object:

The DataAdapter is the class at the core of ADO .Net’s disconnected data
access. It is essentially the middleman facilitating all communication between the
database and a Data Set. The DataAdapter is used either to fill a Data Table or Data
Set with data has been manipulated; the DataAdapter can commit the changes to the
database by calling the Update method.

The Data Adapter provides four properties that represents database

commands:

 Select Command

 Insert Command

 Delete Command

 Update Command

17
Sqlserver description

Microsoft SQL Server is a Structured Query Language (SQL) based,

client/server relational database. Each of these terms describes a fundamental part of
the architecture of SQL Server.

Database

A database is similar to a data file in that it is a storage place for data. Like a
data file, a database does not present information directly to a user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.

A database typically has two components: the files holding the physical
database and the database management system (DBMS) software that applications use
to access data. The DBMS is responsible for enforcing the database structure,
including:

 Maintaining the relationships between data in the database.

 Ensuring that data is stored correctly and that the rules defining data
relationships are not violated.
 Recovering all data to a point of known consistency in case of system failures.
Client/Server:

In a client/server system, the server is a relatively large computer in a central

location that manages a resource used by many people. When individuals need to use
the resource, they connect over the network from their computers, or clients, to the
server.
Examples of servers are: In a client/server database architecture, the database files and
DBMS software reside on a server. A communications component is provided so
applications can run on separate clients and communicate to the database server over
a network. The SQL Server communication component also allows communication
between an application running on the server and SQL Server.

18
Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and
statements (language) defined by the DBMS software. There are several different
languages that can be used with relational databases; the most common is SQL. Both
the American National Standards Institute (ANSI) and the International Standards
Organization (ISO) have defined standards for SQL. Most modern DBMS products
support the Entry Level of SQL-92, the latest SQL standard (published in 1992).

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that

improve your ability to install, deploy, manage, and use SQL Server across several
sites.

Scalability

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 95/98 to large, multiprocessor servers
running Microsoft Windows NT®, Enterprise Edition.

Data warehousing

SQL Server includes tools for extracting and analyzing summary data for
online analytical processing (OLAP). SQL Server also includes tools for visually
designing databases and analyzing data using English-based questions.

System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.

Databases

A database in Microsoft SQL Server consists of a collection of tables that

contain data, and other objects, such as views, indexes, stored procedures, and
triggers, defined to support activities performed with the data. The data stored in a

19
database is usually related to a particular subject or process, such as inventory
information for a manufacturing warehouse.

Entity Integrity Constraint:

 Entity Integrity Constraints are of two types:

 Unique Constraints

 Primary Key Constraint

 The unique constraints designate a column or a group of columns as a

unique key. The constraint allows only unique values to be stored in
the column Sql Server rejects duplication of records when the unique
key constraint is used.

The primary key constraint is similar to the unique key constraint. The
primary key constraint just like the former avoids duplication of values. Its needs it
best felt when a relation has to be set between tables, because in addition to prevent in
duplication it also does not allow null values.

Referential Integrity Constraint:

The Referential Integrity Constraint enforces relationship between tables. It

designates a column or a combination of columns as a foreign key. The foreign key
establishes a relationship with a specified primary or unique key in another table,
called the referenced key. In this relationship, the table containing the foreign key is
called a child table and the table containing the referenced key is called the parent
table.

20
 5. SOFTWARE DESIGN

5.1 Design Overview (Software arch and Application arch)

The design phase begins with the requirements specification for the software
to be developed. Design is the first step to moving from the problem domain towards
the solution domain. Design is essentially the bridge between requirement
specification and the final solution for satisfying the requirements. It is the most
critical factor affecting the quality of the software.

The design process for software system has two levels.

1. System Design or Top level design

2. Detailed Design or Logical Design

System Design:

In the system design the focus on the deciding which modules are needed for
the system, the specification of these modules and how these modules should be
interconnected.

Detailed Design:

In detailed design the interconnection of the modules or how the specifications

of the modules can be satisfied is decided. Some properties for a software system
design are

 Verifiability

 Completeness

 Consistency

 Traceability

 Simplicity / Understandability

21
5.2 UML Design (state, activity, collaboration also)

UML diagrams

Introduction

Modeling is an activity that has been carried out over the years in software
development. When writing applications by using the simplest languages to the most
powerful and complex languages, you still need to model. Modeling can be as
straightforward as drawing a flowchart listing the steps carried out by an application.

Why do we use modeling?

Defining a model makes it easier to break up a complex application or a huge

system into simple, discrete pieces that can be individually studied. We can focus
more easily on the smaller parts of a system and then understand the "big picture."
Hence, the reasons behind modeling can be summed up in two words:

 Readability

 Reusability

Readability: brings clarity—ease of understanding. Understanding a system is the

first step ineither building or enhancing a system. This involves knowing what a
system is made up of, how it behaves, and so forth. Modeling a system ensures that
it becomes readable and, most importantly, easy to document. Depicting a system
to make it readable involves capturing the structure of a system and the behavior of
the system.

Reusability: is the byproduct of making a system readable. After a system has

been modeled to make it easy to understand, we tend to identify similarities or
redundancy, be they in terms of functionality, features, or structure.

INTRODUCTION TO UML

The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, , and documenting the artifacts of software systems, as well as for
business modeling and other non-software systems. The UML represents a collection
of best engineering practices that have proven successful in the modeling of large and

22
complex systems. The UML is a very important part of developing objects oriented
software and the software development process.

Goals of UML

The primary goals in the design of the UML were:

 Provide users with a ready-to-use, expressive visual modeling language so

they can develop and exchange meaningful models.

 Provide extensibility and specialization mechanisms to extend the core

concepts.

 Be independent of particular programming languages and development

processes.

 Provide a formal basis for understanding the modeling language.

 Encourage the growth of the OO tools market.

 Support higher-level development concepts such as collaborations,

frameworks, patterns and components.

 Integrate best practices.

Why we use UML?

As the strategic value of software increases for many companies, the industry
looks for techniques to automate the production of software and to improve quality
and reduce cost and time-to-market. These techniques include component technology,
visual programming, patterns and frameworks. Businesses also seek techniques to
manage the complexity of systems as they increase in scope and scale. In particular,
they recognize the need to solve recurring architectural problems, such as physical
distribution, concurrency, replication, security, load balancing and fault tolerance.
Additionally, the development for the World Wide Web, while making some things
simpler, has exacerbated these architectural problems. The Unified Modeling
Language (UML) was designed to respond to these needs.

23
UML Diagrams

The underlying premise of UML is that no one diagram can capture the
different elements of a system in its entirety. Hence, UML is made up of nine
diagrams that can be used to model a system at different points of time in the software
life cycle of a system.

The nine UML diagrams are:

 Use case diagram:

The use case diagram is used to identify the primary elements and processes
that form the system. The primary elements are termed as "actors" and the processes
are called "use cases." The use case diagram shows which actors interact with each
use case.

 Class diagram:

The class diagram is used to refine the use case diagram and define a detailed
design of the system. The class diagram classifies the actors defined 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. Each class in the class diagram
may be capable of providing certain functionalities. These functionalities provided by
the class are termed "methods" of the class. Apart from this, each class may have
certain "attributes" that uniquely identify the class.

 Object diagram:

The object diagram is a special kind of class diagram. An object is an instance

of a class. This essentially means that an object represents the state of a class at a
given point of time while the system is running. The object diagram captures the state
of different classes in the system and their relationships or associations at a given
point of time.

 State diagram:

A state diagram, as the name suggests, represents the different states that
objects in the system undergo during their life cycle. Objects in the system change
states in response to events. In addition to this, a state diagram also captures the
24
transition of the object's state from an initial state to a final state in response to events
affecting the system.

 Activity diagram:

The process flows in the system are captured in the activity diagram. Similar
to a state diagram, an activity diagram also consists of activities, actions, transitions,
initial and final states, and guard conditions.

 Sequence diagram:

A sequence diagram represents the interaction between different objects in

the system. The important aspect of a sequence diagram is that it is time-ordered. This
means that the exact sequence of the interactions between the objects is represented
step by step. Different objects in the sequence diagram interact with each other by
passing "messages".

 Use case diagram

A collaboration diagram groups together the interactions between different

objects. The interactions are listed as numbered interactions that help to trace the
sequence of the interactions. The collaboration diagram helps to identify all the
possible interactions that each object has with other objects.

 Component diagram:

The component diagram represents the high-level parts that make up the
system. This diagram depicts, at a high level, what components form part of the
system and how they are interrelated. A component diagram depicts the
components culled after the system has undergone the development or construction
phase.

 Deployment diagram:

The deployment diagram captures the configuration of the runtime

elements of the application. This diagram is by far most useful when a system is
built and ready to be deployed. Now that we have an idea of the different UML
diagrams, let us see if we can somehow group together these diagrams to enable us
to further understand how to use them.

25
UML Diagram Classification—Static, Dynamic, and Implementation

A software system can be said to have two distinct characteristics: a structural,

"static" partand a behavioral, "dynamic" part. In addition to these two characteristics,
an additional characteristic that a software system possesses is related to
implementation. Before we categorize UML diagrams into each of these three
characteristics, let us take a quick look at exactly what these characteristics are.

 Static:

The static characteristic of a system is essentially the structural aspect of the

system. The static characteristics define what parts the system is made up of.

 Dynamic:

The behavioral features of a system; for example, the ways a system behaves
in response to certain events or actions are the dynamic characteristics of a
system.

 Implementation:

The implementation characteristic of a system is an entirely new feature that

describes the different elements required for deploying a system.

The UML diagrams that fall under each of these categories are:

 static

 Use case diagram

 Class diagram

 Dynamic

 Object diagram

 State diagram

 Activity diagram

 Sequence diagram

 Collaboration diagram

26
Implementation:

o Component diagram

o Deployment diagram

Finally, let us take a look at the 4+1 view of UML diagrams.

Views of UML Diagrams

Design viewConsidering that the UML diagrams can be used in different

stages in the life cycle of a system, let us take a look at the "4+1 view" of UML
diagrams. The 4+1 view offers a different perspective to classify and apply UML
diagrams. The 4+1 view is essentially how a system can be viewed from a software
life cycle perspective. Each of these views represents how a system can be modeled.
The different views are:

 Design View:

The dynamic behavior of a system is the structural view of the system. This
gives an idea of what a given system is made up of. Class diagrams and object
diagrams form the design view of the system.

 Process View:

The dynamic behavior of a system can be seen using the process view. The
different diagrams such as the state diagram, activity diagram, sequence
diagram, and collaboration diagram are used in this view.

 Component View:

Component view shows the grouped modules of a given system modeled

using the component diagram

 Deployment View:

The deployment diagram of UML is used to identify the deployment modules

for a given system.

27
 Use case View:

Finally, we have the use case view. Use case diagrams of UML are used to
view a system from this perspective as a set of discrete activities or
transactions.

UML Diagrams:

Collaboration Diagrams

Admin Login

Admin Add Collaboration Diagram

DAL : sqlhelper
4 : ExecuteNonQuery()

DataBase

3 : ExecuteNonQuery()
5 : Response To ExecuteNonQuery()

BAL : clsState

2 : InsertCity()
6 : Return Response()

7 : Show Result()

City
1 : Add City()

Admin

28
Registration Collaboration Diagram

DAL : SqlHelper

3 : ExecuteNonQuery()

DataBase

2 : ExecuteNonQuery()

4 : Response to ExecuteNonQuery()

BAL : ClsRegistration

1 : Registration()

6 : Show Result() 5 : Return Response()

Registration

29
JobRecuriter Update Profile

5 : Response To ExecuteNonQuery()
DataBase

BAL : clsJobrecuriterProfile

4 : ExecuteNonQuery() 3 : ExecuteNonQuery()

2 : UpdateProfile()
6 : Return Response()

DAL : sqlhelper

7 : Show Result()
Update JobRecuriter Profile

1 : ModifyProfile()

JobRecuriter

30
City

DataBase 5 : Execute_Nonquery() Dal : sqlhelper

4 : InsertCities()

6 : return response() Bal : clsCity

3 : btn_Add()

2 : Invalid Data()
frmCity

1 : lnkCity()

Admin

31
Country

DataBase

5 : Execute_Nonquery()
Dal : sqlhelper

4 : InsertCountries()

6 : return response()

Bal : clsCountry

3 : btn_Add()

2 : Invalid Data()

frmCountry

1 : lnkCountry()

Admin

32
User Registration

DataBase 5 : Execute_Nonquery()
Dal : sqlhelper

4 : InsertUserDetails()

6 : return response()

Bal : clsUser

3 : btn_submit()

2 : Invalid Data()
frmUser

1 : lnkUser()

Home

33
Sequence Diagrams:

SEQUENCE DIAGRAMS

Sequence Diagrams Represent the objects participating the interaction

horizontally and time vertically.

Admin Login

Bal : AdminLogin Dal : SqlHelper DataBase

Admin Login

1 : Login()

2 : CheckUser()

3 : Execute NonQuery()

4 : Exeute NonQuery()

5 : Response to ExecuteNonQuery()

6 : Get Response()

7 : Show Result()

34
Admin Add Country Sequence Diagram

Admin Country BAL : clsCountry DAL : sqlhelper DataBase

1 : Add Country()

2 : InsertCountry()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

35
Admin Add State Sequence Diagram

Admin State BAL : clsState DAL : sqlhelper DataBase

1 : Add State()

2 : InsertState()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

36
Admin Add City Sequence Diagram

Admin City BAL : clsState DAL : sqlhelper DataBase

1 : Add City()

2 : InsertCity()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

37
Jobseeker Update Profile Sequence Diagram

JobSeeker Update Jobseeker Profile BAL : clsUpdateJobSeekerProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

38
JobRecuriter Update Profile Sequence Diagram

JobRecuriter Update JobRecuriter Profile BAL : clsJobrecuriterProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

39
Registration Sequence Diagram

DAL :SqlHelper
Registration BAL :ClsRegistration DataBase

1 : Registration()

2 : ExecuteNonQuery()

3 : ExecuteNonQuery()

4 : Response to ExecuteNonQuery()

5 : Return Response()

6 : Show Result()

40
Activity Diagrams:

Login Activity

[Enter User Name and Password]

Get Details

[Submit]

Validate Data

Rejected No yes Accepted

41
Jobseeker Registration Activity

[Enter User Name and Password]

Get The Details

[submit]

Validate Details

[Enter Details]
Get Details

[submit]

Validate Data

Accepted

[Success Fully Registered]

42
Admin Activity Diagram:

[Enter User Name and Password]

Get Data

[Submit]

Validate Data

No

Yes

[Administration] [Generate Reports]

Get the Data

Country State
[Submit]

Get the Data Get the Data

Validate Data

[Submit] [Submit]
No

Validate Data Validate Data

[Successfully Generated]
No
No

Yes
Yes

[Successfully Done]

43
Job Recuriter Activity Diagram:

Enter User Information

Get Data

[Submit]

Validate Data

No

Yes

Personal information
Login Information

Get the Data Get the Data

[Submit]
[Submit]
Validate Data
Validate Data

No

No Yes

Yes

[Successfully Done]

44
5.3 DATA DICTONARY

After carefully understanding the requirements of the client the the entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of data entry.

City Detail

Country Detail

Experience Details

Functional Area

45
Job Opening Detail

Jobseeker Response to Recruiter

Job Type Detail

Location Master

46
Qualification

Recruiter Account Details

Recruiter Organization Details

Recruiter Response to Jobseeker

47
Skill Master

State detais

Student Detail

Admin Login

Jobseeker Background Details

48
Contact Details

Jobseeker Job Details

Jobseeker Registration

49
Jobseeker Resume

Jobseeker Technical Details.

5.4User Interfaces or Output Screens.

fig 5.4.1 Administration Home page

50
Fig:5.4.2 Administration Job Catagory

51
Fig:5.4.3 JobSeeker Login

52
Fig:5.4.4 TechnicalSkills Details

53
Fig:5.4.5 Academic Details

54
Fig:5.4.6 Career Path

55
Fig:5.4.7 Job Opening Details

56
Fig:Select Location To Select Jobs

57
Fig:View details of Jobseeker

58
Fig: Recruiter Login

59
60
 6 TESTING

6.1. INTRODUCTION

Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. In fact, testing is
the one step in the software engineering process that could be viewed as destructive
rather than constructive.

A strategy for software testing integrates software test case design methods
into a well-planned series of steps that result in the successful construction of
software. Testing is the set of activities that can be planned in advance and conducted
systematically. The underlying motivation of program testing is to affirm software
quality with methods that can economically and effectively apply to both strategic to
both large and small-scale systems.

6.2. STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system

engineering defines the role of software and leads to software requirement analysis
where the information domain, functions, behavior, performance, constraints and
validation criteria for software are established. Moving inward along the spiral, we
come to design and finally to coding. To develop computer software we spiral in
along streamlines that decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral.
Unit testing begins at the vertex of the spiral and concentrates on each unit of the
software as implemented in source code. Testing progress by moving outward along
the spiral to integration testing, where the focus is on the design and the construction
of the software architecture. Talking another turn on outward on the spiral we
encounter validation testing where requirements established as part of software
requirements analysis are validated against the software that has been constructed.
Finally we arrive at system testing, where the software and other system elements are
tested as a whole.

61
 UNIT TESTING

MODULE
TESTING

Component SUB-SYSTEM
Testing TESING

SYSTEM
TESTING
Integration Testing

ACCEPTANCE
TESTING
User
Testing

6.3 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the
module. The unit testing we have is white box oriented and some modules the steps
are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that

 All independent paths have been exercised at least once

 All logical decisions have been exercised on their true and false sides

62
 All loops are executed at their boundaries and within their operational bounds

 All internal data structures have been exercised to assure their validity.

To follow the concept of white box testing we have tested each form .we have
created independently to verify that Data flow is correct, All conditions are exercised
to check their validity, All loops are executed on their boundaries.

2. BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to

derive test cases for all the functions. The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graph.

Determine the Cyclomatic complexity of resultant flow graph, using formula:

V(G)=E-N+2 or

V(G)=P+1 or

V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

63
3. CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and
false aspects. And all the resulting paths were tested. So that each path that may be
generate on particular condition is traced to uncover any possible errors.

4. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of
testing. These were particularly useful in nested statements.

5. LOOP TESTING

In this type of testing all the loops are tested to all the limits possible. The
following exercise was adopted for all loops:

 All the loops were tested at their limits, just above them and just below them.

 All the loops were skipped at least once.

 For nested loops test the inner most loop first and then work outwards.

 For concatenated loops the values of dependent loops were set with the help of
connected loop.

64
 7. SYSTEM SECURITY

7.1. Introduction

The protection of computer based resources that includes hardware, software,

data, procedures and people against unauthorized use or natural

Disaster is known as System Security.

System Security can be divided into four related issues:

 Security

 Integrity

 Privacy

 Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to

the hardware and operation systems to protect against deliberate or accidental damage
from a defined threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and
destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and programs,

appropriate physical security and safety against external threats such as eavesdropping
and wiretapping.

PRIVACY defines the rights of the user or organizations to determine what

information they are willing to share with or accept from others and how the
organization can be protected against unwelcome, unfair or excessive dissemination
of information about it.

CONFIDENTIALITY is a special status given to sensitive information in a database

to minimize the possible invasion of privacy. It is an attribute of information that
characterizes its need for protection.

65
7.2. SECURITY IN SOFTWARE

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

controls to avoid the system from failing. It is always important to ensure that only
valid data is entered and only valid operations are performed on the system. The
system employees two types of checks and controls:

CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that only
valid data is entered. Client side validation saves server time and load to handle
invalid data. Some checks imposed are:

 VBScript in used to ensure those required fields are filled with suitable data only.
Maximum lengths of the fields of the forms are appropriately defined.

 Forms cannot be submitted without filling up the mandatory data so that manual
mistakes of submitting empty fields that are mandatory can be sorted out at the
client side to save the server time and load.

 Tab-indexes are set according to the need and taking into account the ease of user
while working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are necessary
to save the system from failing and intimating the user that some invalid operation has
been performed or the performed operation is restricted. Some of the server side
checks imposed is:

 Server side constraint has been imposed to check for the validity of primary key
and foreign key. A primary key value cannot be duplicated. Any attempt to
duplicate the primary value results into a message intimating the user about those
values through the forms using foreign key can be updated only of the existing
foreign key values.

 User is intimating through appropriate messages about the successful operations

or exceptions occurring at server side.

66
Various Access Control Mechanisms have been built so that one user may not agitate
upon another. Access permissions to various types of users are controlled according to
the organizational structure. Only permitted users can log on to the system and can
have access according to their category. User- name, passwords and permissions are
controlled o the server side.

8.CONCLUSION

It has been a great pleasure for me to work on this exciting and challenging
project. This project proved good for me as it provided practical knowledge of not
only programming in ASP.NET and VB.NET web based application and no some
extent Windows Application and SQL Server, but also about all handling procedure
related with “PROJECT NAME”. It also provides knowledge about the latest
technology used in developing web enabled application and client server technology
that will be great demand in future. This will provide better opportunities and
guidance in future in developing projects independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The merits of
this project are as follows: -

 It’s a web-enabled project.

 This project offers user to enter the data through simple and interactive forms.
This is very helpful for the client to enter the desired information through so much
simplicity.

67
 The user is mainly more concerned about the validity of the data, whatever he is
entering. There are checks on every stages of any new creation, data entry or
updation so that the user cannot enter the invalid data, which can create problems
at later date.

 Data storage and retrieval will become faster and easier to maintain because data
is stored in a systematic manner and in a single database.

 Allocating of sample results becomes much faster because at a time the user can
see the records of last years.

 Easier and faster data transfer through latest technology associated with the
computer and communication.

LIMITATIONS:

 The size of the database increases day-by-day, increasing the load on the database
back up and data maintenance activity.

 Training for simple computer operations is necessary for the users working on
the system.

9.FUTURE IMPROVEMENT

 This System being web-based and an undertaking of Cyber Security Division,

needs to be thoroughly tested to find out any security gaps.

68
 A console for the data Centre may be made available to allow the personnel to
monitor on the sites which were cleared for hosting during a particular period.

 Moreover, it is just a beginning; further the system may be utilized in various

other types of auditing operation viz. Network auditing or similar
process/workflow based applications...

69
70
10. BIBLIOGRAPHY

 FOR .NET INSTALLATION

www.support.mircosoft.com

 FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com

www.15seconds.com

 FOR SQL

www.msdn.microsoft.com

 FOR ASP.NET

www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

71