Study On Developing A Web Work Tracker Computer Science Essay

Published:

The main idea in developing "Web Work Tracker" , a Web based application is, it is a sub-discipline of project management in which software projects are planned, monitored and controlled. It is an easy to implement and simple to use web-based project management software that is fully customizable to client's projects and workflow.

It is a web application having four modules client, Project manager, Team Leader, and Developer.

The work tracker includes creating new users and viewing all the users to registered client. Client can create project and assign project manager to it by choosing one of the user from the users list. Client can choose the users according to the best of their reputation. He can search users from his page through giving search words as given under the search field.

Visual Studio 2008 (C# .net) is used to develop this application .Active Servlet Pages (ASP) was used to develop the frontend pages (forms). And SQL is used to store the data. During this project, I learned some unknown features of these technologies. And, I also learned about the Software development cycle in the process of developing this application.

CHAPTER 1

INTRODUCTION

CHAPTER 1

INTRODUCTION

Lady using a tablet
Lady using a tablet

Professional

Essay Writers

Lady Using Tablet

Get your grade
or your money back

using our Essay Writing Service!

Essay Writing Service

This application helps clients in effectively tracking and planning projects, and can also be used to support businesses in an effective, but simple manner. This application can also be used to test whether a project management is effective or not.

Here, it gives the introduction with background details about this project.

It is described as three sections. The first segment tells about background to the project. Second one describes goal of the project. The final section tells about the objective of the project.

1.1 Background Research

These are the basic back ground research to do the project. This back ground research helped me lot in designing the following things:

Client design (ASP Forms and C# .net)

This helped me in developing the Active Server Pages (ASP Pages) as front end using c#.net. This also allows me in testing the validations. Some functions I used using the research are listed below:

Adding Client

Adding project

Negotiating with user

Reports to the client

User design (ASP Forms and C# .net)

This is also same like the client design and some other functions using this are:

Adding user

Negotiating With the client

Creating modules and tasks

Report generating

Database design (SQL Queries, 2008)

In this I have come across designing the tables and retrieving the data from the tables using queries. The following are some done using this research:

Creating Tables

Entering data into tables

Generating queries

Retrieving table data using queries

1.2 Aim

Aim of this project is to develop an online software application management system and testing it in manual method. A web application where anyone around the world who is interested in doing software applications/projects from home or like a part time job can access it. In this application the user can either choose the work from the project or the client can assign a work to the user.

This application should be developed using Visual Studio 2008(VS 2008) and SQL to store the data.

1.3 Objectives

The following objectives are discussed before going to start application development and executed successfully.

Project allows the user to create his/her account and can view his/her profile.

For the new user this should provide a registration page and login authentication to access the data in the application. The login mechanism should be that effective to login the valid user.

Negotiation discussion between the clients to normal users.

This negotiation is for the process of selecting them as project Managers, Team Leaders and lead developers. This should allow the user and client to know their needs and requirements as well.

Search engine for getting required results.

This search should get the results required for both the clients and users.

Reputation

This should provide reputation of a registered or existing project member depending upon the number of projects handled and years of experience. This should be able to add the reputation depending upon the users work done in the project or application.

CHAPTER 2

LITERATURE REVIEW

CHAPTER 2

LITERATURE REVIEW

Lady using a tablet
Lady using a tablet

Comprehensive

Writing Services

Lady Using Tablet

Plagiarism-free
Always on Time

Marked to Standard

Order Now

The software development life cycle used in this application will be followed by the client server architecture.

This is a Client server application with two tire architecture. Firstly, we have to know what "Client server Architecture" is.

Client Server Architecture:

Server fulfills the request sent by the client. It is more useful when it used in a network where it can also be used for the applications in the same computer (John, 2009).

Client server communication is done by various models. Let's have a look on some of them (Web developer notes, n.d.).

Static HTML pages

An html file is requested by the client to the server and machine in turn sends it to the client. Now the client will display the file sent by the server. These files are stored in the Server machines.

CGI Scripts

CGI Scripts is bit different .These scripts run at the server. Client requests a request to the server with some parameters. A dynamic HTML page was sent back to the client after executing those parameters at server. This dynamic HTML Page was displayed by the client.

Server side scripting technologies

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

In Simple, Client server technology separates the functions of an application into two i.e. client and server (Smitha, 2008).

Characteristics of Client server Technology

They are run in different machines in general.

Single server can have multiple clients and one single client can have multiple servers.

We can upgrade client and server without affecting others.

Server is the one where Client starts the dialogue at first (Smitha, 2008).

Client Server Architecture benefits

Simple in implementation.

Rapid development of the application.

New hardware can be added easily and can implement multiple software tools.

Two-tier architectures

Client system and Server machine are the two used in this two-tier architecture. The communication of client with the server will be direct. Server will be a database management system and the client will be installed in another user desktop. The client fetches the data directly from the database management system i.e. server with no intervening server. The below picture will give you a clear understanding of the two tier architecture (Oracle, n.d.).

Software Development Life Cycle:

Many individuals use many software applications developed in this challenging Information Technology (IT). Implementation of software process models is the main reason why these applications were developed successfully.

A process model is a "simplified description of a software process from a particular perspective" (Ian, 2007).

Various phases involved in developing a system. The development of the software project is elaborated by these phases. The phases involved in development life cycle are as followed (Ian, 2007).

Requirements Analysis

Design

Development

Coding

Testing

There are different process models which are listed below.

Incremental /linear sequential process models

Spiral model

Rapid action development model

Formal transformation model

Prototyping models

Component Assembly model (Ian, 2007).

2.2.1 Waterfall Model

There are many models in software development process as discussed above. But many development processes use Waterfall model. The scoop below will explain you in detail (Hunterkhan.wordpress, n.d.).

1. System Requirements Analysis

2. Feasibility study

3. Systems Analysis and Design

4. Code Generation

5. Testing

6. Maintenance

7. Implementation

2.2.1.1 System Requirements Analysis

The first essential or vital thing required for any software development is system. Also the system requirement may vary based on the software product that is going to get developed. So a careful analysis has to be made about the system requirement needed for the development of the product. After the analysis and design of the system requirement phase the system required for the development would be complete and the concentration can be on the software development process.

2.2.1.2 Feasibility study

After making an analysis in the system requirement the next step is to make analysis of the software requirement. In other words feasibility study is also called as software requirement analysis. In this phase development team has to make communication with customers and make analysis of their requirement and analyze the system. By making analysis this way it would be possible to make a report of identified area of problem. By making a detailed analysis on this area a detailed document or report is prepared in this phase which has details like project plan or schedule of the project, the cost estimated for developing and executing the system, target dates for each phase of delivery of system developed and so on. This phase is the base of software development process since further steps taken in software development life cycle would be based on the analysis made on this phase and so careful analysis has to be made in this phase.

2.3.3. Systems Analysis and Design

Lady using a tablet
Lady using a tablet

This Essay is

a Student's Work

Lady Using Tablet

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Examples of our work

This is an important phase in system development .Here analysis is made on the design of the system that is going to be developed. In other words database design, the design of the architecture chosen, functional specification design, low level design documents, high level design documents and so on takes place. Care must be taken to prepare these design documents because the next phases namely the development phase is based on these design documents. If a well structured and analyzed design document is prepared it would reduce the time taken in the coming steps namely development and testing phases of the software development life cycle.

2.3.4. Code Generation

This is the phase where actual development of the system takes place. That is based on the design documents prepared in the earlier phase code is written in the programming technology chosen. After the code is developed generation of code also takes place in this phase. In other words the code is converted into executables in this phase after code generation.

2.3.5. Testing

A software or system which is not tested would be of poor quality. This is because this is the phase where system developed would be tested and reports are prepared about bugs or errors in system. To do this testing phase there are different levels and methods of testing like unit testing, system test and so on. Based on the need the testing methods are chosen and reports are prepared about bugs. After this process the system again goes to development phase for correction of errors and again tested. This process continues until the system is found to be error free. To ease the testing process debuggers or testing tools are also available.

2.3.6. Maintenance

After the testing phase is completely through and the system is found to be error free it is delivered to the customer. But no real system would be error free even then. This is because when the system gets executed in real user system scenarios there would be possibilities of lot of bugs and errors. This phase is called the maintenance phase and the errors in this are recorded and changes has to be made in the system accordingly and again testing phase comes into picture.

2.3.7. Implementation

This is the final stage when the system gets into live.

The above software development process are all vital for a system to get developed with quality and thus to achieve customer satisfaction which is the main objective of any software development process.

CHAPTER 3

SYSTEM DEFINATION

CHAPTER 3

SYSTEM DEFINATION

The main goal of the project is to develop a Web based application which can be accessed from anywhere in the world by anyone interested in doing software projects/applications.

3.1 Existing System

Internet is the most useful thing in this ever changing world. With respect to the world the internet and its function also keep on changing. In the internet we can browse many applications.

In these applications we can come across one application where the users and clients get register. The clients can assigned the task as per the user's ability and his or her field of interest and work done by him/her previously. And some clients allows user to have their task themselves using the bidding option.

3.2 Proposed System

As discussed above there is no Web application which can do a complete software project. That only allows the user to do the small applications through bidding options and client request. This application will allow the users to look into the projects available in the application and can be requested to do the project he was interested in.

In this application the user must register into the application and must login through valid authentication. The application is useful for the clients who wants to do the project from different places and also can track their project being at home. This will allow user to do the project on internet. Which consumes the time of user and client in doing a big and small projects as well.

CHAPTER 4

REQUIREMENT ANALYSIS

CHAPTER 4

REQUIREMENT ANALYSIS

In this chapter we are going to discuss the detailed function of the application. The application was divided into two categories Client and user. Requirements were prepared separately for each.

4.1 Client Requirements

The following are the client side requirements

Login/Logout

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

Create new project

The client after logging in can be able to create the project.

View the user details

Client must view the users' details to assign the task and work to be done.

Search and select the user to assign the task.

To assign the task he should search for required user.

Select project manager for the project

Client must select project manger of his/her choice.

Get the selected project report.

Client must track the report of the project.

Get the module report.

Get the task report.

4.2 User Requirements

Following are the user requirements.

Login/Logout

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

Create new user account

User must be able to create a new user account.

View the user profile

User should be able to view his own profile.

Create module by project manager

Project manager should create a module.

Assign modules to the team leader

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

Create task from the module

Assign task to the developer

Finally create report on task by developer

The report of the task must be updated by the developer.

Create report on module by team leader

Create report on project by project manager

Product delivery to the client.

The final product must be delivered to the client by project manager.

CHAPTER 5

SYSTEM DESIGN

CHAPTER 5

SYSTEM DESIGN

5.1 Database Design

This part describes about the backend data base storage tables used, and the queries used for making transaction to front end application.

5.1.1 Normalization

For a better database it should not have any flaws in it. These flaws can be removed using this method called Normalization. There are different normalization forms and following each form one by one we can reduce the flaws and get a proper data base system (Koch & Lonely, 1995).

Now I am going to discuss whether I got the normalized form in this project or not.

5.1.1.1 First Normal Form

In this normalization form usually the database should not have the repeated fields and there should not be any complex fields as well. As the data base in this application is simple and no repeated fields. And all tables have Primary keys. So, we can confirm the database of the application is in first normal form.

5.1.1.2 Second Normal Form

In this second normalization form no records should be dependent on the value in a table except the primary key. Inserting, updating and deleting will be inconsistent if this normalization is not used.

The second thing to be followed in this normalization is to use foreign keys. These foreign keys are used when more tables need same information they are to be separated into different tables and use foreign keys to get the data. In the database of this application no different tables have same data. The data used maximum number of times is retrieved using foreign keys.

5.1.1.3 Third Normal Form

Delete the field which is not dependent of the key. This is the third normalization form and by this the database in the application passes this normal form as unwanted fields were deleted.

.5.1.2 Tables:

WT_Clients: To store client details.

WT_Message: To store the messages

WT_Modules: To store the module information.

WT_ProjectMembers: To store the selected project members.

WT_Projects: To store the project information.

WT_Tasks: To store the task information.

WT_Users: To store the new user account information

Table-1 WT_Clients

Column Name

Data Type

Client ID (Primary key)

Number

Not null

Password

Varchar

50

Client Name

Varchar

50

Address

Varchar

1000

Contact No

Number

20

Email ID

Varchar

50

Table-1 stores the data of the client. In this table no field takes null value.

Client ID is the primary key cannot be null at all. The pass word and client name are the credentials for the client to login. It will be validated at client side and with valid authentication.

Table-2 WT_Message

Column Name

Data Type

Mail Id (Primary key)

Number

Not Null

Subject

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

Project 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 generating the message i.e.(creator ID) and the other will be receiving the Message. Creator ID can be from WT_Client table or from WT_Users table. Project ID and Role Req is used in the process of negotiation. Message status is used to see whether the message has been seen or not.

Table-3 WT_Modules

Column Name

Data Type

Module ID (Primary key)

Number

Not Null

Module Name

Varchar

50

Module Creator ID (Foreign key)

Number

Project ID (Foreign Key)

Number

Description

Varchar

1000

Start date

Date

Due Date

Date

Module Status

Varchar

50

Percentage completed

Number

Assigned To ID (Foreign Key)

Number

Report

Varchar

Maximum

This table-3 WT_Modules is for the storing all the information used to create a module. Module ID is the primary key. Module Creator ID (user id of the project manager who creates modules),Project ID and Assigned To ID(User id of the project member who was assigned to do this task) are foreign keys.

Table-4 WT_ProjectMembers

Column Name

Data Type

Project Member ID (Primary key)

Number

User ID (Foreign Key)

Number

Project ID (Foreign Key)

Number

Role

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

Table-5 WT_Projects

Column Name

Data Type

Project ID (Primary key)

Number

Not Null

Project Name

Varchar

50

Client ID (Foreign key)

Number

Description

Varchar

1000

Start date

Date

Due Date

Date

Project Status

Varchar

50

Percentage completed

Number

Technologies

Varchar

Budget

Number

Report

Varchar

Maximum

WT_Projects store the data of the project including the budget, Technologies and percentage completed. Here Project ID is the primary key and Client ID is the foreign Key. Project status give the information on start of project and completion of the project to the user and client as well.

Table-6 WT_Tasks

Column Name

Data Type

Task ID (Primary key)

Number

Not Null

Task Name

Varchar

50

Module ID (Foreign key)

Number

Creator ID (Foreign Key)

Number

Description

Varchar

1000

Start date

Date

Due Date

Date

Task 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. Instead of Module data task data will be stored in this table.

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 projects

Number

Projects

Varchar

50

Experience

Number

This table contains the user data that is registered by the user at the time of registration.

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

5.1.3 SQL Procedures

SQL Procedures give you the way of handling tables and retrieving the data from the database. In this we have joining the two different tables and SQL stored procedures.

5.1.3.1 Joins between Tables

Creating Project and selecting project manager.

Client creates project and selects one user as project manager from WT_Users table. As discussed above in the table user information is stored in WT_Users table. And project is stored in WT_Projects table.

Module creation and assigning.

Modules are created by project manager and assigning them to team leaders in WT_Modules. Created modules were stored in WT_Modules table. Modules assigned to team leaders will join the table WT_ProjectMembers.

Task Creation and assigning.

Create tasks and stores it in WT_Tasks and assign them to developers WT_ProjectMembers.

Negotiation with the user.

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

Role assigning to users.

Users' roles 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 password.

WT_CheckCredentials:

Validates the normal user username and password.

WT_CreateUser:

Creates new account,and can retrive, delete insert data.

WT_Membership:

Add user as a project member(role),and can retrive, delete insert data.

WT_Module:

Creates module for project,and can retrive, delete insert data.

WT_Task:

Creates task details for module,and can retrive, delete insert data.

5.2 Client Design

Diagram - 1

Diagram - 2

Diagram 1 & 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 using the credentials 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 data for the both client and user of the application.

Here, the flow is as follows,

1) Client creates project

2) Project will sub divided into modules

3) Module divided into tasks.

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

