team work management system

7/30/2019 Team work management system

1/120

INDEX

Chapter 1 : Introduction 2

Chapter 2 :(a) Literature Survey 6

(b) Outcome 12

Chapter 3 : Problem Formulation & Methodology 17

Chapter 4 : Work Done & Result 40

Data Flow Diagram 46

E-R Diagram 51

Screens 53

Chapter 5 : Conclusion and Future scope 71

Chapter 6 : Bibliography 75

Appendices 77

Coding 77

Team Work Flow System Page 1


2/120

Chapter : 1

INTRODUCTION



3/120

What Is TeamWork?

Teamwork is a joint action by two or more people, in which each person contributes with

different skills and express his or her individual interests and opinions to the unity and efficiency

of the group in order to achieve common goals. This does not mean that the individual is no

longer important; however, it does mean that effective and efficient teamwork goes beyond

individual accomplishments. The most effective teamwork is produced when all the individuals

involved harmonize their contributions and work towards a common goal. + Teamwork Is an old

old wooden ship - - In order for teamwork to succeed one must be a team player. A team player

is one who subordinates personal aspirations and works in a coordinated effort with other

members of a group, or team, in striving for a common goal. Businesses and other organizations

often go to the effort of coordinating team building events in an attempt to get people to work as

a team rather than as individualsThe forming-storming-norming-performing model takes the

team through four stages of team development and maps quite well on to many project

managementlife cycle models, such as initiation - definition - planning - realization. - - As teams

grow larger, the skills and methods that people require grow as more ideas are expressed freely.

Managers must use these to create or maintain a spirit of teamwork change. The intimacy of a

small group is lost, and the opportunity for misinformation and disruptive rumors.

While individual skill and effort in sports is important, teamwork is paramount. Teamwork has

also become increasingly acknowledged as an essential skill for employees in companies both

small and large. Todays increasingly global economy places a premium on teamwork in the

workplace. For companies that often produce goods on one continent and then over a matter of a

few days must transport, store and deliver them to customers on another continent, teamwork is

not just important, it is essential. Teamwork has become so valued that many large corporations

have developed specific tests to measure potential employees teamwork abilities. Many

companies are even acknowledging this in their job titles by changing the designation of

supervisors or managers to team leader.

Teamwork can be more than two people but the importance is working as one. It doesn't matter

whether one like the person or not bringing you talents together can help one rise to their best!

http://en.wikipedia.org/wiki/Project_managementhttp://en.wikipedia.org/wiki/Project_managementhttp://en.wikipedia.org/wiki/Project_managementhttp://en.wikipedia.org/wiki/New_product_developmenthttp://en.wikipedia.org/wiki/Project_managementhttp://en.wikipedia.org/wiki/Project_managementhttp://en.wikipedia.org/wiki/New_product_development


4/120

Teamwork management system

Before building the key components of the application, one has to build the infrastructurefirst. This infrastructure is common in many applications that you will build. Most applications

have to have a user authentication method of some sort. In this application, youll be building a

structure that allows members (the term for users in this application) to be added to any number

of teams. Data in the project, file sharing, and discussion forum systems will all be related to the

teams created by members. The team leader can add and remove members at will. When a

member is added or removed, a message is generated automatically and sent to the member. I

chose to create a separate system for messaging instead of sending the messages to external

email programs. By keeping the messages internal to the system, you could change the web site

to a secure one using SSL (Secure Socket Layer) and provide even better security for the

message being sent.

The application should capture the details of the project, its location and the company. It

must also maintain the employees their specialization along with his pay details. The employees

must be kept track of number of hours they spent on a specific project. It also has the provision

to enter details of the task carried out for that specific project. The application provides for

generation of reports, like total number of hours put in by an employee during a specific period

of time, total number of hours a specific project has taken etc. This software must be designed to

access universally and different higher-level officials from hr and other departments should be

provided with employee performance track. As an add-on for this provide a smart device/pocket

pc application for all these higher-level officials to instantly find the same info from other

applications like excel, pdfs or even with proprietary application. The appraisal process can be

very simple using this application and it even should provide features as Automation, password-

protection, confidentiality and restrictions. In simple terms this should be an application that

combines multiple human resources functions related to appraisal into one package.



5/120

Existing System:

No proper coordination between different Applications and Users.

Cannot Upload and Download the latest updates.

Less Security, Fewer Users - Friendly.

No use of Web Services and Remoting.

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

The development of the new system contains the following activities, which try to automate the

entire process keeping in view of the database integration approach.

It provides high level of security with different level of authentication.

User friendliness is provided in the application with various controls.

The system makes the overall project management much easier and flexible.

There is no risk of data mismanagement at any level while the project development is

under process.

Readily upload the latest updates, allows user to download the alerts by clicking the

URL.



6/120

Chapter : 2

LITERATURE SURVEY & OUTPUT



7/120

Literature Survey

The literatures studied for the purpose of this project include lectures, books and some research

papers. Firstly a research paper By Jaime Herrera S., Expert in human-resource development

and organizational development San Jos, Costa Rica October 2001

The raison d'tre of an organization must be to assure the full satisfaction of its customers

and of everyone within it (employees, suppliers and shareholders).

An organization must be socially responsible and be aware of its role within the concept of

sustainable development. An organization must be a world of continuous learning, intellectual

capital and emotional intelligence, and be highly flexible and responsive so that it can swiftly

adapt to an ever more chaotic, complex and interdependent environment in which change is

increasingly non-linear, discontinuous, unpredictable and even destructive.

An organization must be, then, a system of hearts and minds that function and are driven as one

towards a common goal, a group of people who will work together and learn together and create

synergy both inside and outside the organization.

In reconceiving the future, the following are needed, inter alia:

To create a new customer-centred organizational model based on highly productive processes and

systems run by people to whom the power to act and the responsibility for achieving successful

results have been delegated.

To promote the development of a leadership which, rooted in natural principles and values, will

unleash and democratize creative power and decision-making in the organization and generate

intellectual capital.

The organization of the future has a structure that can be reconfigured so as to make the best use

of teams that are flexible and whose make-up varies over time, in coordination with and as a

consequence of the satisfaction of market needs and expectations, the behaviour of competitors



8/120

and other market factors, the acquisition of essential competencies and the formation of

groupings to provide access to capabilities and resources for those who do not possess them.

It requires teams whose members are drawn from different departments and disciplines and

possess a broad array of knowledge, talent and skills, teams in which open dialogue, acceptance

of ideas, trust, cooperation and creativity predominate.

The managing of processes requires a series of management paradigms for which supervisors are

responsible. The management style must change from one ofcontrol to one ofinstruction and

guidance. There must be a move to the concept of an organization without boundaries.

An organization without boundaries has a structure based on a model that stresses the free

circulation of individuals, information, ideas, processes, tasks and resources of every kind.

The attention of managers and leaders must be focused on how these boundaries can be made

porous, so that ideas, information, capabilities, information, rewards and actions can be deployed

quickly wherever they are most needed.

The boundaries of an organization can be likened to the flexible, permeable membrane of a

living organism in constant evolution.

