50409621013-t.kandhan-project issue and monitoring management

7/28/2019 50409621013-t.kandhan-project Issue and Monitoring Management

1/101

PROJECT ISSUE AND

MONITORING MANAGEMENT

By

KANDHAN T

50409621013

Under the Guidance

Of

Mr.D.SUDHAGAR,M.C.A.,M.Phil.,M.E.,

Senior Lecturer Of MCA

ARUNAI ENGINEERING COLLEGE

A PROJECT REPORT

Submitted to the

FACULTY OF INFORMATION AND COMMUNICATION

ENGINEERING

In partial fulfillment of the requirements

for the award of the degree

Of

MASTER OF COMPUTER APPLICATIONS

June 2012


2/101

BONAFIDE CERTIFICATE

Certified that this project report titled PROJECT ISSUE AND MONITORING

MANAGEMENT , is the bona fide work of KANDHAN T, having Register Number

50409621013, who carried out under my supervision and guidance. Certified further, that to the

best of my knowledge that the work reported herein does not form part of any other project

report or dissertation on the basis of which a degree or award was conferred on an earlier

occasion on this or any other candidate.

Dr.A.Saravanan., M.C.A., Ph.D

Internal Guide Head of the Department

Submitted to the Project Viva Voce Examination held on ____________

Internal Examiner External Examiner


3/101

i

ACKNOWLEDGEMENTS

I thank the almighty God for giving physical mental strength and ability for the effective

completion of this project.

I take this opportunity to express my deep sense of gratitude and respectiful regards to

our esteemed Chairman Mr.E.V.Velu M.A, honorable vice chairman Mr.E.V.V.Kumaran M.E

for various facilities provided to me. I dedicate my sincere thanks on this occasion to our

respected Principal Dr.K.Mohanavelu Ph.D

I thankful to our respected Head of Departmen Dr.A.Saravanan, M.C.A.,Ph.D and

Internal guide Mr.D.SUDHAGAR,M.C.A.,M.Phil.,M.E., Department of MCA ARUNAI

Engineering College, Tiruvannamalai for his consistent encouragement during the project work.

His motivation helped me to achieve great things, during the course of study.

Finally with great enthusiasm I express my thanks to all my department lectures for

providing necessary information and their sustained interest in my part of truthful completion

KANDHAN T


4/101

ii

ABSTRACT

Project management is a methodical approach to planning and guiding project

processes from start to finish. According to the Project Management Institute, the

processes are guided through five stages: Initiation, Planning, Executing, Controlling and

Closing. Project management can be applied to almost any type of project and is widely

used to control the complex processes of software development.

The main aim of the project describes Project details as well as Employee details who

are involved in the Project. It also keeps track of the Project planning such as total no the

modules, man power, cost efficiency, duration, software and hardware requirements. And

records the employee details such as id, name, platform, designation etc,

The administrator has the provision for assigning project module to the employees.

An Admin is responsible person for assigning Start date and end date for the module

completion. If there is any delay in completing the assigned module within the period then

the Issue module keeps track of the reason for delay of completion and the actual

completion date of the module.

If there is any need to send mail to some one then the mail composer module is used.

Using the mail composer module the communication between the admin and

employees and also between the employees is made simpler.


5/101

iii

CONTENTS

LIST OF FIGURES

FIGURE NO FIGURE NAME PAGE NO

CHAPTER

NO

TITLE PAGE NO

ABSTRACT Ii

1 INTRODUCTION TO PROJECT AREA 1

2 LITERATURE SURVEY ON THE PROJECT 3

3 NEED OF THE SYSTEM 16

4 SYSTEM ANALYSIS 18

4.1 PROBLEM DESCRIPTION 18

4.2 SOFTWARE & HARDWARE REQUIREMENTS 22

4.3 EXISTING SYSTEM 23

4.4 PROPOSED SYSTEM 29

5 SYSTEM DESIGN 32

5.1 SYSTEM FLOW DIAGRAM 32

5.2 DATA FLOW DIAGTRAM 33

6 SYSTEM IMPLEMENTATION 42

7 SYSTEM TESTING 46

8 BENEFITS OF THIS PROJECT 57

9 INPUT & OUTPUT SCREENS 62

10 SCOPE FOR FURTHER DEVELOPMENT 91

11 CONCLUSION 92

12 REFERENCES 93


6/101

iv

5.1 5.1 System Flow Architectural Design 32

5.2 Level 0 DFD for Project Definition 33

5.3 Level 1 DFD for Module Definition 34

5.4 Level 2 DFD for Employee Definition 35

5.5 Level 3 DFD for Employee Allotment 36


7/101

1

CHAPTER 1

INTRODUCTION TO PROJECT AREA

Any IT organization needs its own system for tracking various tasks. This project is

a web application which tracks various tasks of Cert Technology.

Objective and Goal

The objective of this system development is to develop a web based Application to

automate certain activities of the client organization. The primary Goal is to provide ease in

administration and audit.

Application

The system to be developed aims to provide a good service to the clients organization.

Purpose

The system aims in providing automated support for the entire organizational needs.

Scope

The scope of the project is to develop a web Application. This system maintains all thedetails regarding the projects


8/101

2

Problem Definition

The project aimed to be developed is to manage certain activitiesin the organization or

company. The proposed system is an enhancement over the existing system .It should

provide the support for maintaining details like project details ,employee details ,client

details which are done manually.

The existing system consists of Dynamic pages where the user(Employee) can

interact with the system by filling forms with associate details It should provide the

support for maintaining details client-details ,Employee-details, module-details, issue-

details, project-details which are done manually.


9/101

3

CHAPTER 2

LITERATURE SURVEY ON THE PROJECT

Purpose

Assist the Survey Research Coordinator or Project Leader in planning,

implementing, andoverseeing research and evaluation projects, as well as provide data

management, data analysis, reportwriting, and presentation of results for various projects.

Project Development:

Participate in tasks related to the development phase of new MPHI projects, including:

Identify funding opportunities;

Participate in project development teams and meetings;

Prepare literature reviews; and

Assist in the production of project outlines, proposals, work plans, and budgets.

Survey Research:

Assist the Survey Research Coordinator in the design and implementation of survey

research projects, including:

Participate in administrative duties of the unit, including recruitment and training of data

collection personnel, implementation of project work plans, timelines, and human subjects

documents and other documentation of project activities;

Participate in the design of research projects, including the development of survey instruments,

protocols, sample tracking systems, and training materials;

Conduct sample management activities such as loading, tracking and reviewing respondent

information;


10/101

4

Supervise the implementation of data collection and data management systems; supervise

survey shifts and provide feedback to data collection staff and shift leaders as needed;

Review and enter survey interviewer and shift leader timesheets;

Develop administrative systems to facilitate the efficiency of operations and ensure quality of

data-related services, including testing CATI survey programming, reviewing call information

sheets and editing and verifying survey data;

Provide daily verbal progress reports on project activities to the Survey Research Coordinator;

and

Provide data analyses and report production for projects.

GIS Research:

Assist the GIS Lab Coordinator in the design and implementation of GIS research projects,

including:

Participate in research design and implementation, including the construction of base maps

,geocoding, linking data tables, and data analysis;

Participate in reporting, including developing maps and associated data tables for publication

and report writing MPHI is an Affirmative Action/Equal Opportunity Employer Research

Associate SRU PD revised 3.10.08 Page 2of 2

Attend training as needed; and

