SOFTWARE PROJECT MANAGEMENT TOOL Project Report

A
PROJECT REPORT
ON

SOFTWARE PROJECT MANAGEMENT TOOL
Submitted in partial fulfillment of the requirement for the award of

BACHELOR OF TECHNOLOGY
IN
INFORMATION TECHNOLOGY
2010-2011
Submitted
By

A.SAI CHARAN

08M11A1205
Under the Guidance of,
Mr. J.VENKATESH ,M.Tech

DEPARTMENT OF INFORMATION TECHNOLOGY

BANDARI SRINIVAS INSTITUTE OF TECHNOLOGY
(Approved by AICTE, Recognized by Govt. of A.P. and affiliated to J.N.T.U., Hyd.)
GOLLAPALLY(V), CHEVELLA(M), R.R.DIST

i

BANDARI SRINIVAS INSTITUTE OF TECHNOLOGY
(Approved by AICTE, Recognized by Govt. of A.P. and affiliated to J.N.T.U., Hyd.)
GOLLAPALLY (V), CHEVELLA (M), R.R.DIST

CERTIFICATE
This is to certify that the dissertation entitled “SOFTWARE PROJECT MANAGEMENT
TOOL”. being submitted by Mr. A.Sai Charan bearing hall ticket No: 08M11A1205 in
partial fulfillment of the requirement for the Award of the Degree of Bachelor of Technology
in INFORMATION TECHNOLOGY, Jawaharlal Nehru Technological University,
Hyderabad, is a record of the bonafide work carried out by him under our guidance and
supervision during the period 2010-2011.
The results presented in this thesis have been verified and are found to be satisfactory. The
result embodied in this project has not been submitted to any other university or institute for
the award of any degree or diploma.

Internal Guide

Head of the Department

Mr.J.Venkatesh

Mr.M.Narendhar

Assistant Professor

Assistant Professor

Department of IT

Department of IT

EXTERNAL EXAMINAR
ii

DECLARATION

I A. Sai Charan bearing Roll No: 08M11A1205, a bonafide student of Bandari Srinivas
Institute Technology, would like to declare that the project titled “SOFTWARE
PROJECT MANAGEMENT TOOL”. A partial fulfillment of BACHELOR OF
TECHNOLOGY Degree course of Jawaharlal Nehru Technological University is my
original work in the year 2011 under the guidance of Mr. J.Venkatesh, Associate Professor
of the Department of Information Technology & Engineering.

DATE:
PLACE:

NAME:
A.SAI CHARAN

iii

ROLL.NO:
08M11A1205

ACKNOWLEDGEMENT
This work has been during project period, this present project work method of education is
really a good opportunity to put theoretical knowledge into a planned exercise with an aim to
solve a real life business problem and also develop confidence to face various situations.
I Thanks to Dr.A.Naidu Principal of Bandari Srinivas Institute of
Technology for providing congenial atmosphere and encouragement.
I express my sincere thanks to Head of the Department Mr.M.Narendhar Associate
Professor for giving me moral support and his kind attention and valuable guidance to me
throughout this course.
I would like to express my deep and foremost gratitude to my internal guide Mr.J.Venkatesh
Associate Professor. He has always been a source of inspiration and motivation for me.

iv

ABSTRACT
The project entitled “Software Project Management Tool” deals with the various levels of
project development and will account for time used in analysis, design, Programming, testing
and verification etc.
It is well known fact that software companies undertake huge projects more than one
at a time. Hence there is a profound need for the organizations to manage all the projects
efficiently and ensure that projects cycle goes on smoothly and they are completed on time.
During the lifetime of a project, the organization has to commemorate all the activities
of the project. This tool makes it easier for the organization to monitor the project. It
maintains records and tracks various parameters that influence software project development
process and helps the management to take decisions at various stages of the project
development.
The product will assist the organization in maintaining record of every project it
undertakes. All the information relevant to the projects like size, time, effort and departments
involved, etc is maintained by this tool.

v

LIST OF CONTENTS
S.No

Title

1.

INTRODUCTION

1

1.1

DEFINITION

1

1.2

DESCRIPTION

1

1.3

OBJECTIVES

2

1.4

OVERVIEW

2

1.5

PROBLEMS IN EXISTING SYSTEM

3

1.6

SOLUTION OF THESE PROBLEMS

5

2.

Page.No

SYSTEM ANALYSIS

6

2.1

REQUIREMENT ANALYSIS

6

2.2

SOFTWARE REQUIREMENT SPECIFICATIONS

6

2.3

PROPOSED SYSTEM

7

2.4

ROLES

8

2.5

OPERATIONAL FEASIBILITY

9

3.

HARDWARE AND SOFTWARE SPECIFICATIONS

10

4.

LITERATURE SURVEY

11

4.1

11

4.2

ASP.NET

18

4.3

C#.NET

24

4.4
5.

INTRODUCTION TO .NET FRAME WORK

SQL SERVER

28

SYSTEM DESIGN

32

5.1

INTRODUCTION

32

5.2

DATA FLOW DIAGRAMS

33

5.3

E-R DIAGRAM

42

5.4

UML DIAGRAMS

43

vi

6.

SYSTEM ENVIRONMENT

47

7.

IMPLEMENTATION

58

7.1

SOURCE CODE

58

7.1.1

Home page

58

7.1.2

HR Login

60

8. SYSTEM TESTING

62

8.1

TESTING STRATEGY

62

8.2

SYSTEM TESTING

65

8.3

DISCUSSION AND RESULTS

66

9. CONCLUSION

78

9.1

78

SUGGESTION FOR FURTHER DEVELOPMENT

10. REFERENCES

79

vii

LIST OF FIGURES
Fig. No

Name of the Figure

Page No’s

4.1.1

Architecture of CLI Diagram

13

4.1.2

Versions of .net Diagram

17

5.2.1

SPMT DFD Diagram

35

5.2.2

Client DFD Diagram

36

5.2.3

BDO DFD Diagram

37

5.2.4

PM LEVEL1 Client Diagram

38

5.2.5

PM LEVEL 2Client Diagram

39

5.2.6

HR DFD Diagram

40

5.2.7

Developer DFD Diagram

41

5.3.1

E-R Diagram

42

5.4.1

Class Diagram

43

5.4.2

Usecase Diagram

44

5.4.3

Client Sequence Diagram

45

viii

LIST OF ABBREVIATIONS
S.NO

SYMBOL

DESCRIPTION

1

SPMT

Software Project Management Tool

2

BDO

Business Development Officer

3

HR

Human Resource

4

PM

Project Manager

5

DFD

Data Flow Diagram

6

ER

Entity Relationship

7

HTML

Hyper Text Markup Language

8

XML

Extensible Markup Language

9

GUI

Graphical User Interface

10

JIT

Just In Time

11

IIS

Internet Information Services

12

SQL

Structured Query Language

13

DBMS

Database Management System

14

OLTP

Online Transaction Processing

15

DSS

Decision Support System

16

ADO

ActiveX Data Objects

17

ASP

Active Server Pages

18

CLI

Common Language Infrastructure

ix

1. INTRODUCTION
1.1

DEFINITION:
Software Project Management Tool

deal with the various levels of project

development and will account for time used in phase viz analysis, design, coding, testing and
implementation etc.

1.2

DESCRIPTION:
Software Project Management Tool gives the management clear picture of usage of

time by projects. By analyzing the results provided by the software. They might resify the
defects in utilizing time and take remedial actions.
Software Project Management Tool gives the individual reports of the project, which
contains time used for various tasks. In this tool client gives requirements to the BDO and
makes an agreement with him. The new project information is entered by the BDO, based on
the project information the project manager will take resources from the HR and assign
activities to developers who are working under him. Employees fill the time sheet and
complete the task assigned to them .these completed tasks are tested and finally the project is
submitted to the client. This project deals with five modules – Client, Business development
officer (BDO), Developer, Human Resource Manager (HR), Project Manager (PM).
Client deals with checking the status of the project by the client. Only the authenticated client
login to the web page and checks in which phase the project is.
BDO deals with collecting the requirements from the client and add the client details and
project details into the database and also views and updates the respective details
Developer deals with filling the timesheets. Updating and viewing the timesheets and also
checking the project status.
HR deals with providing resources to the project manager by checking the employee details
like skill and designation. HR can also view the status of the project.
PM deals with planning the project i.e. dividing the project into different tasks and assigning
those tasks to the developers. PM also checks the timesheets of developers. Fills his own
timesheet, updates and views the timesheet. PM can also check the status of the project.

Software Project Mangaement Tool (SPMT) will do the following tasks:
•

Record different phases of project.

•

Define phase wise tasks.

•

Keep a track of project schedules.

•

Record project definition.

•

Phase wise project closures.

•

Assign resources to a project.

•

Access control for resources.

•

Take daily efforts from each resource.

1.3 OBJECTIVES
The objectives of this application is functionality and architecture of the ‘Software
Project Management Tool ’, and to estimate the effort of the project.
The general objectives are:
•

Maintain project details.

•

Maintain client details.

•

Maintain employee details.

•

Maintain timesheet for various levels project.

1.4

OVERVIEW

Software development has inherit problem with determining the time it takes to complete it.
Software programming is quite different than say, nail production. When one produces nails
it is known how many nails machine produces per hour. If you need to produce x number of
nails figuring the time it takes is easy. If you need 12h of time, you know that one of your