Learning to solve problems collaboratively, to analyse data and present solutions to peers, and to

work collaboratively is a crucial skill sought by employers.

Distance can be encouraged to work independently and collaboratively in a web-based learning

environment.

Research strongly supports the advantages of cooperative learning over competitive

individualised learning across a range of contexts (McLoughlin 2001). The dialogue and

interaction scaffold cognitive change and understanding is greater compared with learners

working independently. Online communication technology allows students to share information,

divide a task and assign sub-tasks and combine parts for a joint product. Teamwork can be taught

in a progressive way building to complex tasks.



9/120

Teamwork in Healthcare: Promoting Effective Teamwork in Healthcare in Canada

CANADIAN HEALTH SERVICES RESEARCH FOUNDATION

To prepare this report, an interprofessional research team conducted in-depth interviews with key

informants and undertook a wide-ranging survey of peer-reviewed and grey literature on the

components of teamwork; effectiveness of teams; types of interventions; healthcare team

dynamics; and the impact of government infrastructure, legislation, and policy on teamwork in

the Canadian healthcare system. The development of the report was also guided by

Interprofessional Education for Collaborative Patient-Centred Practice: An Evolving

Framework, developed for a 2004 Health Canada initiative on Interprofessional Education for

Collaborative Patient-Centred Practice (IECPCP).

From these sources the team identified the challenges of building and maintaining effective

teamwork. These include the lack of a common definition of teams and teamwork; the

relationship between teamwork and collaboration; the spectrum of collaboration in healthcare;

organizational factors affecting teamwork; and the implications of current policy, regulation,

and legislation on teams.

What can be done? The fundamental change in the healthcare system required to support

teamwork requires a collaborative effort. Leadership and commitment are needed at all levels of

the healthcare system to implement and maintain teamwork over the long term.

A number of projects involving different health providers and patients are going on across the

country and around the world

that we can learn from. For instance, teams work most effectively when they have a clear

purpose; good communication; co-ordination; protocols and procedures; and effective

mechanisms to resolve conflict when it arises. Teams function better when they are working inan organizational culture that supports teamwork and they have strong leadership and effective

administrative support.



10/120

Other studies underscore that the task defines the team, with the make-up and functioning of

teams varying with the patient and the complexity of his or her needs. With this fluidity, health

professionals need training to learn new ways of working together and to become aware of the

roles and responsibilities of all members.

SPECTRUM OF COLLABORATION

A wide range of collaboration can occur depending on the type of care required. While the

concerns of many individuals, families, and communities can be met within the scope of practice

of one profession, when healthcare includes consultation or referral to another professional the

practice shifts to interdependent and interprofessional practices. Generally, higher levels of

collaboration are needed when health needs are complex and individuals receiving care require

the skills of several health professionals. As shown in the diagram below, collaboration among

health professionals is dynamic and occurs within a spectrum from:

Independent parallel practice with autonomous health professionals working side by side

Consultation and referral where health professionals exchange information

Interdependent co-provision of care with interdependent decision-making.

TEN PRINCIPLESOF SUCCESSFUL TEAMS

Ian Morley (1990) has developed 10 principles of teamwork in doing total development

work:

1. Select cohesive teams, based on sentiments of mutual liking and respect for each

others expertise.

2. Bring specialists from all major functional areas into the PDT



11/120

3. Ensure a common vision of the concurrent process.

4. Organize controlled convergence to solutions that everyone understands and everyone

accepts.

5. Organize vigilant information processing and encourage actively open-minded

thinking. Avoid the facile, premature consensus.

6. Maintain the best balance between individual and group work. Let individuals do the

things that individuals do best-for example, the initial generation of new concepts.

7. Use systematic methods.

8. Use formal and informal communication.

9. Select at least some of the members according to how well suited they are to the

specific type of development work. One example is how static or dynamic the

concepts underlying the work are. A person who is proficient in applying standards to

rapidly completed static designs may have difficulty with dynamic conceptual work.

The opposite is also true.

10. Provide principled leadership. The leader must emphasize improved process, making

it visible to the team. He or she must take the primary responsibility for helping to

empower members of the team.



12/120

OUTPUT

After studying all those research papers and the books we came to the following conclusions.It isnot an easy task to change a company's institutional culture, preserve and consolidate worthwhile

values and instil new values among the staff. The group responsible for following up on this

cultural change, which is something any organization must have, has a hard and never-ending

task.

However, this is an issue that affects us all, and so we all must be concerned with seeing the

transformation carried out in the best way possible. WE CAN ALL HELP by doing our bit. If we

set an example, we can have an influence on the rest.

Let us do what we can to ensure that our organization is the best place in the world to work, for

the benefit of the organization itself, for our own sake and for our country. We can do it if we all

pull together!

Teamwork as a concept has grown over the last 20 years. However, teamwork success is not

automatic. Teams have to be established for the right reasons. Team member selection is very

important, as is ensuring that the team purpose is clear and agreed upon.

The nature of our society can create competition between teams. It is a part of our competitive

society. If you think of teams in a sporting context, you immediately think of two competing

teams. That is the way sport is constructed.

Team Organization

Five Possible Roles in Teamwork:

The Administrator is the person who coordinates the team and first shares the project.

The Team Leader is the person responsible for the project.

A Teammate is any team member working on any part of the shared project.



13/120

Mark-up can be served by any of the previous three roles. The Mark-up features

facilitates communication between designers during a project. It allows you to point out

problematic elements with a color highlight or to add new elements intended.

Viewers can access but make no modification of the project.



It provides high level of security with different level of authentication.




under process.

Readily upload the latest updates, allows user to download the alerts by clicking the

URL.

Modules:

1. Teams

2. Projects

3. Tasks

4. Search

5. Admin

6. Reports



14/120

Module Description:

1. Teams

There will be different teams in the project and in each team there should be a project leader, a

project manager and team members. Team leader will add a member into his team or delete a

member from his team at his will.

2. Projects

The project manager should assign projects to the teams, Hr people should add a new project into

the database and project managers should assign a project to the teams.

3. Tasks

Each person (Team leader, project manager, Team member) in the team should have a task such

as for team leader adding and deleting team members at his will and project manager should

assign projects to the teams and he can view reports of team member and team leader.

4. Search

Search option should be provided to search for an employee by his employee id.

5. Admin

Admin can create, modify and delete or otherwise manage the users and.

a) Create: Creates a new user with all the required elements

b) Modify: Modifies an existing user to change its access privileges

c) Delete: Deletes an existing user, where there is no longer any activity.



15/120

6. Reports

Team member should add hourly report, so that team leader can see what he has done in that day.

Team Leader should also add hourly report, so that project manager can view the status of the

project. By seeing both reports project manager should add a daily report, so that they can see the

status of the project.

Privilege of Different Roles

Administrator:

o Allow the signing in of other Team Members.

o Disconnect Team Members.

o Alter other Team Members' passwords.

o Handle the Administrator and Team Leader passwords.

o Define or modify backup options.

Team Leader:

o A physical person (maybe the administrator) or a fictitious person identified by a

password only.

