Task Management System

PROJECT REPORT TASK MANAGEMENT
SYNOPSIS
1
PROJECT OVERVIEW
The “THE TASK MANAGEMENT (HUMAN RESOURCE MANAGEMENT PROJECT)” is

real time software that brings greater organization and effectiveness to the full range of Human
Resource functions and responsibilities.
This software automates the task management inside the organization, there by saving the
valuable time and efforts of employees. This software provides for easy, accurate and timely
retrieval of Employee and activity-oriented information through menu driven, user-friendly
operations.
 OBJECTIVE
The Objective Of Our Project Is To:
1. This software would completely automate the HR management.
2. Would save precious time and effort of officials.
3. Minimize the possibility of human error.
4. All the records related to different employees of the department would be saved for the
future reference.
5. Generation of computerized reports by just using the few clicks of a mouse.
2
PROBLEM DEFINITION AND SPECIFICATION
Our Problem Is to Design an Effective and Easy-To-Use “HRMS” Software that meet the
information need of all levels of Management and facilitates Decision Support, Planning,
Monitoring, Control of Daily Activities.
 SPECIFICATION
1. It Provides Easy And Efficient Interface To Interact With.
2. Would save precious time and effort of officials.
3. Minimize the possibility of human error.
4. All the records related to different employees of the department would be saved for the
future reference.
5. Generation of computerized reports by just using the few clicks of a mouse.
6. It Manages Ur Data Or Account Details With Proper Care.
7. Its powerful record keeping, monitoring and reporting capabilities will save you time,
while reducing your exposure to employment related lawsuits by ensuring you have
proper documentation.
3
• What is the problem?
The problem is to convert a manual system into an automated one.
• Why is it important to solve the problem?
This is done to save the time and help the users to keep a record for themselves to
avoid any sort of confusion and conflicts.
• What are the possible solutions to the problem?
This problem can be easily solved on any of the following programming language
• C#
• VB
• What exactly are the data input to the system and what exactly are the data output
required of the system?
Data input to the system may be:

• Id of administrator or user
• Password of administrator
• USER_ID that is unique.
• USER password
Data output to the system may be:

• Admin page
• User Main Page
• Employee details
4
• Project details
• Employee’s Salary details
• Client details
• PopUp window showing project deadline to the user.
• Display of an ERROR MESSAGE when the user enters an invalid data.
• If there are external software or hardware with which the developed software has to
interface, then what exactly would the data interchange formats with the external system
be?
After the analyst has understood the exact customer problems, he proceeds to identify and
resolve those problems. The most important problems that the analyst has to identify and
eliminate are the problems of anomalies, inconsistencies, and incompleteness.
• Anomaly
An anomaly is the ambiguity in the problem. When a problem is anomalous,

several interpretation of the requirement is possible.
• Inconsistency
The problem becomes inconsistent, if any one of the requirements contradicts

another. It means some part of the problem contradicts with some other part.
• Incompleteness
Incomplete information regarding the problem is one where some of the

requirements have been over looked. Often, incompleteness is caused by the inability of
the customer to visualize and anticipate the entire feature that would be required in a
system to be developed
5
EXISTING SYSTEM
The HR Administration falls short of controlling the employee’s activities in analyzing his/her
strengths and weakness. The decision for appraisal of assigning next project to the employee or
to show him/her the deadline of project – where lies with proper projection. He is not provided
with the detailed project information done or to be assigned based on Application / Verticals.
1. DRAWBACKS IN EXISTING SYSTEM:
 Need of extra manual effort.

 It used to take much time to find any employee
 Not very much accurate.
 Does not provide any information about client.
 Deadline of project not shown to employees.
 Danger of losing the files in some cases.
2. NEED FOR THE NEW SYSTEM
The new system can be used to manage the cases more accurately and efficiently. The need for
software that can process information much faster than existing and can therefore help to
increase the flow of work and timely availability of information was inevitable. In order to
satisfy all above requirement, this software system has been developed and enhanced.
3. BENEFITS OF THE PROPOSED SYSTEM
6
The new system will not only increase the efficiency of the system but also Provide user friendly
interface. The user will have easy access of the various forms. This will not only increase the
clarity in the working style of the System but also reduces the valuable resources.
4. ADVANTAGES OF PROPOSED SYSTEM:

 Very fast and accurate.
 No need of any extra manual effort.
 No fever of data loss.
 Just need a little knowledge to operate the system.
 Doesn’t require any extra hardware device.
 Employees on their main form get the message of project deadline coming.
 Provide information about clients.
 At last very easy to find the employees.
END USERS TO THE SYSTEM

Since the system is intranet based, hence restrictions to unauthorized and unauthenticated access
have to be managed efficiently.
The system is permitted to allow two types of users:
1. ADMIN LEVEL USER:
The user at the admin level also acts as the administrator of the system and can excise full
control to the system resources.
The admin level user is entitled to perform the following tasks.
• Perform transaction level data entry based as per the system requirements.
• View the project details issued to each employee.
• Authorized each employee to use the system by providing user id and password.
7
• View the details of each employee their employee id, departments, salary information,
project details etc.
• View the details of each client existing in the database.
• Create new client and project in the database.
• Performing miscellaneous operations like editing, deleting any employee records, project
details, salary details etc.
2. AUTHORIZED LEVEL USER:
The user at this level is allowed to perform the following tasks on the system:
• .Perform transaction level data entry as per the system requirements.
• View his/her profile.
• View the project details assigned to his/her.
• View his/her salary details
• Performing miscellaneous operations like changing his login password for proper
security measures
TECHNICAL ENVIRONMENT FOR THE PROPOSED SYSTEM
Following will be the minimum requirement of hardware to run the software, which will be
developed. Different specification for server and client is given below.
HARDWARE:
 Pentium Processor : 2.1 GHz and above

 512 MB or higher RAM
 3x72 GB or Higher SCSI Hard disk
 CD-ROM Drive
 104 Keyboards
 PS/2 Mouse
8
 USB Ports – 2 or higher

 LAN Card (10/100 Mbps)
 Modem 56 Kbps
 Color Monitor – 14” or 15”
 Printers
 UPS 2 KVA or higher
 16 ports Unmanaged Switch (For Networking)
SOFTWARE
All software’s must be licensed one. No pirated software should be used as this may lead to virus
in the system and may corrupt the database files and other software.
 SQL Server 2005

 Visual Studio 2005
 Anti Virus Software
 Front-end--Project will be developed using ASP.NET (Platform) with C#.Net as
language.
 Back-end: -- MSSQL-Server 2005
 Technology - Ajax
9
TECHNOLOGY USED
ASP.NET is a new and powerful technology for writing dynamic web pages. It is a convergence
of two major Microsoft technologies - Active Server Pages (ASP) and .NET. It is part of the
.NET Framework. It 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 such as:
Increased Productivity
• Easy Programming Model ASP.NET makes building real world Web applications
dramatically easier. ASP.NET server controls enable an HTML-like style of declarative
programming that lets you build great pages with far less code than with classic ASP or
Technologies like PHP or JSP. Best of all, ASP.NET pages work in all browsers –
including Fire fox, Opera, Safari, and Internet Explorer.
Built Upon Standards
• XHTML Compliance Creating XHTML-compliant pages are easy with ASP.NET.

Web controls support rendering valid, well-formed XHTML markup with a simple
configuration option.
• Accessibility Support Create Web applications usable by the widest possible audience
support for building and testing accessible Web applications.
10
Improved Security
• Application Services There is no need to write common code for managing users and
personalization with ASP.NET, as these features are included as application services.
ASP.NET membership services provide best practices guidance and support for
managing access to your Web applications.
• Built-in Protection ASP.NET provides built-in protection from many common forms of
hacker attacks, including cross-site scripting, request-replay attacks and more.
Improved Performance and Scalability
• Caching: Caching can dramatically improve the performance of Web applications, and
ASP.NET supports many forms of caching. Output caching improves the rendering of
controls to XHTML. Database caching enables the application to be notified when the
underlying database changes, eliminating unnecessary queries.
• Web-Farm Session State ASP.NET session state lets you share session data user-
specific state values across all machines in your Web farm. Now a user can hit different
servers in the web farm over multiple requests and still have full access to her session.
Extensible Architecture
• Provider Model The application services of ASP.NET use the provider model to
connect to external services for storage and more. This enables the developer to change
the database or other service used to store the membership, personalization or site map
information by editing the configuration.
• Web Parts Easily build portal applications with the built-in Web part functionality.
Create Web applications that enable end users to organize and personalize their page
content and layout.
About Web-Server
A web server is software that manages web pages and makes them available to ‘client’
browser – via a local network or over the Internet. In the case of the internet, the web
11
server and browser are usually on two different machines, possibly many miles part.
However, in a more local situation we might set up a machine that runs the web server
software, and then use a browser on the same machine to look at its web pages.
• There are web servers available like Apache, Internet Information Services (IIS) and
Iplanet’s Enterprise server.
PROJECT DEVELOPMENT AND TEAM STRUCTURE:
The following diagram depicts team structure for development.
PROJECT
PROJECT LEADER
PROGRAMME
TRAINEE
Where for “TASK MANAGEMENT SYSTEM” project the designation and name are:
Project Manager : Mr. Vikram Singh Kandari

Project Programmer : Mr. Durgesh Mishra
12
Four P’s Formula:

Effective software project management focuses on the four P’s: people, product, process
and project. The order is not arbitrary. Forgetting that Software engineering work is an
intense human endeavor results in unsuccessful project management. Moreover lack of
proper communication with the customer risks the building of an elegant solution of the
wrong problem.
Management Spectrum of the Project:
Explanation of the four p’s
People
Project Product
Dependency
Order
Process
1)The People:
The people management maturity model defines the following key practice areas for software
people: Selection, performance, management, training, compensation, career development, work
design and team culture.
As far as this project was concerned the Project guide had a very good experience of how to
develop an efficient database design with a minimum redundancy was very much motivating. He
was full of brilliant ideas, which could be incorporated into the system.
13
2) The Product:
What do we want to deliver to the customer, obviously a product a solution to his/her problems.
Hence objective and scope of work should be define clearly to understand the requirements. It
may help the manager to select a best approach within constraint imposed by delivery deadlines,
budgetary restrictions, Personnel availability etc.
Before the project plan for the project could be finalized and its objective and scope were
established, various alternative solutions were considered and technical management constraints
were identified.
It was on this basis that:
Realistic breakdown of the project tasks could be made.

A manageable project schedule that provided a meaningful indication of progress could be
made. Effective assessment of the risks was made.
3) The Process:
A software process provides the framework from which a comprehensive plan for software
development can be established. A small number of framework activities are applicable to all
software projects regardless of their size or Complexity.A number of different tasks set – tasks,
milestones, deliverables and quality assurance points –enable the framework activities to be
adapted to the characteristics of the software project and the requirements of the project team.
4) The Project:
A proper planning is required to monitor the status of development and to control the
complexity. Most of the project are coming late with cost overruns of more than 100%. In order
to manage a successful project, we must understand what can go wrong and how to do it right.
Software surprises are always risky and we should minimize them. We should have a planning
mechanism to give warning before the occurrence of any surprise. All four factors (People,
product, process and project) are important for the success of the project.
14
Co-ordination and Communication Techniques Used:
Comprehensive Communication was conducted
1) With the employees in the Administration department.
2) With the higher authorities to determine what they expect the system to do.
3) With the Community on dispute to determine the kind of reports they want the system to
generate so that they can review the working of the system on basis of these reports.
15
METHODOLOGY
The system has been designed keeping in mind the requirements not fulfilled by the existing
system and also trying out new, innovative aspects that provide ease of use and efficient
functionality to the system.
The project thus not only acts as a corrective but also as a perfective maintenance approach to
the existing system.
SOFTWARE DEVELOPMENT PROCESS
The Development Process model used is the Waterfall Development Model.
The stages covered are as follows:
• Software Requirement Specifications (SRS)
• Analysis and Design
• Testing
• Deployment
• Support
16
Keywords used in system

documentation
17
 Generic Technology keywords
Databases, Network and middleware, Programming
 Specific Technology keywords
MS-SQL server, MS-Access, C#, Asp.Net
 Project type keywords
Analysis, Design, Implementation, Testing, User Interface
18
TASK MANAGEMENT SYSTEM
CONTENTS PAGE NOs.

1. LITERATURE SURVEY
1.1 Company Profile
1.2 Programming language & Development Tools
2. INTRODUCTION OF THE PROJECT

2.1 HRMS
2.2 Task Management System
2.3 Definition of the problem
3. EXISTING STATE OF ART
4. TOOLS USED FOR SOFTWARE DEVELOPMENT
5. PROPOSED SYSTEM/SOLUTION
5.1 Proposed solution
5.2 Feasibility Study
5.3 Module Description
5.4 SRS Report
6. SDLC/DATA FLOW DIAGRAM/OBJECT FLOW DIAGRAM

6.1 System Analysis and Design
6.1.1 DFDs
6.1.2 ER Diagrams
6.1.3 Project Flow
6.1.4 Flow Chart
6.1.5 Database Design
6.2 Coding Style
6.3 Testing
6.3.1 Screens
6.4 Software Implementation
6.5 Software Maintenance
7. RESULT & SIGNIFICANT IMPROVEMENTS OF THE SYSTEM
8. CONCLUSION
9. BIBLIOGRAPHY / REFERENCES
19
LITERATURE SURVEY
COMPANY PROFILE
20
INTECH SOFTWARE SERVICES PVT. LTD.