5) Users can be selected as project members.

5.2 Users Design

Diagram - 4

In user's module, a new user is added and he will be selected as project member, similarly other users get created and selected as project members.

Then after Project manager will selects the team leaders and team leaders will selects the developers.

Given project will be divided into modules by project manager, further this module can be divided into tasks and assigned to developers.

Each of the project members should feeds the report, finally these reports can be seen by client.

CHAPTER 6

APPLICATION FUNCTIONALITY

CHAPTER 6

APPLICATION FUNCTIONALITY

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

Client

Project 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

Creating Project

Select Project Manager

Functionality:

Client can create his/her own account to access the web site.

Register client:

If the client is new then he/she can create his/her account. If the client is already a user can directly login into the application.

Login:

Select client radio button and login with credentials. If the credentials were right he/she can access the page. If the credentials were wrong there will be message In the same page showing wrong credentials.

My Account Profile:

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

Users:

Client can select the users as his/her project team member. For this

negotiation is done between client and the selected user.

Create Project:

Client can put his project requirements analysis so that the users can find the project and the interested user can raise their opinion on the project and can be assigned by the client.

My Project:

Client can see his/her project details created by them.

Project Members:

He/she can see his/her project members i.e. each and every user from the project manager to the Normal user he/she can view the details of the user they wish.