Provide daily verbal progress reports on project activities to the GIS Lab Coordinator.


11/101

5

Program Evaluation:

Participation in instrument development, data collection, management, and analysis;

Participate in fulfillment of all project reporting requirements, including, but not limited to,project quarterly reports, annual reports, final reports and development of presentations;

Serve as a contact with principal investigators, advisory groups, project partners, clients and

community agencies; and

Represent CHE and MPHI in dissemination activities including conferences, publications, and

committees.

Administration and Communication:

Maintain good communication with data collection staff, clients, project partners and

coworkers;

Function as a representative of CHE as a member on various MPHI committees;

Maintain a positive, strong, credible, professional and interpersonal relationship with all parties

relevant to CHE projects, and represent the best interests of MPHI at all times; and

Perform other duties as required.

Important Skills and Characteristics:

This position requires strong organizational and problem solving skills, which includes

the abilityto manage multiple tasks and respond to multiple demands. Must have effective

written and oral communication skills, as well as the ability to network and collaborate with

funding agencies, advisory groups, program staff, and individuals of diverse backgrounds. Skill

in research and evaluation design and data management and analysis are important. Must be

proficient in using


12/101

6

computers and computer software (e.g. Excel, Access, SPSS, Word, PowerPoint). Experience in

statistical analysis, telephone survey methods, SPSS, CATI software, and GIS software

preferred. Ability to plan, coordinate and provide formal training in survey methods. Qualified

candidate must have the ability to work both independently and as a member of a team. Must be

able to

work with minimal supervision. Position requires flexible and analytic thinking as well as

excellent interpersonal skills. Experience in supervising others is preferred.

RESPONSIBILITY FOR THE WORK OF OTHERS

Occasional Leader:

Occasional leaders lead some projects and serve as a team member on others.

IMPACT ON PROJECTS, SERVICES AND OPERATIONS

The person in this position assists the Survey Research Coordinator in the development

ofprojects and conducts project activities. The effective implementation of these duties

contributesto timely and satisfactory completion of projects, enhances the development of CHE

projects, andenhances the reputation of MPHI.


13/101

7

REQUIRED COMMUNICATION

Contact Person/Group Frequency Purpose

1. Survey research coordinator Daily Receive supervision, project work assignments

2. GIS lab coordinator Daily Receive supervision, project work assignments

3. Project coordinator/Project leader Daily Receive supervision, project work assignments

4. Program Director Weekly-Daily Receive supervision, project work assignments

5. Research Associate Daily Share info

6. Shift leaders/Research asst. Daily Provide supervision, assign tasks

7. Data collection staff Daily Provide supervision, assign tasks

8. Clients & partners Weekly-Daily Updates, planning, problem-solving

9. Survey participants As needed Gather information, explain projects

"For purposes of employment standards, this classification is "exempt" from overtime provisions

of theFair Labor Standards Act."


14/101

8

Software traceability

That is the ability to relate artefacts which are created during the

development of a software system (e.g. requirements, design and code artefacts) with each

other,the stakeholders that created them, and/or the rationale underpinning their exact form has

beenrecognised as a significant capability in the software development and maintenance process,

and asan important factor for the quality of the final product.

Traceability information can be used to support the analysis of the implications and

integration ofchanges requested in the system development process; the maintenance and

evolution of softwaresystems and documentation; the reuse of software systems and their

components; and theinspection and testing of software systems.

The software and system engineering communities have long standing interests in the

area oftraceability and have developed numerous approaches and techniques to establish and

maintaintraceability. More specifically, research in this area has been mainly concerned with the

study anddefinition of different types of traceability relations; the generation of these relations;

thedevelopment of architectures, tools, and environments for managing traceability information;

andthe empirical investigation of organisational practices regarding the establishment and

deploymentof traceability information in the software development life cycle.

In this tutorial, we present an overview of the state of the art and practice in software

traceability,discuss the main scientific and technological advances in this area, present the

availabletechnologies and their contributions, and identify issues that require further research in

the field.

The tutorial is intended for practitioners, managers, researchers, and teachers with

interests insoftware development and the management of software systems and development

processes. Thetutorial may also be attended by students that follow a university programme in

computing at alllevels


15/101

9

Engaging with new stakeholders for disruptive innovation: Radical Transactiveness and

management of risk

Making these possibilities a reality on a large enough scale to make a significant

contribution to pro-poor development will require a conscious effort to mainstream very different

practices throughout the business decision-making process. In some cases change can partly rely

on the basis of ethics and morality itself, and compliance with corporate codes of conduct, on the

assumption that not all TNE managers are as bad or as Machiavellian as they are often painted.

Change can also be argued partly on the basis that modern management Best Practice

increasingly emphasises the importance not only of flexible working, but crucially of creativity,

innovation and flexibility. Recent approaches to business creativity focus on the importance ofincreased employee diversity, lateral thinking, and conventional R&D and technology

management. In the wake of high profile corporate scandals like Enron the recent concept of

Radical transparency involves going beyond statutory accounting requirements to a full and

open disclosure of the firms current activities, strategies, and impacts. This has become

increasingly important to maintain general business confidence.

The organisers of the 2004 BoP workshop go even further that Nelson and Prescott to assert

that innovation is not only possible, but increasingly an imperative. Data from US indicates

acceleration in turnover of firms. It is argued that enterprise survival and competitive advantage

in the fast changing world cannot rely on lowering cost or differentiation in existing industries

and businesses. Future competitive advantage will increasingly depend on the capacity for

exploration, disruptive innovation, creative destruction, and corporate imagination. More rad-

ical innovations will allow firms to reap higher profits due to longer competitor response times.

What is needed is a new capability focused on engaging the stakeholders necessary for

managing disruptive change and creating competitive imagination.


16/101

10

Base of pyramid draft protocol Code of Conduct

The BOP Protocol is a process-based framework by which a corporation can acquire a

deep understanding of local needs and perspectives and then develop sustainable business

models in partnership with BoP communities. The Protocol, which is written from the

perspective of the corporation, is divided into three interdependent phases, each with specific

business outcomes:

Opening Up Launch non-business specific immersion guided by two-way dialogue and

humility to co-identify local needs, capabilities and business opportunities

Building the Ecosystem Generate a diverse network of partners to advance ideas for mutual

value creation and to support the co-creation of a business plan

Enterprise Creation Formalize a business venture by pilot testing, evaluating, and scaling-out

business experiments that generate triple-bottom-line value for all constituencies

BOP DRAFT CODE OF CONDUCT

Design businesses that increase earning power, remove constraints, and build potential in

the BoPEnsure that wealth generated by the business is shared equitably with the local

community Utilize only the most appropriate and sustainable technologiesPromote the

development of affected communities as broadly as possibly in ways that defined by local

people themselves.

Track the triple bottom line impacts associated with the entire BoP business system.

Monitor and address any unintended negative impacts associated with the business

model.

Share best practices with local partners to the extent possible.

Report transparently and involve key stakeholders in on-going dialogue.

Commit to increase community value regardless of the business outcome.


17/101

11

Such innovation moreover requires engagement of new stakeholders. Conventional

management stakeholder analysis focuses on groups that are critical to the firms survival in its

current business: investors, employees, customers, suppliers, and the government, and others

whose claims are considered powerful, urgent, and legitimate by managers. By doing so, it is

argued that firms can gain competitive advantages in the form of customer loyalty, supplier

relationships, lower employee turnover, and improved reputation. Radical Transparency is

