We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

The chief thought in developing “ Web Work Tracker ” , a Web based application is, it is a sub-discipline of undertaking direction in which package undertakings are planned, monitored and controlled. It is an easy to implement and simple to utilize web-based undertaking direction package that is to the full customizable to client ‘s undertakings and work flow.

It is a web application holding four faculties client, Project director, Team Leader, and Developer.

GET EVEN A BETTER ESSAY WE WILL WRITE A CUSTOM
ESSAY SAMPLE ON
Study On Developing A Web Work... TOPICS SPECIFICALLY FOR YOU

The work tracker includes making new users and sing all the users to registered client. Client can make undertaking and assign undertaking director to it by taking one of the user from the users list. Client can take the users harmonizing to the best of their repute. He can seek users from his page through giving hunt words as given under the hunt field.

Ocular Studio 2008 ( C # .net ) is used to develop this application.Active Servlet Pages ( ASP ) was used to develop the frontend pages ( signifiers ) . And SQL is used to hive away the informations. During this undertaking, I learned some unknown characteristics of these engineerings. And, I besides learned about the Software development rhythm in the procedure of developing this application.

Chapter 1

Introduction

Chapter 1

Introduction

This application helps clients in efficaciously tracking and be aftering undertakings, and can besides be used to back up concerns in an effectual, but simple mode. This application can besides be used to prove whether a undertaking direction is effectual or non.

Here, it gives the debut with background inside informations about this undertaking.

It is described as three subdivisions. The first section Tells about background to the undertaking. Second one describes end of the undertaking. The concluding subdivision Tells about the aim of the undertaking.

1.1 BackgroundA Research

These are the basic back land research to make the undertaking. This back land research helped me batch in planing the undermentioned things:

Client design ( ASP Forms and C # .net )

This helped me in developing the Active Server Pages ( ASP Pages ) as front terminal utilizing hundred # .net. This besides allows me in proving the proofs. Some maps I used utilizing the research are listed below:

Adding Client

Adding undertaking

Negociating with user

Reports to the client

User design ( ASP Forms and C # .net )

This is besides same like the client design and some other maps utilizing this are:

Adding user

Negociating With the client

Making faculties and undertakings

Report bring forthing

Database design ( SQL Queries, 2008 )

In this I have come across planing the tabular arraies and recovering the information from the tabular arraies utilizing questions. The followers are some done utilizing this research:

Making Tables

Entering informations into tabular arraies

Generating questions

Recovering table informations utilizing questions

1.2 Aim

Aim of this undertaking is to develop an online package application direction system and proving it in manual method. A web application where anyone around the universe who is interested in making package applications/projects from place or like a portion clip occupation can entree it. In this application the user can either take the work from the undertaking or the client can delegate a work to the user.

This application should be developed utilizing Ocular Studio 2008 ( VS 2008 ) and SQL to hive away the informations.

1.3 Aims

The undermentioned aims are discussed before traveling to get down application development and executed successfully.

Undertaking allows the user to make his/her history and can see his/her profile.

For the new user this should supply a enrollment page and login hallmark to entree the information in the application. The login mechanism should be that effectual to login the valid user.

Negotiation treatment between the clients to normal users.

This dialogue is for the procedure of choosing them as undertaking Managers, Team Leaders and lead developers. This should let the user and client to cognize their demands and demands as good.

Search engine for acquiring required consequences.

This hunt should acquire the consequences required for both the clients and users.

Repute

This should supply repute of a registered or bing project member depending upon the figure of undertakings handled and old ages of experience. This should be able to add the repute depending upon the users work done in the undertaking or application.

Chapter 2

LITERATURE REVIEW

Chapter 2

LITERATURE REVIEW

The package development life rhythm used in this application will be followed by the client waiter architecture.

This is a Client waiter application with two tyre architecture. First, we have to cognize what “ Client waiter Architecture ” is.

Client Server Architecture:

Server fulfills the petition sent by the client. It is more utile when it used in a web where it can besides be used for the applications in the same computing machine ( John, 2009 ) .

Client waiter communicating is done by assorted theoretical accounts. Let ‘s hold a expression on some of them ( Web developer notes, n.d. ) .

Inactive HTML pages

An hypertext markup language file is requested by the client to the waiter and machine in bend sends it to the client. Now the client will expose the file sent by the waiter. These files are stored in the Server machines.

CGI Scripts

CGI Scripts is bit different.These books run at the waiter. Client requests a petition to the waiter with some parametric quantities. A dynamic HTML page was sent back to the client after put to deathing those parametric quantities at waiter. This dynamic HTML Page was displayed by the client.

Server side scripting engineerings

Using server side technologies a dynamic response is generated by the waiter in this 3rd theoretical account. Server side engineerings available are Active Server Pages ( ASP ) , Personal Home Pages ( PHP ) , Java Server Pages ( JSP ) , and Server Side Includes ( SSI ) .

In Simple, Client waiter engineering separates the maps of an application into two i.e. client and waiter ( Smitha, 2008 ) .

Features of Client waiter Technology

They are run in different machines in general.

Single waiter can hold multiple clients and one individual client can hold multiple waiters.

We can upgrade client and waiter without impacting others.

Server is the 1 where Client starts the duologue at first ( Smitha, 2008 ) .

Client Server Architecture benefits

Simple in execution.

Rapid development of the application.

New hardware can be added easy and can implement multiple package tools.

Two-tier architectures

Client system and Server machine are the two used in this two-tier architecture. The communicating of client with the waiter will be direct. Server will be a database direction system and the client will be installed in another user desktop. The client fetches the informations straight from the database direction system i.e. waiter with no step ining server. The below image will give you a clear apprehension of the two tier architecture ( Oracle, n.d. ) .

Software Development Life Cycle:

Many persons use many package applications developed in this ambitious Information Technology ( IT ) . Execution of package procedure theoretical accounts is the chief ground why these applications were developed successfully.

A procedure theoretical account is a “ simplified description of a package procedure from a peculiar position ” ( Ian, 2007 ) .

Assorted stages involved in developing a system. The development of the package undertaking is elaborated by these stages. The stages involved in development life rhythm are as followed ( Ian, 2007 ) .

Requirements Analysis

Design

Development

Coding

Testing

There are different procedure theoretical accounts which are listed below.

Incremental /linear consecutive procedure theoretical accounts

Coiling theoretical account

Rapid action development theoretical account

Formal transmutation theoretical account

Prototyping theoretical accounts

Component Assembly theoretical account ( Ian, 2007 ) .

2.2.1 Waterfall Model

There are many theoretical accounts in package development procedure as discussed above. But many development procedures use Waterfall theoretical account. The scoop below will explicate you in item ( Hunterkhan.wordpress, n.d. ) .

1. System Requirements Analysis

2. Feasibility survey

3. Systems Analysis and Design

4. Code Generation

5. Testing

6. Care

7. Execution

2.2.1.1 System Requirements Analysis

The first indispensable or critical thing required for any package development is system. Besides the system demand may change based on the package merchandise that is traveling to acquire developed. So a careful analysis has to be made about the system demand needed for the development of the merchandise. After the analysis and design of the system requirement stage the system required for the development would be complete and the concentration can be on the package development procedure.

2.2.1.2 Feasibility survey

After doing an analysis in the system requirement the following measure is to do analysis of the package demand. In other words feasibleness survey is besides called as package demand analysis. In this stage development squad has to do communicating with clients and do analysis of their demand and analyse the system. By doing analysis this manner it would be possible to do a study of identified country of job. By doing a elaborate analysis on this country a elaborate papers or study is prepared in this stage which has inside informations like undertaking program or agenda of the undertaking, the cost estimated for developing and put to deathing the system, mark day of the months for each stage of bringing of system developed and so on. This stage is the base of package development procedure since farther stairss taken in package development life rhythm would be based on the analysis made on this stage and so careful analysis has to be made in this stage.

2.3.3. Systems Analysis and Design

This is an of import stage in system development.Here analysis is made on the design of the system that is traveling to be developed. In other words database design, the design of the architecture chosen, functional specification design, low degree design paperss, high degree design paperss and so on takes topographic point. Care must be taken to fix these design paperss because the following stages viz. the development stage is based on these design paperss. If a good structured and analyzed design papers is prepared it would cut down the clip taken in the coming stairss viz. development and proving stages of the package development life rhythm.

2.3.4. Code Generation

This is the stage where existent development of the system takes topographic point. That is based on the design paperss prepared in the earlier stage codification is written in the scheduling engineering chosen. After the codification is developed coevals of codification besides takes topographic point in this stage. In other words the codification is converted into executables in this stage after codification coevals.

2.3.5. Testing

A package or system which is non tested would be of hapless quality. This is because this is the stage where system developed would be tested and studies are prepared about bugs or mistakes in system. To make this proving stage there are different degrees and methods of proving like unit testing, system trial and so on. Based on the demand the proving methods are chosen and studies are prepared about bugs. After this procedure the system once more goes to development stage for rectification of mistakes and once more tested. This procedure continues until the system is found to be error free. To ease the proving procedure debuggers or testing tools are besides available.

2.3.6. Care

After the proving stage is wholly through and the system is found to be error free it is delivered to the client. But no existent system would be error free even so. This is because when the system gets executed in existent user system scenarios at that place would be possibilities of batch of bugs and mistakes. This stage is called the care stage and the mistakes in this are recorded and alterations has to be made in the system consequently and once more proving stage comes into image.

2.3.7. Execution

This is the concluding phase when the system gets into live.

The above package development procedure are all critical for a system to acquire developed with quality and therefore to accomplish client satisfaction which is the chief aim of any package development procedure.

Chapter 3

SYSTEM DEFINATION

Chapter 3

SYSTEM DEFINATION

The chief end of the undertaking is to develop a Web based application which can be accessed from anyplace in the universe by anyone interested in making package projects/applications.

3.1 Existing System

Internet is the most utile thing in this of all time altering universe. With regard to the universe the cyberspace and its map besides maintain on altering. In the cyberspace we can shop many applications.

In these applications we can come across one application where the users and clients get registry. The clients can delegate the undertaking as per the user ‘s ability and his or her field of involvement and work done by him/her antecedently. And some clients allows user to hold their undertaking themselves utilizing the command option.

3.2 Proposed System

As discussed above there is no Web application which can make a complete package undertaking. That merely allows the user to make the little applications through command options and client petition. This application will let the users to look into the undertakings available in the application and can be requested to make the undertaking he was interested in.

In this application the user must register into the application and must login through valid hallmark. The application is utile for the clients who wants to make the undertaking from different topographic points and besides can track their undertaking being at place. This will let user to make the undertaking on cyberspace. Which consumes the clip of user and client in making a large and little undertakings every bit good.

Chapter 4

REQUIREMENT ANALYSIS

Chapter 4

REQUIREMENT ANALYSIS

In this chapter we are traveling to discourse the elaborate map of the application. The application was divided into two classs Client and user. Requirements were prepared individually for each.

4.1 Client Requirements

The followers are the client side demands

Login/Logout

This is to login into the application and logging off when the undertaking is finished.

Create new undertaking

The client after logging in can be able to make the undertaking.

View the user inside informations

Client must see the users ‘ inside informations to delegate the undertaking and work to be done.

Search and choose the user to delegate the undertaking.

To delegate the undertaking he should seek for required user.

Select undertaking director for the undertaking

Client must choose undertaking trough of his/her pick.

Get the selected undertaking study.

Client must track the study of the undertaking.

Get the faculty study.

Get the undertaking study.

4.2 User Requirements

Following are the user demands.

Login/Logout

This is to login into the application and logging off when the undertaking is finished

Create new user history

User must be able to make a new user history.

View the user profile

User should be able to see his ain profile.

Create faculty by undertaking director

Undertaking director should make a faculty.

Assign faculties to the squad leader

Module created by the user must be able assign to the squad leader.

Create undertaking from the faculty

Assign undertaking to the developer

Finally create study on undertaking by developer

The study of the undertaking must be updated by the developer.

Create study on faculty by squad leader

Create study on undertaking by undertaking director

Merchandise bringing to the client.

The concluding merchandise must be delivered to the client by undertaking director.

Chapter 5

SYSTEM DESIGN

Chapter 5

SYSTEM DESIGN

5.1 Database Design

This portion describes about the backend informations base storage tabular arraies used, and the questions used for doing dealing to look end application.

5.1.1 Standardization

For a better database it should non hold any defects in it. These defects can be removed utilizing this method called Normalization. There are different standardization signifiers and following each signifier one by one we can cut down the defects and acquire a proper information base system ( Koch & A ; Lonely, 1995 ) .

Now I am traveling to discourse whether I got the normalized signifier in this undertaking or non.

5.1.1.1 First Normal Form

In this standardization signifier normally the database should non hold the repeated Fieldss and there should non be any complex Fieldss as good. As the information base in this application is simple and no perennial Fieldss. And all tabular arraies have Primary keys. So, we can corroborate the database of the application is in first normal signifier.

5.1.1.2 Second Normal Form

In this 2nd standardization signifier no records should be dependent on the value in a tabular array except the primary key. Inserting, updating and canceling will be inconsistent if this standardization is non used.

The 2nd thing to be followed in this standardization is to utilize foreign keys. These foreign keys are used when more tabular arraies need same information they are to be separated into different tabular arraies and use foreign keys to acquire the information. In the database of this application no different tabular arraies have same informations. The informations used maximal figure of times is retrieved utilizing foreign keys.

5.1.1.3 Third Normal Form

Delete the field which is non dependent of the key. This is the 3rd standardization signifier and by this the database in the application passes this normal signifier as unwanted Fieldss were deleted.

.5.1.2 Tables:

WT_Clients: To hive away client inside informations.

WT_Message: To hive away the messages

WT_Modules: To hive away the faculty information.

WT_ProjectMembers: To hive away the selected undertaking members.

WT_Projects: To hive away the undertaking information.

WT_Tasks: To hive away the undertaking information.

WT_Users: To hive away the new user history information

Table-1 WT_Clients

Column Name

Data Type

Client ID ( Primary key )

Number

Not void

Password

Varchar

50

Client Name

Varchar

50

Address

Varchar

1000

Contact No

Number

20

Email ID

Varchar

50

Table-1 shops the informations of the client. In this table no field takes void value.

Client ID is the primary key can non be null at all. The base on balls word and client name are the certificates for the client to login. It will be validated at client side and with valid hallmark.

Table-2 WT_Message

Column Name

Data Type

Mail Id ( Primary key )

Number

Not Null

Capable

Varchar

Maximum

Message

Varchar

Maximum

Creator ID ( Foreign Key )

Number

Creator Type

Varchar

50

To ID ( Foreign key )

Number

To ID Type

Varchar

50

Message Status

Boolean

Sent Date

Date

Undertaking ID ( Foreign key )

Number

Role Req

Varchar

50

In this Table-2 WT_Message Mail ID is the primary key and Creator ID, To ID and Project ID are the foreign keys. One is bring forthing the message i.e. ( creator ID ) and the other will be having the Message. Creator ID can be from WT_Client tabular array or from WT_Users tabular array. Undertaking ID and Role Req is used in the procedure of dialogue. Message position is used to see whether the message has been seen or non.

Table-3 WT_Modules

Column Name

Data Type

Module ID ( Primary key )

Number

Not Null

Faculty Name

Varchar

50

Module Creator ID ( Foreign key )

Number

Undertaking ID ( Foreign Key )

Number

Description

Varchar

1000

Start day of the month

Date

Due Date

Date

Faculty Status

Varchar

50

Percentage completed

Number

Assigned To ID ( Foreign Key )

Number

Report

Varchar

Maximum

This table-3 WT_Modules is for the hive awaying all the information used to make a faculty. Module ID is the primary key. Module Creator ID ( user Idaho of the undertaking director who creates faculties ) , Project ID and Assigned To ID ( User Idaho of the undertaking member who was assigned to make this undertaking ) are foreign keys.

Table-4 WT_ProjectMembers

Column Name

Data Type

Undertaking Member ID ( Primary key )

Number

User ID ( Foreign Key )

Number

Undertaking ID ( Foreign Key )

Number

Function

Varchar

50

Table-4 WT_ProjectMembers contains Project Member ID as the primary key and User ID and Project Id as the Foreign Key. Role is allotted after dialogue.

Table-5 WT_Projects

Column Name

Data Type

Undertaking ID ( Primary key )

Number

Not Null

Undertaking Name

Varchar

50

Client ID ( Foreign key )

Number

Description

Varchar

1000

Start day of the month

Date

Due Date

Date

Undertaking Status

Varchar

50

Percentage completed

Number

Technologies

Varchar

Budget

Number

Report

Varchar

Maximum

WT_Projects store the information of the undertaking including the budget, Technologies and per centum completed. Here Project ID is the primary key and Client ID is the foreign Key. Undertaking position give the information on start of undertaking and completion of the undertaking to the user and client every bit good.

Table-6 WT_Tasks

Column Name

Data Type

Undertaking ID ( Primary key )

Number

Not Null

Undertaking Name

Varchar

50

Module ID ( Foreign key )

Number

Creator ID ( Foreign Key )

Number

Description

Varchar

1000

Start day of the month

Date

Due Date

Date

Undertaking Status

Varchar

50

Percentage completed

Number

Assigned To ID ( Foreign Key )

Number

Report

Varchar

Maximum

This table Table-6 WT_Tasks is same as the Table-3 WT_Modules. Alternatively of Module informations undertaking informations will be stored in this tabular array.

Here the primary key is Task ID and Module ID, Creator ID and Assigned To ID are the foreign key.

Table-7 WT_Users

Column Name

Data Type

User Id ( Primary key )

Number

Not Null

User Name

Varchar

20

UPassword

Number

20

Email ID

Varchar

50

Mobile No:

Number

Address

Varchar

1000

Number of undertakings

Number

Undertakings

Varchar

50

Experience

Number

This tabular array contains the user informations that is registered by the user at the clip of enrollment.

Here User ID is the primary Key and UPassword is User watchword.

5.1.3 SQL Procedures

SQL Procedures give you the manner of managing tabular arraies and recovering the information from the database. In this we have fall ining the two different tabular arraies and SQL stored processs.

5.1.3.1 Articulations between Tables

Making Project and choosing undertaking director.

Client creates undertaking and selects one user as undertaking director from WT_Users tabular array. As discussed above in the tabular array user information is stored in WT_Users tabular array. And undertaking is stored in WT_Projects tabular array.

Module creative activity and assignment.

Faculties are created by undertaking director and delegating them to team leaders in WT_Modules. Created faculties were stored in WT_Modules tabular array. Faculties assigned to squad leaders will fall in the tabular array WT_ProjectMembers.

Task Creation and delegating.

Create undertakings and shops it in WT_Tasks and delegate them to developers WT_ProjectMembers.

Negotiation with the user.

Negotiation is done in WT_Message tabular array and the WT_Users or WT_ProjectMembers were linked here.

Role delegating to users.

Users ‘ functions are saved in WT_ProjectMembers and it is joined with WT_Users.

5.1.3.2 SQL Stored Procedures

WT_CheckClientCredentials:

Validates the client usr name and watchword.

WT_CheckCredentials:

Validates the normal user username and watchword.

WT_CreateUser:

Creates new history, and can retrive, cancel insert informations.

WT_Membership:

Add user as a undertaking member ( function ) , and can retrive, cancel insert informations.

WT_Module:

Creates faculty for undertaking, and can retrive, cancel insert informations.

WT_Task:

Creates task inside informations for faculty, and can retrive, cancel insert informations.

5.2 Client Design

Diagram – 1

Diagram – 2

Diagram 1 & A ; 2: Client Use Case Diagram

The above diagrams show the flow for the client of the application.

Diagram 1 shows how a client logs in utilizing the certificates and

WT_Client

WT_Projects

WT_Users

WT_Modules

WT_Tasks

WT_ProjectMembers

WT_Message

Diagram – 3

Data Flow Diagrams: The above diagram shows the flow of informations for the both client and user of the application.

Here, the flow is as follows,

1 ) Client creates undertaking

2 ) Undertaking will stand in divided into faculties

3 ) Faculty divided into undertakings.