Report:

He can see the project report module report, and task report created by different team members of the project.

6.2 User Functionality

Parameters:

User Name

Password

Number of projects handled

Projects handled

Experience

Functionality:

User can create his own account to access the web site.

In User functionality there are major functionalities which are followed :

Login Form

Project creation

Role Assigning

Task Creation

Task Assigning

Search

Reputation

Login form:

Here, any user can login to access the web site and his/her contents. If the user doesn't have an account then he can go to user account creation form i.e. registration through login page or from the home page.

Parameters:

User Name

Password

Functionality:

If the user is already an existing member then he will redirected to the projects page. Else he will get validation error message like invalid user name or password.

Project creation:

Parameters:

Project

Description

Technologies

Budget

Functionality:

After logging in the client can create the project by entering the details in the add project form. In these details there will be description of the project due dates and budget proposed by client and the technologies to be used. Any user(not client) can view these details and can contact the client through negotiation.

Role Assigning

Parameters:

Negotiation

Functionality:

The next step is to select the project manager from the users list. Here first client will negotiate with the selected user then user gets a message. The user will now give the reply to the client about his opinion. Once project manager got selected he will read the project description and choose team leaders from the users list through negotiation same like client selected the project manager. Here, project manager or Team Leader can create modules or tasks for the project or modules.