targeted primarily at managing core stakeholdersthose who can directly affect the current

business by virtue of their power, urgency, or salience.

Hart and Sharma however go even further to argue for Radical Transactiveness (RT) by

which TNEs seek new forms of engagement with communities and dialogue with stakeholders

previously considered extreme or fringe. (See Figure 1). Drawing on Robert Chambers Putting

the Last First they argue that stakeholder integration needs to move beyond the static

management of known parties in the center of a network to the dynamic process of identifying

and engaging actors from the fringe.: the poor, weak, isolated, non-legitimate, disinterested,

and even non-human (See Figure 2). The RT framework proposes that firms should fan out to

identify these fringe stakeholders by following the linkages of existing stakeholder networks to

the periphery to consciously seek out remote stakeholders that are non-legitimate, non-urgent,

and powerless. These arguments have been further reinforced in a BoP background paper by

Erik Simanis which present a critique of conventional stakeholder analysis in the corporate

sector (Simanis 2004).

The concern with these new stakeholders is partly to avoid stakeholder swarms and avoid

unanticipated conflicts with Internet-connected smart mobs like the attacks on Monsanto and

manage disruptive change. However, it is also seen as necessary for competitive imagination

in identifying and developing new future products, services, markets, and business models.


18/101

12

Radical Transactiveness helps firms cast a wider, more inclusive net in order to to continuously

acquire and combine knowledge from fringe stakeholders with radically differing views. Putting

the last first reverses the logic of the established business and seeks to generate imagination and

ideas about unmet needs, potential new products, and business innovations. The capability of

fanning in requires building the managerial capacity for empathizing with diverse and

disconfirming stakeholder perspectives; understanding the culture, thought processes, and

language of distant stakeholders; and acquiring the capability to reconcile the contradictions

between the existing business model and the views of fringe stakeholders. By generating

complex interactions, firms can develop the intimacy and trust needed for honest two-way

exchange to occur between managers and those on the fringe of the companys established

stakeholder network. Furthermore it is argued that RT not only helps individual enterprises, but

also impacts the macro-level through identification of new strategies for a smarter form of

globalization which seek from the outset to address social and environmental problems.

New trends in market research

The main focus of attention so far has been on TNEs as suppliers of products needed by

very poor people. Participants at the BoP workshop presented a number of examples of changes

and efforts by TNE management to understand and engage with poor communities and produce

products which significantly benefit them. A number of Case Studies are given in Prahalad 2005,

notably developments in soap and detergents which can decrease diarrhoeal infections and which

are marketed with a health message. Other examples can be found from partners in ETI and other

partners in ethical trade.

Some new approaches to market research

Hewlett-Packards Living Lab Established In the village of Kuppam in India to look at

possibilities of information technology and Internet products and services for use by the rural

poor in developing countries.


19/101

13

Unliver Limited

Unilever Head Office has begun adding managers from subsidiaries in low-income

countries to its board of directors and top management committees. This has led to increased

innovation in conventional R&D and product development.

Hindustan Level Limited (ULLUnilevers Indian subsidiary) requires its managers to

spend six weeks living in rural areas to generate knowledge about the hygiene needs and

practices of the rural poor. This knowledge has resulted in new product ideas (such as a

combined soap and shampoo bar) and promotional programs (such as street theatre) for rural

markets. The company has also created a rural R&D center in rural India that focuses specifically

on technology and product development to serve the needs of the poor and sources raw materials

almost exclusively from local producers.

These innovations have also been adopted by Unilever subsidiaries in Brazil and other

developing countries. HLL requires all company employees to spend six weeks living in rural

villages and actively seeking local consumer insights and preferences as they develop new

products. HLL uses a wide variety of local partners to distribute their products and also supports

the efforts of those partners to build additional capabilities. By developing local understanding

and empathy, and experimenting with co-development through new partnerships, HLL has been

able to generate substantial revenues and profits from operating in low-income markets. Indeed,

by the late 1990s, low-income markets represented more than half of HLLs business.

DuPont Biotechnology Advisory Panel

Set up to consciously seek divergent views from a diversity of stakeholders from India,

Africa, and Latin America to help it formulate a more robust strategy for biotechnology

development. The company has purposefully invited environmental advocates such as the former


20/101

14

head of Greenpeace International to provide divergent views on the issue. Exposing senior

managers and business leaders to radically different perspectives has resulted in significant

modifications and improvements to the companys approach to and strategy for biotechnology

commercialization. New ideas have been generated for future business models in accordance

with the companys push to move away from products based upon petrochemical feed stocks and

into knowledge-intensive businesses with a biological base.

Excel Industries

In Excel industries, one of Indias largest chemical companies, managers spend time in

poor villages to generate radical new ideas and innovations. The CEO of Excel Industries asked

his managers to avoid prejudices and biases by stating, Who are you to adopt a village? Go and

be a part of it. Let the village adopt you.

A key part of this change are new trends in market research methodologies which include

Participatory Learning and Action techniques, ethnography, photography and video. New

participatory and qualitative market research tools have been the subject of a number of recent

workshops and conferences like the AboutWithAndFor conference held in November 2004Illinois Institute for Technology. At the BoP workshop a number of examples were given where

the use of qualitative and participatory methods in poor communities had led to both more

reliable information than previously gained through questionnaires and where it had led to new

and profitable products.

However market research on its own is not a solution. Market research to identify

which products poor people can be persuaded to buy (manipulated into buying

through advertising?) at a profit is not the same thing as identifying products from

which they will significantly benefit. Poor people like anyone else can be

manipulated into buying things which are positively harmful (e.g. cigarettes, strong

alcohol, skin-bleaching cosmetics) and are in many senses more vulnerable

because they have less choice, less access to information and are under just as


21/101

15

much pressure to maintain some self-respect through status symbols. Moreover

there are serious dangers that firstly TNEs will be able to use their power to

supplant local producers through advertising, packaging and other forms of

promotion even if their products are not as beneficial and do not employ local

labour on such good terms. Secondly through gathering local knowledge and

expertise they may be stealing local intellectual property rights before local people

are aware of the value and significance of their knowledge.


22/101

16

CHAPTER 3

NEED OF THE SYSTEM

Project reviews carried out at any time during project execution are focused on performing either

a general project management review or a specific project review. The purpose of a general

project management review is to ensure that the:

1. Parameters of a successful project are in place such as strong sponsorship, adequate and

experienced project resources, good project plan with effective project controls, regular

risk management and so on

2. Project objectives, scope and plan are being executed and changes are being controlled

properly

3. Implementation deliverables are on track and those deliverables are of an appropriate

quality

4. Project status is on track and risks and issues are being managed

5. Project reporting is accurate, clear, concise and complete

Specific Project Review

Specific project reviews are used at selected project points to confirm that deliverables are fit for

purpose. This may be done internally by an independent member of the project team or by an

external person. Reviews might include:

Design review to ensure that the design meets the requirements

Quality review to ensure that procedures and documentation are complete and of

the required standard


23/101

17

Compliance review to ensure that the project complies with applicable regulation,

legislation or internally mandated policies

Service readiness review to ensure that technology, processes and procedures are

ready for use


24/101

18

CHAPTER 4

SYSTEM ANALYSIS

4.1 PROBLEM DESCRIPTION

This section specifies the hardware and the software requirements of the System. The

Specification listed is the minimum configuration required for the system to be developed.

The section also consists of a short description about the softwares and the tools

used for the development of the system.

Project management is a methodical approach to planning and guiding project