Intech Software Services Pvt Ltd an ambitious convergence of dedicated professionals and has
its own vision that is its guiding light to all its clients. Its prime objective is to remain on the
leading edge of the technology without losing sight of customer requirements. We have always
won accolades from past and present clients for our dedication. Their working areas are schools /
colleges, BPO, Consultancy solutions, traders, financial institutions, manufacturing units,
distribution networks, service sectors, NGOs etc.Their approach focuses on new ways of
business combining IT innovation and adoption while also leveraging an organization’s current
IT assets. Their work with large global corporations and new products or services and to
implement prudent business and technology strategies in today’s environment. Intech Software
Services Pvt Ltd has its Development and Document Processing center located Dehradun,
uttarakhand India.
Intech Software Services Pvt. Ltd. comprises of a team of professionals segmented into five
teams:
- Interactive design
- Content Management
- Marketing
- Technology
- Project Management
Intech Software Services Pvt. Ltd. will always live up to achieve the mission of achieving
excellence through world class practices and standards in quality and project management. The
company has dedicated itself to achieve high level Customer Satisfaction by executing quality
work.
Commitment, Credibility, Quality and teamwork are their guiding values. They believe in the
highest quality products and services for all of their customers. They believe their customers are
greatest asset, and they are dedicated to serving their needs.
They apply technology with innovation and responsibility to achieve two broad objectives:
• Effectively address the business issues our customers face today.
• Generate new opportunities that will help them stay ahead in the future.
21
This approach rests on:

• A strategy where we architect, integrate and manage technology services and solutions -
we call it AIM for success.
• A robust offshore development methodology and reduced demand on customer resources.
• A focus on the use of reusable frameworks to provide cost and times benefits.
They combine the best people, processes and technology to achieve excellent results -
consistency. We offer customers the advantages of:
Speed:
They understand the importance of timing, of getting there before the competition. A rich
portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested
methodology ensures that we follow a predictable, low - risk path to achieve results. Our track
record is testimony to complex projects delivered within and evens before schedule.
Expertise:
Our teams combine cutting edge technology skills with rich domain expertise. What’s equally
important - they share a strong customer orientation that means they actually start by listening to
the customer. They’re focused on coming up with solutions that serve customer requirements
today and anticipate future needs.
A full service portfolio:

They offer customers the advantage of being able to Architect, integrate and manage technology
services. This means that they can rely on one, fully accountable source instead of trying to
integrate disparate multi vendor solutions
Services:
Intech Software Services Pvt. Ltd. strives to provide you custom software solutions that will help
you to remain in step with your competition by continuously improving your information
technology based business solutions. For this, we use modern software development platforms,
software development tools as well as employ latest project management techniques.
22
Using structured methodologies and proven IT processes helps to reduce complexity, risks and
costs associated with Information technology outsourcing. We can help you develop customized
software applications and assist you thorough out the entire software development Life Cycle,
including project management, systems analysis and design, software development,
implementation and training.
In a nutshell our strong technical team can help ensure that the client-server products and
services we provide meet your expectations.
Our Application development service offerings includes:

- Custom Application Development
- Integrated Web Solutions
- Graphics and Multimedia
- Mobile Games and Applications
The best solution for a company is the one that allows it to conduct its current business more
efficiently and at a lower cost, By reducing the cost of attracting new customers, delivering
products more efficiently and reducing costs, profits will increase.
1. Custom Application Development

Our offshore outsourcing software application development services include customized
application development as well as product development. At Intech Software Services Pvt. Ltd,
we use technology to create powerful solutions that are focused on such critical areas as
enhancing customer relations and increasing revenue opportunities.
We use state-of-the-art technologies to translate your IT vision into reality and create powerful
solutions that are focused on enhancing customer relations, increasing revenue opportunities and
the creation of new competitive advantage for you.
At Intech Software Services Pvt Ltd., we focus on building applications using software
components which reduce cost and time of development. Our business model also includes co-
development of products where we share revenue and risk together.
We provide solutions like
- Client - Server Application Development
- Distributed Application Development
23
- Enterprise Application Integration

- Browser Based Applications
Offshore Outsourcing Application Development Process

Feasibility Analysis - Feasibility is one of the most important aspect of any project. An
application or product that is feasible at one point in time, may become infeasible later.
Identifying the possible future scenario, technical and economical feasibility study is conducted
to decide goal and development requirements.
System Analysis and Prototyping - System analysis and prototyping is done based on client
requirements. Functionalities and user interface design is done at this stage. Implementation - Based on
system analysis and prototypes, coding takes place.
Testing - Requirement testing and product testing is done after implementation.
2. Integrated Web Solutions
Websites have appeared as the most cost-effective way to promote business. The advantages of
web market are that the products can be seen worldwide monitoring and dealing with customers
have reduced to everyday interaction.
We provide Web Solutions to enhance your business, marketing and profit goals.Intech Software
Services Pvt. Ltd. has a proven record of success in the design and development of web solutions
over the years. We develop and support web solutions of any scope from small advertising sites
to big corporate.
The complexities associated with this medium are emancipated that keep proliferating every day.
And it is our assurance to provide a tangible solution to every problem and complexity. Our
creative team is experienced in designing for the full range of media from traditional print and
exhibition projects, to all manner of digital creative.
We provide world-class web solutions including technical content solutions, corporate solutions,
e-commerce and other customized solutions. Our Solutions are bound to save big money and
24
help drive you towards efficiency.

You can rely on us, as we are 24 X 7 days available, providing top quality services and smooth
client support system. So, why not we draw the maximum mileage from our web solutions?
3. Graphics and Multimedia

Flash Animation Design
Flash animations can create emotions and feelings that static text and pictures cannot. Coupled
with sound and music, it can be a very compelling factor that warrants long attention span of
your audience when used correctly.
In addition, Flash animations can explain complex technical information much better than static
content. Product usage procedure, process flow chart, technical infrastructure and information
organization are area that Flash animations excel in.
Intech Software Services Pvt. Ltd. can help you convey that emotional thought or that technical
explanation with ease. Our creative team has delivered a number of Flash animated
introductions, slideshows, effects and simulations for our clients.
Our esteemed technical team is proud to have pioneered special ways to content managed Flash
animations. This translates to fresh and dynamic content for your Flash animations, saving you
cost, time and giving you the competitive edge.
4. Mobile Games and Applications

Intech Software Services Pvt. Ltd. has expertise to develop online games, multiplayer games,
mobile games, Flash games, E-learning games and educational games.
Online games are an effective medium for brand promotion and sustenance. Research has
established that making the brand a part of a game play or advertising in online games can achieve up to
60% increase in awareness for a new product. And also those in-game animated ads achieve twice the recall
of static billboards.
Online games are efficient educational tools. The increasing interest in ‘pleasurable learning’
proves that games could be a good solution in educating through delightful means.
Intech Software Services Pvt. Ltd. takes conscious efforts to design customized online games
that optimize brand impression, and also to evolve tactical educational games that are functional
by nature.
25
What is a mobile game?

It is an interface boasting variety and change. Games are full of positive ions that help infuse
energy and freshness in a somewhat “MAD” world that we live in today. If there is anything that
needs some innovation and charging up, it surely is our mind and that is what a game does the
best. Today nothing can be more accessible than a game on a mobile phone. So, we do love
them! Don’t we…
What is a mobile application?