workers can handle the overtime and omitting for the sake of argument certain safety
concerns, your worker will be as productive at hour 1 as hour 12. Unfortunately, software
development is much harder than nail manufacturing. There are many more unknowns - risks
that have to be accounted for. In order to attain rapid software development, four different
aspects have to be considered. These are:
•

Risk management

•

Avoiding common mistakes

•

Practicing development fundamentals

•

Following practices leading to best possible schedule

The rest of this guide will discuss each of above four elements of project management. All of
above are equally important, if any of above four is omitted then the whole structure might
fail. The reason for "might" is the risk based aspect - as mentioned before things may go right
or wrong. It's all about leaning in favor of successful resolution instead of using methods that
increase the chance of failure. One of the methods that increase risk, but are widely used due
to their simplicity, is programmer total commitment. This disorganized way of project
management has its successes, however these successes are a result of inefficient, hard work not of smart work that can be achieved by following above four principles.

1.5

PROBLEMS IN EXISTING SYSTEM

People
•

Management decreased developer motivation.

•

Under-trained developers, developers with low qualifications.

•

Keeping problem developers (non-team players) on the team against wishes of all
other team members.

•

Company encouraged developer "heroics", emphasis on "can-do" attitudes.

•

Adding people to projects that are over-running their schedule.

•

Working environment that prevents developers from focusing on their work.
Customer interactions that are too frequent or lead to open conflicts.

•

Unrealistic expectations, usually in the area of project scheduling, wishful thinking.

•

Absence of executive project sponsorship, absence of agreement between all parties
involved in the project.

•

Absence of customer involvement in the project causing delivery of software that
doesn't meet customer expectations which in turn cause feature creep.

•

Involving developers in company politics more than is necessary.
Process

•

Schedules that are to short for the project at hand - too much emphasis on optimism.

•

No risk management or insufficient risk management.

•

Problems with contractors (part of risk assessment)

•

Luck of, or insufficient project planning. Throwing out plans when placed under
excessive pressure to complete project. Deliberately omitting non-code related
activities, like design, due to excessive pressure.

•

Spending excessive amounts of time on project approval and budgeting.

•

Poor design and poor quality assurance.

•

To few controls placed on the development process causing schedule slips to go
unnoticed.

•

Attempting to enter project "polishing" stage to early or more than once (frequent
attempts to get it shipped).

•

Thinking that project which is in trouble can be saved by "catch up" later on.

Product
•

Too many requirements, attempting to build systems that can do everything.

•

Adding to many new features to the ongoing project - feature creep.

•

Allowing developers to use new technology project for reasons other than project
requirement.

•

Attempting to treat software research as regular software development.
Technology

•

Silver bullet technology syndrome, over-estimating benefits of new tools and
technology.

•

Changing tools or methods in the middle of the project.

•

Failure to keep code backups, no source control software.

1.6

SOLUTIONS OF THESE PROBLEMS

•

There is no one single best practice that leads to the best software development
method. For each specific project a method has to be chose that is appropriate for it.
For example, mission critical software products have to be of much higher quality
than a screen saver software.

•

Not all projects need to optimize their development speed, many upper managers ask
for speed but mean other things. For example, client will talk about quick
development when they really want to minimize project overall cost.

•

Unless product has a strong schedule constraint development speed might not be of
top priority. If speed is not the most important factor, concentrate on quality.

•

Remember, you can deliver projects with only 2 branches of the trade-off triangle.

•

There is an absolute limit on the minimal time it will take to complete any given
project.

•

Projects cannot have 100% probability of completing on any given time because they
involve risks (not everything in a project is certain) thus we are dealing with
probabilities of completing on a given date.

•

Projects that are rapidly developed can be seen by customers as slow because they
don't provide a lot of feedback as to project progress.

•

Remember that cutting time from the top most (done 1st) stages of the project will
force you to pay back in time many times over in lower stages of the project. For
example, design flow will cost much more to fix in the construction phase than design
phase.

2. SYSTEM ANALYSIS
2.1

REQUIREMENT ANALYSIS
A requirement is a feature that must be included in the actual design and

implementation, getting to know the system to be implemented is of prime importance.
Main emphasis is on:
The inputs to the system.
The output expected from the system.
The people involved in the working of the system.
The volume of DATA (inputs) and the amount of Information (outputs) that will be
involved.
With respect to the system itself, the following facts are taken into consideration.
The major process involved.
The main points of application.
The processing rules for the collected data.
The exceptions that may be present.
The checks that should be placed in order to avoid wrong entries.

2.2

SOFTWARE REQUIREMENT SPECIFICATION

PURPOSE:The purpose of this document is that it deals with various levels of project
development and will account for time used in analysis, design, programming, testing and
verification etc.
SCOPE:The tool involved in giving the management the clear picture of the usage of time by
projects by analyzing the results provided by the software.
Documentation overview:This document has major sections.


Section1 provides an overview of entire software requirement specification.



Section2 provides the product that will be produced.



Section3 addresses the specific requirements of the system.

2.3

PROPOSED SYSTEM
To take advantage of the latest technology and to facilitate client to make

Online inquires about their project status a tool need to be developed. The tool should
accomplish the following functions:


The tool should be able to manage all the projects effectively and ensure

that

projects cycle goes on smoothly and they are completed on time.


While accepting client’s requirements, all necessary validations should be performed.

It should also store the client’s details.


The system should generate the following reports:



Client’s details list.



Employee details list.



Project details list.



Allocated tasks list.

INVESTIGATION:
For the study of the project, I met the client and collect his requirements and got the
information about various levels of project development and time assigned for each phase.
The main objective of this study is to determine whether the proposed system is feasible
or not. Solution strategies are usually generated without regard for feasibility because one
cannot be both creative and critical at the same time. Hence feasibility analysis is a must to
arrive at the most appropriate solution strategy. This feasibility analysis is done after the
thorough study of the system.
The planning objective is achieved through a process of information discovery that leads
to reasonable estimation.

Keeping the following aspects in mind, the system analysis for the development of the project
is done.
Identify the drawbacks of the existing system.
Identify the need for conversion.
Perform feasibility study.
Identify hardware, software and the database requirements.
Create a system definition that performs the foundation for the subsequent work.

SOFTWARE SCOPE:
The first activity in software project planning is the determination of the software
scope. The functions and performance allocated to software should be assesses to establish a
project scope. Software scope describes function, performance, reliability and constraints.

ESTIMATION:
Software project planning estimate can be done in many ways such as Lines Of Code
(LOC) based estimation, Functional Point Estimation (FP), Process Based Estimation. We
should select best of them depending on the requirement.

RESOURCE AVAILABILITY:
The resources which are common to any system, consist of human effort,
information and development resource. Developing any system with out satisfactory
resources is inappropriate and impossible. The design development team for this project
consists of five members or roles that are responsible for software development and internal
testing and its usage. Information assembly is vital to this project. Various sources of
information are available.

2.4

ROLES

Business Development Officer:
He is a person who actually, interacts with the people who are demanding
the project. He collects all the requirements of their projects.

Project Manager:

The manger from the name itself indicates that to manage the projects. He plans the
project and takes requirements from the HR. he then divides the project into tasks and assigns
those tasks to the developers. He fills his own timesheet and also checks the developer’s
timesheets.

Developer:
He deals with the actual coding part i.e. filling the time sheets and perform coding
according to the time allotted to him. He then submits the filled timesheets and completed
task to the system.

Human Resource Manager:
His main activity is to provide resources to the project. he also checks the time
sheets and decides the remuneration for the work done according to the time, in that
timesheet.

Client:
He is the person who demands the project and specifies the time, for which he needs
the project back done. If the time is large slot then he has to accept the problems, and partial
results. So that, he could place the new requirements for his project along with the
advancement in the technology used.

2.5

OPERATIONAL FEASIBILITY:
The system is operationally feasible, it is made so easy that operator will not

encounter any problem during working, as it is very user-friendly. Operational feasibility
checks the scope of the system. The system under consideration should have enough
operational research.
It is observed that the proposed system would provide a very interactive means to
share information and have a far and wide range. The proposed system would make the
information more interactive. Thus operational feasibility of the proposed system id found to
be high.

3. HARDWARE AND SOFTWARE SPECIFICATION
Hardware Specification
Processor

:

Intel P-IV based system

Processor Speed

:

250 MHz to 833MHz

RAM

:

512MB

Hard Disk

:

8GB to 30GB

Software Specification
Language

:

Technologies

C#.NET
:

ASP.NET

Database

:

SQL SERVER 2000

Web/Application server

:

Internet Information services (IIS)

Operating System

:

Windows NT/2000/XP

4. L I T E R A T U R E SURVEY
4.1 INTRODUCTION TO .NET FRAMEWORK
The Microsoft .NET Framework is a software technology that is available with several
Microsoft Windows operating systems. It includes a large library of pre-coded solutions
to common programming problems and a virtual machine that manages the execution of
programs written specifically for the framework. The .NET Framework is a key Microsoft
offering and is intended to be used by most new applications created for the Windows
platform.