processes from start to finish. According to the Project Management Institute, the

processes are guided through five stages: Initiation, Planning, Executing, Controlling and

Closing. Project management can be applied to almost any type of project and is widely

used to control the complex processes of software development.

The main aim of the project describes Project details as well as Employee

details who are involved in the Project. It also keeps track of the Project planning such as

total no the modules, man power, cost efficiency, duration, software and hardware

requirements. And records the employee details such as id, name, platform, designation

etc,

The administrator has the provision for assigning project module to the

employees. An Admin is responsible person for assigning Start date and end date for the

module completion. If there is any delay in completing the assigned module within the

period then the Issue module keeps track of the reason for delay of completion and the

actual completion date of the module.


25/101

19

If there is any need to send mail to some one then the mail composer module is

used. Using the mail composer module the communication between the admin and

employees and also between the employees is made simpler.

Home Page:

The home page contains the Title of the project as Project Tracking System

with a Login for the Administrator which as the following Link

o Client-Info

o Employee-Info

o Project-Info

o Issue-Tracker

o Mail-Composer

Employee-Provision:

This is the final module called Employee provision which as some links like:

o Project-list

o Emp-list

o Issue-Info

o Mail-Composer


26/101

20

MODUELS:

Client Information:

This deals with registering the client information for the company with The

following details like Client-Id, Client-Name, Address, Contact Person, Designation

Contact-No, Email-Id etc. This is registration are made by Administrator.

Employee Information:

This deals with registering the employee information for the company which

is done by the Administrator with the following details like Employee-Id, Employee-

Name, DOB, Address, Contact-No, Email-Id, Designation, Platform, User-Name,

Password, Confirm Password.

Project Information:

This deals with registering the project information for the company which is

done by the Administrator with the following details like Client-Id, Project-Id, Name of the

Project, Platform to develop, No of Modules, Period, Starting-date, and Ending-date.

Scheduling Information:

This deals with registering the project scheduling information , which is done

by the Administrator to the employee with the following details like Project-Id, Module

Name, Assigned to whom, No of Days, Starting-date, Ending-date


27/101

21

Project issue Information:

This gives project issue information which is done by the

administrator in the scheduling information and it is stored in the issue

tracker for the Admin to view to know the Current status of the project.


28/101

22

4.2 SOFTWARE & HARDWARE REQUIREMENTS

SYSTEM CONFIGURATION:

4.2.1 Software Configuration

ServerOperatingSystem - Windows2000Server

Client Operating System - Windows XP

Web Server - IIS 5.0 with .Net Framework SDK

Server Side Script - ASP.Net using VB.Net

Markup Languages - HTML

Style Language - CSS

DBMS - MS SQl Server

Web Browser - Microsoft Internet Explorer 6

4.2.2. Hardware Configuration

Main Processor : Pentium 4

Network : Windows Xp

Clock Speed : 133MHZ

Memory RAM : 128MB

Hard Disk Capacity : 20GB

Monitor : Samsung

Floppy Disk Drive : 1.44MB

CD ROM Drive : 52x

Keyboard : 101 Keys


29/101

23

4.3. EXISTING SYSTEM

4.3.1.About ASP.NET

ASP.NET is the latest version of Microsoft's Active Server Pages technology

(ASP).ASP.NET is a part of the Microsoft .NET framework, and it is a powerful tool for

creating a dynamic and interactive web pages.ASP.NET is the latest version of Microsoft's

Active Server Pages technology (ASP).

You should already know

Before you continue you should have a basic understanding of the following:

WWW, HTML and the basics of building Web pages Scripting languages like JavaScript or VBScript

The basics of server side scripting

ASP

ASP is a server side scripting technology that enables scripts (embedded in

web pages) to be executed by an Internet server.

ASP is a Microsoft Technology

ASP stands for Active Server Pages

ASP is a program that runs inside IIS

IIS stands for Internet Information Services

IIS comes as a free component with Windows 2000

IIS is also a part of the Windows NT 4.0 Option Pack

The Option Pack can be downloaded from Microsoft

PWS is a smaller - but fully functional - version of IIS

PWS can be found on your Windows 95/98 CD


30/101

24

ASP File

An ASP file is just the same as an HTML file

An ASP file can contain text, HTML, XML, and scripts

Scripts in an ASP file are executed on the server

An ASP file has the file extension ".asp"

Work of ASP

When a browser requests an HTML file, the server returns the file

When a browser requests an ASP file, IIS passes the request to the ASP engine

The ASP engine reads the file, line by line, and executes the scripts in the file

Finally, the ASP file is returned to the browser as plain HTML

Before you study ASP .NET, it would help to have a basic understanding

of Microsoft's ASP technology.

ASP+

ASP+ is the same as ASP.NET. ASP+ is just an early name used by

Microsoft when they developed ASP.NET.

ASP.NET

ASP 3.0 is the latest version of ASP, but there will never be an ASP 4.0

version.ASP.NET is the next generation ASP, but it's not an upgraded version of ASP.

ASP.NET is an entirely new paradigm for server-side ASP scripting.

ASP.NET is a part of the .NET Framework. Microsoft spent three years

rewriting ASP.NET from the ground up, and ASP.NET is not fully backward compatible

backward compatible with ASP 3.0

ASP .NET has better language support, a large set of new controls are

added and XML based components , and better user authentication. ASP .NET provides


31/101

25

increased performance by running compiled code.ASP .NET code is not fully backward

compatible with ASP.

New in ASP .NET

Better language support

Programmable controls

Event-driven programming

XML-based components

User authentication, with accounts and roles

Higher scalability

Increased performance - Compiled code

Easier configuration and deployment

Not fully ASP compatible

Language Support

ASP .NET uses the new ADO .NET.

ASP .NET supports full Visual Basic, not VBScript.

ASP .NET supports C# (C sharp) and C++.

ASP .NET supports JScript as before.

ASP .NET Controls

ASP.NET contains a large set of HTML controls. Almost all HTML

elements on a page can be defined as ASP.NET control objects that can be controlled by

scripts. ASP .NET also contains a new set of object oriented input controls are, like

programmable list boxes and validation controls.


32/101

26

Event Aware Controls

All ASP .NET objects on a Web page can expose events that can be

processed by ASP .NET code. Load, Click and Change events handled by code makes

coding much simpler and much better organized.

ASP .NET Components

ASP.NET components are heavily based on XML. Like new AD

Rotator, that uses XML to store advertisement information and configuration.

User Authentication

ASP .NET supports forms-based user authentication, including cookie

management and automatic redirecting of unauthorized logins.

User Accounts and Roles

ASP .NET allows for user accounts and roles, to give each user (with a

given role) access to different server code and executables.

High Scalability

Much has been done with ASP .NET to provide greater scalability. Server to

server communication has been greatly enhanced, make it possible to scale an application

over several servers. One example is this is the ability to run XML parsers, XSL

transformations and even resource hungry session objects on other servers.

Compiled Code

The first request for an ASP .NET page on the server will compile the ASP

.NET code and keep a cached copy in memory. The result of this is greatly increasedperformance.

4.3.2. About VB.NET

.NET is a clean break away from the last decade of Visual Basic.


33/101

27

you're new to Visual Basic, or if you want to make the step up to technology, you will

find tutorials here from ADO.NET to VS.NET

VB.NET has made it possible for whole new categories of various

nternet applications (such as Web services implemented with UDDI,SOAP)

become available. Most of these are programmed using XML.