4 ) Negotiation message communicating was done between users and clients.

5 ) Users can be selected as undertaking members.

5.2 Users Design

Diagram – 4

In user ‘s faculty, a new user is added and he will be selected as undertaking member, likewise other users get created and selected as undertaking members.

Then after Project director will choose the squad leaders and squad leaders will choose the developers.

Given undertaking will be divided into faculties by undertaking director, further this faculty can be divided into undertakings and assigned to developers.

Each of the undertaking members should feeds the study, eventually these studies can be seen by client.

Chapter 6

APPLICATION FUNCTIONALITY

Chapter 6

APPLICATION FUNCTIONALITY

The functionality of the application is divided into four classs and they are:

Client

Undertaking Manager

Team Leader

Developer.

Home page is the initial page at the start of the application.

Here client functionality is different from other three. So, the other three were described in User functionality as they are the users of similar functionality at most.

6.1 Client Functionality

Parameters:

User Name

Password

Making Undertaking

Select Project Manager

Functionality:

Client can make his/her ain history to entree the web site.

Register client:

If the client is new so he/she can make his/her history. If the client is already a user can straight login into the application.

Login:

Choice client wireless button and login with certificates. If the certificates were right he/she can entree the page. If the certificates were incorrect at that place will be message In the same page demoing incorrect certificates.