The pre-coded solutions that form the framework's Base Class Library cover a large range of
programming needs in a number of areas, including user interface, data access,
database connectivity, cryptography, web application development, numeric algorithms,
and network communications. The class library is used by programmers, who combine it
with their own code to produce applications.
Programs written for the .NET Framework execute in a software environment that
manages the program's runtime requirements. Also part of the .NET Framework, this runtime
environment is known as the Common Language Runtime (CLR). The CLR provides the
appearance of an application virtual machine so that programmers need not consider the
capabilities of the specific CPU that will execute the program. The CLR also provides other
important services such as security, memory management, and exception handling. The
class library and the CLR together compose the .NET Framework.
PRINCIPAL DESIGN FEATURES INTEROPERABILITY
Because interaction between new and older applications is commonly required, the .NET
Framework provides means to access functionality that is implemented in programs that
execute outside the .NET environment.Access to COM components

is provided

in

the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the
framework; access to other functionality is provided using the P/Invoke feature.

COMMON RUNTIME ENGINE
The Common Language Runtime (CLR) is the virtual machine component of the .NET
framework. All .NET programs execute under the supervision of the CLR, guaranteeing
certain properties and behaviors in the areas of memory management, security, and exception
handling.
BASE CLASS LIBRARY
The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of
functionality available to all languages using the .NET Framework. The BCL provides
classes which encapsulate a number of common functions, including file reading and
writing, graphic rendering, database interaction and XML document manipulation.
SIMPLIFIED DEPLOYMENT
Installation of computer software must be carefully managed to ensure that it does not
interfere with previously installed software, and that it conforms to security requirements.
.NET framework includes design features and tools that help address these requirements.
SECURITY
The design is meant to address some of the vulnerabilities, such as buffer overflows, that
have been exploited by malicious software. Additionally, .NET provides a common
security model for all applications.
PORTABILITY
The design of the .NET Framework allows it to theoretically be platform agnostic, and
thus cross-platform compatible. That is, a program written to use the framework should
run without change on any type of system for which the framework is implemented.
Microsoft's commercial implementations of the framework cover Windows, Windows CE,
and the Xbox
360.
In addition, Microsoft submits the specifications for the Common Language Infrastructure
(which includes the core class libraries, Common Type System, and the Common
Intermediate Language), the C# language, and the C++/CLI language to both ECMA and

the ISO, making them available as open standards. This makes it possible for third parties
to create compatible implementations of the framework and its languages on other platforms.
ARCHITECTURE

Fig: 4.1.1 Visual overview of the Common Language Infrastructure (CLI)
COMMON LANGUAGE INFRASTRUCTURE
The core aspects of the .NET framework lie within the Common Language
Infrastructure, or CLI. The purpose of the CLI is to provide a language-neutral platform
for application development and execution, including functions for exception handling,
garbage collection, security, and interoperability. Microsoft's implementation of the CLI
is called the Common Language Runtime or CLR.

ASSEMBLIES
The intermediate CIL code is housed in .NET assemblies. As mandated by specification,
assemblies are stored in the Portable Executable (PE) format, common on the Windows
platform for all DLL and EXE files. The assembly consists of one or more files, one of
which must contain the manifest, which has the metadata for the assembly. The
complete name of an assembly (not to be confused with the filename on disk) contains its
simple text name, version number, culture, and public key token.
The public key token is a unique hash generated when the assembly is compiled, thus two
assemblies with the same public key token are guaranteed to be identical from the point of

view of the framework. A private key can also be specified known only to the creator of the
assembly and can be used for strong naming and to guarantee that the assembly is from
the same author when a new version of the assembly is compiled (required to add an
assembly to the Global Assembly Cache).
METADATA
All CLI is self-describing through .NET metadata. The CLR checks the metadata to
ensure that the correct method is called. Metadata is usually generated by language
compilers but developers c a n c r e a t e t h e i r

own

metadata t h r o u g h c u s t o m

a t t r i b u t e s . Metadata c o n t a i n s information about the assembly, and is also used to
implement the reflective programming capabilities of .NET Framework.
SECURITY
.NET has its own security mechanism with two general features: Code Access Security
(CAS), and validation and verification. Code Access Security is based on evidence that is
associated with a specific assembly. Typically the evidence is the source of the
assembly (whether it is installed on the local machine or has been downloaded from
the intranet or Internet). Code Access Security uses evidence to determine the permissions
granted to the code. Other code can demand that calling code is granted a specified
permission. The demand causes the CLR to perform a call stack walk: every assembly of
each method in the call stack is checked for the required permission; if any assembly is not
granted the permission a security exception is thrown.
When an assembly is loaded the CLR performs various tests. Two such tests are
validation and verification. During validation the CLR checks that the assembly contains
valid metadata and CIL, and whether the internal tables are correct. Verification is not so
exact. The verification mechanism checks to see if the code does anything that is 'unsafe'.
The algorithm used is quite conservative; hence occasionally code that is 'safe' does not
pass. Unsafe code will only be executed if the assembly has the 'skip verification'
permission, which generally means code that is installed on the local machine.
NET Framework uses appdomains as a mechanism for isolating code running in a
process. Appdomains can be created and code loaded into or unloaded from them
independent of other appdomains. This helps increase the fault tolerance of the application,
as faults or crashes in one appdomain do not affect rest of the application. Appdomains
can also be configured independently with different security privileges. This can help

increase the security of the application by isolating potentially unsafe code. The
developer, however, has to split the application into sub domains; it is not done by the CLR.
CLASS LIBRARY
Namespaces in the BCL
System
System. CodeDom System. Collections System. Diagnostics System. Globalization System.
IO
System. Resources
System. Text
System. Text. Regular Expressions
Microsoft .NET Framework includes a set of standard class libraries. The class library is
organized in a hierarchy of namespaces. Most of the built in APIs are part of either
System.* or Microsoft.* namespaces. It

encapsulates a large number of common

functions, such as file reading and writing, graphic rendering, database interaction, and
XML document manipulation, among others. The .NET class libraries are available to
all .NET languages. The .NET Framework class library is divided into two parts: the
Base Class Library and the Framework Class Library.
The Base Class Library (BCL) includes a small subset of the entire class library and is the
core set of classes that serve as the basic API of the Common Language Runtime. The
classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are
considered to be a part of the BCL. The BCL classes are available in both .NET
Framework as well as its alternative implementations including .NET Compact
Framework, Microsoft Silver light and Mono.The Framework Class Library (FCL) is a
superset of the BCL classes and refers to the entire class library that ships with .NET
Framework. It includes an expanded set of libraries, including Win Forms, ADO.NET,
ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows
Communication Foundation among

others. The FCL is much larger in scope than

standard libraries for languages like C++, and comparable in scope to the standard
libraries of Java.
MEMORY MANAGEMENT
The .NET Framework CLR frees the developer from the burden of managing memory

(allocating and freeing up when done); instead it does the memory management itself. To
this end, the memory allocated to instantiations of .NET types (objects) is done
contiguously from the managed heap, a pool of memory managed by the CLR. As long as
there exists a reference to an object, which might be either a direct reference to an object
or via a graph of objects, the object is considered to be in use by the CLR. When there is
no reference to an object, and it cannot be reached or used, it becomes garbage.
However, it still holds on to the memory allocated to it. .NET Framework includes a
garbage collector which runs periodically, on a separate thread from the application's
thread, that enumerates all the unusable objects and reclaims the memory allocated to
them.
The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep
garbage collector. The GC runs only when a certain amount of memory has been used or
there is enough pressure for memory on the system. Since it is not guaranteed when the
conditions to reclaim memory are reached, the GC runs are non-deterministic. Each .NET
application has a set of roots, which are pointers to objects on the managed heap
(managed objects). These include references to static objects and objects defined as local
variables or method parameters currently in scope, as well as objects referred to by CPU
registers.
When the GC runs, it pauses the application, and for each object referred to in the
root, it recursively enumerates all the objects reachable from the root objects and marks
them as reachable. It uses .NET metadata and reflection to discover the objects
encapsulated by an object, and then recursively walk them. It then enumerates all the
objects on the heap (which were initially allocated contiguously) using reflection. All
objects not marked as reachable are garbage. This is the mark phase. Since the memory
held by garbage is not of any consequence, it is considered free space. However, this
leaves chunks of free space between objects which were initially contiguous. The objects
are then compacted together, by using memory to copy them over to the free space to
make them contiguous again. Any reference to an object invalidated by moving the
object is updated to reflect the new location by the GC.
The application is resumed after the garbage collection is over.The GC used by
.NET Framework is actually generational.Objects are assigned a generation; newly
created objects belong to Generation 0. The objects that survive a garbage collection are

tagged as Generation 1, and the Generation 1 objects that survive another collection
are Generation 2 objects. The .NET Framework uses up to Generation 2 objects.Higher
generation objects are garbage collected less frequently than lower generation objects.
This helps increase the efficiency of garbage collection, as older objects tend to have a
larger lifetime than newer objects. Thus, by removing older (and thus more likely to
survive a collection) objects from the scope of a collection run, fewer objects need to be
checked and compacted.
FRAMEWORK
Microsoft started development on the .NET Framework in the late 1990s originally under the
name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions
of
.NET 1.0 was released.

Fig: 4.1.2 the .NET Framework stack.

Version
1.0
1.1
2.0
3.0

Version Number
1.0.3705.0
1.1.4322.573
2.0.50727.42
3.0.4506.30

Release Date
2002-01-05
2003-04-01
2005-11-07
2006-11-06