Task creation:

Parameters:

Module Name

Description

Functionality:

Modules are created by the project managers and the tasks are created by the Team leaders. In the task creation function the data of who created task and due date of that task and the description can be seen. Assign those modules and tasks to the selected Team leaders and Developers respectively.

Task Assigning:

Parameters:

Roles

Tasks

Functionality:

Now these modules and tasks are assigned to the team leaders and developers respectively. This task assigning functionality is based on the parameters Roles and Tasks. With respective to the role the task is assigned.

Finally at the end of the work each team leader will submit their work report to the Project Manager.

Search:

This helps to use the functionality more efficiently. Workload of the server can be reduced using this search function.

Functionality:

Search field is set for getting the required results immediately. For clients, they can search for the best eligible users for the position of project manager for his project. As well as project members can search for their requirement.

Reputation:

"Reputation is the strongest determinant of any corporation's or individual's sustainability." (Peter j. Firestein, n.d.) .

Functionality:

In this application reputation also plays a vital role. Depending on the reputation of the user the client can wish the user to select as project manager and followed to lower roles.

This reputation of an user can be added by either team leader or project manager or by the client.

CHAPTER 7

APPLICATION IMPLIMENTATION

CHAPTER 7

APPLICATION IMPLIMENTATION

The application implementation is done in three parts as below.