My Account Profile:

After a successful login the client can see his/her user profile.

Users:

Client can choose the users as his/her undertaking squad member. For this

dialogue is done between client and the selected user.

Create Undertaking:

Client can set his undertaking demands analysis so that the users can happen the undertaking and the interested user can raise their sentiment on the undertaking and can be assigned by the client.

My Undertaking:

Client can see his/her undertaking inside informations created by them.

Undertaking Members:

He/she can see his/her undertaking members i.e. each and every user from the undertaking director to the Normal user he/she can see the inside informations of the user they wish.

Report:

He can see the undertaking study faculty study, and task study created by different squad members of the undertaking.

6.2 User Functionality

Parameters:

User Name

Password

Number of undertakings handled

Undertakings handled

Experience

Functionality:

User can make his ain history to entree the web site.

In User functionality there are major functionalities which are followed:

Login Form

Undertaking creative activity

Role Assigning

Undertaking Creation

Undertaking Delegating

Search

Repute

Login signifier:

Here, any user can login to entree the web site and his/her contents. If the user does n’t hold an history so he can travel to user history creative activity signifier i.e. enrollment through login page or from the place page.

Parameters:

User Name

Password

Functionality:

If the user is already an bing member so he will redirected to the undertakings page. Else he will acquire proof mistake message like invalid user name or watchword.