4.2 ASP.NET
SERVER APPLICATION DEVELOPMENT
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications h o s t t h e c o m m o n l a n g u a g e runtime, which allows your
custom managed code to control the behavior of the server. This model provides you with all
the features of the common language runtime and class library while gaining the
performance and scalability of the host server.

The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.

SERVER-SIDE MANAGED CODE
ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is
a complete architecture for developing Web sites and Internet-distributed objects using
managed code. Both Web Forms and XML Web services use IIS and ASP.NET as
the publishing mechanism for applications, and both have a collection of supporting
classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are distributed,
server-side application components similar to common Web sites. However, unlike Webbased applications, XML Web services components have no UI and are not targeted for
browsers such as Internet Explorer and Netscape Navigator. Instead, XML Web services
consist of reusable software components designed to be consumed by other applications,
such as traditional client applications, Web-based applications, or even other XML Web
services. As a result, XML Web services technology is rapidly moving application
development and deployment into the highly distributed environment of the Internet
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web

Forms pages in any language that supports the .NET Framework. In addition, your code no
longer needs to share the same file with your HTTP text (although it can continue to do so if
you prefer). Web Forms pages execute in native machine language because, like any other
managed application, they take full advantage of the runtime. In contrast, unmanaged ASP
pages are always scripted and interpreted .

ASP.NET

pages

are

faster,

more

functional, and easier to develop than unmanaged ASP pages because they interact with
the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid
in development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an extensible
data format), and WSDL ( the Web Services Description Language). The .NET
Framework is built on these standards to promote interoperability with non-Microsoft
solutions.

For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its
WSDL description, and produce C# or Visual Basic source code that your application can
use to become a client of the XML Web service. The source code can create classes derived
from classes in the class library that handle all the underlying communication using
SOAP and XML parsing. Although you can use the class library to consume XML
Web services directly, the Web Services Description Language tool and the other tools
contained in the SDK facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET Framework provides a set
of classes that conform to all the underlying communication standards, such as SOAP,
WSDL, and XML. Using those classes enables you to focus on the logic of your service,
without concerning yourself with the communications

infrastructure required by

distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will
run with the speed of native machine language using the scalable communication of IIS.

ACTIVE SERVER PAGES.NET
ASP.NET is a programming framework built on the common language runtime that can be
used on a server to build powerful Web applications. ASP.NET offers several important
advantages over previous Web development models:
•

Enhanced Performance. ASP.NET is compiled common language runtime code

running on the

server.

Unlike

its

interpreted

predecessors,

ASP.NET

can

take

advantage of early binding, just-in-time compilation, native optimization, and caching
services right out of the box. This amounts to dramatically better performance before you
ever write a line of code.

•

World-Class Tool Support. The ASP.NET framework is complemented by a rich

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

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

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

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

submission and client authentication to deployment and site configuration. For example,
the ASP.NET page framework allows you to build user interfaces that cleanly separate
application logic from presentation code and to handle events in a simple, Visual Basic - like
forms processing model. Additionally, the common language runtime simplifies
development, with managed code services such as automatic reference counting and garbage
collection.

•

Manageability. ASP.NET employs a text-based, hierarchical configuration system,

which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied
without the aid of
philosophy

local

extends

administration

tools.

This

"zero

local

administration"

to deploying ASP.NET Framework applications as well. An

ASP.NET Framework application is deployed to a server simply by copying the necessary
files to the server. No server restart is required, even to deploy or replace running compiled
code.

•

Scalability and Availability. ASP.NET has been designed with scalability in mind,

with features

specifically

tailored

to

improve

performance

in

clustered

and

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

•

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

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

Security. With built in Windows authentication and per-application configuration,

you can be assured that your applications are secure.
LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#,
Visual Basic, and Java Script.
WHAT IS ASP.NET WEB FORMS?
The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with
existing pages), the ASP.NET Web Forms framework has been specifically designed to
address a number of key deficiencies in the previous model. In particular, it provides:

•

The ability to create and use reusable UI controls that can encapsulate common

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

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

(not "spaghetti code").

•

The ability for development tools to provide strong WYSIWYG design support for

pages (existing ASP code is opaque to tools).

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

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

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

CODE-BEHIND WEB FORMS

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

INTRODUCTION TO ASP.NET SERVER CONTROLS

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

map

to

one

of

the

controls

is

assigned

the

type

of

System.Web.UI.HtmlControls.HtmlGenericControl.

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

In addition to supporting standard HTML input controls, ASP.NET enables developers to
utilize richer custom controls on their pages. For example, the following sample
demonstrates how the <asp:adrotator> control can be used to dynamically display rotating
ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script library
or cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common functionality.

5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built
by third parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list
server controls.
8. ASP.NET validation controls provide an easy way to do declarative client or server
data validation.

4.3 C#.NET
ADO.NET OVERVIEW
ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the web
with scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects, and
also introduces new objects. Key new ADO.NET objects include the Dataset, Data
Reader, and Data Adapter.

The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the DataSet -- that is separate and distinct from
any data stores. Because of that, the DataSet functions as a standalone entity. You can
think of the DataSet as an always disconnected recordset that knows nothing about the
source or destination of the data it contains. Inside a DataSet, much like in a database,
there are tables, columns, relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then, it
connects back to the database to update the data there, based on operations performed while
the DataSet held the data. In the past, data processing has been primarily connection-based.
Now, in an effort to make multi-tiered apps more efficient, data processing is turning to a
message-based approach that revolves around chunks of information. At the center of
this approach is the DataAdapter, which provides a bridge to retrieve and save data
between a DataSet and its source data store. It accomplishes this by means of requests to
the appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model that works
with all models of data storage: flat, relational, and hierarchical. It does this by having
no
'knowledge' of the source of its data, and by representing the data that it holds as collections
and data types. No matter what the source of the data within the DataSet is, it is manipulated
through the same set of standard APIs exposed through the DataSet and its subordinate
objects.
While the DataSet has no knowledge of the source of its data, the managed provider has
detailed and specific information. The role of the managed provider is to connect, fill, and
persist the DataSet to and from data stores. The OLE DB and SQL Server .NET Data
Providers (System.Data.OleDb and System.Data.SqlClient)

that are part of the .Net

Framework provide four basic objects: the Command, Connection, DataReader and
DataAdapter. In the remaining sections of this document, we'll walk through each part
of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they
are, and how to program against them.
The following sections will introduce you to some objects that have evolved, and some that
are new. These objects are:

•

Connections. For connection to and managing transactions against a database.

•

Commands. For issuing SQL commands against a database.

•

DataReaders. For reading a forward-only stream of data records from a SQL Server
data source.

•

DataSet. For storing, Remoting and programming against flat data, XML data and
relational data.

•

DataAdapters. For pushing data into a DataSet, and reconciling data against a

database.

When dealing with connections to a database, there are two different options: SQL Server
.NET

Data

Provider

(System.Data.SqlClient) and

OLE

DB

.NET

Data

Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET
Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE DB

.NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).

CONNECTIONS
Connections are used to 'talk to' databases, and are represented by provider-specific
classes such as SqlConnection. Commands travel over connections and resultsets are
returned in the form of streams which can be read by a DataReader object, or pushed into a
DataSet object.
COMMANDS
Commands contain the information that is submitted to a database, and are represented by
provider-specific classes such as SqlCommand. A command can be a stored procedure
call, an UPDATE statement, or a statement that returns results. You can also use input
and output parameters, and return values as part of your command syntax. The example
below shows how to issue an INSERT statement against the Northwind database.
DATAREADERS
The DataReader object is somewhat synonymous with a read-only/forward-only cursor
over data. The DataReader API supports flat as well as hierarchical data. A DataReader
object is returned after executing a command against a database. The format of the
returned DataReader object is different from a recordset. For example, you might use the
DataReader to show the results of a search list in a web page.
DATASETS AND DATAADAPTERS DATASETS
The Dataset object is similar to the ADO Recordset object, but more powerful, and with
one other important distinction: the DataSet is always disconnected. The DataSet
object represents a cache of data, with database-like structures such as tables, columns,
relationships, and constraints. However, though a DataSet can and does behave much like
a database, it is important to remember that DataSet objects do not interact directly with
databases, or other source data.
This allows the developer to work with a programming model that is always consistent,
regardless of where the source data resides. Data coming from a database, an XML file,
from code, or user input can all be placed into DataSet objects. Then, as changes are
made to the DataSet they can be tracked and verified before updating the source data.
The GetChanges method of the DataSet object actually creates a second DatSet that
contains only the changes to the data. This DataSet is then used by a DataAdapter (or
other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to produce and
consume XML data and XML schemas. XML schemas can be used to describe
schemas interchanged via WebServices. In fact, a DataSet with a schema can actually be
compiled for type safety and statement completion.
DATAADAPTERS (OLEDB/SQL)
The DataAdapter object works as a bridge between the DataSet and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand
and SqlConnection) can increase overall performance when working with a Microsoft
SQL Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection
objects.
The DataAdapter object uses commands to update the data source after changes have
been made to the DataSet. Using the Fill method of the DataAdapter calls the
SELECT command; using the Update method calls the INSERT, UPDATE or DELETE
command for each changed row. You can explicitly set these commands in order to control
the statements used at runtime to resolve changes, including the use of stored procedures.
For ad-hoc scenarios, a CommandBuilder object can generate these at run-time based
upon a select statement. However, this run-time generation requires an extra round-trip
to the server in order to gather required metadata, so explicitly providing the INSERT,
UPDATE, and DELETE commands at design time will result in better run-time
performance.
1. ADO.NET is the next evolution of ADO for the .Net Framework.
2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two
new objects, the DataSet and DataAdapter, are provided for these scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache for updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in order to do
inserts, updates, and deletes. You don't need to first put data into a DataSet in order to insert,
update, or delete it.
Also, you can use a DataSet to bind to the data, move through the data, and navigate
data relationships