o Modify design standard and convention: project scale, project management tools

like layers and stories, drawing attributes, measurement units, object library and

so on.

Teammate:

o Work in the workspace defined using the standard and convention set by the

Team Leader.

o Workspace: the part of the shared project reserved by a Teammate.

Mark-up:

o Can not create any new elements.

o Only add corrections or highlight elements that need to be checked or modified by

other Teammates.



16/120

Viewer:

o Can open a copy of the project, save as an individual project.

o Modifications made to this copy by the Viewer do not appear in the team project.



17/120

Chapter : 3

PROBLEM FORMULATION & METHODLOGY



18/120

Problem Formulation & Methodology

Problem With The System

The application should capture the details of the project, its location and the company. It

must also maintain the employees their specialization along with his pay details. The employees

must be kept track of number of hours they spent on a specific project. It also has the provision

to enter details of the task carried out for that specific project. The application provides for

generation of reports, like total number of hours put in by an employee during a specific period

of time, total number of hours a specific project has taken etc. This software must be designed to

access universally and different higher-level officials from hr and other departments should be

provided with employee performance track. As an add-on for this provide a smart device/pocket

pc application for all these higher-level officials to instantly find the same info from other

applications like excel, pdfs or even with proprietary application. The appraisal process can be

very simple using this application and it even should provide features as Automation, password-

protection, confidentiality and restrictions. In simple terms this should be an application that

combines multiple human resources functions related to appraisal into one package.

Existing System:

No proper coordination between different Applications and Users.

Cannot Upload and Download the latest updates.

Less Security, Fewer Users - Friendly.

No use of Web Services and Remoting.

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



19/120

Reasons for Team Building

Reasons for Team Building include

Improving communication

Making the workplace more enjoyable

Motivating a team

Getting to know each other

Getting everyone "onto the same page", including goal setting

Teaching the team self-regulation strategies

Helping participants to learn more about themselves (strengths and weaknesses)

Identifying and utilizing the strengths of team members

Improving team productivity

Practicing effective collaboration with team members

TEAM WORK

To make a group means follow a deliberate action to identify and

eliminate the difficulties, to make a good work. The absence of

objectives creates feelings of frustration and dissatisfaction for

the incapacity to change things. Teammates accuse other people

for their mistakes and inactivity.

Team Work is a plural process; it can not be made by a person. When workers are

meeting to make groups, each person gives their knowledge, motivations, values and capacities.

The ways in which these people get involve could be positive or negative. In some cases,



20/120

members neutralize other ones and the result is the absence of effectiveness, or passivity. In

other cases, they sum their efforts totally or partially. But, there exists another possibility: the

interaction makes a transcendental state that exceeds the contribution of any of the members and

the sum of all of them. When this happens the team has developed synergy. The total is superior

to the sum of the parts. The group exceeds the sum of the individual contributions; this is the

meaning of team work.

We can see an example of Team Work functions: A boss and his employer are going to

make a decision. Both of them were studying a technical paper that contains tips to facilitate the

situation, the data and the logic necessary to a complex, but necessary decision. Suppose that

they will take a test to show how much they know about the technical paper. In the test (100

points) one makes 70 points and the other one gets 50 points.

When discussion begins, they can neutralize each other and they will be confused about

the situation, the data and the logic necessary to make a good decision. The media can be reduce

to 60 or 50 at the end of the discussion. It means that they are going to be in an incomprehension

state. Thats not impressive.

In other hand, they can joy their knowledge and get in comprehension levels. In this case,

the action represents a 60: above the decision that could take the teammate less prepare, but

below the decision of the best prepare of them. Thats not impressive too.

Exist a third possibility: if each of them put his knowledge to the disposition to the other

they can resolve the situation using the free and sincere dialogue. The final point is going to be

99. Thats impressive.

Synergy Team Work is an intelligent group working together. Team Work brings

impressive results if the members of the group give all their dedication, effort, information and

recommendations to get the goals.

The project team approach has been proven to be the most successful organizational

structure used to implement new product development. One of the most important factor in the

future success of the concurrent engineering effort is the acquired knowledge of ilities in the

design and development of engineering team.



21/120

The goal of concurrent engineering is the interactive work of different disciplines that

affect a product to make it better.

Minimize the product life cycle

Decrease product cost

Maximize product quality

Team work

One of the principal tools of concurrent engineering in the accomplishment of its goal is

team work. This is were human resources are working together with the objective of surviving

and having success in the actual global market; recognizing its sophistication. and that it is

highly competitive.

For this reason is imperative to improve our products and service, taking advantage of all

the opportunities; from simple improvements through greater and not so frequent scientific and

technological innovation. The complexity of organizational processes today, requires individuals

with specific knowledge in the different areas of the evaluated process, and in the techniques and

tools of the team work. This is the most effective way to obtain and use the experience and

knowledge of the employees to provide increased quality of processes, services and products.

MULTIFUNCTIONAL PRODUCT DEVELOPMENT TEAM



22/120

In the best form of basic concurrent engineering, each

product is developed by a multifunctional product development

team (PDT). The PDT makes all decisions about the product

design, production system, and field-support system. Although the

PDT must grow and then later shrink in size and, in so doing,

change its composition somewhat, there is never any sudden change. In particular, at the

transitions in process phases, there are not any sudden changes in the PDT. Continuity is

maintained; throwing results over the wall is avoided. All decisions are made with the full

participation of the people who have all of the relevant knowledge.

Basic concurrent engineering is best carried out by a multifunctional product

development team (PDT) led by a strong product manager. All functions of the corporation

should participate. People who are doing significant work for the specific product development

program should be part of the PDT while they are doing the programs work. There is a vast

psychological difference between performing a task within a support group and performing it as

a member of the PDT. As a PDT member, the contributor will:

understand the specific requirements,

have the necessary close communications with other members of the PDT, and

be dedicated to the utilization of the task results to make design decisions.

All three of these benefits are much less likely to materialize if the contributor remains

outside the PDT. It is important that the people on the PDT from each function be able to:

represent the knowledge of that function, and

gain the commitment of that function to the decisions that are made.



23/120

Dysfunction will occur if the information is not provided or is wrong, or if the function

subsequently disowns the decisions and wants major changes. For example, if the PDT decides

to use an aluminum die casting and if later, when the product enters into production, the

production operations people want a fiber-reinforced polymer part, then rework of the

development will become rampant. Strong, complete multifunctional product development team

is essential for success.

Some people will stay on the PDT throughout the development program, while others

will be on the team only during the phase or task that requires their expertise. The important

criterion is that there should not be any sudden changes in the composition or size of the PDT,

since that would reduce teamwork and cause lack of continuity.

Even while a member of a team, the individual still does much independent work, but the

work is done for the team. Membership in the team makes the goals of individual work more

holistic. The individuals work contributes effectively to the overall development program.

Although we refer to the team, it is actually a team of teams. The chief engineer who

leads the PDT and the managers who report directly to him or her constitutes one team. They are

responsible for everything related to the product and its development program. They include the

subsystem leaders, for each product subsystem has a team. Many critical interfaces have a