Undertaking creative activity:

Parameters:

Undertaking

Description

Technologies

Budget

Functionality:

After logging in the client can make the undertaking by come ining the inside informations in the attention deficit disorder undertaking signifier. In these inside informations there will be description of the undertaking due day of the months and budget proposed by client and the engineerings to be used. Any user ( non client ) can see these inside informations and can reach the client through dialogue.

Role Assigning

Parameters:

Negotiation

Functionality:

The following measure is to choose the undertaking director from the users list. Here first client will negociate with the selected user so user gets a message. The user will now give the answer to the client about his sentiment. Once project director got selected he will read the undertaking description and take squad leaders from the users list through dialogue same like client selected the undertaking director. Here, undertaking director or Team Leader can make faculties or undertakings for the undertaking or faculties.

Undertaking creative activity:

Parameters:

Faculty Name

Description

Functionality:

Faculties are created by the undertaking directors and the undertakings are created by the Team leaders. In the undertaking creative activity map the informations of who created undertaking and due day of the month of that undertaking and the description can be seen. Assign those faculties and undertakings to the selected Team leaders and Developers severally.

Undertaking Assignment:

Parameters:

Functions

Undertakings

Functionality:

Now these faculties and undertakings are assigned to the squad leaders and developers severally. This undertaking delegating functionality is based on the parametric quantities Roles and Tasks. With several to the function the undertaking is assigned.