4.4 SQL SERVER -2005
A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase,
paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update
and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics of people,
things and events. SQL Server stores each data item in its own fields. In SQL Server, the
fields relating to a particular person, thing or event are bundled together to form a single
complete unit of data, called a record (it can also be referred to as raw or an occurrence).
Each record is made up of a number of fields. No two fields in a record can have the same
field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time,
you define any additional fields or change the definition of existing fields.
SQL SERVER TABLES
SQL Server stores records relating to each other in a table. Different tables are created for
the various groups of information. Related tables are grouped together to form a database.
PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies
each record in the table. The Unique identifier is called the Primary Key, or simply the
Key. The primary key provides the means to distinguish one record from all other in a table.
It allows the user and the database system to identify, locate and refer to one particular
record in the database.
RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one
table. SQL Server makes it very easy to link the data in multiple tables. Matching an
employee to the department in which they work is one example. This is what makes
SQL Server a relational database management system, or RDBMS. It stores data in two
or more tables and enables you to define relationships between the table and enables you
to define relationships between the tables.
FOREIGN KEY

When a field is one table matches the primary key of another field is referred to as a
foreign key. A foreign key is a field or a group of fields in one table whose values match
those of the primary key of another table.
REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains consistency
between them. Ensuring that the data among related tables is correctly matched is referred
to as maintaining referential integrity.
DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract view of the
data. This system hides certain details of how the data is stored and maintained. Data
abstraction is divided into three levels.
Physical level: This is the lowest level of abstraction at which one describes how the data
are actually stored.
Conceptual Level: At this level of database abstraction all the attributed and what data
are actually stored is described and entries and relationship among them.

View level:

This is the highest level of abstraction at which one describes only part of

the database.
ADVANTAGES OF RDBMS
•

Redundancy can be avoided

•

Inconsistency can be eliminated

•

Data can be Shared

•

Standards can be enforced

•

Security restrictions ca be applied

•

Integrity can be maintained

•

Conflicting requirements can be balanced

•

Data independence can be achieved.

DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost of

purchasing of developing the software, the hardware has to be upgraded to allow for
the extensive programs and the workspace required for their execution and storage.
While centralization reduces

duplication, the lack of duplication requires that the

database be adequately backed up so that in case of failure the data can be recovered.
FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS) because it is the
only Database that meets the uncompromising requirements of today’s most demanding
information systems. From complex decision support systems (DSS) to the most rigorous
online transaction processing (OLTP) application, even

application that require

simultaneous DSS and OLTP access to the same critical data, SQL Server leads the
industry in both performance and capability.
SQL SERVER is a truly portable, distributed, and open DBMS that delivers
unmatched performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially
designed for online transactions processing and for handling large database application.
SQL SERVER with transactions processing option offers two features which contribute to
very high level of transaction processing throughput, which are the row level lock manager
ENTERPRISE WIDE DATA SHARING
The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the
systems in the organization to be linked into a singular, integrated computing resource.
PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and operating systems
platforms,

including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary

platforms. This portability gives complete freedom to choose the database server platform
that meets the system requirements.
OPEN SYSTEMS
SQL SERVER offers a leading implementation of industry –standard SQL.
SQL Server’s open architecture integrates SQL SERVER and non –SQL SERVER
DBMS with industry’s most comprehensive collection of tools, application, and third party
software products SQL Server’s Open architecture provides transparent access to data

from other relational database and even non-relational database.

DISTRIBUTED DATA SHARING
SQL Server’s networking and distributed database capabilities to access data stored on
remote server with the same ease as if the information was stored on a single local
computer. A single SQL statement can access data at multiple sites. You can store
data where system requirements such as performance, security or availability dictate.
UNMATCHED PERFORMANCE
The most advanced architecture in the industry allows the SQL SERVER DBMS to
deliver unmatched performance.

SOPHISTICATED CONCURRENCY CONTROL
Real World applications demand access to critical data.

With most database Systems

application becomes “contention bound” – which performance is limited not by the CPU
power or by disk I/O, but user waiting on one another for data access. SQL Server
employs full, unrestricted row-level locking and contention free queries to minimize
and in many cases entirely eliminates contention wait times.

NO I/O BOTTLENECKS
SQL Server’s fast commit groups commit and deferred write technologies dramatically
reduce disk I/O bottlenecks. While some database write whole data block to disk at commit
time, SQL Server commits transactions with at most sequential log file on disk at commit
time, On high throughput systems, one sequential writes typically group commit multiple
transactions. Data read by the transaction remains as shared memory so that other
transactions may access that data without reading it again from disk. Since fast commits
write all data necessary to the recovery to the log file, modified blocks are written back to
the database independently of the transaction commit, when written from memory to disk.

5. SYSTEM DESIGN
5.1 INTRODUCTION
The most creative and challenging phase of the life cycle is system design. The term
design describes a final system and the process by which it is developed. It refers to the
technical specifications that will be applied in implementations of the candidate system. The
design may be defined as “the process of applying various techniques and principles for the
purpose of defining a device, a process or a system with sufficient details to permit its
physical realization”. The designer’s goal is how the output is to be produced and in what
format. Samples of the output and input are also presented. Second input data and database
files have to be designed to meet the requirements of the proposed output. The processing
phases are handled through the program Construction and Testing. Finally, details related to
justification of the system and an estimate of the impact of the candidate system on the user
and the organization are documented and evaluated by management as a step toward
implementation.
The importance of software design can be stated in a single word “Quality”. Design provides
us with representations of software that can be assessed for quality. Design is the only way
where we can accurately translate a customer’s requirements into a complete software
product or system. Without design we risk building an unstable system, which might fail if
small changes are made. It may as well be difficult to test, or could be one who’s quality
can’t be tested. So it is an essential phase in the development of a software product.
The following steps are followed in designing software:
The statements of functions desired from software to be developed are recognized.
The database design steps are applied to identify the various entities and relationships
between them. General access methods are then applied to the conceptual schema to get the
logical model, which is then further transformed into relational tables.
The concept of s/w engineering is then applied to get logical architecture of the system
comprising of different modules each containing all the related functions.

5.2 DATA FLOW DIAGRAMS
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
DFDs are two types

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,
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.

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:

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

SPMT DFD
CLIENT

BDO

Project
Details

Client
Information

Details
Task

SPMT
Time
Sheets

Plan

HRM

PM

Reqirement Implementation
Plan
s

Manpower

Fig: 5.2.1

DEVELOPER

Client DFD

D3

Login
Client Message

User acounts

D2

P1

project DB

P3

Client
C
Acoounts

BDO

Authentication

Agreement Proposal

Cost,tim
e

Uid, pwd

P4

D1
Client DB
C
Acoounts

Status

D2

Fig:5.2.2

Project DB

Cl
ie
nt
C
A

Time

BDO DFD
D3

BDO

User Acount

P4

P1

Authentication

Status Checking

BDO
uid,pw
d

D2

D1

Client DB

Project DB
ProvidingDetailss

Agreement process
P2

D2 Project DB

P3

Client,Pr
oj

Cost,tim
e

Fig: 5.2.3

Client

PM Level1 Client
PM
P1

Messege

D2

Project DB

P2
Authentication
PM

Project Details

P3
Acquires

Project

Planning Process
Uid,pwd

Platfor

Time

m
D3 User Account
D2 Project DB

Requesting
P4
Requesting

P5
Task Allocation

Resources

Checking
task Progress

Time,Durat
ion

Time,Quali
ty

Developer
HR

PM
Fig: 5.2.4

PM Level2 DFD
HR

P3.1
Retrieving

P3.2
Project

P4.4
Feedback

Project infor

Plan Process

From Official

Dev

Uid,pw
d

Uid,pw
d

Uid,pw
d

P3.3

D2
Officials

Approval of
The plan

D2

Fig: 5.2.5

Developer

Uid,pw
d

PM

HUMAN RESOURCE:

P1

H
Message

Authentication

H

D2

Project

P2

Taking Project
Plan

D3

Checking

Uid,pw
d
User Accounts
Checking

D4

P5

Status

Employee

P3
Resources availability

Fig: 5.2.6

Allocates

P4Resources

H

D2
H

Project

SOFTWARE PROJECT MANAGEMENT TOOL Project Report

Developer DFD:

D3

D2

User Accounts

Authentication
P1

Project DB

Submission Of
P4

Developer

Tasks&Time Sheet

Login

PM

Process

Message

Uid,pwd

D2

Accepting
Tasks

P2

Uid,pwd

Project DB

Viewing Project
details

P3
D2

PM

Fig: 5.2.7

Project DB

5.3 E-R Diagram
The following diagrams depicts various entities involve in the Software project management
tool and relationships those entities.
Checks

Requirements

Provides

Accepts
Works for

Assigns

Views