dedicated team. Teams are formed wherever the new product needs them. Although the complete

PDT for a large, complex product may have several hundred members, it is rare for any one

operational team to have more than 20 members. Many have only a few members. The formation

of the best interlocking structure of teams is a key success factor.

TEN PRINCIPLESOF SUCCESSFUL TEAMS

Ian Morley (1990) has developed 10 principles of teamwork in doing total development

work:



24/120

1. Select cohesive teams, based on sentiments of mutual liking and respect for each

others expertise.

2. Bring specialists from all major functional areas into the PDT

3. Ensure a common vision of the concurrent process.

4. Organize controlled convergence to solutions that everyone understands and everyone

accepts.

5. Organize vigilant information processing and encourage actively open-minded

thinking. Avoid the facile, premature consensus.

6. Maintain the best balance between individual and group work. Let individuals do the

things that individuals do best-for example, the initial generation of new concepts.

7. Use systematic methods.

8. Use formal and informal communication.

9. Select at least some of the members according to how well suited they are to the

specific type of development work. One example is how static or dynamic the

concepts underlying the work are. A person who is proficient in applying standards to

rapidly completed static designs may have difficulty with dynamic conceptual work.

The opposite is also true.

10. Provide principled leadership. The leader must emphasize improved process, making

it visible to the team. He or she must take the primary responsibility for helping to

empower members of the team.

The organization and leadership on the multifunctional product development team help to

develop the successful practice of Morleys 10 principles. If these and the principles are

practiced, then any of the three product-focused modes can be successful-heavyweight product

manager, project execution team, or independent PDT.

ANALYSIS



25/120

In addition to listening to ideas from within the organization for implementation, it was

also felt that Cadillac should learn from others experiences with implementing simultaneous

engineering. The organization development manager and champion began meeting with others

in a similar capacity for other organizations. A network meeting took place monthly, then

quarterly and provided many invaluable insights. These allowed Cadillacs future efforts to

benefit from other organizations previous learning.

The learning highlighted cultural issues, organization structure, physical location,

education and training, as well as different business objectives as transformation issues for the

simultaneous engineering teams. For example, some organizations had teams focused on current

product improvement. Some teams formed in a matrix organization found opposition for their

involvement from line management. In addition to the network attended, the organizational

development manager and the champion participated in other organizations simultaneous

engineering education and raining events to get ideas for Cadillacs future kick-off sessions.

ORGANIZATIONAL DESIGNAND PLANNING

In September 1985, the SESC and the executive staff participated in two simultaneous

engineering vision and implementation strategy development workshops to assure alignment

prior to establishing simultaneous engineering teams. One result was the shared vision developed

simultaneous engineering as follows:

Simultaneous engineering is a process in which appropriate disciplines are

committed to work interactively to conceive, approve, develop, and implement

product programs that meet pre-determined Cadillac objectives.



26/120

A further development was the pyramid structure. Cadillac has adopted the pyramid as

the symbol Simultaneous Engineering. At the base or foundation, is the Cadillac executive staff

who supports and nurtures the process with the ultimate objective of satisfying our customers-at

the top of the pyramid.

The role of top management in the simultaneous engineering environment is to:

Sanction the simultaneous engineering process

Set simultaneous engineering policy and direction

Provide the environment in which simultaneous engineering can flourish

Any time an organization sets out to make a significant change in the way it does

business, it is going to take a great deal of time and education for all employees to make it work.

But, without top managements leadership, support, patience, and commitment nothing will be

accomplished. Next on the pyramid is the steering committee whose job is to:

Plan and implement simultaneous engineering policy and direction

Allocate the necessary resources

Serve as liaison to communicate the process to the total organization

Monitor and lead the process



27/120

Next are vehicle teams that are responsible for managing all steps of product

development in their vehicle program. Each vehicle team comprises members representing all

staffs of the organization. The roles of the vehicle team are to:

Develop the vehicle strategy including defining the target market and specific

demographics. This vehicle strategy must be consistent with the overall divisional

strategy.

Establish the overall vehicle goals required to meet this strategy.

Manage the vehicle content. Provide complete, consistent, stable, and timely

program definition for each vehicle.

Assure the needs and expectations of the customers are met or exceeded.

Manage the continuous improvement of the vehicles quality, reliability,

durability, and performance.

As Cadillac developed the structure for simultaneous engineering, the car was sectioned

into specific vehicle systems and created six corresponding vehicle system management teams.

These were the exterior component/body mechanical, chassis/powertrain application, seats and

interior trim, electric/electronic, body-in-white, instrument panel/heating, and air-conditioning

systems. The role of each one of these vehicle system management teams was to manage their

vehicle system in order to optimize the business decisions that are made in that area of the

vehicle.

The vehicle system management teams and the vehicle teams are in the same layer of the

pyramid. This symbolized their partnership and interdependence to accomplish the task.

The product development and improvement teams (PDITs) are responsible for the actual

design of components that are part of the six vehicle systems. Each PDIT has varying core

memberships, depending on its purpose, but can draw members from any area of the

organization and suppliers. One hundred percent of the vehicle is covered by these simultaneous

engineering teams.

In some companies the simultaneous engineering approach calls for product development

teams (PDTs). These teams include process and product engineers in the development phase of

products, then disband when the particular product goes into production. Unlike these PDTs,



28/120

Cadillacs PDITs have cradle to grave responsibility for the productions and continuous quality

improvement of that component or part. Cadillac PDITs focus on all business aspects of their

assigned portion of the vehicle: quality, cost, timing, technology, reliability, and profitability. It

is as if they are running their own business. Cadillac eventually created 66 PDITs with an

average of eight team members.

The structure of the pyramid is similar to a matrix organization structure although

Cadillac has formally maintained its centralized functional structure. Each team member still

reports to a staff area and has other assignments as well. With the exception of the vehicle teams,

all other simultaneous engineering teams elect their own chairpersons and do not have a manager

as in typical matrix structure. The teams receive expectations and leadership from the next team

down in the pyramid.

Each of the vehicle systems management teams is responsible for business decisions

concerning its systems, as well as determining what vehicle subsystems require the formation of

PDITs. Each PDIT, in turn, has similar business decision-making responsibilities at a

component or subsystem level.

The vision was developed and the structure was determined. Roles and responsibilities

were defined and the strategy for simultaneous engineering was ready for the next stage of

implementation. The new expectations of team members would require them to learn about

other part of the business. In addition, most team members were familiar with planning and

decision-making in the context of their individual staff, but not with cross-staff teams. Normally

this type of decision-making is not experienced in a centralized organization except at the

executive staff level. The need to develop consensus decision-making skills and teamwork was

acknowledged. A great need existed to provide education and training.



29/120

Methodology

SDLC METHODOLOGIES

This Document plays a vital role in the development life cycle (SDLC) as it describes the

complete requirement of the system. It is meant for use by the developers and will be the basic

during testing phase. Any changes made to the requirements in the future will have to go through

formal change approval process.

WATER FALL MODEL was being chosen because all requirements were known beforehand

and the objective of our software development is the computerization/automation of an alreadyexisting manual working system.