DB Implementation

Client Implementation

User implementation

7.1 Hardware and Software Requirements

To implement this project server system requires the following requirements.

Hardware Requirements

RAM: 1 GB

Hard Disk: 40 GB 

Software Requirements

Operating System: windows XP sp2 or higher

.Net Framework 3.5.

7.2 Database Implementation

This segment describes the steps for creating the database of the Web Work Tracker application.

Download and install SQL Server Express edition, or higher version compatible for windows operating system.

Connect to SQL Database server using Visual Studio.

Create the tables Users, clients, projects, modules, tasks and project members using the queries.

This completes the Database creation of the application.

CHAPTER 8

TESTING

CHAPTER 8

TESTING

Testing is very important for software quality assurance and reliability. Testing is done to find the bugs. Testing is started when the development phase coding is done. It is to test-How the System is working? The main intention of testing is identifying the bugs while executing the program. The bugs found will be fixed using testing types.

Test Cases:

Scope: Validate User credentials.

Requirements: Valid User.

Sl No.

Action Performed

Expected Results

1

User name and password entered.

Redirected to projects page.

2

Wrong username and correct password given

Invalid username or password.

3

Right user name and wrong password given

Invalid user name or password

Problems/Issues: None.

Report: Successfully Executed.

Scope: check the user account creation.

Requirements: User account successfully created.

Sl No.

Action Performed

Expected Results

1

All fields entered.

Redirected to result page and shown successfully created.

2

Wrong inputs given to some fields.

Invalid Mobile Number, Numeric Only,.

Problems/Issues: None.

Report: Successfully Executed.

Scope: check the client account creation.

Requirements: client account successfully created.

Sl No.