Finally at the terminal of the work each squad leader will subject their work study to the Project Manager.

Search:

This helps to utilize the functionality more expeditiously. Workload of the waiter can be reduced utilizing this hunt map.

Functionality:

Search field is set for acquiring the needed consequences instantly. For clients, they can seek for the best eligible users for the place of undertaking director for his undertaking. Equally good as undertaking members can seek for their demand.

Repute:

“ Repute is the strongest determiner of any corporation ‘s or single ‘s sustainability. ” ( Peter j. Firestein, n.d. ) .

Functionality:

In this application repute besides plays a critical function. Depending on the repute of the user the client can wish the user to choose as undertaking director and followed to take down functions.

This repute of an user can be added by either squad leader or undertaking director or by the client.

Chapter 7

APPLICATION IMPLIMENTATION

Chapter 7

APPLICATION IMPLIMENTATION

The application execution is done in three parts as below.

DB Implementation

Client Execution

User execution

7.1 Hardware and Software Requirements

To implement this undertaking waiter system requires the undermentioned demands.

Hardware Requirements

Random-access memory: 1 GB

Difficult Disk: 40 GBA

Software Requirements

Operating System: Windowss XP sp2 or higher

.Net Framework 3.5.

7.2 Database Implementation

This section describes the stairss for making the database of the Web Work Tracker application.