We cannot separate the two for one gives us the energy and inspiration to reign over the real
puzzles of our lives while the other simplifies our job by providing innovative solutions to do
what we do normally and what is best described as complex mechanical tasks, at just click of a
button. They in turn save us the much needed time that we would like to spend with our loved
ones.
With their rich expertise and experience in information technology they are in the best
position to provide software solutions to distinct business requirements.
26
PROGRAMMING LANGUAGE & DEVELOPMENT TOOLS
ENVIRONMENT: Introducing the .NET Platform
The .NET Framework is a managed type-safe environment for application development and
execution. The .NET Framework manages all aspects of your program’s execution. It allocates
memory for the storage of data and instructions, grants or denies the appropriate permissions to
your application, initiates and manages application execution, and manages the reallocation of
memory from resources that are no longer needed. The .NET Framework consists of two main
components: the common language runtime and the .NET Framework class library.
The common language runtime can be thought of as the environment that manages code
execution. It provides core services, such as code compilation, memory allocation, thread
management, and garbage collection. Through the common type system (CTS), it enforces strict
type-safety and ensures that code is executed in a safe environment by also enforcing code
access security.
The .NET Framework class library provides a collection of useful and reusable types that
are designed to integrate with the common language runtime. The types provided by the .NET
Framework are object-oriented and fully extensible, and they allow you to seamlessly integrate
your applications with the .NET Framework. The .NET Framework is designed for cross-
language compatibility, which means, simply, that .NET components can interact with each other
no matter what supported language they were written in originally. So, an application written in
Microsoft Visual Basic .NET might reference a dynamic-link library (DLL) file written in
Microsoft Visual C#, which in turn might access a resource written in managed Microsoft Visual
C++ or any other .NET language. This language interoperability extends to full object-oriented
27
inheritance. A Visual Basic .NET class might be derived from a C# class, for example, or vice
versa.
This level of cross-language compatibility is possible because of the common language
runtime. When a .NET application is compiled, it is converted from the language in which it was
written (Visual Basic .NET, C#, or any other .NET-compliant language) to Microsoft
Intermediate Language (MSIL or IL). MSIL is a low-level language that the common language
runtime can read and understand. Because all .NET executables and DLLs exist as MSIL, they
can freely interoperate. The Common Language Specification (CLS) defines the minimum
standards to which .NET language compilers must conform. Thus, the CLS ensures that any
source code successfully compiled by a .NET compiler can interoperate with the .NET
Framework.
The CTS ensures type compatibility between .NET components. Because .NET applications are
converted to IL prior to deployment and execution, all primitive data types are represented as
.NET types. Thus, a Visual Basic Integer and a C# int are both represented in IL code as a
System.Int32. Because both languages use a common type system, it is possible to transfer data
between components and avoid time-consuming conversions or hard-to-find errors.
Visual Studio .NET ships with languages such as Visual Basic .NET, Visual C#, and Visual C++
with managed extensions, as well as the JScript scripting language. You can also write managed
code for the .NET Framework in other languages. Third-party tools and compilers exist for
Fortran, Cobol, Perl, and a host of other languages
All of these languages share the same cross-language compatibility and inheritability.
Thus, you can write code for the .NET Framework in the language of your choice, and it will be
able to interact with code written for the .NET Framework in any other language.
28
V C# Vb.net Jscript. …
I net
S
U Common Language Specification (CLS)
A
L
Window
s Forms Web Form Web Service
S
T
U ADO.Net and XML
D
I
O .Net Framework Classes
. Common Language Runtime

Ne
t Windows COM+ Services
t
Microsoft .NET Architecture Hierarchy
Features of the .NET Platform

• Multilanguage Development
• Platform and Processor Independence
• Versioning Support
• Security
Components of the .NET Architecture

As we mentioned earlier, there is a lot to the .NET Framework. In this section,
We identify the individual components and describe their features and how they
Fit into the overall picture.
29
. NET Runtime
The heart of the .NET Framework is the CLR. Similar in concept to the Java Virtual Machine, it
is a runtime environment that executes MSIL code. Unlike the Java environment, which is the
concept of one language for all purposes, the .NET platform supports multiple programming
languages through the use of the Common Language Specification, which defines the output
required of compilers that want to target the CLR.
Managed/Unmanaged Code
Because all code targeted at the .NET platform runs with the CLR environment, it is referred to
as managed code. This simply means that the execution of the code and its behavior is managed
by the CLR. The metadata available with managed code contains the information required to
allow the CLR to manage its safe execution. By safe execution we mean memory and security
management, type safety, and inter-language interoperability. Unmanaged code can write to
areas of memory it does not own, execute instructions at arbitrary locations in memory, and
exhibit any number of other bad behaviors that cannot be managed or prevented by the CLR.
Most of the applications running on Windows today are unmanaged.
Intermediate Language
The .NET intermediate language, MSIL, is defined in the Common LanguageSpecification. It is
an amalgam of a low-level language similar in many ways to aMachine language and a higher
object language. You can write applications directly in MSIL, much as you can write directly in
assembly language. Thankfully, this is not necessary for most purposes.
Compiling
Running your C# code through the C# compiler produces two important pieces of
30
Information: code and metadata. The following sections describe these two items and then finish
up by examining the binary building block of .NET code: the assembly
Microsoft Intermediate Language (MSIL)
The code that is output by the C# compiler is written in a language called Microsoft Intermediate
Language or MSIL. MSIL is made up of a specific set of instructions that Specify how your code
should be executed. It contains instructions for operations such as variable initialization, calling
object methods, and error handling, just to name a few. C# is not the only language in which
source code changes into MSIL during the compilation process. All .NET-compatible languages,
including Visual Basic .NET and Managed C++, produce MSIL when their source code is
compiled. Because all of the .NET languages compile to the same MSIL instruction set, and
because all of the .NET languages use the same runtime, code from different languages and
different compilers can work together easily.
MSIL is not a specific instruction set for a physical CPU. It knows nothing about the
CPU in your machine, and your machine knows nothing about MSIL. How, then, does your
.NET code run at all, if your CPU can't read MSIL? The answer is that the MSIL code is turned
into CPU-specific code when the code is run for the first time. This process is called "just-in-
time" compilation, or JIT. The job of a JIT compiler is to translate your generic MSIL code into
machine code that can be executed by your CPU.You may be wondering about what seems like
an extra step in the process. Why generate MSIL when a compiler could generate CPU-specific
code directly? After all, compilers have always done this in the past. There are a couple of
reasons for this.
First, MSIL enables your compiled code to be easily moved to different hardware.
Suppose you've written some C# code and you'd like it to run on both your desktop and a
31
handheld device. It's very likely that those two devices have different types of CPUs. If you only
had a C# compiler that targeted a specific CPU, then you'd need two C# compilers: one that
targeted your desktop CPU and another that targeted your handheld CPU. You'd have to compile
your code twice, ensuring that you put the right code on the right device. With MSIL, you
compile once. Installing the .NET Framework on your desktop machine includes a JIT compiler
that translates your MSIL into CPU-specific code for your desktop.
Installing the .NET Framework on your handheld includes a JIT compiler that translates
that same MSIL into CPU-specific code for your handheld. You now have a single MSIL code
base that can run on any device that has a .NET JIT compiler. The JIT compiler on that device
takes care of making your code run on the device. Another reason for the compiler's use of MSIL
is that the instruction set can be easily read by a verification process. Part of the job of the JIT
compiler is to verify your code to ensure that it is as clean as possible. The verification process
ensures that your code is accessing memory properly and that it is using the correct variable
types when calling methods that expect a specific type. These checks ensure that your code
doesn't execute any instructions that could make the code crash.
The MSIL instruction set was designed to make this verification process relatively
straightforward. CPU-specific instruction sets are optimized for quick execution of the code, but
they produce code that can be hard to read and, therefore, hard to verify. Having a C# compiler
that directly outputs CPU-specific code can make code verification difficult or even impossible.
Allowing the .NET Framework JIT compiler to verify your code ensures that your code accesses
memory in a bug-free way and that variable types are properly used.
32
The Execution Flow In .Net
33
Common Type System
The .NET applications, regardless of their source languages all share a common type system.
What this means is that you no longer have to worry when doing development in multiple
languages about how a data type declared in one language needs to be declared in another.
Any .NET type has the same attributes regardless of the language it is used in. Furthermore,
all .NET data types are objects, derived from System. Object. Because all data types derive from
a common base class, they all share some basic functionality, for example the ability to be
converted to a string, serialized, or stored in a collection.
. NET Base Class Library (BCL)
If I could have bought a library that offered everything the .NET Base Class Library offers when
I started programming, a year’s salary would have seemed reasonable—there really is that much
to it. Almost everything in the .NET environment is contained within the BCL. Let’s look at a
“Hello World” example:
Using System;
Class Hello
{Public static void Main ()
{Console.WriteLine ("Hello World");}
The only function contained in this simple program is a call to the WriteLine method of
the Console class. What is really unique about the .NET environment is that .NET languages
don’t have to implement even the most basic functions; they are available in the BCL. Because
all .NET languages share the same common set of libraries, the code being executed by your C#
program is the same code being executed by a program written in another language. This means
34
that all languages that target the .NET environment essentially share the same capabilities,
except they have different syntax.
TECNOLOGY: The ASP.NET
ASP.NET adds many features to and enhances many of the capabilities in classic ASP.
ASP.NET isn’t merely an incremental improvement to ASP; it’s really a completely new
product, albeit a new product designed to allow the same development experience that ASP
developers have enjoyed. ASP.NET is a set of components that provide developers with a
framework with which to implement complex functionality. Two of the major improvements of
ASP.NET over traditional ASP are scalability and availability. ASP.NET is scalable in that it
provides state
Services that can be utilized to manage session variables across multiple Web servers in a server
farm. Additionally, ASP.NET possesses a high performance process model that can detect
application failures and recover from them. Along with improved availability and scalability,
ASP.NET provides the following additional benefits:
Simplified development: ASP.NET offers a very rich object model that developers can use to
reduce the amount of code they need to write.
Language independence: ASP pages must be written with scripting. In other words, ASP pages
must be written in a language that is interpreted rather than compiled. ASP.NET allows compiled
languages to be used, providing better performance and cross-language compatibility.
35
Simplified deployment: With .NET components, deployment is as easy as copying a component
assembly to its desired location.
Cross-client capability: One of the foremost problems facing developers today is writing code
that can be rendered correctly on multiple client types. For example, writing one script that will
render correctly in Internet Explorer 5.5 and Netscape Navigator 4.7, and on a PDA and a mobile
phone is very difficult, if not impossible, and time consuming. ASP.NET provides rich server-
side components that can automatically produce output specifically targeted at each type of
client.
Web services: ASP.NET provides features that allow ASP.NET developers to effortlessly
create Web services that can be consumed by any client that understands HTTP and XML, the de
facto language for inter-device communication.
Performance: ASP.NET pages are compiled whereas ASP pages are interpreted. When an
ASP.NET page is first requested, it is compiled and cached, or saved in memory, by the .NET
Common Language Runtime (CLR). This cached copy can then be re-used for each subsequent
request for the page. Performance is thereby improved because after the first request, the code
can run from a much faster compiled version.
36
PROGRAMMMING LANUAGE: C#.Net
Introducing C#
C#, the new language introduced in the .NET Framework, is derived from C++. However, C# is
a modern, objected-oriented (from the ground up) type-safe language.
Language features
The following sections take a quick look at some of the features of the C# language
Classes
All code and data in C# must be enclosed in a class. You can't define a variable outside of a
class, and you can't write any code that's not in a class. Classes can have constructors, which
execute when an object of the class is created, and a destructor, which executes when an object
of the class is destroyed. Classes support single inheritance, and all classes ultimately derive
from a base class called object. C# supports versioning techniques to help your classes evolve
over time while maintaining compatibility with code that uses earlier versions of your classes. As
an example, take a look at a class called Family. This class contains the two static fields that hold
the first and last name of a family member as well as a method that returns the full name of the
family member.
Class Class1
Public string FirstName;
Public string LastName;
Public string FullName ()
Return FirstName + LastName;
37
Note Single inheritance means that a C# class can inherit from only one base class.
C# enables you to group your classes into a collection of classes called a namespace.
Namespaces have names, and can help organize collections of classes into logical groupings.
These classes are contained within the Microsoft namespace.
Data types
C# lets you work with two types of data: value types and reference types. Value types hold actual
values. Reference types hold references to values stored elsewhere in memory. Primitive types
such as char, int and float, as well as enumerated values and structures, are value types.
Reference types hold variables that deal with objects and arrays. C# comes with predefined
reference types (object and string), as well as predefined value types (sbyte, short, int, long, byte,
ushort, uint, ulong, float, double, bool, char, and decimal). You can also define your own value
and reference types in your code. All value and reference types ultimately derive from a base
type called object.
C# allows you to convert a value of one type into a value of another type. You can work
with both implicit conversions and explicit conversions. Implicit conversions always succeed and
don't lose any information (for example, you can convert an int to a long without losing any data
because a long is larger than an int). Explicit conversions may cause you to lose data (for
example, converting a long into an int may result in a loss of data because a long can hold larger
values than an int). You must write a cast operator into your code to make an explicit conversion
happen.
You can work with both one-dimensional and multidimensional arrays in C#.
Multidimensional arrays can be rectangular, in which each of the arrays has the same
38
Dimensions, or jagged, in which each of the arrays has different dimensions. Classes and
structures can have data members called properties and fields. Fields are variables that are
associated with the enclosing class or structure. Properties are like fields, but enable you to write
code to specify what should happen when code accesses the value. If the employee's name must
be read from a database, for example, you can write code that says, "When someone asks for the
value of the Name property, read the name from the database and return the name as a string."
Functions
A function is a callable piece of code that may or may not return a value to the code that
originally called it. An example of a function would be the FullName function shown earlier, in
this chapter, in the Family class. A function is generally associated to pieces of code that return
information whereas a method generally does not return information. For our purposes however,
we generalize and refer to them both as functions.
C# and the CLR work together to provide automatic memory management. You don't
need to write code that says "allocate enough memory for an integer" or "free the memory that
this object was using." The CLR monitors your memory usage and automatically retrieves more
when you need it. It also frees memory automatically when it detects that it is no longer being
used (this is also known as Garbage Collection).C# provides a variety of operators that enable
you to write mathematical and bitwise expressions. Many (but not all) of these operators can be
redefined, enabling you to change how the operators work. Classes can contain code and data.
Each class member has something called an accessibility scope, which defines the member's
visibility to other objects.
39
Variables
Variables can be defined as constants. Constants have values that cannot change during the
execution of your code. The value of pi, for instance, is a good example of a constant, because its
value won't be changing as your code runs. Enum type declarations specify a type name for a
related group of constants. C# provides a built-in mechanism for defining and handling events. If
you write a class that performs a lengthy operation, you may want to invoke an event when the
operation is completed. Clients can subscribe to that event and catch the event in their code,
which enables them to be notified when you have completed your lengthy operation. The event
handling mechanism in C# uses delegates, which are variables that reference a function. Note an
event handler is a procedure in your code that determines the actions to be performed when an
event occurs, such as the user clicking a button. If your class holds a set of values, clients may
want to access the values as if your class were an array. You can write a piece of code called an
indexer to enable your class to be accessed as if it were an array. Suppose you write a class
called Rainbow, for example, that contains a set of the colors in the rainbow. Callers may want to
write MyRainbow [0] to retrieve the first color in the rainbow. You can write an indexer into
your Rainbow class to define what should be returned when the caller accesses your class, as if it
were an array of values.
Interfaces
C# supports interfaces, which are groups of properties, methods, and events that specify a set of
functionality. C# classes can implement interfaces, which tell users that the class supports the set
of functionality documented by the interface. You can develop implementations of interfaces
without interfering with any existing code, which minimizes compatibility problems. Once an
interface has been published, it cannot be changed, but it can evolve through inheritance. C#
40
classes can implement many interfaces, although the classes can only inherit from a single base
class.
Attributes
Attributes declare additional information about your class to the CLR. In the past, if you
Wanted to make your class self-describing, you had to take a disconnected approach in
which the documentation was stored in external files such as IDL or even HTML files.
Attributes solve this problem by enabling you, the developer, to bind information to
classes — any kind of information. For example, you can use an attribute to embed
documentation information into a class. Attributes can also be used to bind runtime
information to a class, defining how it should act when used. The possibilities are
endless, which is why Microsoft includes many predefined attributes within the .NET
Framework.
Introducing: ADO.NET
ADO.NET relies on data providers to provide access to the underlying data

source. Each data provider exposes a set of objects that you use to manage connections, retrieve
data, and update data. The core objects are the following:
• Connection
• Command
• DataReader
• DataAdapter
In addition, ADO.NET provides the DataSet object, which provides a disconnected cache of
data. The DataSet object does not require a specific type of data source and is not tied to the
underlying data source that the data was obtained from.
41
Fig. 4.2 working with databases with ADO.Net
ADO.NET OBJECTS
• Connection. This object represents a connection to a database.

• Command. This object represents an SQL statement that is run while connected to a data
source. This object can be a stored procedure or a direct SQL statement.
• DataReader. This object retrieves a read-only, forward-only stream of data from a
database. The DataReader object is designed for connected scenarios and offers better
performance than reading data into a DataSet object at the expense of functionality.
• DataAdapter. This object channels data to and from a DataSet object and the underlying
data source. The DataAdapter object also provides enhanced batch update features that
were previously associated with the ADO Recordset object.
42
• DataSet. The DataSet object represents a disconnected, cached set of data. The DataSet is
independent of the provider and is not tied to the underlying data source that might have
been used to populate it. DataSet can easily be passed from component to component
through the various layers of an application, and it can be serialized as XML.
You should be aware of the way a DataSet is internally constructed because the DataSet contains
a potentially large number of internal objects. This means that a large number of memory
allocations are required to construct a typical DataSet.
A DataSet consists of one or more DataTable objects together with DataRelation objects that
maintain table relationship information. Each DataTable contains DataRow objects and
DataColumn objects. Constraint objects are used to represent a constraint that can be enforced on
one or more DataColumn objects.
SQL SERVER 2005
Microsoft SQL Server 2005 is a full-featured relational database management system (RDBMS)
that offers a variety of administrative tools to ease the burdens of database development,
maintenance and administration. In this article, we'll cover six of the more frequently used tools:
Enterprise Manager, Query Analyzer, SQL Profiler, Service Manager, Data Transformation
Services and Books Online.
Enterprise Manager is the main administrative console for SQL Server installations. It provides
you with a graphical "birds-eye" view of all of the SQL Server installations on your network.
You can perform high-level administrative functions that affect one or more servers, schedule
common maintenance tasks or create and modify the structure of individual databases.
Query Analyzer offers a quick and dirty method for performing queries against any of your SQL
Server databases. It's a great way to quickly pull information out of a database in response to a
user request, test queries before implementing them in other applications, create/modify stored
procedures and execute administrative tasks
43
SQL Profiler provides a window into the inner workings of your database. You can monitor
many different event types and observe database performance in real time. SQL Profiler allows
you to capture and replay system "traces" that log various activities. It's a great tool for
optimizing databases with performance issues or troubleshooting particular problems.
Service Manager is used to control the MSSQLServer (the main SQL Server process), MSDTC
(Microsoft Distributed Transaction Coordinator) and SQLServerAgent processes. An icon for
this service normally resides in the system tray of machines running SQL Server. You can use
Service Manager to start, stop or pause any one of these services.
Data Transformation Services (DTS) provide an extremely flexible method for importing and
exporting data between a Microsoft SQL Server installation and a large variety of other formats.
Books Online is an often overlooked resource provided with SQL Server that contains answers
to a variety of administrative, development and installation issues. It's a great resource to consult
before turning to the Internet or technical support.
A database is stored in a very structured manner. Each database requires some way for a user to
interact with the information within. Such interaction is performed by a database management
system (DBMS). SQL Server is a member of a large category of products known as database
management systems (DBMS). The general purpose of a DBMS is to provide for the definition,
storage, and management of data in a centralized area that can be shared by many users. SQL
Server’s database management system is patterned on the relational model. Relational databases
allow us to store vast amounts of data with far sampler maintenance and smaller storage
requirements than the equivalent flat database. Relations among tables in a relational database
are established using keys. A primary key is a field that uniquely identifies a record so it can be
referenced from a related table. A foreign key is a field that holds identification values to relate
records stored on other tables.
Querying the database
44
With each query of the database, we form a virtual table that contains the results of our query.
Database queries are made with a specific language named SQL (structured query language).
SQL Server 2000 has many performance improvements and features which allows us to
build and manage large databases, query them fast, insert data into them at high rates, partition
them for fast loading and backup and store very large objects or whole files. Central, Shared,
Accessible, Backed up, Version etc. SQL, as a relational data language supports certain basic
functions to control, define and manipulate data. SQL uses the term row to refer to a database
record and the term column to refer to database field
CRYSTAL REPORT
Crystal report is a tool, through which one can easily deliver rich interactive content from
virtually any data source, publish it to the web in a variety of formats and integrate it with
applications. Crystal report is a part of a suite of integrated technologies that ensure data can be
accessed, analyzed, reported on and delivered to any stakeholder anytime, anywhere, by any
device.
• POWERFUL CONTENT CREATION: - Crystal reports provides reports access to all
users, regardless of platform used.
• WIDE VARIETY OF REPORT TYPES: - Crystal Reports can create virtually any report
one can imagine including sub reports, conditional, summary, cross-tab, form, drill-
down, OLAP, top N, multiple details.
• FAST AND EASY REPORT CREATION: - Powerful wizards, experts and built-in
functionality help novice and experts user quickly assemble highly interactive reports.
Customize your reports with logos, pictures, shapes and colures. An extensive formula
language gives developers full control report formatting, complex business logic and data
selection.
• MICROSOFT OFFICE INTEGRATION: - Crystal reports add-ins for Microsoft Excel
and Microsoft Access make reporting from office data a snap.
• INTERACTIVE: - Add charts, drill-down alerting parameters prompts, hyperlink,
geographic mapping, field highlighting, running totals, top N, bottom N, sorting to turn
reports into compelling interactive content.
45
• COMPLEX REPORTS MADE EASY:-Address complex reporting

requirements with expert driven features including grouping, sorting, sub reports and
cross tabs, or use the powerful formula editor.
• FLEXIBLE INFORMATION DISTRIBUTION: - Publish reports to a variety of formats
including XML, PDF, RTF, Word, Excel, text, email and version 7-. Rpt format.
• HIGH PERFORMANCE REPORT PROCESSING: -Crystal reports are up to ten times
faster than version 7! Comprehensive support for SQL data base servers enables faster
report processing and better use of network resources.
• REAL TIME OR SCHEDULED DELIVERY: -Deliver information real time with report
steaming technology or automate content generation or delivery with the flexible new
scheduling feature.
• RICH, INTERACTIVE CONTENT: -See interactive, presentation quality reports in real
time, using zero clients DHTML, Active X.
• UNPRECEDENTED FLEXIBILITY AND CONTROL: The Report Designer Component
(RDC) provides Visual Basic, C++ and other COM Based developers a powerful report
server with a rich object model with complete control over report layout, formatting and
behavior inside data base applications.
• RAPID APPLICATION DEVELOPMENT: With the RDC, you can open, design and
modify reports inside the Visual Basic IDE using familiar Visual Basic Code. Microsoft
Visual InterDev 6.0 developers can write ASP applications with integrated Crystal
Reports using the same object model used in Win 32 applications. And developers using
Microsoft Visual InterDev 6.0 can use the report integration controls to write web
applications and generate Crystal Reports hosted either on a web report Server or an ASP
Server.
• ROYALITY FREE RUNTIME: Access hundreds of royalty-free runtime properties,
methods and events for precedent control over the reporting engine.
• REPORT CREATION AT RUNTIME: Let your user create reports – on the fly- from with
8in your application, using report creation at runtime APIs or the drag-and-report
interface of the embedded Crystal Report Designer Control. Licensing fees apply.
• EASY DATA ACCESS: Connect to over 30 different types of OLAP, SQL and PC
databases using supported native, ODBC and OLE DB connectivity. Or report off in-
memory application data.
46
CUSTOMIZABLE VIEWERS: Customize the zero clients DHTML, ActiveX or Java viewer to
deliver rich, interactive content from applications
HOW WEB APPLICATIONS WORK ?
Web applications use client/server architecture. The Web application resides on a server and
responds to requests from multiple clients over the Internet, as shown in Figure 1-1.
Fig. 4.3 ASP.NET Web application architecture
On the client side, the Web application is hosted by a browser. The application’s user interface
takes the form of Hypertext Markup Language (HTML) pages that are interpreted and displayed
by the client’s browser.
On the server side, the Web application runs under Microsoft Internet Information Services (IIS).
IIS manages the application, passes requests from clients to the application, and returns the
application’s responses to the client. These requests and responses are passed across the Internet
using Hypertext Transport Protocol (HTTP). A protocol is a set of rules that describe how two or
47
more items communicate over a medium, such as the Internet. Figure 1-2 shows how the client
and server interact over the Internet.
Fig.4.4 Client/server interaction in a Web application
The Web application composes responses to requests from resources found on the server. These
resources include the executable code running on the server (what we traditionally think of as the
“application” in Microsoft Windows programming), Web forms, HTML pages, image files, and
other media that make up the content of the application.
Web applications are much like traditional Web sites, except that the content presented to the
user is actually composed dynamically by executable, rather than being served from a static page
stored on the server. Figure 1-3 shows how a Web application composes the HTML returned to a
user.
Fig.4.5 an ASP.NET Web application response from server resources
48
The executable portion of the Web application enables you to do many things that you can’t do
with a static Web site, such as:
• Collect information from the user and store that information on the server
• Perform tasks for the user such as placing an order for a product, performing complex
calculations, or retrieving information from a database
• Identify a specific user and present an interface that is customized for that user
• Present content that is highly volatile, such as inventory, pending order, and shipment
information
This is only a partial list. Basically, you can do anything with a Web application that you can
imagine doing with any client/server application. What makes a Web application special is that
the client/server interaction takes place over the Internet.
What ASP.NET Provides?
ASP.NET is the platform that you use to create Web applications and Web services that run
under IIS. ASP.NET is not the only way to create a Web application. Other technologies, notably
the CGI, also enable you to create Web applications. What makes ASP.NET special is how
tightly it is integrated with the Microsoft server, programming, data access, and security tools.
ASP.NET provides a high level of consistency across Web application development. In a way,
this consistency is similar to the level of consistency that Microsoft Office brought to desktop
applications. ASP.NET is part of the .NET Framework and is made up of several components.
 Visual Studio .NET Web development tools.

These include visual tools for designing Web pages and application templates, project
management, and deployment tools for Web applications.
 The System. Web namespaces.

These are part of the .NET Framework and include the programming classes that deal
with Web-specific items such as HTTP requests and responses, browsers, and e-mail.
49
 Server and HTML controls.

These are the user-interface components that you use to gather information from and
provide responses to users.
In addition to the preceding components, ASP.NET also uses the following, more general
programming components and Windows tools. These items aren’t part of ASP.NET.
However, they are key to ASP.NET programming.
 Microsoft Internet Information Services (IIS).

As mentioned in the previous section, IIS hosts Web applications on the Windows server.
 The Microsoft Visual Basic .NET, Microsoft Visual C#, and Microsoft Visual J#
programming languages.
These three languages have integrated support in Visual Studio .NET for creating Web
applications.
 The .NET Framework.

This is the complete set of Windows programming classes, including the ASP.NET
classes as well as classes for other programming tasks such as file access, data type
conversion, array and string manipulation, and so on.
 Microsoft ADO.NET database classes and tools.

These components provide access to Microsoft SQL Server and ODBC databases. Data
access is often a key component of Web applications.
 Microsoft Application Center Test (ACT).

This Visual Studio .NET component provides an automated way to stress-test Web applications.
ASP.NET is the most complete platform for developing Web applications that run under IIS.
However, it is important to remember that ASP.NET is not platform-independent. Because it is
hosted under IIS, ASP.NET must run on Windows servers. To create Web applications that run
on non-Windows/IIS servers, such as Linux/Apache, you must use other tools—generally CGI.
50
Advantages of ASP.NET
ASP.NET has many advantages over other platforms when it comes to creating Web
applications. Probably the most significant advantage is its integration with the Windows server
and programming tools. Web applications created with ASP.NET are easier to create, debug, and
deploy because those tasks can all be performed within a single development environment—
Visual Studio .NET.
ASP.NET delivers the following other advantages to Web application developers:
• Executable portions of a Web application compiled so they execute more quickly than
interpreted scripts
• On-the-fly updates of deployed Web applications without restarting the server
• Access to the .NET Framework, which simplifies many aspects of Windows

programming
• Use of the widely known Visual Basic programming language, which has been enhanced
to fully support object-oriented programming
• Introduction of the new Visual C# programming language, which provides a type-safe,

object-oriented version of the C programming language
• Automatic state management for controls on a Web page (called server controls) so that
they behave much more like Windows controls
• The ability to create new, customized server controls from existing controls
• Built-in security through the Windows server or through other

authentication/authorization methods
• Integration with ADO.NET to provide database access and database design tools from
within Visual Studio .NET
51
• Full support for Extensible Markup Language (XML), cascading style sheets (CSS), and
other new and established Web standards
• Built-in features for caching frequently requested Web pages on the server, localizing
content for specific languages and cultures, and detecting browser capabilities.
The Waterfall Model
The Waterfall Model is a Linear sequential Process model which suggests a systematic,
sequential approach to software development, that begins at the System level and progresses
through analysis, design, coding, testing and Maintenance. Modeled after the conventional
engineering cycle, the waterfall Model encompasses the following activities:
1) System/information engineering and modeling:

Because software is always part of a larger system, work begins by establishing the
requirements for all system elements and then allocating some subset of these requirements to
software. This system view is essential when software must interface with other elements such as
hardware, people and databases. Information engineering encompasses the Requirements
gathering at strategic business level and at the business area level.
2) Software Requirement Specification:

The requirements gathering process is intensified and focused specifically on software. To
understand the nature of the programs to be built, the software engineer must understand the
information domain for the software as well as the required function; behavior, performance and
interfacing requirements for both the system and software are documented and reviewed with the
customer.
3) Analysis and Design:

Software design is actually a multi step process that focuses on four distinct attributes of a
program: data structure, software architecture, interface representations and procedural
52
(algorithmic) details. The design process translates requirements into a representation of the
software that can be assessed for quality before code generation begins.
4) Code Generation:
The design must be translated into a machine-readable form. The code generation step performs
the task. If design is performed in a detailed manner, code generation can be accomplished
mechanically.
5) Testing:
Once code has been generated program testing begins. The testing process focuses on the
logical internals of the software, assuring that all statements have been tested and of the
functional externals- that is, conducting tests to uncover errors and to ensure that defined input
will produce actual results that agrees with required results
6) Maintenance:
Must be adapted to accommodate changes in its external environment, because the customer
requires functional or performance enhancements. Software Maintenance applies each of the
preceding phases to an already existing program rather than a new one. Despites these phases
various Umbrella activities – such as software quality assurance, software configuration
management and measurement - overlay the process model.
53
Graphical Representation of Waterfall Model
54
55
INTRODUCTION
OF
PROJECT
HUMAN RESOURCE MANAGEMENT SYSTEM
56
To develop a software application that supports the application specific to the HR automation in
an intranet specific to a company there by allowing the integration of all the employees
pertaining to that organization.
To allow the HR of an organization to update the employee details when ever there is a change in
the employee profile pertaining to that organization. Human Resource Management features
make creating and maintaining complete employee files simple and efficient. Its powerful record
keeping, monitoring and reporting capabilities will save you time, while reducing your exposure
to employment related lawsuits by ensuring you have proper documentation. In addition, HRM
reduces the potential for employee grievances by assuring fairness across your workforce. With
HRM, you will identify trends early and make adjustments as needed.
I am working on “Task Management System” which is the one module of HRMS but it itself
comprising of several modules that I am working on, as given below:
 Employee Profile
 Project Details
 Client Details
 Salary Details
 Admin Related Task
 User Related Task
TASK MANAGEMENT SYSTEM
57
The “THE TASK MANAGEMENT (HUMAN RESOURCE MANAGEMENT PROJECT)” is