The first version of Visual Basic, released in May of 1991, was revolutionary

because it gave people the ability to create Windows programs easily and quickly for the

first time. Before Visual Basic, Windows programs were normally written using the

complicated syntax of C++. It as a tricky job for even the most experienced programmers.

Programmers have learned to rely on the "version 2.0" rule over the

years. he rule states that you should generally depend on version2.0 of any really new

product, because it will take that long to work the bugs out and decide whether version 1.0

is actually going to succeed. This has certainly been the case with the .NET Framework

because version 2.0, released in November 2005, completely replaces version 1.0. Visual

Basic 2005 is a "version 2.0" product.

Visual Basic has always been a flagship language for Microsoft and this

didn't change. Visual Basic .NET 1.0 remained a featured language for Microsoft

development in the new .NET world although the new languages, J# and C# were announced

at the same time.

4.3.3. Sql Server

Microsoft SQL Server is a relational database management system (RDBMS)

produced by Microsoft. the code base for Microsoft SQL Server originated in Sybase SQL

Server and was Microsofts entry to the enterprise-level database market, competing

against Oracle, IBM, and later, Sybase itself .SQL server 7.0 was the first true GUI based


34/101

28

database server. A variant of SQL server 2000 was the first commercial database for the

Intel IA64 architecture.

MS SQL server uses a variant of AQL called T-SQL ,or TRANSACTSQL, t-sql

mainly adds additional syntax for us in stored procedures , and affects the syntax of

transaction support.


35/101


36/101

30

Also known as Requirement Analysis. Once the general requirements are gleaned from

the client, an analysis of the scope of the development should be determined and clearly stated.

This is often called a scope document. Certain functionality may be out of scope of the project as

a function of cost or as a result of unclear requirements at the start of development. If the

development is done externally, this document can be considered a legal document so that if

there are ever disputes, any ambiguity of what was promised to the client can be clarified.

Specification

Specification is the task of precisely describing the software to be written, possibly in a

rigorous way. In practice, most successful specifications are written to understand and fine-tune

applications that were already well-developed, although safety-critical software systems are

often carefully specified prior to application development. Specifications are most important for

external interfaces that must remain stable. A good way to determine whether the specifications

are sufficiently precise is to have a third party review the documents making sure that the

requirements are logically sound.

Software architecture

The architecture of a software system refers to an abstract representation of that system.

Architecture is concerned with making sure the software system will meet the requirements of

the product, as well as ensuring that future requirements can be addressed. The architecture step

also addresses interfaces between the software system and other software products, as well as the

underlying hardware or the host operating system.

Stakeholder issues

Users don't understand what they want or users don't have a clear idea of their

requirements

Users won't commit to a set of written requirements

Users insist on new requirements after the cost and schedule have been fixed.
http://en.wikipedia.org/wiki/Program_specificationhttp://en.wikipedia.org/wiki/Software_architecturehttp://en.wikipedia.org/wiki/Program_specificationhttp://en.wikipedia.org/wiki/Software_architecture


37/101

31

Communication with users is slow

Users often do not participate in reviews or are incapable of doing so.

Users are technically unsophisticated

Users don't understand the development process.

Users don't know about present technology.

This may lead to the situation where user requirements keep changing even when system or

product development has been started.

Engineer/developer issues

Possible problems caused by engineers and developers during requirements analysis are:

Technical personnel and end users may have different vocabularies. Consequently, they

may wrongly believe they are in perfect agreement until the finished product is supplied.

Engineers and developers may try to make the requirements fit an existing system or

model, rather than develop a system specific to the needs of the client.

Analysis may often be carried out by engineers or programmers, rather than personnel

with the people skills and the domain knowledge to understand a client's needs properly.


38/101

32

CHAPTER 5

SYSTEM DESIGN

5.1. SYSTEM FLOW DIAGRAM

5.1 System Flow Architectural Design

P

R

O

J

EC

T

T

R

A

C

K

I

N

Home Page Administrator

Login

Project Details

Client-

Info

Employee-

Info

Project-

Info

Module-

Info

Mail-

Composer


39/101

33

5.2. DATA FLOW DIAGRAM

5.2 Level 0 DFD for Project Definition:

Defines Following

Defining Data

Project

Data get Stored

In the following table

Administra Defining

Projec

t

Pro ect

Project

Start &End

Employee

login

Employee-

provision

Project

-List

Employee-

List

Project-

info

Mail-

Composer


40/101

34

Project-Master

5.3 Level 1 DFD for Module Definition:

Enters Following

Defining Module Details

Module

Administrator Defining

Module

Module Id

Module

Description


41/101

35

Data get stored in the

Following table

Module-Master

5.4 Level 2 DFD for Employee Definition:

Defining

Employees Defines Following

Employee details

Start &End

Administrator Defining

Employ

ees

Employee Id

Employee Name Role


42/101

36

Employee Details gets

Stored in the following

Table

Employee-Master

5.5 Level 3 DFD for Employee Allotment:

Alloting of Employees Passes the Requirement

Based on skill

Employee VS Skill

Module

Vs Skill

Yes

HR Department

Employee

Allotment

Verify

Employee

s


43/101

37

Scheduling

Details

Yes

Employe

e

Availabl

e

Employee

Alloted


44/101

38

DATABASE DESIGN

1. Login Table:

Admin-login Text

Admin-password Text

2. ClientTable:

Client-Id N Number

Client-Name Text

Address Text

Contact-Person Text

Designation Text

Contact-No Number

Email-id Text

3. EmployeeTable:


45/101

39

Emp-Id Number

Emp-Name Text

Date-of-Birth Number

Address Text

Contact-No Number

Email-id Text

Designation Text

User-Name Text

Password Text


46/101

40

4. Project-Info Table:

Client-Id Number

Project-Id Number

Name of the project Text

Platform to develop Text

No of Modules Number

Period Number

Starting-date Number

Ending-date Number

5. Module-Info Table:

Project-Id Number

Module-Name Text

Assigned-to Text

No-0f-days Number


Ending-date Number

6. Issue-Info Table:

Choose user-id Number

Name of the project Text


47/101

41

Module-Name Text

Assigned Text


Ending-date Number

Completed-date Number

Reasons Text

Issue Text

SCREEN DESIGN

The screens designed here are


48/101

42

Administrator. aspx

Client-info .aspx

Employee-info.aspx

Project-info.aspx

Module-info.aspx

Issue-info.aspx

Issuetracker.aspx

Compose.aspx

Inbox.aspx

All the above mentioned screens are designed for saving, showing the retrieved details.

CHAPTER 6

SYSTEM IMPLEMENTATION

OVERVIEW OF IMPLEMENTATION


49/101

43

This is the part of the process where computer scientists actually program the code for the

project.

Online project marketing helps the users for purchasing the projects. This project

allows both the users (i.e.,) company and site person from companies will access this

particular process as a company user.

Person other than the above said process will access this procedure as a site user. If he

wants to purchase particular project. He should register in the online project marketing website

otherwise he cannot purchase projects from it.

The main feature of this project provides facility to buy the products easily. This project

is developed using ASP.NET as front-end and MS_SQL as backend.

Implementation is the realization of an application, or execution of a plan, idea, model, design,

specification,standard, algorithm, orpolicy.

In computer science, an implementation is a realization of a technical specification or algorithm

as a program, software component, or other computer system. Many implementations may exist for a given

specification or standard. For example, web browsers contain implementations ofWorld Wide Web Consortium-