Action Performed

Expected Results

1

All fields entered.

Redirected to result page and shown successfully created.

2

Wrong inputs given to some fields.

Invalid Mobile Number, Numerics Only,Invalid Email ID.

Problems/Issues: None.

Report: Successfully Executed.

Scope: check the Project Manager Login.

Requirements: Project Manager logged in successfully.

Sl No.

Action Performed

Expected Results

1

User name and password entered.

Redirected to My Project Page.

2

Wrong inputs given.

Invalid User Name or Password.

3

Click on My account Profile

Shows the user account details.

4

Click on My Project

Shows the current project, on which user is working.

5

Click on Modules

Shows modules of the project.

6

Click on the create module

Shows the new module creation page.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Create Module for a project.

Requirements: Module created successfully.

Sl No.

Action Performed

Expected Results

1

Click on create module

Shows the page in which user can creates new module.

2

Fill all the fields correctly

Your module is created Successfully.

3

Fill some fields and leave rest of the fields as empty.

Required fields error message displayed.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Team leader Login.

Requirements: User login was successful.

Sl No.

Action Performed

Expected Results

1

User name and password entered.

Redirected to My Project Page.

2

Wrong inputs given.

Invalid User Name or Password.

3

Click on My account Profile

Shows the user account details.

4

Click on My Project

Shows the current project, on which user is working.

5

Click on My Module

Shows the current project module, on which user is working.

6

Click on Tasks

Shows Tasks of the project Module.

7

Click on the create Task

Shows the new Tasks creation page.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Create Task for a project.

Requirements: Task created successfully.

Sl No.

Action Performed

Expected Results

1

Click on create Task

Shows the page in which user can create new Task.

2

Fill all the fields correctly

Your Task is created Successfully.

3

Fill some fields and leave rest of the fields as empty.

Required fields error message displayed.

Problems/Issues: None.

Report: Successfully Executed.

Scope: select user as developer.

Requirements: User selected as developer successfully.

Sl No.

Action Performed

Expected Results

1

Click on Users

Shows the page in which all users can visible.

2

Select negotiate as developer

Request to the user sent successfully.

Problems/Issues: None.

Report: Successfully Executed.

Scope: Report creation on Project, Module and task.

Requirements: Report created successfully.

Sl No.

Action Performed

Expected Results

1

Click on My Project - Project Log entry

Opens Log entry screen.

2

Write report and send it

Report created successfully.

Problems/Issues: None.

Report: Successfully Executed.

CHAPTER 9

CONCLUSIONS & FUTURE WORK

CHAPTER 9

CONCLUSION & FUTURE WORK

9.1 Conclusion

Work tracker is a online web application developed to maintain the projects created by clients and forming a project team to finish the project. The application contains four main categories namely Client side, Project Manager, Team Leader, and Developer.

Here, client creates the project and assigns it to the user from the users list after negotiating with the respective user or vice versa; user selection process is mainly depending on the best reputation rating which will automatically generated depending on the number of years experienced and number of projects handled. Then the project manager will selects the team leaders, through the best reputation rating.

The selection can also be done by the interest of the user after negotiating with respective user /client of the project. Team leader will take-up the module and divide it into task segments. Further these tasks will be get assigned to the developers, who are got selected by the team leaders as above selection process.

When the project gets started, the project report will get updated by the project manager. And team leaders will update the module wise reports and submits the final report. Finally, developers are responsible for submitting their task reports. All these reports are to be send to the client.

Search field gives the optimized results for the client request. And reputation is one best feature in this project. Client can have the best choice to select the top rated users to his project.

This document describes all the functionalities in the project. In the next step it describes the future work, i.e. extra functionalities which will boost up the worth of the application.

9.2 Future Work

When the application is get started usage, I noticed that, it needs some more technology feed for the application make better and unique. These additional tasks extend the communication to Google server. Here, each project member can store and access their project or module or task information to Google server.

Google Calendar:

Each user can store their project start date and due dates to the calendar, It will automatically shows the content whenever the user logins into Google calendar.

Google Spread Sheets:

Every project members can store their reports into Google Spread sheets.

Payment Method :

Payment option is also to be done in future for the payment of the project and respective users. This payment option should be secure as now a days there is lots of fraud being done via internet as well. There is some secure payment method and the best among them which I believe is "PayPal".

Using PayPal payment method every user should have a PayPal account and the money will be transferred from the respective member or client.