Maintains

Fig: 5.3.1

Allocates

5.4 UML DIAGRAMS

CLASS DIAGRAM:

Fig: 4.4.1

Client Sequence Diagram:

Fig: 5.4.3

GUISTANDARDS

Labels
A label consists of read only text or graphics, it identifies components and
communication the status of a process. You can use labels with a component or can use it to
describe a group of components.

Text Field
A Text Field is a rectangular box that displays a single line or text. If the line is too
long to fit in the text field, the text automatically Scrolls horizontally.

Password Field
A Password Field is a variation of text field. When you type in a password field,
instead of characters asterisks (*) are displayed. The asterisks are referred to as a Masking
agent.

List Box
A List Box is used to display a set of items. One can use a list to present user with a
set of choices.

Command Buttons
The Command Buttons is a component with a rectangular box that displays a single
line or text. The text typically consists of a single word that represents the action associated
with that button.

REPORTS
The system should generate the following reports:


Client’s details list.



Employee details list.



Allocated resources list.



Project details list.



Allocated tasks list.

6. SYSTEM ENVIRONMENT
Microsoft .NET Framework
The .Net frame work is a new computing platform that simplifies application
development in the highly distributed environment of the internet. The .NET frame work is
designed to fulfill the following objectives:


To provide a consistent object-oriented programming environment whether object
code is stored and executed locally, executed locally but internet distributed, or
executed remotely.



To provide a code-execution environment that minimizes software deployment and
versioning conflicts.



To provide a code-execution environment that guarantees safe execution of code,
including code created by an unknown or semi-trusted party.



To provide a code-execution environment that eliminates the performance problems
of scripted or interpreted environments.



To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.



To build all communications on industry standards to ensure that code based on the
.NET Framework can integrate with any other code.

The .NET Framework has two main components:
o

The common language runtime.

o

The .NET Framework class library.

The common language runtime is the foundation of the .NET Framework. You can think of
the runtime as an agent that manages code at execution time, providing core services such as
memory management, thread management, and remoting, while also enforcing strict type
safety and other forms of code accuracy that ensure security and robustness. In fact, the
concept of code management is a fundamental principle of runtime. Code that targets the
runtime is known as managed code, while code that does not target the runtime is known as

managed code. The class library, the other main component of the.NET Framework, is a
comprehensive, object-oriented collection of reusable types that you can use to
Develop application ranging from traditional command line or graphical user interface (GUI)
applications to applications to latest innovations provide by Windows applications.
The .net Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code, thereby
creating a software environment that can be exploit both managed and unmanaged features.
The .net Framework not only provides several runtime hosts, but also supports the
development of third-party runtime hosts.
For example, ASP .NET hosts the runtime to provide a scalable, server-side
environment for managed code. ASP .NET works directly with the runtime enable Web
forms applications and XML Web services, both of which are discussed later in this topic.
Internet explorer is an example of an unmanaged application that hosts the runtime.
Using Internet Explorer to host the runtime enables you to embed managed components or
windows forms controls in HTML documents. Hosting the runtime in this way makes
managed mobile code possible, but with significant improvement that only managed code can
offer, such as semi-trusted execution and secure isolated file storage.
The following illustration shows the relationship of the common language runtime
and the class library to your application and to the overall system. The illustration also shows
how managed code operates within a larger architecture.

Features of the common Language Runtime:
The common language runtime manages memory, thread execution, code
execution, code safety verification, compilation, and other system services. These features are
intrinsic to the managed code that runs on the common runtime. Language compilers that
target the .NET Framework makes the features of the .NET Framework available to existing
code written in that language, greatly easing the migration process for existing application.
While the runtime is designed for the software of the future, it also supports of today and
yesterday. Interoperability between managed and unmanaged code enables developers to use
necessary COM components and DLLs.
The runtime is designed to enhance the performance. Although the common
language runtime provides many standards runtime service, managed code is never

interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in
the native machine language of the system on which it is executing. Meanwhile, the memory
manager removes the possibilities of fragmented memory and increases memory locality-ofreference to further increase performance.
Finally the run time can be hosted by high performance, server’s side applications such as
Microsoft SQL Server and internet information services (IIS). This infrastructure enables you
to use managed code to write your business logic, while still enjoying the superior
performance of the industry’s best enterprise servers that supports runtime hosting.

.NET Framework class library:
The .NET Framework class library is a collection of usable types that integrate
with the common language runtime the class library is object oriented providing types from
which your managed codes can derive functionality. This not only makes the .NET
Framework types easy to use, but also reduces the time associated with learning new features
of .NET Framework. In addition, third-party components can integrate seamlessly with
classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces
that you can use to develop your own collection classes. Your collection classes will blend
seamlessly with the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable
you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access.
In addition to these common tasks, the class library type that supports a variety of specialized
development scenarios. For example, you can use the .NET Framework to develop the
following types if applications and services.
1

Console applications

2

scripted or hosted applications

3

windows GUI applications(Windows forms)

4

ASP .NET applications

5

XML Web services

6

Windows services.

For example, the windows forms classes are a comprehensive set of reusable
types that vastly simplify Windows GUI development. If you write an ASP .NET web form
application, you can use the web forms classes.

Client Application Development:
Client applications are the closest to a traditional style of application in windows
based programming. These are the types of applications that display windows or forms on the
desktop, enabling a user to perform a task. Client applications include applications such as
word processors and spreadsheets, as well as custom business applications such as data-entry
tools, reporting tools, and so on. Client applications usually employ windows, menus,
buttons, and other GUI elements, and they likely access local resources such as the file
system and peripherals such as printers.
Another kind of client applications is the traditional ActiveX control (now
replaced by the managed Windows Forms control) deployed over the internet as a web page.
This application is much like other client applications: it is executed natively, has access to
local resources, and includes graphical elements.

ACTIVEX DATA OBJECTS
ADO .NET Overview
ADO .NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the web
with scalability, statelessness, and XML in mind.
ADO .NET uses some ADO objects, such as the Connection and Command
objects, and also introduces new objects. Key new ADO .NET objects include the Data Set,
Data Reader, and Data Adapter.
The important distinction between this evolved stage of ADO .NET and
previous data architectures is that there exists an object--the Dataset--that is separated and
distinct from any data stores. Because of that, the Dataset functions as a standalone entity.
You can think of the Dataset as an always disconnected record set that knows nothing about
the source or destination of the data it contains. Inside a Dataset, much like in a database,
there are tables, columns, relationships, constraints, views, and so forth.

A Data Adapter is the object that connects to the database to fill the Dataset.
Then, it connects back to the database to update the data there, based in operations performed
while the Dataset held the data.
In the past, data processing has been primarily connection based. Now, in an effort to make
multi tired apps more efficient, data processing is truing to a message based approach that
revolves around chunks of information. At the center of this approach is the Data Adapter,
which provides a bridge to retrieve and save data between a Dataset and its source data store.
It accomplishes this by means of requests to the appropriate SQL commands made
against the data store.
The XML based Dataset objects provides a consistent programming model that works
with all models of data storage: flat, relational, and hierarchical. It does this by having no
‘knowledge; of the source of its data, and by representing the data within the Dataset is, it is
manipulated through the same set of standards APIs exposed through the Dataset and its
subordinate objects.
While the Dataset has no knowledge of the source of its data, the managed provider
has detailed and specific information. The role of the managed provider is to connect, fill, and
persists the Dataset to and from data stores. The OLEDB and SQL server .NET Data
Providers (System.Data.OleDb and System.Data.Sqlclient) that are part of the .NET
Framework provider four basic objects: the command, connection, Data Reader and Data
Adapter.
In the remaining sections of this document, well walk through each part of the Dataset and
the OLE DB/SQL Server .NET Data Providers explaining what they are, and how to program
against them.
The following sections will introduce you some objects that have evolved, and some that are
new. These objects are:
Connections. For connection to and transaction against database.
Commands. For issuing SQL commands against a database.
Data Readers. For reading a forward-only stream of data records from a SQL server
data source.
Datasets. For storing, removing and programming against flat data, XML data and relational
data.

Data Adapters. For publishing data into a dataset, and reconciling data against a database.