recommended specifications, and software development tools contain implementations of

programming languages.

In the IT Industry, implementation refers to post-sales process of guiding a client from

purchase to use of the software or hardware that was purchased. This includes Requirements

Analysis, Scope Analysis, Customizations, Systems Integrations, User Policies, User Training

and Delivery. These steps are often overseen by a Project Manager using Project Management

Methodologies set forth in the Project Management Body of Knowledge. Software

Implementations involve several professionals that are relatively new to the knowledge based

economy such as Business Analysts, Technical Analysts, Solutions Architects, and Project

Managers.

In political science, implementation refers to the carrying out of public policy. Legislatures pass

laws that are then carried out by public servantsworking in bureaucratic agencies. This process consists
http://en.wikipedia.org/wiki/Planhttp://en.wikipedia.org/wiki/Modelhttp://en.wikipedia.org/wiki/Designhttp://en.wikipedia.org/wiki/Specificationhttp://en.wikipedia.org/wiki/Specificationhttp://en.wikipedia.org/wiki/Standardizationhttp://en.wikipedia.org/wiki/Algorithmhttp://en.wikipedia.org/wiki/Policyhttp://en.wikipedia.org/wiki/Computer_sciencehttp://en.wikipedia.org/wiki/Computer_programhttp://en.wikipedia.org/wiki/Software_componenthttp://en.wikipedia.org/wiki/Computer_systemhttp://en.wikipedia.org/wiki/Web_browserhttp://en.wikipedia.org/wiki/World_Wide_Web_Consortiumhttp://en.wikipedia.org/wiki/Programming_languageshttp://en.wikipedia.org/wiki/Political_sciencehttp://en.wikipedia.org/wiki/Political_sciencehttp://en.wikipedia.org/wiki/Public_policyhttp://en.wikipedia.org/wiki/Legislatureshttp://en.wikipedia.org/wiki/Legislatureshttp://en.wikipedia.org/wiki/Public_servantshttp://en.wikipedia.org/wiki/Public_servantshttp://en.wikipedia.org/w/index.php?title=Bureaucratic_agencies&action=edit&redlink=1http://en.wikipedia.org/wiki/Planhttp://en.wikipedia.org/wiki/Modelhttp://en.wikipedia.org/wiki/Designhttp://en.wikipedia.org/wiki/Specificationhttp://en.wikipedia.org/wiki/Standardizationhttp://en.wikipedia.org/wiki/Algorithmhttp://en.wikipedia.org/wiki/Policyhttp://en.wikipedia.org/wiki/Computer_sciencehttp://en.wikipedia.org/wiki/Computer_programhttp://en.wikipedia.org/wiki/Software_componenthttp://en.wikipedia.org/wiki/Computer_systemhttp://en.wikipedia.org/wiki/Web_browserhttp://en.wikipedia.org/wiki/World_Wide_Web_Consortiumhttp://en.wikipedia.org/wiki/Programming_languageshttp://en.wikipedia.org/wiki/Political_sciencehttp://en.wikipedia.org/wiki/Public_policyhttp://en.wikipedia.org/wiki/Legislatureshttp://en.wikipedia.org/wiki/Public_servantshttp://en.wikipedia.org/w/index.php?title=Bureaucratic_agencies&action=edit&redlink=1


50/101

44

of rule-making, rule-administration and rule-adjudication. Factors impacting implementation

include the legislative intent, the administrative capacity of the implementing bureaucracy,

interest group activity and opposition, and presidential or executive support.

TYPES OF IMPLEMENTATION

iPower

Phased

Big Bang (financial markets) / Direct Changeover

Hot Standby

Parallel Running

Pilot Introduction

Project Planning

The purpose of project planning is to identify the scope of the project, estimate the work

involved, and create a project schedule. Project planning begins with requirements that define the

software to be developed. The project plan is then developed to describe the tasks that will lead

to completion.

Project monitoring and control

The purpose of project monitoring and control is to keep the team and management up to

date on the project's progress. If the project deviates from the plan, then the project manager can

take action to correct the problem. Project monitoring and control involves status meetings to

gather status from the team. When changes need to be made, change control is used to keep the

products up to date.

Software requirements

Requirements analysis is a term used to describe all the tasks that go into the instigation,

scoping and definition of a new or altered computer system. Requirements analysis is an

important part of the software engineering process; whereby business analysts or software
http://en.wikipedia.org/w/index.php?title=IPower&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Phased&action=edit&redlink=1http://en.wikipedia.org/wiki/Big_Bang_(financial_markets)http://en.wikipedia.org/w/index.php?title=Direct_Changeover&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Hot_Standby&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Parallel_Running&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Pilot_Introduction&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=IPower&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Phased&action=edit&redlink=1http://en.wikipedia.org/wiki/Big_Bang_(financial_markets)http://en.wikipedia.org/w/index.php?title=Direct_Changeover&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Hot_Standby&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Parallel_Running&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Pilot_Introduction&action=edit&redlink=1


51/101

45

developer identify the needs or requirements of a client; having identified these requirements

they are then in a position to design a solution.

Risk management

Risk management is the process of measuring, or assessing risk and then developing

strategies to manage the risk. In general, the strategies employed include transferring the risk to

another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or

all of the consequences of a particular risk. Traditional risk management, which is discussed

here, focuses on risks stemming from physical or legal causes (e.g. natural disasters or fires,

accidents, death, and lawsuits).

Software process

A software development process is concerned primarily with the production aspect of

software development, as opposed to the technical aspect. These processes exist primarily for

supporting the management of software development, and are generally skewed toward

addressing business concerns.

Problems in software projects

The problems in software projects come from three different viewpoints: project

managers, developers and customers. The problems project managers face include: poor roles

definition, lack of estimating and planning skills, lack of decision making skills. Project

managers do need to face the schedule, budget and quality constraints. The problems developers

face include: lack of knowledge in the application area, lack of knowledge about developing

standards, lack of up to date documentations, deadline pressure, changes of application

requirements. The problems customers face include: monetary constraints, receiving products

past the due date.

IMPLEMENTATION FACTORS

Implementation factors are aspects that have to be taken into account when carrying out

implementation projects. There are five implementation factors in the IMM, these are:


52/101

46

Process

Human Resource

Information

Means

Control

In the optimal situation, an implementation project will strive to create balance and alignment

between the five factors. In other words, an organization should focus on all five aspects when

planning and executing implementation projects.

Once the maturity of the implementation factors has been determined, the overall maturity of

the implementation processes can be determined as well. But before this, it is necessary to

analyze the constituent parts of each of the factors, which are also called the IMM-elements.

CHAPTER 7

SYSTEM TESTING


53/101

47

Testing presents an interesting challenge for the software programmer. In testing, a series

of test cases have been created with intent to demolish the software that has been built. Testing

requires that the software developer discard preconceived notations of the correctness of the

software developed and overcome a conflict of interest that occurs when errors are uncovered.

DIFFERENT TYPES OF TESTING

UNIT TESTING:

In this different test modules are tested against the specification of the modules.

Unit testing was done for the verification of the code produced during the coding phase and to

test the internal logic or modules. It refers to the verification of the single program module in

installed environment.

Unit testing is performed on each program to ensure that the program has been built

according to the program specifications and performs the desired actions.

INTEGRATION TESTING:

In this project the modules are integrated properly, the emphasis being and

testing interfaces between modules .internal and external interfaces are tested as each module is