real time software that brings greater organization and effectiveness to the full range of Human
Resource functions and responsibilities.
This software automates the task management inside the organization, there by saving the
valuable time and efforts of employees. This software provides for easy, accurate and timely
retrieval of Employee and activity-oriented information through menu driven, user-friendly
operations.
OBJECTIVE
The Objective Of Our Project Is To:
1 This software would completely automate the HR management.
2 Would save precious time and effort of officials.
3 Minimize the possibility of human error.
4 All the records related to different employees of the department would be saved for the
future reference.
5 Generation of computerized reports by just using the few clicks of a mouse.
58
PROBLEM DEFINITION
Our Problem Is to Design an Effective and Easy-To-Use “HRMS” Software that meet the
information need of all levels of Management and facilitates Decision Support, Planning,
Monitoring, Control of Daily Activities.
• What is the problem?
The problem is to convert a manual system into an automated one.
• Why is it important to solve the problem?
This is done to save the time and help the users to keep a record for themselves to avoid
any sort of confusion and conflicts.
• What are the possible solutions to the problem?
This problem can be easily solved on any of the following programming language
• C#
• VB
• What exactly are the data input to the system and what exactly are the data output required
of the system?
Data input to the system may be:

• Id of administrator or user
• Password of administrator
• USER_ID that is unique.
• USER password
Data output to the system may be:

• Admin page
• User Main Page
• Employee details
59
• Project details
• Employee’s Salary details
• Client details
• Popup window showing project deadline to the user.
• Display of an ERROR MESSAGE when the user enters an invalid data.
• If there are external software or hardware with which the developed software has to
interface, then what exactly would the data interchange formats with the external system
be?
After the analyst has understood the exact customer problems, he proceeds to identify and
resolve those problems. The most important problems that the analyst has to identify and
eliminate are the problems of anomalies, inconsistencies, and incompleteness.
• Anomaly
An anomaly is the ambiguity in the problem. When a problem is anomalous,

several interpretation of the requirement is possible.
• Inconsistency
The problem becomes inconsistent, if any one of the requirements contradicts

another. It means some part of the problem contradicts with some other part.
• Incompleteness
Incomplete information regarding the problem is one where some of the

requirements have been over looked. Often, incompleteness is caused by the inability of
the customer to visualize and anticipate the entire feature that would be required in a
system to be developed
60
EXISTING STATE OF
SYSTEM
61
EXISTING SYSTEM
The HR Administration falls short of controlling the employee’s activities in analyzing his/her
strengths and weakness. The decision for appraisal of assigning next project to the employee or
to show him/her the deadline of project – where lies with proper projection. He is not provided
with the detailed project information done or to be assigned based on Application / Verticals.
DRAWBACKS IN EXISTING SYSTEM:
 Need of extra manual effort.

 It used to take much time to find any employee
 Not very much accurate.
 Does not provide any information about client.
 Deadline of project not shown to employees.
 Danger of losing the files in some cases.
PURPOSE OF THE STYDY:
The HR center is a powerful application designed to allow companies to streamline their human
resource tasks and manager their employees more efficiently
Employee and Client Information
Project Information
Employee’s Salary Information
Approval of new Employee by Admin
HR Documentation Management (i.e. insurance forms, W-2’s etc.)
The HR Center includes a comprehensive employee information database, work information,

beneficiary information, and more for each employee. It comes standard with employee self-
service access allowing employees to update their personal and professional information,project
62
information. It also has role –based access level control that is functionally based on whether a
user is an employee, or an HR admistrators.
OBJECTIVE OF THE STUDY:

To develop a software application that supports Specific to the HR Automation for Task
Management in an intranet to a company there by allowing the interaction of all the employees
pertaining to that organization. To keep track of all the other departments related to that
organization like marketing, research etc.,
To allow the HR department of an organization to update the employee details when ever there is
a change in the employee profile pertaining to that organization. This software would completely
automate the HR management,there by saving precious time and effort of officials.Minimize the
possibility of human error.All the records related to different employees of the department would
be saved for the future reference. Generation of computerized reports by just using the few clicks
of a mouse.
SCOPE OF THE STUDY:

Allow a for the creation of an application specification to the human resource that maintain the
intranet automation of the HR software i.e., which contains the data related to the employee.
PROJECT OVERVIEW AND LIMITTIONS:

This project can be used to identify a employee in the organization. The projects maintain the
details of the entire employee and manage the task related to each employee.This project also
maintain the client information. Each employee is given with unique UserId and Password.
In this I can use the c#.net language. Back end is SQL Server 2005. Duration of this project is 3
months .i was discussed the total modules of Task Management System. Limits are there. In this
project I was taken only HR department from organization.
63
Tools used for Software

development
SYSTEM REQUIREMENTS
64
HARDWARE:
 Pentium Processor : 2.1 GHz and above

 512 MB or higher RAM
 3x72 GB or Higher SCSI Hard disk
 CD-ROM Drive
 104 Keyboards
 PS/2 Mouse
 USB Ports – 2 or higher
 LAN Card (10/100 Mbps)
 Modem 56 Kbps
 Color Monitor – 14” or 15”
 Printers
 UPS 2 KVA or higher
 16 ports Unmanaged Switch (For Networking)
SOFTWARE:
 SQL Server 2005

 Visual Studio 2005
 Anti Virus Software
 Front-end--Project will be developed using ASP.NET (Platform) with C#.Net as
language.
 Back-end: -- MSSQL-Server 2005
 Technology - Ajax
65
Proposed
System/Solution
66
PROPOSED SYSTEM
Decision in assigning proper skillful hands for the project is an important issue in HR Module. The
HR Administrator should report with the personal holding the necessary skills required for the
project assignment. The decision in making analysis about the employee’s skills is a prime
important before booting in. The proposed system of HR Module is the right software to be
incorporated into the Automation of HR Software for helping the organization needs with respect
to skilful Human Resource.
The proposed system provides detail general information about the employee along with
Educational, Certification, Skill and Project details. It enhances the HR Management in adding,
viewing and updating employees’ details and generates various reports regarding employee’s skill
and experience. This TASK MANAGEMENT also provide the full information about the clients
Suggestions and Grievances posted by the employees are upheld for taking care of the necessary
steps in forwarding company’s obligation.
PURPOSE OF THE STYDY:

The HR center is a powerful application designed to allow companies to streamline their human
resource tasks and manager their employees more efficiently
Employee and Client Information
Project Information
Employee’s Salary Information
Approval of new Employee by Admin
HR Documentation Management (i.e. insurance forms, W-2’s etc.)
The HR Center includes a comprehensive employee information database, work information,

beneficiary information, and more for each employee. It comes standard with employee self-
service access allowing employees to update their personal and professional information, project
information. It also has role –based access level control that is functionally based on whether a
user is an employee, or an HR admistrators.
67
OBJECTIVE OF THE STUDY:

To develop a software application that supports Specific to the HR Automation for Task
Management in an intranet to a company there by allowing the interaction of all the employees
pertaining to that organization. To keep track of all the other departments related to that
organization like marketing, research etc.,
To allow the HR department of an organization to update the employee details when ever there is
a change in the employee profile pertaining to that organization. This software would completely
automate the HR management, there by saving precious time and effort of officials. Minimize
the possibility of human error. All the records related to different employees of the department
would be saved for the future reference. Generation of computerized reports by just using the
few clicks of a mouse.
SCOPE OF THE STUDY:

Allow for the creation of an application specification to the human resource that maintain the
intranet automation of the HR software i.e., which contains the data related to the employee.
ADVANTAGES OF PROPOSED SYSTEM:
 Very fast and accurate.

 No need of any extra manual effort.
 No fever of data loss.
 Just need a little knowledge to operate the system.
 Doesn’t require any extra hardware device.
 Employees on their main form get the message of project deadline coming.
 Provide information about clients.
 At last very easy to find the employees.
68
FEASIBILITY STUDY
Once the problem is clearly understood, the next step is to conduct feasibility study, which is
high-level capsule version of the entered systems and design process. The objective is to
determine whether or not the proposed system is feasible.
It mainly determines whether it would be financially and technically feasible to develop the
product. The feasibility study involves the analysis of the problem and collection of all relevant
information relating to the product such as the different data items which would be INPUT to
the system,the PROCESSING required to be carried out on these data, the OUTPUT data
required to be required to be produced by the system, as well as various CONSTRAINTS on the
behavior of the system. The collected data are arrived at the following:-
 An abstract problem definition.
 Formulation of the different solution strategies.
 Analysis of alternative solution strategies to compare their benefits and

shortcomings. This analysis usually requires making approximate estimates
of the RESOURCES required COST of development, and DEVELOPMENT
TIME for each of the options. Thus, during the feasibility study, most of the
high-level architectural design decisions are made.
The three tests of feasibility have been carried out

 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
TECHNICAL FEASIBILITY
69
In Technical Feasibility study, one has to test Whether the proposed system can be developed
using existing technology or not. It is planned to implement the proposed system using java
technology. It is evident that the necessary hardware and software are available for development
and implementation of the proposed system. Hence, the solution is technically feasible. In the
proposed system, the application has made in this way so that it is technically feasible for the
sales promotion. There are some certain types of reports being used in the system to make the
application more users friendly i.e. the Data Report is used. The system has made in such away
that it is being used for a single user as well as multi-user environment. The operating systems
are Windows NT 4.0/Windows 2000/Windows XP/2003. Thus we see that the system is more
technically feasible regarding to operating system. We are using Microsoft SQL Server 2005 as
backend for maintaining the database. SQL Server is a relational database management system
of an object that is formed by the database and an instance of the SQL Server. SQL Server 20005
is Windows based RDBMS. This is one of the powerful RDBMS due to its menu driven facility.
This provides a better service to the user in the sense of taking the backup of data and then
restores it. We can easily mirror the database in the SQL Server 20005.
ECONOMICAL FEASIBILITY
As part of this, the costs and benefits associated With the proposed system compared and the
project is economically feasible only if tangible or intangible benefits outweigh costs. The
system development costs will be significant. Today, software is the most expensive element of
virtually all computer-based systems. A large cost estimation error can make the difference
between profit and loss. Estimation of resources, cost, and schedule for a software engineering
effort requires experience, access to good historical information, and the courage to commit to
quantitative predictions. Estimation carries inherent risk and this risk leads to uncertainty.
Project complexity has a strong effect of the uncertainty inherent in planning. Complexity,
however, is a relative measure that is affected by familiarity with past effort. Project size is
another important factor that can affect the accuracy and efficiency of estimates. As size
increases, the interdependency among various elements of the software grows rapidly. Software
cost and effort estimation will never be an exact science. Too many variables-human, technical,
environmental, political-can affect the ultimate cost of software and effort applied to develop it.
However, software project estimation can be transformed from a black art to a series of
70
systematic steps that provide estimates with acceptable risk. The system is not too costly
according to the features of the application. The cost of the project is balanced So the proposed
system is economically feasible.
OPERATION FEASIBILITY
This application is very easy to operate as it is made user friendly. Main consideration is user’s
easy access to all the functionality of the application
It is a standard that ensures interoperability without stifling competition and innovation among
users, to the benefit of the public both in terms of cost and service quality. The proposed system
is acceptable to users. So the proposed system is operationally feasible.
71
MODULE DESCRIPTION:
The list of modules incorporated with “TASK MANAGEMENT (Human Resource

Management System)” is
 Employee Info Module

 Administration Module
 Project Management Module
 Salary Info Module
 Client Info Module
 Reports
.
1 Employee Info Module

This module deals with the management of the employee information such as the personal and
professional details such as name, qualification, skill, experience, login id, password, etc.,
Importance of modules in any software development side is we can easily understand what the
system we are developing and what its main uses are. At the time of project we may create many
modules and finally we combine them to form a system person, so that it can be easily added to
the database with any duplication of the data.
2 ADMINISTRATION MODULE:
This module deals with the management of the employee information such as the hiring of the
eligible candidate, payments criteria, his personal information maintenance,approval of new
employee,send auto generated password to the employee through mail etc.
3 PROJECT MANAGEMENT MODULE:

This module deals with the management of the projects related with the employee like-projects
that were past dealt, current projects in his account, client, project start date and completion date,
project deadline etc.
72
4 CLIENT MANAGEMENT MODULE:

This module deals with the management of the client information such as client name,unique client
Id,office and residential address,project given by client etc,.
5 SALARY INFO MODULE:

This module deals with the management of the salary information of each employee in the
organization. It contains all necessary details like basic salary,HRA,TDS etc,.Each employee has
auto generated unique Account Id.
6 REPORTS MODULE:
This module is specified for the purpose of the report generation for the HR on desired requests.
73
SRS
REPORT
1. Introduction
74
1.1. Background
1.2. Overall description
1.3. Environment Characteristics
1.3.1.. Hardware
1.3.2. People
1.4. Interfaces
1.4.1. Interfaces with devices
1.4.2. Interface with operating system
1.4.3. Interface with database
1.4.4. Interface with the user
1.5. Constraints
2. Functional Requirements
2.1. Functional partitioning
2.2. Function description
3. Non-Functional Requirement
4. Behavioral Description
4.1 Events and action
5. Validation Criteria
5.1 Performance bounds
5.2 Classes of tests
75
INTRODUCTION
1.1. Background
The “TASK MANAGEMENT SYSTEM” is real time software that brings greater organization
and effectiveness to the full range of Human Resource functions and responsibilities. This
software provides for easy, accurate and timely retrieval of Employee and activity-oriented
information through menu driven, user-friendly operations.
Also we have all the data maintained in our database through which we can take
any information at any time. By doing this the reliability and efficiency increases.
1.2. Overall Description
The project provides easy, effective and efficient approach to employees and admin. It provides
Graphical User Interface which is here are simply form-based and menu-based interface. It also
conceals the complexity of software from users, i.e, Data Abstraction technique is applied.
A comprehensive “Human Resource Management Software” that brings greater organization and
effectiveness to the full range of Human Resource functions and responsibilities.
This software provides for easy, accurate and timely retrieval of Employee and activity-oriented
information through menu driven, user-friendly operations. The software has been designed to
meet the information need of all levels of Management and facilitates Decision Support,
Planning, Monitoring, Control of Daily Activities.
1.3. Environmental Characteristics
1.3.1. Hardware
Minimum Requirements
 Pentium processor(2.1GHZ)
 256 to 768 MB of RAM
 2.5 GB for Visual Studio .NET and 1 GB for Microsoft SQLServer2005.
 52-X CD ROM drive