Download and put in SQL Server Express edition, or higher version compatible for Windowss runing system.

Connect to SQL Database waiter utilizing Ocular Studio.

Make the tabular arraies Users, clients, undertakings, faculties, undertakings and undertaking members utilizing the questions.

This completes the Database creative activity of the application.

Chapter 8

Testing

Chapter 8

Testing

Testing is really of import for package quality confidence and dependability. Testing is done to happen the bugs. Testing is started when the development stage cryptography is done. It is to test-How the System is working? The chief purpose of proving is placing the bugs while put to deathing the plan. The bugs found will be fixed utilizing proving types.

Trial Cases:

Scope: Validate User certificates.

Requirements: Valid User.

Sl No.

Action Performed

Expected Consequences

1

User name and watchword entered.

Redirected to undertakings page.

2

Incorrect username and right watchword given

Invalid username or watchword.

3

Right user name and incorrect watchword given

Invalid user name or watchword

Problems/Issues: None.

Report: Successfully Executed.

Scope: look into the user history creative activity.

Requirements: User history successfully created.

Sl No.

Action Performed

Expected Consequences

1

All Fieldss entered.

Redirected to ensue page and shown successfully created.

2

Incorrect inputs given to some Fieldss.

Invalid Mobile Number, Numeric Merely, .