When dealing with connections to a database, there are two different options: SQL server
.NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider
(System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider.
These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider
is used to talk to any OLE DB Provider (as it uses OLE DB underneath).

Connections
Connections are used to ‘talk to’ databases, and are represented by provide-specific
classes such SQLConnections. Commands travel over connections and result sets are returned
in the format of streams which can be read by a Data Reader Objects, or pushed into a
Dataset objects.

Commands
Commands contain the information that us submitted to a database, and are
represented by provider classes such as SQLCommand. A command can be a stored
procedure call, an UPDATYE statement, or a statement that returns results. You can also use
input and output parameters, and return values as part of your command syntax. The example
below shows how to issue an INSERT statement against the North wide database.

Data Readers
The Data Reader object is somewhat synonymous with a read-only/forward-only
cursor over data. The Data Reader API supports flat as well as hierarchical data. A Data
Reader object is returned after executing a command against a database.
The format of the returned Data Reader object is different from a record set. For
example, you might use the Data Reader to show the results of a search list in a web page.

Data Sets and Data Adapters
Data sets
The DataSet object is similar to the ADO Record set object, but more powerful, and
with one other important distinction: the DataSet is always disconnected. The DataSet object
represents a cache of data, with database-like structure such as tables, columns, relationships
and constrains. However, through a DataSet can and does behave much like a database, it is

important to remember that dataset objects do not interact directly with databases, or other
source data. This allows the developer to work with a programming model that is always
consistent, regardless of where the source data resides.
Data coming from a database, an XML file, from code, or user input can all be placed into
Dataset objects. Then, as changes are made to the Dataset they can be tracked and verified
before updating the source data. The Get Changes method of the Dataset object actually
creates a second Dataset that contains only the changes to the data. This Dataset is then used
by a DataAdapter to update the original data source.
The Dataset has many XML characteristics, including the ability to produce and
consume XML data and XML schemas. XML schemas can be used to describe schemas
interchanged via WebServices. In fact, a Dataset with a schema can actually be compiled for
type safety and statement completion.

Data Adapters
The Data Adapter object works as a bridge between the Dataset and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand and
SqlConnection) can increase overall performance when working with a Microsoft SQL
Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection objects.
The Data Adapter objects uses commands to update the data source after changes
have been made to the Dataset. Using the fill method of the DataAdapter calls the SELECT
command; using the Update method calls the INSERT, UPDATEOR DELETE commands
for each changed row. You can explicitly set these commands in order to control the
statements used at runtime to resolve changes, including the use of stored procedures. For adhoc scenarios, a CommandBuildr object can generate these at run-time based upon a select
statement.
However this run-time generation requires an extra round trip to the server in the
order to gather required metadata. So explicitly providing the INSERTING, UPDATEING,
DELETEINTG commands at design time will result in better run-time performance.
ADO.NET was created with n-Tier, stateless and XML in the forefront. Two new
objects, the dataset and data adapter, are provided for these scenarios.

SQL SERVER

A data base management, or DBMS, gives the user access to their data helps them
transform the data into information. Such as management system includes dbase, paradox,
and IMS, SQL and SQL server. These systems allow users to create update and extract from
their database.
A database is a structured collection of data. Data refers to the characteristics of people,
things and events; SQL server stores each data in its own fields. In SQL server the fields
relating to particular person, thing or event are bundled together to form a single complete
unit of data, called a record (it can also be referred to as a row or an occurrence). Each record
is made up of a number of fields .no two fields in a record can have the same field.
During a SQL server database design project the analysis of your business needs
identifies all the fields or attributes of interest .if your business needs change over time, you
define any additional fields or change the definition of existing fields. SQL server tables
SQL server stores records relating to each other in a table. Different tables are created
for the various groups of information. Related tables are grouped together to form a database.

Primary key
Every table in SQL server has a field or a combination of fields that uniquely
identifies each record in table. The unique identifier is called the primary key, or simply the
key. The primary key provides the means to distinguish one record from all other in a table. It
allows the user and the database system to identify, locate and refer to one particular record
in the database.

Relational database
Sometimes all the information of interest to business operation can be stored in one
table. SQLServer makes it very easy to link the data in multiple tables. Matching an
employee to the department in which they work is one example. This is what makes SQL
server a relational database management system, or RDBMS.
It stores data in two or more tables and enables you to define relationships between the tables
and enables you to define relationships between the tables.

Foreign Key
When a field is one table matches the primary key of another field is referred to
as a foreign key. A foreign key field or a group of fields in one table whose values match
those of the primary key of another table.

Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly matched is
referred to as maintaining referential integrity.

Data Abstraction
A major purpose of database system is to provide users with an abstract view of
the data. This system hides certain details of how data is stored and maintained. Data
abstraction is divided into three levels.
Physical level: This is the lowest level of abstraction at which one describes how the data are
actually stored.
Conceptual Level: At this level of database abstraction all attributed and what data are
actually stored is described and relationship among them
View Level: This is the highest level of abstraction at which one describes only part of the
database.

Advantages of RDBMS
1.

Redundancy can be avoided.

2.

Inconsistency can be eliminated.

3.

Data can be shared.

4.

Standards can be enforced.

5.

Security restrictions can be applied.

6.

Integrity can be maintained.

7.

Conflicting requirements can be balanced.

8.

Data independence can be achieved.

Disadvantages of DBMS
A significant disadvantage of the DBMS System is cost. In addition to the cost of
purchasing of developing the software, the hardware has to be upgrade to allow for the
extensive programs and the workspace required for their execution and storage. While
centralization reduces duplication requires that the database be adequately backed up so that
in case of failure the data can be recovered.

Features of SQL SERVER (RDBMS)
SQL Server is one of the leading database management system (DBMS) because it
is the only Database that that meets the uncompromising requirements of today’s most
demanding information systems. From complex decision support system (DSS) to the most

rigorous online transaction processing (OLTP) application, even application that require
simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry
in both performance and capability
SQL SERVER is a truly portable, distributed, and open DBMS that delivers
unmatched performance, continuous and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially
designed for online transaction processing and for handling large database application.
SQL SERVER with transaction processing option offers two features which
contribute to very high level of transaction processing throughput, which are The row level
lock manager

Enterprise wide Data Sharing
The unrivaled portability and connectivity of the SQL server DBMS enables all the
systems in the organization to be linked into a single, integrated computing resource.

Portability
SQL SERVER is fully portable to more 80 distinct hardware and operating systems
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms.
This portability gives complete freedom to choose the database server platforms that meet the
system requirements

Open System
SQL SERVER offers a leading implementation of industry-standard SQL. SQL
Server’s open architecture integrates SQL SERVER and non-SQL SERVER DBMS with
industry’s most comprehensive collection of tools, application, and third party software
products SQL Server’s open architecture provides transparent to data from other relational
database and even non-relational database.

Distributed Data Sharing
SQL Server’s networking and distributed database capabilities to access data stored
on remote server with the same ease as if the information was stored on a single local
computer. A single SQL statement can access data multiple sites. You can store data where
system requirements such as performance, security or availability dictate.

Unmatched performance

The most advanced architecture in the industry allows SQL SEVER DBMS to
deliver unmatched performance.

Sophisticated Concurrency Control
Real world applications demand access to critical data. With most database
Systems applications becomes “connection bound”- which performance is limited not by the
CPU power or by disk I/O, but user waiting on one another contention free queries to
minimize and in many cases entirely eliminates contention waits times.

No I/O Bottlenecks
SQL Server’s fast commit groups commit and deferred write technologies
dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk
at commit time, SQL SERVER commits transactions with at most sequential log file on disk
at commit time, On high throughput systems, one sequential log file on disk at commit
multiple transactions. Data read by the transaction remains as shared memory so that other
transactions may access that data without reading it again from disk. Since fast commits write
all data necessary to the recovery to the log file, modified blocks are written back to the
database independently of the transactions commit, when written from memory to disk.

7.IMPLEMENTATION
7.1 Source Code
7.1.1 Home Page
<%@

Page

Language="C#"

AutoEventWireup="true"

CodeFile="Home.aspx.cs"

Inherits="_Default" %>
<!DOCTYPE

html

PUBLIC

"-//W3C//DTD

XHTML

1.0

Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
    
<asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Italic="True" FontNames="Monotype Corsiva"
Font-Size="XX-Large" Style="z-index: 100; left: 565px; position: absolute; top:
264px"
Text="INTRODUCTION" ForeColor="Coral"></asp:Label>
Font-Size="Large" Height="179px" Style="z-index: 101; left: 565px; position:
absolute;
top: 330px" Text='The Project enttled "Software Project Management Tool" deal with
the various levels of project development and will account for time used in
analysis,design,programming,testing anaa verification etc.The product willassist the
orhganization in maintaining record of every projectit undertakes.'
Width="382px" ForeColor="DarkRed"></asp:Label>

<asp:LinkButton ID="LinkButton1" runat="server" BackColor="Transparent" FontBold="True"
Font-Italic="True" Font-Names="Monotype Corsiva" Font-Size="X-Large"
ForeColor="IndianRed"
OnClick="LinkButton1_Click" Style="z-index: 102; left: 40px; position: absolute;
top: 195px">CLIENT</asp:LinkButton>
<asp:LinkButton ID="LinkButton2" runat="server" Font-Bold="True" FontItalic="True"
Font-Names="Monotype Corsiva" Font-Size="X-Large" ForeColor="IndianRed"
Style="z-index: 103;
left:

40px;

position:

absolute;

top:

260px"

OnClick="LinkButton2_Click">BDO</asp:LinkButton>
left: 40px; position: absolute; top: 481px" OnClick="LinkButton3_Click">HUMAN
RESOURCE</asp:LinkButton>
left: 40px; position: absolute; top: 405px" OnClick="LinkButton4_Click">PROJRCT
MANAGER</asp:LinkButton>
left:

40px;

position:

absolute;

top:

328px"

OnClick="LinkButton5_Click">DEVELOPER</asp:LinkButton>
Font-Size="XX-Large" Style="z-index: 108; left: 109px; position: absolute; top:
29px"

Text=" SOFTWARE PROJECT MANAGEMENT TOOL" ForeColor="Olive"
Height="43px" Width="647px"></asp:Label>
</div>
</form>
</body>
</html>
7.1.2 HR login:
<%@

Page

Language="C#"

AutoEventWireup="true"

CodeFile="hrlogin.aspx.cs"

Inherits="hrlogin" %>
<!DOCTYPE

html

PUBLIC

"-//W3C//DTD