The relationship of each stage to the others can be roughly described as a waterfall, where

the outputs from a specific stage serve as the initial inputs for the following stage. During each



30/120

stage, additional information is gathered or developed, combined with the inputs, and used to

produce the stage deliverables. It is important to note that the additional information is restricted

in scope; new ideas that would take the project in directions not anticipated by the initial set of

high-level requirements are not incorporated into the project. Rather, ideas for new capabilities

or features that are out-of-scope are preserved for later consideration. After the project is

completed, the Primary Developer epresentative and Primary End-User Representative in

concert with other customer and development team personnel develop a list of recommendations

for enhancement of the current software.


Communicated

Requirements

Requirements

Specification

Design

Specification

Executable

Software

Modules

Integrated

Software

Product

Delivered

Software

Product

Changed

Requirements

Requirements

Engineering

Design

Programming

Integration

Delivery

Maintenance

Product Product

Input Output

Process


31/120

Fig : Water Fall Model

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements of the system?

Demonstrating the system and installing the system at client's location after the acceptance

testing is successful.

Submitting the required user manual describing the system interfaces to work on it and alsothe documents of the system.

Conducting any user training that might be needed for using the system.

Maintaining the system for a period of one year after installation.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input design is as

given below:

To produce a cost-effective method of input.

To achive the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.



32/120

INPUT STAGES:

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion

Data verification

Data control

Data transmission

Data validation

Data correction

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be categorized as follows:

External inputs, which are prime inputs for the system. Internal inputs, which are user communications with the system.

Operational, which are computer departments communications to the system?

Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude about the input

media consideration has to be given to;

Type of input



33/120

Flexibility of format

Speed

Accuracy

Verification methods

Rejection rates

Ease of correction

Storage and handling requirements

Security

Easy to use

Portabilility

Keeping in view the above description of the input types and input media, it can be said that

most of the inputs are of the form of internal and interactive. As Input data is to be the directly

keyed in by the user, the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of processing

to users. They are also used to provide a permanent copy of the results for later consultation. The

various types of outputs in general are:

External Outputs, whose destination is outside the organization.

Internal Outputs whose destination is with in organization and they are the

Users main interface with the computer.

Operational outputs whose use is purely with in the computer department.

Interface outputs, which involve the user in communicating directly with

OUTPUT DEFINITION



34/120

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided

as which form of the output is the most suitable.

For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

OUTPUT MEDIA:

In the next stage it is to be decided that which medium is the most appropriate for the output. The

main considerations when deciding about the output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.



35/120

The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under

the category of internal outputs. The main outputs desired according to the requirement

specification are:

The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the

screen. Keeping in view these outputs, the format for the output is taken from the outputs, which

are currently being obtained after manual processing. The standard printer is to be used as

output media for hard copies.

Input and Output

The main inputs, outputs and major functions of the system are as follows

INPUTS:

Head operator enters his or her user id and password.

Operators enter his or her user id and password.

Technicians enter his or her user id and password.

Sub technicians enter his or her user id and password.

User requests the reports.

User requests the search.

Head operator can edits the personal details and so on.

OUTPUTS:

Head operator receives personal details.

Operator receives the personal details.



36/120

Technicians receive personal and technical details.

Users receive requested reports.

Displays search result.

The following commands specify access control identifiers and they are typically used to

authorize and authenticate the user (command codes are shown in parentheses)

USER NAME (USER)

The user identification is that which is required by the server for access to its file system. This

command will normally be the first command transmitted by the user after the control

connections are made (some servers may require this).

PASSWORD (PASS)

This command must be immediately preceded by the user name command, and, for some sites,

completes the user's identification for access control. Since password information is quite

sensitive, it is desirable in general to "mask" it or suppress type out.



37/120

PERFORMANCE REQUIREMENTS:

Performance is measured in terms of the output provided by the application. Requirement

specification plays an important part in the analysis of a system. Only when the requirement

specifications are properly given, it is possible to design a system, which will fit into required

environment. It rests largely in the part of the users of the existing system to give the requirement

specifications because they are the people who finally use the system. This is because the

requirements have to be known during the initial stages so that the system can be designed

according to those requirements. It is very difficult to change the system once it has been



38/120

designed and on the other hand designing a system, which does not cater to the requirements of

the user, is of no use.

The requirement specification for any system can be broadly stated as given below:

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

FEASIBILITY REPORT

Preliminary investigation examine project feasibility, the likelihood the system will be

useful to the organization. The main objective of the feasibility study is to test the Technical,

Operational and Economical feasibility for adding new modules and debugging old running

system. All system is feasible if they are unlimited resources and infinite time. There are aspects

in the feasibility study portion of the preliminary investigation:

Technical Feasibility

Operation Feasibility

Economical Feasibility

Technical Feasibility

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

following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required to use

the new system?

Will the proposed system provide adequate response to inquiries, regardless of the

number or location of users?



39/120

Can the system be upgraded if developed?

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

Earlier no system existed to cater to the needs of Secure Infrastructure Implementation System.

The current system developed is technically feasible. It is a web based user interface for auditworkflow at NIC-CSD. Thus it provides an easy access to the users. The databases purpose is to

create, establish and maintain a workflow among various entities in order to facilitate all

concerned users in their various capacities or roles. Permission to the users would be granted

based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability

and security. The software and hard requirements for the development of this project are not

many and are already available in-house at NIC or are available as free as open source. The work

for the project is done with the current equipment and existing software technology. Necessary

bandwidth exists for providing a fast feedback to the users irrespective of the number of users

using the system.

Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will

meet the organizations operating requirements. Operational feasibility aspects of the project are

to be taken as an important part of the project implementation. Some of the important issues

raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users?

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

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

benefits?

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

management issues and user requirements have been taken into consideration. So there is no

question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and

would help in the improvement of performance status.



40/120

Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good

investment for the organization. In the economical feasibility, the development cost in creating

the system is evaluated against the ultimate benefit derived from the new systems. Financial

benefits must equal or exceed the costs. The system is economically feasible. It does not require

any addition hardware or software. Since the interface for this system is developed using the

existing resources and technologies available at NIC, There is nominal expenditure and

economical feasibility for certain.



41/120

Chapter : 4

WORK DONE & RESULT

Work Done And Result

PURPOSE OF THE SYSTEM

Team Work is a simple, fast, accurate and easy to use with flexible options for viewing the

essential details. The solution is best suited for individuals working on various projects, which

helps to keep track of all the Projects and their Schedules. This project is the repository for all

documentation associated with a project.



42/120

This is a real time web based application. It provides complete visibility on the project to

all who need access to the information including the Client, the Local Manager, the Technical

Manager and the Programmers assigned to the project. The project control facilitates capturing,

managing time sheet data, enabling us to effectively monitor the time spent on various activities

by each employee. With data being archived in Project Control system, scheduling and planning

fro future projects becomes easy. With security implemented at different hierarchy levels, the

system has features to generate reports basing on various queries like Employee wise activities,

Activity wise Man hours spent by a resource, Process wise analysis, Activity wise Project