Problems/Issues: None.

Report: Successfully Executed.

Scope: look into the client history creative activity.

Requirements: client history successfully created.

Sl No.

Action Performed

Expected Consequences

1

All Fieldss entered.

Redirected to ensue page and shown successfully created.

2

Incorrect inputs given to some Fieldss.

Invalid Mobile Number, Numerics Only, Invalid Email ID.

Problems/Issues: None.

Report: Successfully Executed.

Scope: look into the Project Manager Login.

Requirements: Undertaking Manager logged in successfully.

Sl No.

Action Performed

Expected Consequences

1

User name and watchword entered.

Redirected to My Project Page.

2

Incorrect inputs given.

Invalid User Name or Password.

3

Click on My history Profile

Shows the user history inside informations.

4

Click on My Undertaking

Shows the current undertaking, on which user is working.

5

Click on Modules

Shows faculties of the undertaking.

6

Click on the create faculty

Shows the new faculty creative activity page.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Create Module for a undertaking.

Requirements: Module created successfully.

Sl No.

Action Performed

Expected Consequences

1

Click on create faculty

Shows the page in which user can make new faculty.

2

Fill all the Fieldss right

Your faculty is created Successfully.

3

Fill some Fieldss and leave remainder of the Fieldss as empty.

Required Fieldss error message displayed.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Team leader Login.