incorporated into the structure .this test is designed to uncover errors associated with local are

global data structures are conducted . It is also designed to verify performance levels established

during software design are conducted


54/101

48

Thus all these modules are combined , verified and the information about the

items are properly carried on to the next module and then it is checked .

VALIDATION TESTING:

At the culmination of integration testing, software is completely assembled as a

package, interfacing errors have been uncovered and corrected, and a final series of software

tests-validation testing-may begin. Validation can be defined in many ways but a simple

definition is that validation succeeds when software Function in a manner

SYSTEM TESTING

Testing tests a completely integrated system to verify that it meets its requirements

SYSTEM INTEGRATION TESTING:

System integration testing verifies that a system is integrated to any external or third

party systems defined in the system requirements

DATA AND TEST OUTPUT

TEST CASE FOR CLIENT INFORMATION:
http://en.wikipedia.org/wiki/System_testinghttp://en.wikipedia.org/wiki/System_testinghttp://en.wikipedia.org/wiki/System_integration_testinghttp://en.wikipedia.org/wiki/System_integration_testinghttp://en.wikipedia.org/wiki/System_testinghttp://en.wikipedia.org/wiki/System_integration_testinghttp://en.wikipedia.org/wiki/System_integration_testing


55/101

49

Form Name:clientinfo,aspx

Test

case

No

Test case

Description

Test Steps Test

values

Entered

Expected

Results

Actual

Result

Test

Result

Recom

menda

tion

1 Check the

Client_id

Select the

client-id

Valid Accepted Validated Ok

2 Check the

Client name

Enter the

name

Enter

the

values

Accept

the

values

Validated Ok The

Entries

arevalidat

ed

3 Check the

Address

Enter the

address

Enter

the

values

Accept

the

values

Validated Ok

4 Check the

Contact

Person

Enter the

Name

Enter

the

values

Accept

the

values

Validated Ok

5 Check the

Dsignation

Enter the

designation

Enter

the

values

Accept

the

values

Validated Ok The

Entries

are

validated

6 Check the

Contact No

Enter the

Contact no

Enter

the

Accept

the

Validated Ok


56/101

50

values values

7 Check the

Email-id

Enter theemail-id

Enterthe

values

Acceptthe

values

Validated Ok

TEST CASE FOR EMPLOYEE INFORMATION:Form Name:Empinfo,aspx


57/101

51

Test case

Description

Test Steps Test

values

Entered

Expected

Results

Actual

Result

Test

Result

Recome

ndation

1

Check the

Emp_id

Select the

Emp-id


2

Check the

Emp-name

Enter the

Emp-name

Enter

the

values

Accept

the

values

Validated Ok

3

Check the

D-O-B

Enter the d-

o-b

Enter

the

values

Accept

the

values

Validated Ok

4

Check the

Address

Enter the

Address

Enter

the

values

Accept

the

values

Validated Ok

5

Check the

Contact-No

Enter the

Contact no

Enter

the

values

Accept

the

values

Validated Ok

6

Check the

Email-id

Enter the

Email-id

Enter

the

values

Accept

the

values

Validated Ok

The

Entries

are

validated

7

Check the

Designation

Enter the

Designation

Enter

the

values

Accept

the

values

Validated Ok

8

Check the

Platform

Enter the

platform to

develop

Enter

the

values

Accept

the

values

Validated Ok

9

Check the

User-Name

Enter the

User name

Enter

the

values

Accept

the

values

Validated Ok


58/101

52


59/101

53

TEST CASE FOR PROJECT INFORMATION:

Form Name:proj-info.aspx

Test

case

No

Test case

Description

TestSteps

Testvalues

Entered

ExpectedResults

ActualResult

TestResult

Recommendation

1 Check the

Client_id

Select

the

Client-

id


2 Check the

Project-id

Select

the

Proj-id

Enter

the

values

Accepted Validated Ok

3 Check the

Name of

Project

Enter

the

Name

of the

project

Enter

the

values

Accept

the

values

Validated Ok The

Entries are

validated

4 Check the

Platform to

Develop

Enter

the

platform

to

develop

Enter

the

values

Accept

the

values

Validated Ok

5 Check the

No of Modules

Enter

the No

of

modules

Enter

the

values

Accept

the

values

Validated Ok


60/101

54

6 Check the

Period(months)

Enter

the

Period

Enter

the

values

Accept

the

values

Validated Ok

The

Entries are

validated

7 Check the

Strating-date

Enter

the

starting

date

Enter

the

values

Accept

the

values

Validated Ok

8 Check the

Ending-date

Enter

theEnding

date

Enter

thevalues

Accept

thevalues

Validated Ok

TEST CASE FOR MODULE INFORMATION

Form Name:module-info.aspx


61/101

55

Test

case

No

Test case

Description

Test

Steps

Test

values

Entered

Expected

Results

Actual

Result

Test

Result

Recomendation

1 Check theProj_id

Selectthe Proj-

id


2 Check the

Module

name

Enter

the

module

name

Enter

the

values

Accept

the values

Validated Ok

3 Check the

Assigned towhom

Enter

theassigned

person

Enter

thevalues

Accept

the values

Validated Ok

4 Check the

No-of-days

Enter

the No-

of days

Enter

the

values

Accept

the values

Validated Ok The Entries are

validated

5 Check the

Strating-

date

Enter

the

Strating-date

Enter

the

values

Accept

the values

Validated Ok

6 Check the

Ending-date

Enter

the

Ending-

date

Enter

the

values

Accept

the values

Validated Ok

TEST CASE FOR ISSUE INFORMATION

Form Name:issue-info.aspx

Test

case

No

Test case

Description

Test Steps Test

values

Entered

Expected

Results

Actual

Result

Test

Result

Recomendation


62/101

56

1 Check the

Emp_id

Select the

emp id


2 Check the

Name of

the project

Enter the

name of

project

Enter

the

values

Accept

the

values

Validated Ok

3 Check the

Module

name

Enter the

module

name

Enter

the

values

Accept

the

values

Validated Ok The entries are

inserted

4 Check the

Assigned

person

Enter the

person

Enter

the

values

Accept

the

values

Validated Ok

5 Check the

Strating-date

Enter the

Strating-

date

Enter

the

values

Accept

the

values

Validated Ok

6 Check the

Ending-date

Enter the

Ending-

date

Enter

the

values

Accept

the

values

Validated Ok

7

Check the

completed-

date

Enter the

Completed-

Enterthe

values

Acceptthe

values

Validated Ok


63/101

57

Date

8 Check the

reasons

Enter the

reasons

Enter

the

values

Accept

the

values

Validated Ok The entries are

inserted

9 Check the

issue

Enter the

Issue

Enter

the

values

Accept

the

values

Validated Ok

CHAPTER 8

BENEFIT OF THE PROJECT

Benefits for the Entire Enterprise


64/101

58

All project team members stay connected and share information for effective

collaboration, performance and response. Teams are constantly more knowledgeable, which

leads to better decisions and reduced costs.

Benefits by Role

Role

Management Project Office

Tasks

o Select projects

o Define project objectives, constraints

o Monitor portfolio metrics

Benefits

o Key Performance Indicators to align projects with business objectives

o Accurate dashboards to monitor portfolio

o Advanced reporting functions

Role

Project manager

Tasks

o Plan, track projects and budgets

o Assign resources to tasks

o Evaluate and manage risks

Benefits


65/101

59

o Easy visual project planning

o Charts to spot bottlenecks and underutilization of resources