76
1.3.2. People
Several people contributed for the up coming of this project. The main contribution in the
upcoming of this project was of the respected project heads, the team members and end-users
also which play the important part of critics in the project. The concerned faculty of the project is
Mr. Durgesh Mishra. By their valuable and timely comments and suggestions this project had
come into existence. The group members have contributed a lot in the project completion. The
group members are Amrita Pandey and Udit Dixit. I have performed implementation of software
under the supervision of project head and other senior team members. I was also the part of
testing team for 2 weeks during which we prepared a real-time environment.
1.4. Interfaces
1.4.1. Interface with devices
In this project there is no external device being used in the system. The pen drive
and the CD Rom of the system will be used for the data storage and retrieval
system.
1.4.2. Interface with database
Microsoft Sql Server 2005 as the back end in our project and these are the
databases in which information is kept..
1.4.3. Interface with the user
Asp.Net and C#.Net is used as the interface between the user and the database
.The forms which appear on the screen allow user
~ To view employee information, project details, client details and salary
details.
~ To edit the various details provided.
1.5. Constraints
For proper working of this software the computer should have at least 256 MB of RAM. For the
proper installation of the software 40 GB of HDD is mandatory. The time constraint is of 2
weeks. The security levels are so high there is minimum chance of unauthorized intrusion.
77
2. FUNCTIONAL REQUIREMENTS
It states the functionality required from the system. A processing narrative is provided for each
function. Design constraints are stated and justified and one or more diagram are included to
graphically represent the overall structure of the software and interplay among software
functions and other system elements. The functional requirement includes the following two
main points:
 Functional partitioning
 Functional description
2.1. Functional partitioning:
1) Enter the ID and PASSWORD of the user.
2) Verification of the Id and Password
3) Shown Admin Page.
4) Admin approve the employee who request for the Id and Password when first time
entering their details in the database.
5) The new employee get approve mail by the admin and this mail contain their ID and
Password.
6) Admin view details about any employee, project, client, salary and edit it if required.
7) The User page show project deadline if it is coming.
8) The user view his/her details.
9) Exit.
NON-FUNCTIONAL REQUIREMENTS
78
These are related to the quality issue. There are two views according to the-
USER-
(1)USABILITY-Effort required to learn and operate the software properly.
(2)RELIABILITY- The property that defines how the software will meet its requirements.
(3)FLEXIBILITY-The effort required to modify an operational program to enhance its
functionality.
(4)DESIRED PERFORMANCE-It checks for the efficiency of the software.
DEVELOPER-
(1)MAINTAINABILITY-The effort required to locate and fix errors in operating program.
(2) TESTABILITY-The effort required to test to ensure that the system or a module perform its
intended function.
(3) PORTABILITY- The effort required to transfer the software from one hardware
configuration to other.
4. BEHAVIOURAL DESCRIPTIONS
This usually deals with the works of the administrator. The administrator can perform
various operations like updating, addition, deletion details about employees in the project.The
admin also approve the new employee details and autogenerate the Id and Password for that
emoployee.
5. VALIDATION CRITERION
5.1. Performance Bounds

1. The software is confined to its s/w and h/w specification.
5.2. Classes of Tests

The aim of the testing is to identify all defects existing in a software product. However, foremost
practical systems, even after satisfactorily carrying out the testing phases, it is not possible to
guarantee that the software is error free. Testing provides us a practical way of reducing defects
in a system and increasing the users’ confidence in a developed system. The essential two main
approaches to systematically designing test cases:
79
• Black box testing
• White box testing
Black-Box Testing
In black box testing test cases are designed from an examination of the input\output. Values and
no knowledge of design or code is required. The software is checked for working
according to the needs specified in the SRS document.
White Box Testing

There are several White Box Testing strategies. Each testing strategy based on some heuristic.
One white box strategy is said to be stronger then another strategy, if all types of errors detected
by the first testing strategy are also detected by the second testing strategy, and the second
strategy additionally detects some more types of errors.
When two testing strategy detect errors that are different at least with respect to some types
of errors, they are then called complementary. In the practical design of test cases, if a stronger
testing is performed, then the weaker testing need not be carried out. But using all the
complementary testing strategies should enrich the test suit.
80
SDLC/Data Flow
Diagram/Object Flow
Diagram
81
82
DESIGN
Software design is a multi step process, which focuses on distinct attributes of program: data
structure, software architecture, interface representation, and procedural detail. The design
process translates requirements into a representation of the software that can be assessed for
quality before coding begins. According to requirement, the design is documented. The design
must be translated into a machine-readable form. The code generation step perform this task .If
design is performed in a detailed manner; code generation can be accomplished.
The design phase is the first step while moving from the problem domain to solution
domain. This phase begins when the requirement specification document for the newly
developing system is available. The aim of this phase is to produce a model or a representation of
the system, which is useful to have an overall look of the system without even developing the
entire system. This model of the system is a plan for developing the system. There are three
characteristics for the evaluation of a good design.
• The design should implement all the requirements of the user, which are specified in the SRS
and it must accommodate all the requirements that may not be specified by the Recruiter in
the analysis phase.
• The design should be readable and understandable for the people who involve in developing
and testing the system.
• The design should provide a complete picture of the system, addressing the data functional
domains from the implementation perspective.
Characteristics for good software designs are listed below:

Correctness:
A good design should correctly implement all the functionalities of the system.
Understandability:
83
A good design should be easily understandable.

Efficiency:
It should be efficient
Maintainability:
It should be easily amenable to change.
The goal of the design phase is to transform the requirements specified in the SRS Document
into a structure that is suitable for implementation in some programming language. In technical
terms, during the design phase the “software architecture” is derived from the SRS document.
PROJECT PLANNING
 Project Life Cycle
The Project Life Cycle consists of four phases:
 Project Initiation
The Initiation Phase is the first phase in the project. In this phase a business problem (or
opportunity) is identified and a business case which provides various solution options is defined.
A feasibility study is then conducted to investigate the likelihood of each solution option
84
addressing the business problem and a final recommended solution is put forward. Once the
recommended solution is approved, a project is initiated to deliver the approved solution. A
‘Terms of Reference’ is completed, which outlines the objectives, scope and structure of the new
project, and a Project Manager is appointed. The Project Manager begins recruiting a project
team and establishes a Project Office environment. Approval is then sought to move into the
detailed planning phase.
 Project Planning
Once the scope of the project has been defined in the terms of reference, the project enters the
detailed planning phase. This involves the creation of a:
• Project plan (outlining the activities, tasks, dependencies and timeframes)

• Resource Plan (listing the labor, equipment and materials required)
• Financial Plan (identifying the labor, equipment and materials costs)
• Quality Plan (providing quality targets, assurance and control measures)
• Risk Plan (highlighting potential risks and actions taken to mitigate them)
• Acceptance Plan (listing the criteria to be met to gain customer acceptance)
• Communication Plan (listing the information needed to inform stakeholders)
• Procurement Plan (identifying products to be sourced from external suppliers).
• At this point the project has been planned in detail and is ready to be executed.
 Project Execution
This phase involves the execution of each activity and task listed in the Project plan. While the
activities and tasks are being executed, a series of management processes are undertaken to
monitor and control the deliverables being output by the project. This includes the identification
of changes, risks and issues, the review of deliverable being produced against the acceptance
criteria. Once all of the deliverables have been produced and the customer has accepted the final
solution, the project is ready for closure.
 Project Closure
85
Project Closure involves releasing the final deliverables to the customer, handling over project
documentation, terminating supplier contracts, releasing project resources and communicating
the closure of the project to all stakeholders. The Last remaining step is to undertake a Post
implementation Review to quantify the overall success of the project and list any lessons learnt
for future projects.
DATA FLOW DIAGRAM

A graphical tool used to describe and analyze the moment of data through a system manual or
automated including the process, stores of data, and delays in the system. Data Flow Diagrams
are the central tool and the basis from which other components are developed. The
transformation of data from input to output, through processes, may be described logically and
independently of the physical components associated with the system. The DFD is also know as
a data flow graph or a bubble chart.
CONTEXT DIAGRAM:
The top-level diagram is often called a “context diagram”. It contains a single process, but it
plays a very important role in studying the current system. The context diagram defines the
system that will be studied in the sense that it determines the boundaries. Anything that is not
inside the process identified in the context diagram will not be part of the system study. It
represents the entire software element as a single bubble with input and output data indicated by
incoming and outgoing arrows respectively.
TYPES OF DATA FLOW DIAGRAMS:

Data Flow Diagrams are of two types as follows:
(a) Physical DFD
(b) Logical DFD
86
1. PHYSICAL DFD:
Structured analysis states that the current system should be first understand correctly. The
physical DFD is the model of the current system and is used to ensure that the current system has
been clearly understood. Physical DFDs shows actual devices, departments, and people etc.,
involved in the current system
2. LOGICAL DFD:
Logical DFDs are the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity this is taken
as the basis for drawing the system’s structure charts.
BASIC NOTATION:
The Basic Notation used to create a DFD’s are as follows:
DATAFLOW:
Data move in a specific direction from an origin to a destination.
PROCESS
People, procedures, or devices that use or produce (Transform) Data. The physical component
is not identified.
SOURCE:
87
External sources or destination of data, which may be People, programs,

organizations or other entities.
DATA STORE:
Here data are stored or referenced by a process in
the System
DESIGN:
Design is the first step in moving from problem domain to the solution domain. Design is
essentially the bridge between requirements specification and the final solution.
The goal of design process is to produce a model or representation of a system, which can be
used later to build that system. The produced model is called the “Design of the System”. It is a
plan for a solution for the system.
CONTEXT FLOW DIAGRAM
Description:
Context Flow Diagram gives us the complete details about the inputs and outputs for a given
system. In the above system the main task is to identify a criminal face. So, the operator and
eyewitness are the inputs to our system and criminal face is desired output.
LOGIN PROCESS
88
User Id
LOGIN PROCESS SCREEN
Passpassword
Invalid user Id or Password
ERROR IN
INPUT
Level-1
Description:
The inputs to the process are User Id and Password given by the developer to allow the software
available for the Admin environment. After giving the inputs the details, checks whether the
entered ones are valid are not. It displays screen if match occurs otherwise error message if they
are not matched.
Data Flow Diagram For LOGIN (Level 1)
89
Login-Criteria
ROLE
Admin Id and Task-Mgmt [loginTable]

USER Password
Login
Proces
s
User-Id
Password
Create
Sessio
n Main Form
ID
90
MAIN SCREEN PROCESS
MAIN Approve new

ADMIN SCREEN Emp details and
autogenerate
User-Id ,Password
View,Edit Emp
Profile
View,Edit
Project Details
View Salary
Report
View,Edit Client
Profile
Level -2
Description:
This process mainly explains the different screens that are available for the admin. Here the
selection of the screen depends on the admin and he can select whatever screen he wants. The
different screens that are available are Approve new Employee details, View and Edit Emp
Profile, View and Edit Project Details, view salary report, view and edit client profile.
91
MAIN USER SCREEN PROCESS
MAIN DEADLINE OF
USER SCREEN PROJECT
View his/her
Profile
View
his/herProject
Details
View Salary
Report
Logout
92
Approve Employee Details
Administrator Approve Employee Report

s
Level-3
Description:
This process clearly illustrates adding the details of the Employee such as name, age, gender,
location, address, state and city along with his EMP Id. These details are being added to the
database, if any error is generated then it will be prompted to the admin otherwise we get
message data is successfully added.
93
Add Project Report
DATABASE
ADD
Admin Project DATA IS
Details ADDED
Level-4
Description:
This process clearly illustrates adding the details of the new project such as project Id, Name,
Start date, End date, Deadline, Current Status, Client name etc. These details are being added to
the database, if any error is generated then it will be prompted to the admin otherwise we get
message data is successfully added.
94
Add Client Details
DATABASE
Add Client DATA