Requirements: User login was successful.

Sl No.

Action Performed

Expected Consequences

1

User name and watchword entered.

Redirected to My Project Page.

2

Incorrect inputs given.

Invalid User Name or Password.

3

Click on My history Profile

Shows the user history inside informations.

4

Click on My Undertaking

Shows the current undertaking, on which user is working.

5

Click on My Module

Shows the current undertaking faculty, on which user is working.

6

Click on Tasks

Shows Tasks of the undertaking Module.

7

Click on the create Undertaking

Shows the new Tasks creative activity page.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Create Task for a undertaking.

Requirements: Task created successfully.

Sl No.

Action Performed

Expected Consequences

1

Click on create Undertaking

Shows the page in which user can make new Task.

2

Fill all the Fieldss right

Your Undertaking is created Successfully.

3

Fill some Fieldss and leave remainder of the Fieldss as empty.

Required Fieldss error message displayed.

Problems/Issues: None.

Report: Successfully Executed.

Scope: choice user as developer.

Requirements: User selected as developer successfully.

Sl No.

Action Performed

Expected Consequences

1

Click on Users

Shows the page in which all users can visible.

2

Choice negotiate as developer

Request to the user sent successfully.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Report creative activity on Project, Module and undertaking.

Requirements: Report created successfully.

Sl No.

Action Performed

Expected Consequences

1

Click on My Project – Undertaking Log entry

Opens Log entry screen.

2

Write study and direct it

Report created successfully.

Problems/Issues: None.

Report: Successfully Executed.

Chapter 9

CONCLUSIONS & A ; FUTURE WORK

Chapter 9

CONCLUSION & A ; FUTURE WORK

9.1 Decision

Work tracker is a on-line web application developed to keep the undertakings created by clients and organizing a undertaking squad to complete the undertaking. The application contains four chief classs viz. Client side, Project Manager, Team Leader, and Developer.

Here, client creates the undertaking and delegate it to the user from the users list after negociating with the several user or frailty versa ; user choice procedure is chiefly depending on the best repute evaluation which will automatically bring forth depending on the figure of old ages experienced and figure of undertakings handled. Then the undertaking director will choose the squad leaders, through the best repute evaluation.

The choice can besides be done by the involvement of the user after negociating with several user /client of the undertaking. Team leader will take-up the faculty and split it into undertaking sections. Further these undertakings will be acquire assigned to the developers, who are got selected by the squad leaders as above choice procedure.

When the undertaking gets started, the undertaking study will acquire updated by the undertaking director. And squad leaders will update the faculty wise studies and submits the concluding study. Finally, developers are responsible for subjecting their undertaking studies. All these studies are to be send to the client.

Search field gives the optimized consequences for the client petition. And repute is one best characteristic in this undertaking. Client can hold the best pick to choose the top rated users to his undertaking.

This papers describes all the functionalities in the undertaking. In the following measure it describes the hereafter work, i.e. excess functionalities which will hike up the worth of the application.

9.2 Future Work

When the application is acquire started use, I noticed that, it needs some more engineering provender for the application make better and alone. These extra undertakings extend the communicating to Google waiter. Here, each undertaking member can hive away and entree their undertaking or faculty or undertaking information to Google waiter.

Google Calendar:

Each user can hive away their project start day of the month and due day of the months to the calendar, It will automatically demo the content whenever the user logins into Google calendar.

Google Spread Sheets:

Every undertaking members can hive away their studies into Google Spread sheets.

Payment Method:

Payment option is besides to be done in hereafter for the payment of the undertaking and several users. This payment option should be unafraid as now a yearss there is tonss of fraud being done via cyberspace every bit good. There is some unafraid payment method and the best among them which I believe is “ PayPal ” .

Using PayPal payment method every user should hold a PayPal history and the money will be transferred from the several member or client.

Share this Post!

Send a Comment

Your email address will not be published.

Kylie Garcia

Hi there, would you like to get such a paper? How about receiving a customized one?

Check it out