o Capacity planning

o Views and charts to measure real projects success

o Accurate views of project status

o Cost and budget management

o Risk management

Role

Team Worker

Tasks

o Accomplish the planned work

o Raises issues

o Create and update documents

o Fill in timesheet and expense sheets

Benefits

o Collaborative environment

o Personal dashboards to track tasks

o Automatic notifications of assigned documents or tasks, and delays directly in the

mailbox or calendar

o Centralized document management

o Risk or issue creation

o Easy-to-use timesheets


66/101

60

Role

Stakeholders

Tasks

o Stay informed about the projects' progress and expenses

Benefit

o

Access accurate data via Lotus Notes or web browserRole

IT administrator

Tasks

o Easy to install

o No external dependencies on .DLLs, .EXEs and no external database or (ODBC)

connections necessary

o Install the system and upgrades

Benefits

o Scales easily and runs on any of six available Lotus Domino platforms

o Easy to use and manage

o Quick ROI

In Time Tiger, we have designed a time and project tracking system that accurately predicts

project outcome, simplifies project monitoring and removes the pain of submitting time spent.

With Time Tiger you get four key benefits. It is these core values alongside powerful features

such as Supervisor Approval, Microsoft Project integration and a one-click export to Microsoft

Excel that make Time Tiger a key contributor to the success of your projects.


67/101

61

Quick, painless time tracking.

The only way to ensure complete, accurate entry of time information is to make the process

painless for the user. Time Tiger displays an always-available palette of individual tasks and

responsibilities on each user's desktop. All they need to do to track time is to click on the activity

they are currently working on. It sounds simple because it is, and you owe it to your people to

keep their project tracking duties as painless as possible.

One-click snapshot of project health.

Now there is a simple, accurate way of assessing whether or not your projects are on track. You

can select any project, task or sub-task and instantly view its performance against budget and

schedule. Time Tiger uses Earned Value methods, a powerful standard being adopted in the

project management community, to determine project status. With one click you can view a

snapshot of variance to plan and forecasted outcome for any project, task or sub-task on a single

screen. Need to see the details? Earned Value reports display performance over time or detailed

statistics for the time period you select.

Powerful, customizable reporting.

In addition to the pre-formatted reports you would expect from any time tracking system, Time

Tiger includes our simple and powerful Analysis feature. Analysis allows you to slice and dice

your time data to answer almost any real-world question you can come up with. Find out what

percentage of a project's time was spent in each phase, or whether a greater time spent on

planning translates to less time on implementation and support.

The tools to learn from your projects.

As you complete one project and move to the next, Time Tiger will give you the information you

need to plan better, implement better, and learn about how your organization does work. The


68/101

62

combination of accurate time entry (accurate because it is easy), and targeted, powerful reporting

allows you to feed what you've learned from one project cycle into the next, constantly

improving your process with each project you do.

Financial performance:

Projects need to yield a financial return in excess of their weighted average cost of

capital.

Economic performance:

Projects need to generate benefits to society beyond those generated to financiers

of the project, generally an economic rate of return of over 10 percent. Not all benefits are

easily valued in dollar terms, and we equally consider qualitative aspects in this rating.

Environmental and social performance:

Projects have to meet IFCs environmental and social Performance Standards. We

also consider a clients performance improvements in how they manage their environmental

and social performance.

Private sector development impact: projects need to improve the condition of the

private sector, which can be measured, for example, through the number of follow-up

investments by other private sector companies in the sector in which IFC has invested.


69/101

63

CHAPTER 9

INPUT & OUTPUT SCREENS


70/101

64


71/101

65


72/101

66


73/101

67


74/101

68


75/101

69


76/101

70


77/101

71


78/101

72


79/101

73


80/101

74


81/101

75


82/101

76


83/101

77


84/101

78


85/101

79


86/101

80


87/101

81


88/101

82


89/101

83


90/101

84


91/101

85


92/101

86


93/101

87


94/101

88


95/101

89


96/101

90


97/101

91


98/101

92

CHAPTER 10

SCOPE FOR FURTHER DEVELOPMENT

This project Project Tracking systemwas developed for the web browser. It will also

be optimized for the screen solution 1024 x 768.

Any change required in the functional requirements, which is within the scope of

proposal, must be initiated through request. Such request for change will be considered and

assimilated into the deliverables before the commencement of design phase .Changes

requested after the commencement of the design phase will have commercial implication

and additional person-days required to perform the impact analysis, assimilate the changes

in the production of the software.

We will include more advance concepts in this Project Tracking system. It helps

organizations growth, high performance and its popularity. Each module will be designed

with very advanced fields in future. For example present client module not includes the

second person contact name. In future we will include that option .If we include that option

it helps when the first person not available time. It will improve our speed of delivery also

satisfy the client needs as much as possible.

The employee module able to include experience field. It shows the knowledge

for employee in that particular work assignment. So we can easily allocate the work to very

knowledgeable person in on organization. It

also helps to improve sped of work finished in a project. Like this field, we can include

more advanced concepts in this module. Not only this module all the module having that

type of capability. So we are easily include the future enhancement in this project its easy.


99/101

93

CHAPTER 11

CONCLUSION

This Project Issue And Monitoring Management software is much useful for

companies and site users to purchase and view the available projects. Companies and site

users can quote their requirements for the projects to the specified company. It reduces

time loss by traveling directly to the company to purchase the project.

This Project has no boundaries it can be further modified, restructured, updated

etc, So that more valuable and useful features like adding new tables, interfacing with other

design applications can be included.


100/101

94

REFERENCES

1.Guide to Web Application and Platform Architectures

By StafanJablonski, IliaPetrov, Christian Meiler, Udo Mayer

2. Real Web Project Management Case Studies and Best Practices from

the Trenches

By Thomas JShelford, Jeff A Salvage, Gregory A Remillard

3. .NET Compact Framework Pocket Guide

By Wei-Meng Lee

4. Programming Asp.netBy Jesse Liberty, Dan Hurwitz

5. Visual Basic .Net PowerCoding

By Paul Kimmel

6. A Programmers Introduction to Visual Basic .Net

By Craig Utley

7. Python in a Nutshell

By Alex Martelli

8. Programmer .NET Components

9.The State of IT Project Management in the UK - the definitive study,

By ComputerWeekly.com, French Thornton and Templeton College, Oxford.

10.A free project management articles blog from Method 123.

11."The Demise of the Waterfall Model Is Imminent" and Other Urban Myths,

By Phillip A. Laplante and Colin J. Neill, Penn State University. ACM Queue vol. 1,

no. 10, February 2004 Project Management Best Practices (pdf), by Margo Visitacion, Giga

Information Group.

12.The Ethics of Software Project Management, By Donald Gotterbarn and Simon Rogerson,

The Computer Ethics Conference, Linkping University, Sweden, 1997.

13.Project Management, an introduction from the Impact Factory.


101/101

95

14.The Project management proverbs are a source of wisdom-disguised-as-humour. Read them!

15.One Hundred Rules for NASA Project Managers

16.Successful Software Management: 14 Lessons Learned, Johanna Rothman, The Journal of

Defense Software Engineering, December 2003

17.The Software Project Survival Guide, By Construx Software has loads of good advice.

18.A Project Management Primer (pdf), By Nick Jenkins.

19.The Tale of Three Project Managers, By Mike Harding Roberts, HRA Consulting. A subtle

parable

50409621013-t.kandhan-project issue and monitoring management

Documents