Admin Details UPDATED
Level-5
Description:
This process clearly illustrates adding the details of the Client Details such as name, regulatory
region, country, company control unit, Office address, location and along with his Client Id.
These details are being added to the database, if any error is generated then it will be prompted to
the admin otherwise we get message data is successfully added.
Level-6
95
DATABASE
Add DATA
Admin Compensatio UPDATED
n Report
Level-7
Description:
This process clearly illustrates adding the details of the Employees Compensation Report such as
name, salary range, and annual income, tax of income, loans, present annual income, facilities,
and insurance and along with his EMP Id. These details are being added to the database, if any
error is generated then it will be prompted to the admin otherwise we get message data is
successfully added.
Data Flow Diagram For USER-CREATION (Level 0)
USER User
Creation
96
Data Flow Diagram For USER-CREATION (Level 1)
user
Contac
Personal Profess t
details ional details
details
submit
Admin
approves
details
Auto generate
User-Id and
Password
97
E-R DIAGRAM (Entity relationship diagram):-
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
Entity
An entity is an object or concept about which you want to store information.
Attribute
Attributes are the properties or characteristics of an entity.
Keyattribute
A key attribute is the unique, distinguishing characteristic of the entity. For example, an
employee's social security number might be the employee's key attribute.
98
Multivaluedattribute
A multivalued attribute can have more than one value. For example, an employee entity can have
multiple skill values.
Derivedattribute
A derived attribute is based on another attribute. For example, an employee's monthly salary is
based on the employee's annual salary.
Relationships
Relationships illustrate how two entities share information in the database structure.
99
Cardinality
Cardinality specifies how many instances of an entity relate to one instance of another
entity.Ordinarily is also closely linked to cardinality. While cardinality specifies the occurrences
of a relationship, ordinarily describes the relationship as either mandatory or optional. In other
words, cardinality specifies the maximum number of relationships and ordinarily specifies the
absolute minimum number of relationships.
Recursiverelationship
In some cases, entities can be self-linked. For example, employees can supervise other
employees.
100
PROJECT FLOW:
Project flow represents the flow of the system at different steps, there are two types of user
single Admin and multiple department users which perform different functions. A user id and
password for login will be created by the admin.
User can change its password.
USER
Department
Admin User
Master Approve Change Main User Report-

database Admin/ Password page Generatio
entries by user n
form accounts
Add Delete Search Update View his/her

Details details Details Details profile, project and
salary details
Project Deadline Cannot

Message is Edit and
shown on main Delete any
page details
Fig: Project Flow of “TASK MANAGEMENT SYSTEM”
101
FLOW CHART
A typical definition of "Flow Chart" usually reads something like:
A flow chart is a graphical or symbolic representation of a process. Each step in the process is
represented by a different symbol and contains a short description of the process step. The flow
chart symbols are linked together with arrows showing the process flow direction.
The first cool thing about flow charts is that they let you see the process flow at a glance, so my
first alternate definition of "Flow Chart" is a Snap Shot of your Business Processes. The is
commonly called an As-Is Flowchart. You can tell a lot about the complexity (and often over-
complexity) of many business processes just by looking at an as-is flow chart of them - without
even reading the text in the symbols. You can easily see the flow of information and materials,
branches in the process, opportunities for infinite loops, the number of process steps, inter-
departmental operations, and more.
The second cool thing about flow charts is that they let you see the process flow at different
levels, so my second alternate definition of "Flow Chart" is a Zoom Lens for your Business
Processes. Flow charts are often categorized in 3 levels: high-level, mid-level and low-level
(detailed). A high-level flow chart could be a process defined at the company-wide or large
system level. Mid-level flow chart could be a process defined at the department level, and a low-
level flow chart could be a process defined at working level.
For example, I used to run a test department. Product validation was a process step included in a
high-level flow chart in the New Product Introduction procedure. The validation test process
itself was documented in a mid-level flow chart showing the general department activities
required to support the validation testing process. And, some ISO work flow instructions had
low-level, detailed flow charts documenting how to conduct individual test types.
Some flow chart tools (including Microsoft Excel) allow you to add hyperlinks to flow chart
symbols. The hyperlinks let you click on a flow chart symbol, drilling down from a high-level
process step to a detailed set of process flow steps. This truly gives you the zoom lens capability.
102
The third cool thing about flow charts is that they let you perform risk-free experiments, so with
that in mind my third and final alternate definition of "Flow Chart" is a Process Test Bed. All
process improvements require change, and most changes involve risk, require work, cost money,
or instill some level of emotional uncertainty and fear. You can mitigate each of these by
creating process flow charts of any proposed business operation changes. Each flow chart can be
a "what-if" that helps the involved players more easily see the risks involved.
A Note on Flowchart Symbols
Different flow chart symbols have different meanings. The most common flow chart symbols
are:
Terminator: An oval flow chart shape indicating the start or end of the process.
Process: A rectangular flow chart shape indicating a normal process flow step.
Decision: A diamond flow chart shape indication a branch in the process flow.
Connector: A small, labeled, circular flow chart shape used to indicate a jump in the process
flow.
Data: A parallelogram that indicates data input or output (I/O) for a process.
Document: used to indicate a document or report .
A really simplistic flow chart showing the flow chart symbols described above can be seen
below:
103
Start
Login
Enter user-Id
and password
Is
vali
d?
Admin Page
View, Edit, and Delete Approves new

any details about Employee
Employee
Exit
Stop
104
DATABASE DESIGN
DATABASE
A database is a set of data, organized for easy access. The database is an actual
data; it is the database that you will be accessing when you need to retrieve data.
DATA DICTIONARY
The data dictionary is a set of tables Oracle uses to maintain information about the
database. The data dictionary contains information about tables, indexes, clusters and so on.
DBA (DATABASE ADMINISTRATOR)

The DBA is the person responsible for the operation, configuration and performance of
the database. The DBA is charged with keeping the database operating smoothly, ensuring that
backups are done on regular basis (and that backups work), and installing new software. Other
responsibilities might include planning for future expansion and disk space needs, creating
databases and table spaces, adding users and maintaining security, and monitoring the database
and retuning it as necessary. Large installations might have teams of DBA’s to keep the system
running smoothly; alternatively, the task might be segmented among the DBA’s.
A database management system (DBMS) consists of a collection of interrelated data and a set of
programs to access those data. The collection of data, usually referred to as the database,
contains information about one particular enterprise. The primary goal of a DBMS is to provide
an environment that is both convenient and efficient to use in retrieving and sorting database
information.
Database systems are designed to manage large bodies of information. The management
of data involves both the definition of storage of information and the provision of mechanisms
105
for the manipulation of information. We used relational database management system (RDBMS)
for developing this system. The goal of a relational- database management system (RDBMS)
design is to generate a set of relation schemas that allows us to store information without
unnecessary redundancy. It also allows us to retrieve information easily.
Redundancy
Redundancy means repetition of information i.e., same information may be written or stored in
many places (files). This redundancy may lead to data inconsistency i.e., the various copies of
the same data. When we access this inconsistent data, system may give wrong information. To
reduce the data redundancy we use the concept of normalization.
Normalization
Normalization of data is a process in which unsatisfactory relation schemas are decomposed by
breaking up their attribute into smaller relation schemas that possess desirable properties.
Normal forms provide a formal framework for analyzing relation schemas based on their keys
and the functional dependencies among attributes to database designers. The concurrent process
model is often used as the paradigm for the development of Recruiter server system that is
composed of a set of functional component. When applied to Recruiter /server, the concurrent
process model defines activity in two dimensions--a system dimension and a component
dimension. System level issues are addressed using three activities: design, assembly, and use.
The component dimension is addressed with two activities: design and realization. Concurrency
is achieved in two ways:
• System and activities occur simultaneously and can be modeled using the state-oriented
approach described previously.
• A typical Recruiter server application is implemented with many components, each
Of which can be designed and realized concurrently.
106
Introduction to data dictionary
Data dictionaries are an integral component of structured analysis, since data flow diagrams by
themselves do not fully describe the subject of the investigation/. The data flow diagrams
provide the additional details about the project/system.
Data Dictionary (Definition)
A data dictionary is a catalog- a repository- the elements in a system. These elements center on
the data and the way they are structured to meet user requiremen6ts and organization needs. A
data dictionary consists of a list of all the elements composing the data flowing through a system.
The major elements are data flow, data stores, and processes. The data dictionary stores details
and descriptions of these elements.
Describing Data Elements

Each entry in the data dictionary consists of a set of details describing the data used or produced
in the system. Each item is identified by a data name, description, alias, and length and has
specific values that are permissible for it in the system being studied.
DATABASE TABLES
As a backend the SQL server 2005 has been used to create tables and procedures to hold and
process the data.
STRUCTURE OF TABLES WITH SNAP-SHOTS
107
[loginTable]
TABLE 1: Contain the LOGIN-Information like ID, login-name, password.
108
[EmployeeDetails]
TABLE 2: Contain the Employee Information like-personal details, contact details and
professional details
109
[mDesignation]
TABLE 3: Contain the Designation-Information like ID, name, remarks
110
[mDepartment]
TABLE 4: Contain the Department-Information like ID, name, Head of Department, remarks
111
[mProject]
TABLE 5: Contain the Project-Information like ID, name, start date, end date, deadline, client
name, status, remarks
112
[ClientInfo]
TABLE 6: Contain the Client-Information like ID, name, contact details etc.
113
[SalaryInfo]
TABLE 7: Contain the Salary-Information like Employee Acc ID, basic salary, HRA, Net salary
114
[mCasteCategory]
TABLE 8: Contain the information for CasteCategory-master like ID, Title.
115
[mCity]
TABLE 9: Contain the information for City-master like ID, Title and also contain the entries for
foreign key.
116
[mCountry]
TABLE 10: Contain the information for country-master like ID, Title.
117
[mState]
TABLE 11: Contain the information for state-master like ID, Title.
118
[mNationality]
TABLE 12: Contain the information for Nationality-master like ID, Title.
119
[mQualification]
TABLE 13: Contain the information for Qualification-master like ID, Title.
120
[Database Diagrams –showing relationship among different tables]

mDepartment
mDept_Id
mDept_Name
mDept_Head
mDept_Remarks
EmployeeDetails
Emp_Id
Emp_Fname
Emp_MiddleName
Emp_Lname
Emp_DOB
Emp_Gender
Emp_CurrAddress
Emp_ResAddress
mDesignation
Emp_PhoneNo
mDesg_Id
Emp_MobileNo
mDesg_Name
Emp_Email
mDesg_Remarks
mCasteCategory_Id
mReligion_Id
mBloodGroup_Id
Emp_ImagePath
mCity_Id
mState_Id
mCountry_Id mProject
mNationality_Id mProj_Id
mProj_Id mProj_Name
mDesg_Id Proj_StartDate
mDept_Id Proj_EndDate
mQualification_Id Proj_TimeDuration
Emp_WorkExp mDept_Id
Emp_PreOrg Client_Name
Emp_PreDesg Proj_Status
Emp_DOJ Proj_Deadline
Emp_Remarks Proj_Remarks
121
mCountry
mCountry_Id
mCountry_Title
EmployeeDetails
Emp_Id
Emp_Fname
Emp_MiddleName
Emp_Lname
mState
Emp_DOB mState_Id
mCity Emp_Gender mCountry_Id
mCity_Id Emp_CurrAddress mState_Title
mState_Id Emp_ResAddress mState_Remarks
mCountry_Id Emp_PhoneNo
mCity_Title Emp_MobileNo
mCiity_Remarks Emp_Email
mCasteCategory_Id
mReligion_Id
mBloodGroup_Id
mCasteCategory
mCasteCategory_Id
Emp_ImagePath
mCasteCategory_Title
mCity_Id
mState_Id
mNationality
mCountry_Id
mNationality_Id
mNationality_Id
mNationality_Title
mProj_Id
mDesg_Id
mDept_Id
mQualification_Id
Emp_WorkExp
Emp_PreOrg
Emp_PreDesg
Emp_DOJ
Emp_Remarks
122
[Stored procedure for INSERT QUERY]
123
[stored procedure for VALIDATION CHECK]
124
CODING-STYLE
125
GOOD CODING STYLE
• There are several component of good style

• Naming Convention(variables, controls, and subroutine names)
• Indented and properly spaced code
• Documented code
• Cohesive Modules
• Minimum Coupling
• Minimize data scope where possible
Good Coding Style Aids
Modifiability
• Code must be easily understood and modified.

• Almost each code is modified during its lifetime.
• A good style will help people to easily modify other’s code
Transportability
• To increase productivity and usability, a program should be easy to transport to different

environments and computers.
• A good style of programming is to isolate all machine dependent areas of code and label
them as such
• Input/Output is a typical area where/operating system dependencies surface
126
Readability
• Use of good indentation, blank lines, and comments aid in reading section of code.
• To improve readability, use identifiers that mean something or are relevant to the value
they represent.
• Indent segments of code in loops or in conditional statements.
• Make good use procedures and function to modularize program
Usability
• The user should be presented with a consistent, easily understandable, and a friendly
interface.
• Use error recovery techniques that help the user. Also make certain that your error
message are consistent and helpful
• User interface management system are becoming increasingly important in computing

especially with the advent of graphical workstation with windowing systems.
Efficiency
• A well thought out program is nearly always an efficient program.

• Efficiency is not just speed but takes several aspects into consideration.
• Optimize your code without reducing readability to zero. This efficiency with restriction
Do’s of Good Coding Style
• Use a few standard, agreed upon control constructs.

• Use gotos in a disciplined way.
127
• Introduce user defined data types to model entities in the problem domain.
• Hide data structure behind access functions.
• Provide standard documentation prologues for each subprogram and/or compilation unit.
• Carefully examine routine having very few and with too many executable statements.
• Use indentation, parentheses, blank spaces, blank lines and borders around blocks of
comments to enhance readability.
Don’ts of Good Coding Style
• Don’t be too clever.