analysis, Time wise project analysis, and also a strong report generating a capability, which

increases the performance of the project.

PROBLEMS IN THE EXISTING SYSTEM:

It is limited to a single system.

It is less user-friendly.

It is having lots of manual work (Manual system does not mean that you are working

with pen and paper, it also include working on spread sheets and other simple software's).

The present system is very less secure.

It is unable to generate different kinds of report.

It doesnt have the mail and file upload feature.



43/120

SOLUTION OF THESE PROBLEMS





It can be accessed over the Internet.

Various classes have been used to provide file upload and mail features.


under process.

Report generation feature is provided using Crystal Reports to generate different

kinds of reports like bar graphs, pie charts and table type charts etc.

It provides high level of security using different protocols like https etc.

STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been developed a graphics concept in mind,

associated through a browses interface. The GUIS at the top level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically,

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

The interfaces help the administrations with all the transactional states like Data insertion, Data

deletion and Date updation along with the extensive data search capabilities.



44/120

The operational or generic user interface helps the users upon the system in transactions through

the existing data and required services. The operational user interface also helps the ordinary

users in managing their own information helps the ordinary users in managing their own

information in a customized manner as per the assisted flexibilities.

Number of Modules

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

The modules involved are:

Administrator

Employee (Team)

Projects List

Client (Task)

Report

Authentication

Administrator:-

The administrator is the super user of this application. Any body except admin cannot enter into

this page. The admin can give authenticate to user & gives privileges that which portion they can

access. The admin can create new users. The administrator has all the information about all the

users & about all the projects. There is two-sub module of administrator

Projects: - This contains the information about all the projects i.e. project list, and also

information about manager of the project, starting date and completion date etc.



45/120

Users: - This contains the information about all the users and role of the users.

Time Period: - Here Admin will add all the project timings from when the project has

started and when it has to complete and the client to them will give this time. Based on

the timing he will assign the task to the employee.

Rate / Hours: - Here Admin will decide all the charges for the project and he will assign

the hours for the project in between the employee in how many hour what task to be

completed and what task to be done.

Project status: - Project Status is decided based on the student and what the task they have

doing in the project is and daily employee has to give the status of the project which was

given to them by the higher authority.

Employee:-

This module is actual workplace for a members or Employee i/e. for authenticate users. In this

module the users takes care of his project i.e. how many project he/she handle. I.e. all the

documents about the projects, project activities, starting date & completion date of the project.

And assign that to which team to develop which project, which is the project leader of thisproject, who is the programmer etc.

Projects:-

This module handles a specific project. In this new project can be added. This handles all the

tasks of the project. Complete List of the project should be add in the organization and the task

should be add in the list by admin. This module is again has some sub modules:

Details

Organizations

Milestones



46/120

Documents

Announcements

Client:-

This module contains complete information about the client. Client is the person who provides

the project to the organization and he gives the complete starting date and ending date and all the

specification of the project and the specific requirement where the project to be developed.

Reports:-

This module contains all the information about the reports generated by the Employees, Status

Report and Report based on work of the Employee.

Authentication:-

This module contains all the information about the authenticated user. User without his username

and password cant enter into the login if he is only the authenticated user then he can enter to

his login and he can see the all the information related to the project which he is developing.



47/120

Data Flow Diagram

CONTEXT DIAGRAM -LEVEL 0


TEAM WORK

Client Employee

Reports

AdminProject

Select

Client_id

Client_detai

ls

Emp_details

Select emp_id

Provide services

Receive report

Send

Report

Receive

services

Send

Project

Project

report


48/120

LEVEL 1 PROJECT DETAILS



49/120

LEVEL 1- EMPLOYEE DETAILS


Project

Details

Project

Project Master

Select Proj_id

Proj_details

Org_Project

1.1

Proj_ID

Type

Proj_name

Org_ID


50/120

LEVEL 1- CLIENT DETAILS


Employee

Details

Employee

Employee Master

Select Emp_id

Emp_details

Employee Project

1.1

Emp_ID

Emp_name

Status

Report


51/120


Admin

Project

Details

Client

1. 3

Provider

Services

Receive

Report

Receive Services

Send Report

Receive Report & Order

Send Report & Order

Project


52/120

E R Diagram



53/120



54/120

SCREENS



55/120

Team Work Home Page



56/120

Team Work Admin Login



57/120

Administration Home



58/120

Manage Department



59/120

Manage Project Type



60/120

Manage Country



61/120

Manage State



62/120

Manage City



63/120

Manage Status



64/120

Find User



65/120

Current News On Project



66/120

Find Employee on Project



67/120

Report



68/120

Employee Login



69/120

Available Project



70/120

Project Description



71/120

Employee Details



72/120

Contact us



73/120

Chapter : 5

CONCLUSION & FUTURE SCOPE



74/120

Conclusion

It has been a great pleasure for us to work on this exciting and challenging project. This

project proved good for me as it provided practical knowledge of not only programming in

ASP.NET and C#.NET web based application and no some extent Windows Application and

SQL Server, but also about all handling procedure related with Teamwork Management

System. It also provides knowledge about the latest technology used in developing web enabled

application and client server technology that will be great demand in future. This will provide

better opportunities and guidance in future in developing projects independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The merits of this project

are as follows: -

Its a web-enabled project.

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

The user is mainly more concerned about the validity of the data, whatever he is entering.

There are checks on every stages of any new creation, data entry or updation so that the user

cannot enter the invalid data, which can create problems at later date.

Sometimes the user finds in the later stages of using project that he needs to update some of

the information that he entered earlier. There are options for him by which he can update the

records. Moreover there is restriction for his that he cannot change the primary data field.

This keeps the validity of the data to longer extent.

User is provided the option of monitoring the records he entered earlier. He can see the

desired records with the variety of options provided by him.

From every part of the project the user is provided with the links through framing so that he

can go from one option of the project to other as per the requirement. This is bound to be



75/120

simple and very friendly as per the user is concerned. That is, we can sat that the project is

user friendly which is one of the primary concerns of any good project.

Data storage and retrieval will become faster and easier to maintain because data is stored in

a systematic manner and in a single database.

Decision making process would be greatly enhanced because of faster processing of

information since data collection from information available on computer takes much less

time then manual system.

Allocating of sample results becomes much faster because at a time the user can see the

records of last years.

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

communication.

Through these features it will increase the efficiency, accuracy and transparency,

LIMITATIONS:

The size of the database increases day-by-day, increasing the load on the database back up

and data maintenance activity.

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



76/120

Future Scope

This System being web-based and an undertaking of Cyber Security Division, needs to be

thoroughly tested to find out any security gaps.

A console for the data centre may be made available to allow the personnel to monitor on

the sites which were cleared for hosting during a particular period.

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

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

applications...



77/120

Chapter : 6

REFERENCES



78/120

References

Standards

ANSI/IEEE 1028: Standard for Software Reviews and Audits

ANSI/IEEE 1058.1: Standard for Software Project Management Plans

ANSI/IEEE 1074: Standard for Software Lifecycle Processes

SEI/CMM: Software Project Planning Key Process Area

Articles

Jaime Herrera S., Expert in human-resource development and organizational

development San Jos, Costa Rica October 2001

Teamwork in Healthcare: Promoting Effective Teamwork in Healthcare in Canada

CANADIAN HEALTH SERVICES RESEARCH FOUNDATION

Ian Morleys (1990) principles of teamwork

Internet Resources

www.developer.com

www.15seconds.com

http://www.elucidata.org/refs/seglossary.pdf

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

http://www.developer.com/http://www.15seconds.com/http://www.elucidata.org/refs/seglossary.pdfhttp://www.msdn.microsoft.com/net/quickstart/aspplus/default.comhttp://www.developer.com/http://www.15seconds.com/http://www.elucidata.org/refs/seglossary.pdfhttp://www.msdn.microsoft.com/net/quickstart/aspplus/default.com


79/120

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

http://en.wikipedia.org/wiki/Teamwork

www.4guysfromrolla.com/index.aspx

www.google.com

http://www.fmexpense.com/quickstart/aspplus/default.comhttp://en.wikipedia.org/wiki/Teamworkhttp://www.4guysfromrolla.com/index.aspxhttp://www.google.com/http://www.fmexpense.com/quickstart/aspplus/default.comhttp://en.wikipedia.org/wiki/Teamworkhttp://www.4guysfromrolla.com/index.aspxhttp://www.google.com/


80/120

Coding



81/120

Team Work Home Page

To make a group means follow a deliberate actionto identify and eliminate the difficulties, to make a good work. The absence ofobjectives creates feelings of frustration and dissatisfaction for theincapacity to change things. Teammates accuse other people for their mistakesand inactivity.

Team Work is a plural process; it can not be made by a person. Whenworkers are meeting to make groups, each person gives their knowledge,motivations, values and capacities. The ways in which these people get involvecould be positive or negative. In some cases,members neutralize other ones and the result is the absence of

effectiveness, or passivity. Inother cases, they sum their efforts totally or partially. But, there existsanother possibility: the interaction makes a transcendental state that exceedsthe contribution of any of the members and the sum of all of them. When thishappens the team has developed synergy. The total is superior to the sum of theparts. The group exceeds the sum of the individual contributions; this is themeaning of team work.

Admin Login



82/120

Admin Login

Login ID:

Password:



83/120

Welcome toAdministration

ADD city

using System;using System.Data;using System.Configuration;using System.Collections;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Web.UI.HtmlControls;

public partial class Administration_frmAddCity : System.Web.UI.Page{

clsCity_Logic objCity = new clsCity_Logic();protected void Page_Load(object sender, EventArgs e){

if (!IsPostBack){

BindStatus();BindCountry();

}

}

void BindStatus(){

DataSet dsStatus = objCity.GetStatus();ddlStatus.DataSource = dsStatus.Tables[0];ddlStatus.DataTextField = "StatusName";ddlStatus.DataValueField = "StatusId";ddlStatus.DataBind();ddlStatus.Items.Insert(0, "Select");

}

void BindCountry(){

DataSet dsCountry = objCity.GetCountry();ddlCountryName.DataSource = dsCountry.Tables[0];ddlCountryName.DataTextField = "CountryName";ddlCountryName.DataValueField = "CountryId";ddlCountryName.DataBind();ddlCountryName.Items.Insert(0, "Select");

}void BindState(){

DataSet dsState = objCity.GetState();



84/120

ddlStateName.DataSource = dsState.Tables[0];ddlStateName.DataTextField = "StateName";ddlStateName.DataValueField = "StateId";ddlStateName.DataBind();ddlStateName.Items.Insert(0, "Select");

}

protected void btnSubmit_Click(object sender, EventArgs e){

if (ddlCountryName.SelectedItem.Text != "Select"){

if (ddlStateName.SelectedItem.Text != "Select"){

if (ddlStatus.SelectedItem.Text != "Select"){

objCity.pro_CityName = txtCityName.Text.Trim();objCity.pro_CityDescription = txtCityDescription.Text.Trim();objCity.pro_StateName = ddlStateName.SelectedItem.Text;objCity.pro_StateId = Convert.ToInt32(ddlStateName.SelectedItem.Value);objCity.pro_StatusName = ddlStatus.SelectedItem.Text;objCity.pro_StatusId = Convert.ToInt32(ddlStatus.SelectedItem.Value);objCity.pro_CountryName = ddlCountryName.SelectedItem.Text;objCity.pro_CountryId = Convert.ToInt32(ddlCountryName.SelectedItem.Value);objCity.AddCity();Response.Redirect("frmManageCity.aspx");

}lblErrorStatus.Visible = true;

}else{

lblErrorStateName.Visible = true;

}}else{

lblErrorCountryName.Visible = true;

}

}protected void btnBack_Click(object sender, EventArgs e)

{Response.Redirect("frmManageCity.aspx");

}protected void ddlCountryName_SelectedIndexChanged(object sender, EventArgs e){

if(ddlCountryName.SelectedItem.Text!="Select"){

objCity.pro_CountryName = ddlCountryName.SelectedItem.Text;



85/120

objCity.pro_CountryId = Convert.ToInt32(ddlCountryName.SelectedItem.Value);BindState();

}

}

}

ADD EMPLOYEE


public partial class Admin_frmAddEmployee : System.Web.UI.Page{

clsEmployee_Logic objEmployee = new clsEmployee_Logic();clsCommon_Logic objCommon = new clsCommon_Logic();protected void Page_Load(object sender, EventArgs e){

if (!IsPostBack){

BindDept();BindCountry();BindStatus();

BindState();BindCity();

}}void BindCountry(){

DataSet dsCountry = objCommon.GetCountryName();ddlCountryName.DataSource = dsCountry.Tables[0];ddlCountryName.DataTextField = "CountryName";ddlCountryName.DataValueField = "CountryId";ddlCountryName.DataBind();ddlCountryName.Items.Insert(0, "Select");

}

void BindState(){

DataSet dsState = objCommon.GetStateName();ddlStateName.DataSource = dsState.Tables[0];ddlStateName.DataTextField = "StateName";ddlStateName.DataValueField = "StateId";ddlStateName.DataBind();ddlStateName.Items.Insert(0, "Select");



86/120

}void BindCity(){

DataSet dsCity = objCommon.GetCityName();ddlCityName.DataSource = dsCity.Tables[0];ddlCityName.DataTextField = "CityName";

ddlCityName.DataValueField = "CityId";ddlCityName.DataBind();ddlCityName.Items.Insert(0, "Select");

}void BindStatus(){

DataSet dsStatus = objCommon.GetStatusName();ddlStatus.DataSource = dsStatus.Tables[0];ddlStatus.DataTextField = "StatusName";ddlStatus.DataValueField = "StatusId";ddlStatus.DataBind();ddlStatus.Items.Insert(0, "Select");

}void BindDept(){

DataSet dsDept = objCommon.GetDeptName();ddlDept.DataSource = dsDept.Tables[0];ddlDept.DataTextField = "DeptName";ddlDept.DataValueField = "DeptId";ddlDept.DataBind();ddlDept.Items.Insert(0, "Select");

}protected void btnSubmit_Click(object sender, EventArgs e){

objEmployee.EmpName = txtEmployeeName.Text.Trim();objEmployee.Address = txtAddress.Text.Trim();objEmployee.CountryId = Convert.ToInt32(ddlCountryName.SelectedItem.Value);objEmployee.StateId = Convert.ToInt32(ddlStateName.SelectedItem.Value);objEmployee.CityId = Convert.ToInt32(ddlCityName.SelectedItem.Value);objEmployee.ContactNo = txtContactNo.Text.Trim();objEmployee.DeptId = Convert.ToInt32(ddlDept.SelectedItem.Value);objEmployee.EmailId = txtEmailId.Text.Trim();objEmployee.StatusId = Convert.ToInt32(ddlStatus.SelectedItem.Value);objEmployee.Password = txtPassword.Text.Trim();int i=objEmployee.AddEmployeeDetails();

if (i == 1){

Response.Redirect("frmManageEmployee.aspx");

}if (i == -2){

lblError.Visible = true;lblError.Text = "Sorry This user name is already existing please choose another

username";}



87/120

}protected void btnBack_Click(object sender, EventArgs e){

Response.Redirect("frmManageEmployee.aspx");}protected void ddlCountryName_SelectedIndexChanged(object sender, EventArgs e)

{ if (ddlCountryName.SelectedItem.Text != "Select"){

objCommon.pro_CountryId = Convert.ToInt32(ddlCountryName.SelectedItem.Value);BindState();

}}protected void ddlStateName_SelectedIndexChanged(object sender, EventArgs e){

if (ddlStateName.SelectedItem.Text != "Select"){

objCommon.pro_StateId = Convert.ToInt32(ddlStateName.SelectedItem.Value);BindCity();

}}protected void ddlCityName_SelectedIndexChanged(object sender, EventArgs e){

}}

EMPLOYEE ON PROJECT

using System;using System.Data;using System.Configuration;

using System.Collections;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Web.UI.HtmlControls;

public partial class Admin_frmAddEmployeeOnProject : System.Web.UI.Page{

clsProject_Logic objProject=new clsProject_Logic();clsEmployee_Logic objEmp=new clsEmployee_Logic();private string strError = "No Data Available";

protected void Page_Load(object sender, EventArgs e){

if (!IsPostBack){

BindProject();BindData();

}string Msg = "Do you want to Add these Employees to this Project?";



88/120

btnAddToProj.Attributes.Add("onClick", "return confirm('" + Msg + "');");}public void BindProject(){

//From GetCurrentNerws() we can get All the project names which were not fixed thedelivery date

DataSet dsGetProject = objProject.GetCurrentNews();ddlProjectName.DataSource =dsGetProject.Tables[0];ddlProjectName.DataTextField = "ProjectName";ddlProjectName.DataValueField = "ProjectId";ddlProjectName.DataBind();ddlProjectName.Items.Insert(0, "Select");

}

void BindData(){

try{

//objEmp.e = txtCountryName.Text.Trim();objEmp.Sort_On = "";if (ViewState["Sort_On"] != null)

objEmp.Sort_On = ViewState["Sort_On"].ToString() + " " +ViewState["Sort_By"].ToString();

lblError.Visible = false;DataSet dsTemp = objEmp.GetFreeEmployee();DataTable dtTemp = dsTemp.Tables[0];if (dtTemp.Rows.Count > 0){

lblError.Visible = false;btnAddToProj.Visible = true;

}else{

lblError.Visible = true;lblError.Text = strError;btnAddToProj.Visible = false;

}gvAddEmpOnProj.DataSource = dtTemp;gvAddEmpOnProj.DataBind();if (dtTemp.Rows.Count == 0){

this.Lbl_Pageinfo.Visible = false;}else{

Int16 intTo;

Int16 intFrom;if (gvAddEmpOnProj.PageSize * (gvAddEmpOnProj.PageIndex + 1) 1000000){

lblError.Visible = true;lblError.Text = "please upload a document of size below 1MB only";return;

}else{

docName = Path.GetFileName(fileuploadDoc.PostedFile.FileName);objSpecification.SpecificationType= docName;lblError.Visible = false;

}Doc_Repository_FolderName = Server.MapPath("../" +

ConfigurationManager.AppSettings["Document"]);if (!Directory.Exists(Doc_Repository_FolderName)){

Directory.CreateDirectory(Doc_Repository_FolderName);}fileuploadDoc.PostedFile.SaveAs(Doc_Repository_FolderName + docName);

}else{

lblError.Visible = true;lblError.Text = "Please upload a document of correct format(only

*.pdf,*.doc,*.execl,*.powerpoint,*.xml are allowed)";return;

}}else{

lblError.Visible = true;lblError.Text = "Please upload a document";return;

}objSpecification.AddSpecification();

Response.Redirect("frmAdminHome.aspx");

}void BindProjectId(){

DataSet dsProjectId = objSpecification.GetProjectName();ddlProjectId.DataSource = dsProjectId.Tables[0];ddlProjectId.DataTextField = "ProjectName";ddlProjectId.DataValueField = "ProjectId";



93/120

ddlProjectId.DataBind();ddlProjectId.Items.Insert(0, "Select");

}protected void btnBack_Click(object sender, EventArgs e){

Response.Redirect("frmAdminHome.aspx");

}}

ADD STATE


public partial class Administration_frmAddState : System.Web.UI.Page{

clsState_Logic objState = new clsState_Logic();protected void Page_Load(object sender, EventArgs e){

if (!IsPostBack){

BindStatus();BindCountry();

}

}void BindStatus(){

DataSet dsStatus = objState.GetStatusName();ddlStatus.DataSource = dsStatus.Tables[0];ddlStatus.DataTextField = "StatusName";ddlStatus.DataValueField = "StatusId";ddlStatus.DataBind();ddlStatus.Items.Insert(0, "Selct");

}void BindCountry(){

DataSet dsCountry = objState.GetCountryName();

ddlCountryName.DataSource = dsCountry.Tables[0];ddlCountryName.DataTextField = "CountryName";ddlCountryName.DataValueField = "CountryId";ddlCountryName.DataBind();ddlCountryName.Items.Insert(0, "Selct");

}protected void btnSubmit_Click(object sender, EventArgs e){

objState.pro_StateName = txtStateName.Text.Trim();



94/120

objState.pro_StateDescription = txtStateDescription.Text.Trim();objState.pro_CountryName = ddlCountryName.SelectedItem.Text;objState.pro_CountryId =Convert.ToInt32(ddlCountryName.SelectedItem.Value);objState.pro_StatusName = ddlStatus.SelectedValue;objState.pro_StatusId = Convert.ToInt32(ddlStatus.SelectedItem.Value);objState.AddState();

Response.Redirect("frmManageState.aspx");}protected void btnBack_Click(object sender, EventArgs e){

Response.Redirect("frmManageState.aspx");}

}

ADD STATUS

using System;using System.Data;using System.Configuration;

using System.Colle