XHTML

1.0

Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
Font-Size="XX-Large" Font-Underline="True" ForeColor="Olive" Style="z-index:
100;
left: 250px; position: absolute; top: 47px" Text="HR Login Screen"></asp:Label>
Font-Size="X-Large" ForeColor="IndianRed" Style="z-index: 101; left: 88px;
position: absolute;
top: 180px" Text="User Id"></asp:Label>

Font-Size="X-Large" ForeColor="IndianRed" Style="z-index: 102; left: 86px;
position: absolute;
top: 253px" Text="Password"></asp:Label>
<asp:TextBox ID="TextBox1" runat="server" Style="z-index: 103; left: 239px;
position: absolute;
top: 177px"></asp:TextBox>
<asp:TextBox ID="TextBox2" runat="server" Style="z-index: 104; left: 248px;
position: absolute;
top: 254px" TextMode="Password"></asp:TextBox>
<asp:Button ID="Button1" runat="server" Font-Bold="True" Font-Italic="True" FontNames="Monotype Corsiva"
Font-Size="Large" ForeColor="IndianRed" OnClick="Button1_Click" Style="zindex: 105;
left: 274px; position: absolute; top: 359px" Text="Ok" />
<asp:Button ID="Button2" runat="server" Font-Bold="True" Font-Italic="True" FontNames="Monotype Corsiva"
Font-Size="Large" ForeColor="IndianRed" Style="z-index: 106; left: 377px;
position: absolute;
top: 360px" Text="Cancel" />
<asp:Label ID="Label4" runat="server" Style="z-index: 108; left: 214px; position:
absolute;
top: 467px" Text="Label"></asp:Label>
</div>
</form>
</body>
</html>

8. SYSTEM TESTING

Testing is the process of confirming that a program or system does what it is proposed off,
Testing is the only way to assure the quality of s/w and it is an umbrella activity rather that a
separate phase. This is an activity to be performed in parallel with the s/w efforts and one that
consists of its own phase of analysis, design, implementation, execution and maintenance.

8.1 TESTING STRATEGY
Unit Testing:
This testing method considers a module as single unit and checks the unit at
interfaces and communities with other modules rather than getting into details at statement
level. Here the module will be treated as BLACKBOX, which will take some inputs and
generate output. Outputs for a given set of input combination are pre calculated and are
generated by the module.
Integration Testing:
Here all the pre-tested individual modules will be assembled to create a larger
system and tests are carried out at system level to make sure that all modules are working in
synchronous with each other. This testing methodology helps in making sure that all modules
which are running perfectly when checked individually and are also running cohesion with
other modules. For this testing we create test-cases to check all modules once and then a
generated test combination of test paths throughout the system to make sure that no path is
making its way into chaos.
Validation Testing:
Testing is major quality control measure employed during software development. Its basic
function is to detect errors. Sub functions when combined may not produce than it is desired.
Global data structures can represent the problems. Integrated testing is a systematic technique
for constructing the program structure while conducting the tests. To uncover errors that are
associated with interfacing the objective is to make test modules and built a program structure
that has detected by design. In a non-incremental integration all the modules are combined in
advance and the program is tested as a whole. Here error will appear in an end-less loop
function.. In incremental testing the program is constructed andtested in small segments
where the errors are isolated and corrected.

Different incremental integration strategies are
1.

Top-Down integration

2.

Bottom-Up integration

3.

Regression integration

Testing means quality test. Testing is a process of executing a program with the intent
of finding error. A good test case is one that has a high probability of finding an as yet un
discovered error.
Objective should be to design test that systematically uncover different classes of
error and to do with a minimum amount of time and effort. Testing cannot show the absence
of defects, it can only show that sw defects are present. It is important to keep this statement
in a mind as testing is being conducted.
Any engineering product can be tested in one of the two ways.
Knowing the specific function that a product has been designed to perform, test can
be conducted that demonstrates each function is fully operational. This approach is called
‘BLACK BOX TEXTING’
Knowing the internal working of the product, test can be conducted to ensure that “all
gears mesh”, that is, that internal operation of the product performs according to specification
and all internal components have been adequately exercised. This approach is called
“WHITE BOX TESTING”.
These approaches provide a mechanism that can help to ensure the completeness of
tests and provide the highest likelihood for uncovering errors in s/w.
The goals of verification and validation are to access and improve the quality of work
products generated during development and modification of s/w. These are 2 types of
verification namely.
1.

Life-cycle verification

2.

Formal verification.

Validation is the process of evaluating s/w at the end of s/w development process.
Quality assurance is a planned and systematic pattern of action necessary to provide

adequate confirms to the technical requirement.
Walkthroughs are sessions where the material being examined is examined is
presented by a review and evaluated by a team of reviewers.
Inspection involves assessing the s/w life cycle and improving the quality of work
products.
Life-cycle verification is the process of determining the degree to which the work
products of a given phase of the development cycle fulfill the specification established during
prior phases.
Formal verification is a rigorous mathematical demonstration that source code
confirms to its specification.
High quality can be achieved through testing of source code alone.
Although a program should be totally free of errors, this seldom the case for large s/w
products. There are 3 major categories of s/w error.
1.

Requirement errors

2.

Design errors

3.

Implementation errors
Quality assurance defines the objective of the project and reviews the overall

activities so that the errors are corrected early in the development process.
During analysis and design, an s/w verification plan and acceptance test plan is
prepared. The verification plan describes the methods to be used in verifying that the
requirements are satisfied by the design documents and that the source is consistent with the
requirements specification and design documents. The acceptance test plan includes test
cases, outcomes and capabilities demonstrated by each test case. Following completion of the
verification plan and
Acceptance plan, an s/w verification review is held to evaluate the adequacy of the plans.
During product evolution, in-process audits are conducted to verify consistency and
completeness of the work products. Items to be audited for consistency include interface
specification for hardware and software and people: internal design verses functional

requirements verses test descriptions.
Prior to product delivery, a functional audit and a physical audit performed. The functional
audit reconfirms that all the requirements have been met. The physical audit verifies that the
source code and all associated documents are complete, consistent with one another and
ready to deliver. An s/w verification summary is prepared to describe the results of all
reviews.

8.2 SYSTEM TESTING
A system is tested for online responses, volume of transactions, stress, recovery from
failure and usability. System testing involves two kinds of activities-integration testing and
acceptance testing.
ACCEPTANCE TESTING
It involves planning and execution of functional tests and stress tests in order to
demonstrate that the implemented system satisfies its requirements.
Tools to special importance during acceptance testing include:
4.

Testing

COVERAGE

ANALYZER-RECORDS

THE

CONTROL

PATHS

FOLLOWED FOR EACH TEST USER.
5.

TRIMING ANALYZER-also calls a profiler, reports the time spent in various regions

of the code are areas to concentrate on to improve system performance.
6.

Coding standards-static analyzer and standard checkers are used to insert code for

deviations from standard and guidelines.
ALPHA and BETA TESTING
If s/w is developed as product to be used by many customers, it is impractical to
perform formal acceptance test with each one. So, one most developers use Alpha and Beta
testing to uncover that only the end user seems able to find.
Alpha testing is conducted by the customer in the presence of many project leaders
and recorded the errors and usage problems what they faced.
Beta testing is conducted at customer site by the end users of the s/w, the customer
recorded that encountered during beta testing and sent those problems to us regular intervals.
Then we made the modification and released to the entire customer base.

8.3 DISCUSSION AND RESULTS
HOME PAGE

This is the home page where all the modules will be directed to their login page.

WELCOME CLIENT

This is Client login page.

BDO LOGIN

This page is used by Business Development Officer to login to his own page.

BDO HOME

In this page BDO schedules his clients status.

DEVELOPER LOGIN

This is developer login page.

DEVELOPER HOME PAGE

This is developer home page.

VIEW TIME SHEET:

This page is used to view time sheet.

PROJECT STATUS:

This page is used to know the project status.

PM LOGIN SCREEN:

This is project manager login page.

PM HOME PAGE:

This is project manager home page to know the status of project.

HR LOGIN SCREEN:

This is project manager home page to know the status of project.

HR HOME PAGE:

This page shows human resource home page.

9. CONCLUSION
All the objectives that had been charted out in the initial phases were achieved
successfully.
System Features:
System satisfies all the requirements for which the company developed the system.
System has strong security. System is fully GUI based. It is easy operate and user friendly.
Platform includes the inbuilt backup and recovery facility.
Working on the project was a good experience. Working together in teams helped
us to communicate better. We understand the importance of planning and designing as a part
of software development.
The concept of peer-reviews helped to rectify the problems as and when they
occurred and also helped us to get some valuable suggestions that were incorporated by us.
Developing the project has helped us to gain some experienced on real time development
procedures.
9.1 SUGGESTION FOR FURTHER DEVELOPMENT
System required sufficient RAM and faster server to run the application properly.

10. REFERENCES

C# .NET

:

C# .NET Unleashed

SQL Server 2000

:

SQL Unleashed

ASP.Net

:

ASP.Net Unleashed

http://www.msdn.Microsoft.com/webservices

SOFTWARE PROJECT MANAGEMENT TOOL Project Report

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to SOFTWARE PROJECT MANAGEMENT TOOL Project Report (20)

Recently uploaded (20)

SOFTWARE PROJECT MANAGEMENT TOOL Project Report