• Avoid null then statements.
• Avoid then if statements.
• Don’t nest too deeply.
• Avoid obscure side effects.
• Don’t sub optimize.
• Don’t use an identifier for multiple purposes.
128
129
TESTING
SOFTWARE TESTING
Software testing is the process used to help identify the correctness, completeness,
security and quality of developed computer software. With that in mind, testing can never
completely establish the correctness of arbitrary computer software. In computability theory, a
field of computer science, an elegant mathematical proof concludes that it is impossible to solve
the halting problem, the question of whether an arbitrary computer program will enter an infinite
loop, or halt and produce output. In other words, testing is criticism or comparison, that is
comparing the actual value with an expected one.
Software testing may be viewed as a sub-field of software quality assurance but typically exists
independently (and there may be no SQA areas in some companies). In SQA, software process
specialists and auditors take a broader view on software and its development. They examine and
130
change the software engineering process itself to reduce the amount of faults that end up in the
code or deliver faster
Following testing techniques has been used at different steps while Twenty Point Monitoring
Program module development and enhancement.
1. WHITE BOX AND BLACK BOX TESTING
In the terminology of testing professionals (software and some hardware) the phrases
"white box", or "glass box", and "black box" testing refer to whether the test case developer has
access to the source code of the software under test, and whether the testing is done through
(simulated) user interfaces or through the application programming interfaces either exposed by
(published) or internal to the target.In white box testing the test developer has access to the
source code and can write code that links into the libraries which are linked into the target
software. This is typical of unit tests, which only test parts of a software system. They ensure
that components used in the construction are functional and robust to some degree.
In black box testing the test engineer only accesses the software through the same interfaces that
the customer or user would, or possibly through remotely controllable, automation interfaces that
connect another computer or another process into the target of the test. For example a test
harness might push virtual keystrokes and mouse or other pointer operations into a program
through any inter-process communications mechanism, with the assurance that these events are
routed through the same code paths as real keystrokes and mouse clicks
2. GUI TESTING
GUI Presents interesting challenges for software engineers. Because of reusable component
provided as part of GUI development environment, the creation of the user interface has become
less time consuming and more precise.
Because modern GUIs have the same look and feel, a series of standard test can be derived. Now
since this system is developed under Windows XP by using VB.Net so we have also tested for
GUIs.
131
The main aspect of GUI testing has been the Bilingual feature. In which the data has to be
entered in the Hindi font and reports should be generated in proper Hindi format. At some point
the English language has also been used to give instructions to the users so that the
communication gap between the software and the user would be minimized.
In forms for the district level/state level users where the data entry is being done, the proper eye
catching instructions are given with images so that navigation and workflow can be maintained
in order to get better results by the software for the longer period of time when multiple clients
are putting their requests to the server in tandem.
3. ALPHA, BETA AND GAMMA TESTING
In software development, testing is usually required before release to the general public.
This phase of development is known as the alpha phase. Testing during this phase is known as
alpha testing.
In the first phase of alpha testing, developers test the software using white box techniques.
Additional inspection is then performed using black box or grey box techniques. This is usually
done by a dedicated testing team. This is often known as the second stage of alpha testing.
Once the alpha phase is complete, development enters the beta phase. Versions of the software,
known as beta-versions, are released to a limited audience outside of the company. The software
is released to groups of people so that further testing can ensure the product has few faults or
bugs. Sometimes, beta-versions are made available to the open public to increase the feedback
field to a maximal number of future users.
Testing during the beta phase, informally called beta testing, is generally constrained to black
box techniques although a core of test engineers are likely to continue with white box testing in
parallel to the beta tests.
Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy"
(defect-ridden) products. It is not a term of art among testers, but rather an example of referential
humor.
132
4. SYSTEM TESTING
System testing is a phase of software testing in which developers see if there are any
communications flaws--either not passing information or passing incorrect information--between
modules.Testing that attempts to discover defects that are properties of the entire system rather
than of its individual components
5. REGRESSION TESTING
A regression test re-runs previous tests against the changed software to ensure that the
changes made in the current software do not affect the functionality of the existing software.
Regression testing can be performed either by hand or by software that automates the process.
Regression testing can be performed at unit, module, system or project level
For the regress testing, simultaneously from more than one client terminals data entry has been
done and reporting features is also tested successfully.
133
SCREENSHOTS
134
[LOGIN - PAGE]
135
[ADMIN PAGE]
136
[APPROVAL PAGE-Admin approves new employee details and send user-id and password
into the employee email-id]
137
[NEW EMPLOYEE ENTRY FORM--3 steps]
138
[VALIDATION APPLIED]
139
140
[ENTER NEW PROJECT DETAILS]
141
[ENTER NEW CLIENT DETAILS]
[VIEW PROJECT DETAILS]
142
[CLIENT DETAILS]
[SALARY INFORMATION]
143
[EDITING PROJECT DETAILS]
144
[EMPLOYEE DETAILS]
145
[USER MAIN PAGE]
[USER CHANGING PASSWORD]
146
[USER VIEW ONLY HIS/HER DETAILS]
147
148
SOFTWARE
IMPLEMENTATION
IMPLEMENTATION PHASE
149
The implementation is the final and important phase. It involves User training, system
testing and successful running of the developed system. The users test the developed system
when changes are made according to the needs. The testing phase involves the testing of the
developed system using various kinds of data. An elaborate testing of data is prepared and
system is tested using the tests data.
It is mainly concerned with the user training site selection and preparation and file conversion.
Once the system has been designed it is ready for implementation. Implementation is concerned
with those tasks leading immediately to a fully operational system. It involves programmers,
users & operation management, it includes the final testing of complete system to the user
satisfaction and supervision of initial operations of the system. Implementation of the system
includes providing security to the system so that some person may not misuse it.
Implementation is the stage where theoretical design turned into a working system.
Implementation is planed carefully to propose system to avoid unanticipated problems. Many
preparations involved before and during the implementation of proposed system. The system
needed to be plugged in to the organization’s network then it could be accessed from anywhere,
after a user logins into the portal. The tasks that had to be done to implement the system were to
create the database tables in the organization database domain. Then the administrator was
granted his role so that the system could be accessed.
The next phase in the implementation was to educate the system. A demonstration of all the
functions that can be carried out by the system was given to examination department person, who
will make extensive use of the system.
150
SOFTWARE
MAINTENANCE
SOFTWARE MAINTENANCE
151
The mention of word “maintenance” brings up the image of a screwdriver-welding mechanics

with soiled hands hold onto the bagful of spare part. It is the objective of this Project to clear up
this misconception, provide some intuitive understanding of the software maintenance projects,
and to familiarize the readers with the latest technique in software maintenance. Software
maintenance denotes any changes made to a software product after it has been delivered to the
customer. Maintenance is inevitable for almost any kind of product. However most of the
product needs maintenance due to the wear and tear caused due to its regular and rough use. On
the other hand, software product do not need maintenance on this count, but need maintenance to
correct error, enhance features, port to new platform, etc.
CHARACTERSTIC OF SOFTWARE MAINTENANCE
Software maintenance is becoming an importance activity of a large number of organizations.

This is no surprise, given the rate of hardware obsolescence, the immortality of a software
product, and the demand of the user community to see the existing software product run on
newer platform, run in newer environments, and/or with enhanced features. When the hardware
platform changes and the software product perform some low level functions, maintenance is
necessary.
TYPES OF SOFTWARE MAINTENANCE
The requirements of software maintenance arise on account of three main reasons .
Corrective :
Corrective maintenance of software maintenance becomes necessary to rectify the bugs
observe while the system is in use.
Adaptive:
A software product might need maintenance when the customer need the product to run
on new platform, on new operating system, or when they need the product to be interface with
the new hardware or software.
152
Perfective:
Software product needs maintenance to support the new features that user wants it to
support, to change different functionalities of the system according to customer demands, or to
enhance the performance of the system.
153
Result and Significant

Improvements
154
LIMITATIONS
Like any other standard application software (or any type of application in real world),
this developed software too has limitations. Although compared, this software “Task
Management System (A Human Resource management System)” right now has numerous
limitations and but in future with enhancement it can be substituted for a real “Human Resource
management System”. Here is listing of known confines under this application:
• As this is a web-based application, it is not providing excellent user interface and GUI
features. However, attempts have been maintained to provide a sort of good user interface.
• We are not using the security algorithm to encrypt or decrypt the user name and password
therefore there are chances that the confidential information provided by the user may get
tampered.
• As this a live project still the administrator part has to made more affective to perform
functional tasks.
155
FUTURE PROSPECTS
The project is open to further expansion. Succession is a natural phenomenon for any software
and there are areas open for further improvement. These systems have been designed in such a
way that the modifications can always be incorporated without affecting the modules.
Efforts have been made to cover all user requirements to the extents possible and to make it user
friendly. Input screens have designed in such a way that user have practically no possible in
entering the information.
CONCLUSION
156
Web based application is the magic of today’s world. The object of “Task management System
(A Human Resource management System)” project is to harness the power of Internet for our
practical and potential one. This software automates the task management inside the
organization, there by saving the valuable time and efforts of employees. This software provides
for easy, accurate and timely retrieval of Employee and activity-oriented information through
menu driven, user-friendly operations.
To develop a software application that supports the application specific to the HR automation
in an intranet specific to a company there by allowing the integration of all the employees
pertaining to that organization.
I hope this comprehensive “TASK MANAGEMENT SYSTEM” brings greater organization
and effectiveness to the full range of Human Resource functions and responsibilities.
This software provides for easy, accurate and timely retrieval of Employee and activity-oriented
information through menu driven, user-friendly operations.
The software has been designed to meet the information need of all levels of Management and
facilitates Decision Support, Planning, Monitoring, Control of Daily Activities.
Finally, I can appreciate the power of ASP.NET technology and programming language like
“C#.NET” in maintaining the project.
157
BIBLIOGRAPHY
BOOKS REFERRED
The following books were used extensively for the project development and implementation.
1. ASP.NET 2.0 Unleashed
158
Stephen walther
2. “ASP.NET Database Programming” Hungry Minds, Inc.

Publishing Company Limited.
By Jason Butler and Tony Caud
3. C# by Wrox
4. SQL Server 2005 Bible

Wiley Publishing, Inc.
5. SQL Server 2005 Express for Developers, Apress

By Robin Dewson
WEBSITES REFERRED
The following links were searched and exploited extensively for the project development and
implementation.
1 www.syngress.com/solutions
2 www.hungryminds.com
3 www.codeproject.com
4 www.aspfree.com
5 www.theserverside.net
6 www.murach.com
7 www.webmasterworld.com
8 www.msdn.microsoft.com
159
160

Task Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Task Management System

Uploaded by

Copyright:

Available Formats

PROJECT REPORT TASK MANAGEMENT

The “THE TASK MANAGEMENT (HUMAN RESOURCE MANAGEMENT PROJECT)” is

The Objective Of Our Project Is To:

1. This software would completely automate the HR management.

2. Would save precious time and effort of officials.

3. Minimize the possibility of human error.

5. Generation of computerized reports by just using the few clicks of a mouse.

PROBLEM DEFINITION AND SPECIFICATION

1. It Provides Easy And Efficient Interface To Interact With.

2. Would save precious time and effort of officials.

3. Minimize the possibility of human error.

5. Generation of computerized reports by just using the few clicks of a mouse.

6. It Manages Ur Data Or Account Details With Proper Care.

• What is the problem?

The problem is to convert a manual system into an automated one.

• Why is it important to solve the problem?

• What are the possible solutions to the problem?

Data input to the system may be:

• USER_ID that is unique.

Data output to the system may be:

• User Main Page

• Employee’s Salary details

• PopUp window showing project deadline to the user.

• Display of an ERROR MESSAGE when the user enters an invalid data.

An anomaly is the ambiguity in the problem. When a problem is anomalous,

The problem becomes inconsistent, if any one of the requirements contradicts

Incomplete information regarding the problem is one where some of the

1. DRAWBACKS IN EXISTING SYSTEM:

 Need of extra manual effort.

2. NEED FOR THE NEW SYSTEM

3. BENEFITS OF THE PROPOSED SYSTEM

4. ADVANTAGES OF PROPOSED SYSTEM:

END USERS TO THE SYSTEM

The system is permitted to allow two types of users:

1. ADMIN LEVEL USER:

• View the project details issued to each employee.

• View the details of each client existing in the database.

• Create new client and project in the database.

2. AUTHORIZED LEVEL USER:

• .Perform transaction level data entry as per the system requirements.

• View his/her profile.

• View the project details assigned to his/her.

• View his/her salary details

TECHNICAL ENVIRONMENT FOR THE PROPOSED SYSTEM

 Pentium Processor : 2.1 GHz and above

 USB Ports – 2 or higher

 SQL Server 2005

Built Upon Standards

• XHTML Compliance Creating XHTML-compliant pages are easy with ASP.NET.

Improved Performance and Scalability

PROJECT DEVELOPMENT AND TEAM STRUCTURE:

The following diagram depicts team structure for development.

Project Manager : Mr. Vikram Singh Kandari

Four P’s Formula:

Management Spectrum of the Project:

Explanation of the four p’s

It was on this basis that:

Realistic breakdown of the project tasks could be made.

Co-ordination and Communication Techniques Used:

Comprehensive Communication was conducted

1) With the employees in the Administration department.

SOFTWARE DEVELOPMENT PROCESS

The Development Process model used is the Waterfall Development Model.