E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION

E-FREELANCING
PT1081156 Asia Pacific Institute of Information Technology 1 | P a g e
TABLE OF CONTENTS
CHAPTER 1- INTRODUCTION TO THE PROJECT............................................................................................7
1. INTRODUCTION TO THE SYSTEM ..........................................................................................................7
1.1 PROJECT TITLE.....................................................................................................................................7
1.2 PROJECT ABSTRACT.............................................................................................................................7
1.3 PROJECT BACKGROUND......................................................................................................................8
1.4 PURPOSE OF THE SYSTEM...................................................................................................................8
1.5 RATIONAILE BEHIND THE SYSTEM ......................................................................................................9
1.5.1 TANGIBLE BENEFITS .....................................................................................................................9
1.5.2 INTANGIBLE BENEFITS..................................................................................................................9
1.6 TARGET AUDIENCE............................................................................................................................10
1.7 BRIEF DESCRIPTION OF THE OBJECTIVES OF THE SYSTEM................................................................10
1.8 FEATURES & FUNCTIONALITY OF THE SYSTEM.................................................................................11
1.8.1 CORE FEATURES .........................................................................................................................11
1.8.3 ADVANCED FEATURES................................................................................................................13
1.8.3 SPECIAL FEATURES.....................................................................................................................14
1.8.4 EVIDENCE FOR LIMITING THE PROJECT SCOPE..........................................................................14
1.9 PROJECT SCOPE AND DELIVERABLES ................................................................................................15
1.10 SUCCESS CRITERIA...........................................................................................................................15
CHAPTER 2: PROBLEM DESCRIPTION.........................................................................................................16
2.1 INTRODUCTION TO PROBLEM AREA.................................................................................................16
2.2 WHY THE PROBLEM SHOULD BE STUDIED............................................................................................16
2.3 PROBLEM JUSTIFICATION......................................................................................................................17
2.4 NATURE OF CHALLENGE .......................................................................................................................18
2.5 RECOMMENDED SOLUTION..................................................................................................................18
CHAPTER 3: LITERATURE REVIEW..............................................................................................................20
3.1. JUSTIFICATION FOR CONDUCTING LITERATURE REVIEW ................................................................20
3.2. LITERATURE REVIEW IN THE PRESENT SCENARIO ...........................................................................20
3.3. ACADEMIC RESEARCH......................................................................................................................21
3.3.1 WEBSITES ...................................................................................................................................21
3.3.2 RESEARCH PAPERS .....................................................................................................................22
3.3.3 BOOKS ........................................................................................................................................22

E-FREELANCING
3.3.4 JOURNAL AND WHITE PAPER REFERENCES ...............................................................................23
3.4 DOMAIN RESEARCH ..........................................................................................................................23
3.4.1 WHAT ACTUALLY E-FREELANCING IS?........................................................................................23
3.4.2 EMERGENCE OF E-FREELANCING...............................................................................................24
3.4.3 AREAS OF OPERATION AND ITS IMPORTANCE ..........................................................................24
3.4.4 STATISTICS WORLDWIDE ...........................................................................................................24
3.4.5 ADVANTAGES OF E-FREELANCING.............................................................................................25
3.4.6 FEATURES OF E-FREELANCING...................................................................................................26
3.5 FINDINGS- MARKET RESEARCH.........................................................................................................26
3.5.1 EXISTING SYSTEM IN THE MARKET ............................................................................................27
3.5.2 COMPARATIVE ANALYSIS OF THE THREE FREELANCE MARKET PLACES....................................28
3.5.3 CONCLUSION DERIVED FROM MARKET RESEARCH...................................................................28
3.6 FINDINGS – TECHNOLOGICAL FEASIBILITY........................................................................................29
3.6.1 CURRENT SCENARIO...................................................................................................................29
3.6.2 GROWTH OF USE OF COMPUTERS.............................................................................................29
3.6.3 WEB-DEVELOPM ENT PLATFORM..............................................................................................30
3.6.4 DATABASE ENGINE SELECTION ..................................................................................................31
CHAPTER 4- RESEARCH METHODS.............................................................................................................32
4.1 PRIMARY RESEARCH..........................................................................................................................32
4.1.1 QUESTIONNAIRE ........................................................................................................................32
4.1.2 INTERVIEW.................................................................................................................................33
4.1.3 OBSERVATION............................................................................................................................34
4.2 SECONDARY RESEARCH.....................................................................................................................34
4.2.1 TECHNICAL RESEARCH ...............................................................................................................34
4.2.2 DEVELOPMENT PLAN.................................................................................................................44
4.2.3 GANTT CHART ............................................................................................................................46
CHAPTER 5- ANALYSIS .......................................................................................................................47
5.1 CONCLUSION FROM ANALYSIS OF QUESTIONNAIRE........................................................................47
5.2 CONCLUSION FROM ANALYIS OF INTERVIEW...................................................................................48
5.3 CONCLUSION FROM ANALYSIS OF OBSERVATION............................................................................48
5.4 RISK ANALYSIS...................................................................................................................................49
CHAPTER 6 - SYSTEM DESIGN..........................................................................................................51

E-FREELANCING
6.1 DESIGN METHODOLOGY SELECTED ..................................................................................................51
6.1.1 JUSTIFICATION FOR SELECTION OF OBJECT ORIENTED DESIGN ................................................51
6.2 DESIGN STRATEGY USED...................................................................................................................51
6.2.1 USE CASE DIAGRAMS .................................................................................................................52
6.3.1 SUB USE CASES...........................................................................................................................55
6.2.2 ACTIVITY DIAGRAMS..................................................................................................................69
6.2.3 SEQUENCE DIAGRAMS...............................................................................................................76
6.3 CLASS DIAGRAM................................................................................................................................80
6.4 MAPPING OF ERD TO RELATIONAL DATABASE SCHEMA..................................................................82
6.5 NORMALIZATION ..............................................................................................................................83
6.5.1 WHY DATA NORMALIZATION IS REQUIRED? .............................................................................83
6.5.2 DESIGN METHODOLOGY USED ..................................................................................................83
6.5.3 FIRST NORMAL FORM ................................................................................................................84
6.5.4 SECOND NORMAL FORM (2NF)..................................................................................................85
6.5.5 THIRD NORMAL FORM...............................................................................................................86
6.6 DATA DICTIONARY ............................................................................................................................87
6.7 PHYSICAL DESIGN OF DATABASE ......................................................................................................93
CHAPTER 7: IMPLEMENTATION......................................................................................................95
7.1 ASPECTS FOR IMPLEMENTATION......................................................................................................97
7.1.1 USABILITY ASPECT......................................................................................................................97
7.1.2 TECHNICAL ASPECTS: TOOLS USED FOR MODELLING & IMPLEMENTATION.............................98
7.2 IMPLEMENTATION APPROACH FOLLOWED......................................................................................99
7.3 IMPLEMENTATION OF DIFFERENT MODULES.................................................................................100
7.4 USER MANUAL: E-FREELANCING ....................................................................................................121
7.5 TECHNICAL MANUAL.......................................................................................................................127
CHAPTER 8: TESTING ................................................................................................................................131
8.1 E-FREELANCING TESTING STRATEGIES............................................................................................131
8.1.1 WHY TESTING SHOULD BE DONE?...........................................................................................133
8.1.2 WHO SHOULD DO THE TESTING?.............................................................................................133
8.1.4 SUCCESS/FAILURE CRITERIA.....................................................................................................134
8.2 TESTING DESCRIPTION....................................................................................................................134
8.2.1 UNIT TESTING...........................................................................................................................134

E-FREELANCING
8.2.1.2 WHITE BOX TESTING .............................................................................................................147
8.2.2 INTEGRATION TESTING ............................................................................................................150
8.2.3 SYSTEM TESTING......................................................................................................................153
8.2.3.1 PRE-CONDITION FOR CONDUCTING SYSTEM TESTING.........................................................153
8.2.4 USER ACCEPTANCE TESTING....................................................................................................158
8.2.4.1 END USERS INVOLVED IN USER ACCEPTANCE TESTING........................................................158
8.3 TESTING SUMMARY ........................................................................................................................161
CHAPTER 9: CRITICAL EVALUATION.........................................................................................................162
9.1 BENEFITS OF THE SYSTEM...............................................................................................................162
CHAPTER 10: CONCLUSION......................................................................................................................163
10.1 DEGREE OF SUCCESS.....................................................................................................................163
10.1.1 SUCCESS ASSESSMENT...........................................................................................................163
10.2 LIMITATIONS OF E-FREELANCING.................................................................................................166
10.3 POSSIBLE FUTURE ENHANCEMENTS.............................................................................................166
10.4 WHAT IF THE DEVELOPER GETS A CHANCE TO REDO THE SYSTEM?............................................167
10.5 COMPUTATIONAL CHALLENGES ...................................................................................................167
10.6 LEARNING EXPERIENCE.................................................................................................................167
REFERENCES..............................................................................................................................................169
APPENDIX A – PREPARED QUESTIONNAIRE..............................................................................................172
APPENDIX B – PREPARED INTERVIEW QUESTIONS...................................................................................175
APPENDIX C- ANALYSIS & JUSTIFICATION OF QUESTIONNAIRE ...............................................................177
APPENDIX D- ANALYSIS & JUSTIFICATION OF INTERVIEW........................................................................183
APPENDIX E- ANALYSIS & JUSTIFICATION OF OBSERVATION ...................................................................186
APPENDIX F- PROJECT PROPOSAL FORM (PPF) ........................................................................................187
APPENDIX G- PROJECT SPECIFICATION FORM (PSF).................................................................................190
APPENDIX H: LOG SHEETS.........................................................................................................................204
APPENDIX I: FAST TRACK ETHICAL FORM .................................................................................................205
APPENDIX J: SAMPLE QUESTIONNAIRE & INTERVIEW (FILLED)................................................................206
APPENDIX K: GANTT CHART......................................................................................................................207

E-FREELANCING
List of Tables
Table 1 Fair Bidding Policy ..........................................................................................................................17
Table 2: Recommended Solution for Identified Problems..........................................................................19
Table 3 Comparison between methodologies............................................................................................38
Table 4 Comparison between Web Development Platforms .....................................................................41
Table 5 Risk Analysis ...................................................................................................................................49
Table 6 Risk Assessment & Control.............................................................................................................50
Table 7 Sub Use Case - Registration............................................................................................................56
Table 8 Sub Use Case - Project Creation & Updating..................................................................................58
Table 9 Sub Use Case-Online Certification Test..........................................................................................60
Table 10 Sub Use Case- Online Project Bidding..........................................................................................62
Table 11 Sub Use Case - Payment...............................................................................................................64
Table 12 Sub Use Case - View Report .........................................................................................................66
Table 13 Sub Use Case- Discussion Forum..................................................................................................68
Table 14 Normalization Forms....................................................................................................................84
Table 15Usability Aspects ...........................................................................................................................97
Table 16 Technical Aspects- Development Tools........................................................................................98
Table 17 Technical Aspects - Documentation Tools ...................................................................................98
Table 18 Types of Testing..........................................................................................................................132
Table 19 List of Testers .............................................................................................................................133
Table 20 Hardware & Software Requirements for Testing.......................................................................134
Table 21 Unit Test: Registration................................................................................................................135
Table 22 Unit Test: Login ..........................................................................................................................136
Table 23 Unit Test: Password Recovery & Change ...................................................................................137
Table 24 Unit Test: Project Create & Update............................................................................................138
Table 25 Unit Test: My Projects................................................................................................................139
Table 26 Unit Test: Online Project Bidding...............................................................................................141
Table 27 Unit Test: Online Certification Test............................................................................................142
Table 28 Unit Test: Profile Creation & Updation ......................................................................................143
Table 29 Unit Test: Chat............................................................................................................................144
Table 30 Unit test: Upload Resume ..........................................................................................................145
Table 31 Unit Test: Feedback....................................................................................................................145
Table 32 Unit Test: Discussion Forum.......................................................................................................146
Table 33 GUI Testing.................................................................................................................................155
Table 34 Question Set for Usability Testing..............................................................................................156
Table 35 Usability Test Response Analysis................................................................................................156
Table 36 End Users involved in User Acceptance Testing.........................................................................158
Table 37 Result of Acceptance Testing- Test Case #1...............................................................................159

E-FREELANCING
Table 40 Success Parameter – System Requirements..............................................................................164
Table 41 Success Parameter – Functional Requirements.........................................................................164
Table 42 Success Parameter– Ease of Use................................................................................................165
Table 43 Success Parameter– Ease of Use................................................................................................165
Table 44 Success Parameter- Research Analysis ......................................................................................165
Table of Figures
Figure 1 Statistics from www.freelancer.com ............................................................................................22
Figure 2 Skills in Demand............................................................................................................................24
Figure 3 Registered users on elance.com ...................................................................................................25
Figure 4 Total time spent by full-time freelancers worldwide per week....................................................25
Figure 5 Features of E-Freelancing .............................................................................................................26
Figure 6 Market Research - www.freelancer.com......................................................................................27
Figure 7 Market Research- www.oDesk.com ............................................................................................27
Figure 8 Market Research - www.workana.com ........................................................................................28
Figure 9 Internet Users in the world...........................................................................................................29
Figure 10 Research Plan..............................................................................................................................32
Figure 11 Waterfall model ..........................................................................................................................35
Figure 12 Boehm-Spiral-Model...................................................................................................................37
Figure 13 Three Tier Client Server Architecture .........................................................................................43
Figure 14 Design Strategy Used ..................................................................................................................51
Figure 15 Use Case - E-Freelancing.............................................................................................................52
Figure 16 Use Case- Client ..........................................................................................................................53
Figure 17 Sequence Diagram – Registration...............................................................................................76
Figure 18 Sequence Diagram: Login............................................................................................................77
Figure 19 Sequence Diagram: Post Project.................................................................................................77
Figure 20 Sequence Diagram: Project Bidding............................................................................................78
Figure 21 Sequence Diagram: Online Certification Test.............................................................................79
Figure 22 Class Diagram..............................................................................................................................80
Figure 23 Implementation Approach..........................................................................................................99
Figure 24 Testing Strategy Hierarchical Plan ............................................................................................131
Figure 25 Flow Graph................................................................................................................................148
Figure 26 Compatibility Testing – Web Browsers.....................................................................................157
Figure 27 Compatibility Testing – Operating Systems..............................................................................157

E-FREELANCING
CHAPTER 1- INTRODUCTION TO THE
PROJECT
1. INTRODUCTION TO THE SYSTEM
The system being proposed by the developer is a website which represents a freelance
market place where clients can post projects and freelancers can bid for the projects. It is
system where both the freelancers and the clients will be brought under the same Roof.
This is an era where most of the people prefer to work as a free man and not under the
name of any organization. Online freelance market place is such a platform to such
freelancers where they get paid for their work and at times, this makes work more as a fun
game. Similarly, clients, which can be any organization, any group or any individual,
willing to offer their projects to be outsourced and developed by other people and that too
within a fixed budget range acceptable to both the parties. For both the above two kind of
people, the proposed system is a proper solution - “An online freelance market place”.
1.1 PROJECT TITLE
E-FREELANCING
1.2 PROJECT ABSTRACT
The system being developed will be a Web application system based on .Net framework
using C#. It is an “E-Freelancing” website which will be used by IT project developers,
clients and even IT students. The basic feature of this website will be to provide a
communication channel between a client, seeking a developer for any project, and the
developer/Freelancer, seeking for IT projects for which they will be paid. The client as
well as the freelancer is required to sign up to the website so they can be considered as the
member of the E-Freelancing website. The freelancers will have to pass an online test in
order to participate in the online bidding of the projects available on the website. The
system will also provide a chatting module and a discussion board which will be used for
communication between the clients, developers and other interested parties, in an effective
and efficient manner.

E-FREELANCING
1.3 PROJECT BACKGROUND
These days organizations belonging to every field of work are getting dependent on their
technical employees for any IT related project work or else they need to hire developers
and programmers from somewhere for which they need to make huge payments. Even we
see people search for programmers and developers either to make a website for them or
create any application for their business or ask to perform many more such tasks. All these
problems have a very appropriate solution- Online freelancing.
There are a few online freelancing websites which offer such facilities to hire freelancers
online but they do not guarantee that the developer being hired is completely efficient and
able to take that project. The hiring process of contractors over the existing system is very
complex. The clients are not able to see the complete profile of the available freelancers
before the hiring process starts. Even it is difficult for the freelancers to collect sufficient
information from the website about the clients who are hiring them. This often leads the
clients in turmoil with incompetent developer and the allotted task remains undone. This
system will work to remove such problems and offer people a website which would make
the freelancing and hiring of freelancers a simplified process. The efficiency of the
developers will already be checked by an online test and the price of the projects will be
based on online bidding of the projects.
1.4 PURPOSE OF THE SYSTEM
The purpose of the system is to facilitate the clients/organizations to post their IT related
projects over this website and this website in turn will serve as a freelance market place for
everyone. People who get logged in to the system as freelancers and who have passed the
online eligibility test will be allowed to participate in the bidding process. Thus, this
marketplace is advancement in technology trends where clients, without going anywhere in
search of freelancers will get a very suitable project developer for his/her projects and gets
it done within the minimum time duration and within a limited budget estimated.

E-FREELANCING
1.5 RATIONAILE BEHIND THE SYSTEM
With over 8 million users, you can hire a freelancer to do your contract work at a fraction
of the cost. Whether you need PHP developers, web designers, or content writers, you can
outsource jobs within minutes. Browse through hundreds of skills including copywriting,
data entry, and graphic design or more technical areas like coding HTML, programming
MySQL, and designing CSS. Are you an entrepreneur just starting a company? Find a
quality graphic designer to create a logo to your specifications. Are you looking to grow
your business online? Don't have a website or mobile app? Not a problem, we have
thousands of web developers waiting to hear from you. This accelerates your businesses
growth by giving you the talent you need when you need it.
1.5.1 TANGIBLE BENEFITS
Ease of access to hire freelancers online will save client’s time to complete the project. The
online bidding of the projects may be useful in limiting the time for bidding and hence this
also saves sufficient time to a lot project to a freelancer. The bidding process will further
reduce the cost of the project.
Not only the clients but also the freelancers will be get benefits from this website.
Availability of projects online will prevent the freelancers from being jobless and it will
serve as a source of income to them. A freelancer can be hired for more than one project
according to the bidding value and hence, more projects will result in more monetary gain.
1.5.2 INTANGIBLE BENEFITS
Both the client and the freelancer being hired will be satisfied with the services provided
by E-Freelancing. The client will have to give less effort in finding an appropriate
freelancer for their projects. The bidding process will ultimately bring the development
cost low enough satisfying the budget requirement of the clients. Further the freelancer
bidding for the projects online will bid up to a level to which they are comfortable. The
freelancer signing up in E-Freelancing has to pass an online test based on their

E-FREELANCING
qualifications. This assures the clients that the freelancers they are hiring for their project
are qualified enough to complete the project.
1.6 TARGET AUDIENCE
Any organization or individual who is willing to get their IT related projects made in a
minimum amount possible can use this website and get a suitable developer hired.
Individual working as professional project developers in any organization may also use
this online freelancing service to earn extra money. Freelancers, students having good
knowledge about project development and website designing can use this website as a
source of extra income. All other technical professionals can also make use of this website.
1.7 BRIEF DESCRIPTION OF THE OBJECTIVES OF THE SYSTEM
The main goal of this project is to develop a website which will have two main modules
operating – Client & Freelancer. The website will avail people online working as
freelancers for IT related projects. It will focus on strict bidding for projects and a secure
payment to the freelancers by the clients.
The objectives of the project are:
 Make the complete use of Ajax and JQuery tools so that the system can be made user
friendly, following all the Human Computer Interaction principles.
 Implement a secure and bug free payment gateway so that neither the clients nor the
freelancer should face any kind of payment related problems.
 Implement a successful and transparent online bidding process for the projects.
 Conduct an online test for the freelancers which would be in a very standardized format
and having standard questions which only a well qualified project developer/programmer
will able to pass.
 After a client hires a freelancer, a new feature i.e., online chatting will be enabled between
them which will make sharing of ideas and project related doubt clearances easy.
 The discussion forum will further encourage idea sharing between the freelancers signed
up to the website.

E-FREELANCING
Other Learning Objectives
Besides developing a skillful hand on certain website development related tools like
ASP.NET in Microsoft Visual Studio 2012, few other technologies are also to be learnt to
enhance the user interactivity and usage:
 Learn advanced Designing concepts of Ajax, CSS & JavaScript
 Integration of SMTP server with ASP.NET application
 Integration of Payment Gateway which has to be safe & Secure
 Understand the principles of HCI & implement those in designing the interface of the web
application
 Learn about controlling timers using JavaScript concepts and implement those in designing
the online certification test
 Learn how to invoke events at runtime for implementing chat server
1.8 FEATURES & FUNCTIONALITY OF THE SYSTEM
1.8.1 CORE FEATURES
FEATURES DESCRIPTION
Guest User
Registration
Guest users can register on this web application by providing the
required user details. Users at the time have registration have to
select the role they want for- either Client or Freelancer. An auto
generated alphanumeric password will be sent to the user’s email id
which will be used during login.
Member Login
Users can use the login ID and password sent to their email id to
login to the system. The system will identify the user as Client or
Freelancer and take them to their respective home pages. Admin can
use their already defined user ID & Password to login into the
system
Project Creation &
Posting
Clients can anytime create projects and post it online on E-
Freelancing which will be viewed by all the freelancers and Bidding
process can be started on these projects

E-FREELANCING
View Projects
Open for Online
Bidding
Freelancers could be able to see only those projects whose date &
time of closing the bidding process is still to come and currently
bidding is going on. Projects whose bidding time is over will not be
displayed as available projects
Online Project
Bidding
Freelancers can browse for the projects open for bidding and they
can place their own bid amount. It must be noted that the new bid
amount should be at least 2% lesser than the previous Bid value on
that project.
Edit & Update
profile
Both Clients and Freelancers will have the privilege to edit their
profile details and update it anytime and any number of times. This
data is to be viewed by the Clients at the time of project allotment.
View Reports
Freelancer may see reports regarding their project allotments to
them, project lists and many more. Similarly, clients can see reports
like total projects posted yet, freelancer’s contacted via E-
Freelancing and many more reports. Crystal reports will be
generated for showing reports.
Notifications
Freelancers and Clients get notified for any messages received to
them either by the system or by any other user of E-Freelancing.
Freelancers get notified about new projects posted online and open
for bidding and upon bid closing on such projects in which they have
submitted the lowest bid. Clients get notifications when any
freelancer places new bid on their projects.
Upload/Download
Freelancer’s
Resume
Freelancers have the facility to upload their current resumes online
and Clients on the other hand will be able to download resumes
uploaded by Freelancers. This enhances and improves the hiring
procedure of freelancers for projects.
Password Change
& Recovery
Though the users get their Login ID & Password via email, they will
have the privilege to change their password anytime by following a
safe procedure. In case users forget their password, it can be
recovered by using the “Password Recovery” feature.

E-FREELANCING
Feedback
The freelancers can also send feedback to the admin for certain
updation while they conduct the online certification test. This
feedback feature will enable the admin of the system to manage the
question set for online certification test functionality
View Current
Bidding Status on
Projects
E-Freelancing will have a vast accessibility via internet and thus,
until the bidding is open for a particular project, the project will face
numbers of biddings every moment. Thus, the bidding status will
keep changing according to the bidding frequency. This feature will
enable users to refresh page any time and see the most recent bid
value and the bidder’s name.
Payment Gateway
Integration
This module will perform the payment process of the website. This
is one of the most important modules as this will serve as the
medium of payment which the client can do to E-Freelancing for the
facilities provided
1.8.3 ADVANCED FEATURES
Online
Certification
Test
A freelancer’s eligibility to participate in a bidding process will be
decided by using this functionality. A short test will have to be given by
the freelancer where questions will be related to the website’s policy of
work and the programming language selected by the freelancer. This test
will be mandatory for every freelancer willing to participate in the online
bidding of the projects.
Dash Board
Both the users, clients and freelancers, will get the facility of a dashboard
where they can see their profile details, and details related to other
activities they performed.

E-FREELANCING
1.8.3 SPECIAL FEATURES
Chatting
Client & Freelancer would be able to do test chatting by using this
feature of the system. The developer will try to implement this
functionality with proper care. But the conversation between the users
will not be stored by the system. This facility of E-Freelancing will be
just to provide a communication medium between its users.
File Transfer &
Sharing via Email
At the time of project posting, Clients do not provide the full project
specification. Once the project bidding is completed, Clients will have
the privilege to send/transfer the SRS of the project to their
Freelancers for better understanding of the project.
Discussion Board
Discussion board is a place where users see details of all their major
activities and profile details in an organized manner. The developer
will implement this feature so that Clients & Freelancer can keep track
of their activities on E-Freelancing.
1.8.4 EVIDENCE FOR LIMITING THE PROJECT SCOPE
Though the developer will make all possible efforts to implement all the key features
keeping in mind the needs and requirements of the users, certain limitations are as follows:
 The options provided to the users in customizing the background of the website will be
limited to few options
 The chat conversations between the client and the freelancer will not be saved. It means
the website is just facilitating an online communication mode between the two user
profiles and no saved record can be maintained.
 The questions provided for online test will be limited to specific areas of programming
languages as most of the programming languages follow similar concepts and all
database related queries apply to the similar concepts.

E-FREELANCING
1.9 PROJECT SCOPE AND DELIVERABLES
The project introduces a very user interactive website enabling easy understanding and
working of its functionalities. Both client and freelancer will be offered a common
platform where they can set projects to bid and accept projects as a
developer/programmer respectively.
The main deliverables of this project are:
 An HCI based website – Here people can register and login themselves as a client or
freelancer as per their choice. Further they will be able to login to the site and enjoy the
services offered.
 A very well formatted documentation of the project, having all its contents clearly
elaborated in it. This documentation will also serve as a user manual of the project
system.
1.10 SUCCESS CRITERIA
The project evaluation done jointly by the project supervisor, developer and the end users
will be considered for measuring the success criteria of the project:
1. Meet user requirements – A project’s success is confirmed only when it meets all the
user requirements successfully. This is a very important aspect to decide if a project is
succeeded or failed.
2. System Functionality – Functionality is determined by the working of the system. The
system functionality such as the payment gateway integration, online bidding and test,
profile management are to be evaluated.
3. System Usability – The evaluator may check the system’s usability by checking the
systems recoverability, accessibility and familiarity to the users.
4. Project Management – How well the scheduling has been followed and how well the
project duration and requirements has been fulfilled managing both time and development
cost. These are to be evaluated by the evaluator.
5. Research and Analysis – The developer is required to do a good amount of research and
analysis before and even during the course of project development.
6. Documentation – A very well formatted documentation is to be done which should not
have any grammatical mistake in it and whole content should be clearly specified.

E-FREELANCING
CHAPTER 2: PROBLEM DESCRIPTION
2.1 INTRODUCTION TO PROBLEM AREA
It is important to understand and identify the possible problem areas by analyzing various
facts and figures related to the existing and the proposed system. After conducting the
preliminary research, the developer is quite sure about the problem contexts. Still, he wants
to explore the problem areas in more details.
As the system is based on bidding process mainly, it is important for the developer to
understand the terms and conditions that are applied over the project biddings. One of the
most important things to keep in mind is that the lowest price is not always what your
prospect is looking for. More often than not, organizations are looking for experience.
There are possibilities that at the last moment of project biddings, the bid rate may get
faster and this may increase data traffic to the website. This may sometime create problems
in the bidding process of the projects.
The main areas in which the developer needs to think to identify and sort out proper
solutions are:
 Problems related to bidding of projects where bogus bidding or fake project listing for
bidding process is the most important problems.
 Payment for the project by the client to the freelancer should be safe and secured. The
freelancers must be assured that they will be paid once the project gets completed within
the given time duration.
2.2 WHY THE PROBLEM SHOULD BE STUDIED
For every project’s success, it is important to identify the problems associated with the
system and draft a proper solution for those problems so that they might not affect the
performance of the system at a later stage. This should be done prior to conducting the
literature reviews or the researches related to the technology specifications and

E-FREELANCING
methodologies. The problems may arise not only due to technical faults but also due to
external agent’s involvement (DANIEL, 2009).
The developer’s intention to study about the problems clearly states that the developer
wants the proposed system to be free from all types of problems that are being faced by the
existing system. Thus, for this, a detailed study about the existing system is very much
necessary. Once the problems are identified, the developer can confidently build an error
free system.
2.3 PROBLEM JUSTIFICATION
All problems that may occur in the current system are due to improper management of user
profiles. The project developers should take care of the things like no single user can have
multiple user ID’s on the same website. This does nothing other than creating problems
and over-crowding the database of the system.
Fair Bidding Policy
 Inflating or deflating the bids by submitting bogus bid value just to help any other
person in achieving the lowest bid is illegal and a punishable offence. This
problem may effect to the fair bidding for other freelancers who really deserve to
get the project assigned to them.
 The database often gets crowded by fake registrations and fake project postings
over the website. This not only slows the processing time but also wastes the
freelancer’s time spent on bidding over fake projects.
Table 1 Fair Bidding Policy
Other than the above mentioned problems, some of the basic problems are like user’s
inefficiency to use internet or computer in a very well versed manner. This is one of the
most important problems which must be assured that users even with little knowledge of
computers can be guided well to handle the website by following the instructions provided.

E-FREELANCING
2.4 NATURE OF CHALLENGE
 The foremost challenge in front of the developer is to implement a smooth online bidding
process for the projects. The total time for which the project should be kept on for bidding
is also to be decided and it should not be too long neither too short. It is important to
conduct this bidding in a very fair way without being partial to any of the freelancers
participating in the bidding process.
 Conduct an online test for the freelancers which will then decide the eligibility of the
freelancers to be able to participate in the bidding process. It is a tough task in front of the
developer because the questions should be very much standardized and a lot of questions
are to be stored in the database.
 Last but not the least; this is technically the most challenging aspect of the project
development- payment gateway integration. This will serve as a medium of payment for
the project by the client to the freelancers on completion of the project assigned.
 New technologies like Ajax, Web services, Microsoft Silverlight are to be implemented
and since the developer is new to these, a detailed study is required. Further, during the
project development, the developer might face problems in project’s implementation.
Research regarding new technologies and their implementation techniques is going on.
2.5 RECOMMENDED SOLUTION
SOLUTION DESCRIPTION
Unique
authorization
for each user
The users visiting the website will be asked for a secure
username and password which will be provided to them only
if they sign in using a valid email address and the username
must be unique
Centralized
Database
This will be used to handle all the data of almost every activity
in the database of the system. Making a centralized database
will help the developer to easily find and remove errors (if
any)
Online This is the main functionality of the project where clients will

E-FREELANCING
Bidding be able to put projects on online bidding and the project
allotment to the freelancers will be decided only after the
project bidding gets closed.
Reports for
all activities
Reports will be generated for most of the activities and thus,
the
user will be able to keep track of their activities by seeing their
reports
Profile
Creation &
Updating
The users, both, client and freelancer will be asked to provide
details so that a complete profile could be created and it can be
updated by the user itself.
Online Test This will act like a filter for those freelancers who have no
sufficient knowledge and have signed in to the website
for project bidding. Freelancers qualifying in this test will be
allowed to bid in the projects.
Safe Online
Payment
Gateway
Integration
The developer will try his best to implement this functionality
in the system so that the users can be availed with a payment
facility too for their projects.
Table 2: Recommended Solution for Identified Problems

E-FREELANCING
CHAPTER 3: LITERATURE REVIEW
3. LITERATURE REVIEW
A literature review is a document written by someone to acknowledge the critical points of
current knowledge including substantive findings, as well as methodological and
theoretical contributions to a particular topic. It is a critical and in depth evaluation of
previous research (PRESSMAN, 2005).
3.1. JUSTIFICATION FOR CONDUCTING LITERATURE REVIEW
In order to get an overview of the topic and in case of doing a research work in less time,
literature review is conducted. The overall goal of literature review is to update the
researcher with the current scenario about the topic as well as it forms a basis for another
goal to be achieved by the researcher, such as future research which is basically the
primary research. Literature review produces a critical insight of working approach and the
existing system’s methodologies. The purpose of conducting the literature review in the
context of the proposed system is to summarize the information, ideas and arguments of
others and apart from this, the developer can also provide his critical evaluation on the
existing methodologies.
3.2. LITERATURE REVIEW IN THE PRESENT SCENARIO
E-Freelancing is a very new concept in India and it is prevalent just in the IT Sector
mainly. Nowadays people are getting intended towards this concept and this works on a
single concept:
“ The online market place to bring the contractors and clients under one roof ”.
Though it’s a new concept in India, it has been working in other developed nations from a
longer period. Thus, a large part of the researchers concerned with online project
outsourcing has tended to focus on the qualitative aspects of the project outsourcing being
done online. The literature review mainly tends to focus on the domain research and the

E-FREELANCING
technological feasibility of the system. In case of domain research, the developer have to
state the literal meaning of online project outsourcing, its application and benefits from the
organization as well as developer point of view, and its knowledge sharing aspects.
Throughout the literature review, the developer talks about the system which he is intended
to develop. This system is a website which facilitates online bidding of projects, hiring
freelancers online to get projects done within shorter duration and minimum expense.
Since this concept of online project outsourcing is new in India and prevalent mostly in the
IT sectors, the developer is thus limiting his literature review to activities related to IT
sector only. He is more concerned with the ongoing research and development works
going on in the IT Sector and so, the developer wishes to make such a system which will
provide a helping hand to this industry.
3.3. ACADEMIC RESEARCH
Based upon the preliminary investigation and the existing knowledge, the developer has
summarized and produced an overall summary of his researches and findings. Prior to head
towards the primary and secondary research, the developer has intended to review his
research work with white papers, journals, articles and books related to the existing
system.
3.3.1 WEBSITES
 www.freelancer.com
This is one of the most frequently used website
for online project outsourcing and it works as a very active market place in the current
times. Since this is one of the most commonly used website, it now allows almost all kinds
of projects to be posted on this website.

E-FREELANCING
Figure 1 Statistics from www.freelancer.com
The following two website links also work in similar manner as that of the above website.
Though the later are very new in this field, people register themselves frequently and
project posting is also actively done.
 www.workana.com
 www.oDesk.com
1. W3Schools, 2005, Introduction to ASP.Net [online]. Available from
www.w3schools/asp.net. (Accessed 30th Oct 2013).
2. http://www.ido.net/ShowArticle/54/advantages-of-aspnet-framework. Last accessed 19th
Nov 2013.
3. MSDN Library. (2014). Web Services with ASP.NET. Available:
http://msdn.microsoft.com/en-us/library/ms972326.aspx. Last accessed 23rd Feb 2014.
3.3.2 RESEARCH PAPERS
 Bee Lan Oo, Hing-Po Lo, Benson Teck-Heng Lim, (2012) "The effect of bidding &
success in bidding", Engineering, Construction and Architectural Management, Vol. 19
Iss: 1, pp.25 - 39
3.3.3 BOOKS
 Aggarwal, K.K. Singh, Yogesh. 2008. Third Edition, Software Engineering, New Age
International Publisher, New Delhi.
0
2,000,000
4,000,000
6,000,000
8,000,000
Registered Users Projects Posted

E-FREELANCING
 Daniel MB(ed) 2008, Software Engineering for Modern Web Applications Methodologies
& Technologies, IGI Global, USA.
 John Dingle, 1997. Project Management, Orientation for Decision Makers. Edition.
Butterworth-Heinemann.
 Beaudouin-Lafon, M., Karsenty, A., “Transparency and Awareness in Real-Time
Groupware Systems”, UIST proceedings, 1992, 171-180
3.3.4 JOURNAL AND WHITE PAPER REFERENCES
 Chandrakant Parmar, 2004, Understanding .Net Framework at a glance. From:
http://www.codeproject.com/dotnet/DotNetWhitePaper.asp. Last accessed on 19th Nov
‟.13
 Jakob Nielsen, 1995, Growth of the Web [Online]. From
http://www.useit.com/alertbox/9509.html. Last accessed on 20th Nov‟ 13.
3.4 DOMAIN RESEARCH
3.4.1 WHAT ACTUALLY E-FREELANCING IS?
“A procedure where clients (one who offers the project) post their IT projects online and
set it to bidding, freelancers on the other hand, bid on those projects and the project gets
allotted to the contractor who has set the lowest bid to that project”
The projects are posted online, with all their details and are set to the bidding process.
These projects posted by the clients are visible to the freelancers. Eligible freelancers, the
one who have passed the qualifying eligibility test during profile completion over the
website, are allowed to participate in the secure bidding process. At the end of the process,
the freelancer with the lowest bid over that project is eligible to get the contract of that
project and can contact the respective client.

E-FREELANCING
3.4.2 EMERGENCE OF E-FREELANCING
E-Freelancing belongs to the business industry popularly known as “The Freelance
Marketplace”. According to the research, dating back to the duration of 2001-2006, it was
very difficult for people to work as project freelancer and the same difficulty was faced by
clients who had projects with them to be completed but lack of means to find a suitable
project freelancer hampered their works. Situation changed when this concept of online
project freelancing developed and it became easier for both clients as well as the contractor
to contact each other and get projects done.
3.4.3 AREAS OF OPERATION AND ITS IMPORTANCE
The concept of online project outsourcing being new, it is only prevalent in the IT industry
and it is confined to projects related to IT and Computer based business sectors. The
business mostly includes web-based project developments and providing software
solutions to emerging IT companies.
3.4.4 STATISTICS WORLDWIDE
A large number of people register themselves to the existing systems either as a client or a
contractor. Statistics from one of the existing freelance marketplace Freelance.com says
that since its origin in 2009, about 9.1 Million users have registered themselves to the
website as active participants and almost 5.1 Million projects have been posted and set to
bidding till the current date.
Skills of freelancers mostly in demand can be perceived from the statistics below:
Figure 2 Skills in Demand

E-FREELANCING
Registrations done over the existing system in last two years:
Figure 3 Registered users on elance.com
The statistics below shows the average hours spent per week by the full-time freelancers
worldwide among whom, the freelancers belonging to South America are found the most
active users:
Figure 4 Total time spent by full-time freelancers worldwide per week.
3.4.5 ADVANTAGES OF E-FREELANCING
E-Freelancing acts like a platform for knowledge sharing and providing income source to
those who are not able to come into the lime light of huge IT giants/companies.

E-FREELANCING
The other advantages include:
1) Provides flexible hours of work: The freelancers can work whenever they want. They get
to choose their own hours.
2) Control over Jobs and Clients: Being a freelancer, one gets options to choose whom they
want to work with. If a freelancer doesn’t mesh well with a client’s personality or business
and payment philosophies, he/she can just pass on the opportunity and it is too easy.
3) You’re the Boss: The client as well as the freelancer is the only two people involved in the
deal of the projects. They don’t have to answer to anyone else. Making all the decisions
becomes all sole responsibility of the freelancer and the client.
3.4.6 FEATURES OF E-FREELANCING
Figure 5 Features of E-Freelancing
3.5 FINDINGS- MARKET RESEARCH
In India, no organization/individual is having their website which would facilitate online
project outsourcing. This sometimes stops the Indian freelancers to work for the clients
sitting at a very distant country and they do not participate in this business. Keeping this
fact into consideration, the developer has decided to develop a website called “E-
Freelancing” which will be totally dedicated to the Indian crowd and this will help a lot to
even to the IT companies in India to make use of this website and get projects done in the
minimum possible price.

E-FREELANCING
3.5.1 EXISTING SYSTEM IN THE MARKET
For doing the market research, the following websites has been chosen:
 www.freelanceer.com
Figure 6 Market Research - www.freelancer.com
 www.oDesk.com
Figure 7 Market Research- www.oDesk.com

E-FREELANCING
www.workana.com
Figure 8 Market Research - www.workana.com
3.5.2 COMPARATIVE ANALYSIS OF THE THREE FREELANCE MARKET PLACES
Features FREELANCER WORKANA ODESK
Profile Creation   
Online Test   
Text Chatting No No No
Project Bidding   
Dash Board   No
Discussion Board No No No
Payment mode Online Online Online
Reports No No No
Notifications   
3.5.3 CONCLUSION DERIVED FROM MARKET RESEARCH
After conducting the market research, the developer arrived to the conclusion that the
existing systems do provide project bidding facility but they do not have certain
functionalities which would have increased the websites efficiency. The developer has

E-FREELANCING
decided to implement those missing functionalities in the proposed system and facilitate
the clients and freelancers with more advanced features and experience.
3.6 FINDINGS – TECHNOLOGICAL FEASIBILITY
3.6.1 CURRENT SCENARIO
As already discussed most of the IT companies in India as well as abroad, have lots of
projects which they give either to outside contractors or to some other organization so that
they can save their employee’s time and utilize them in something more productive. These
organizations either post their requirements over their website or use some other web
platforms. Languages like C#, PHP, etc are widely used for creating such websites.
3.6.2 GROWTH OF USE OF COMPUTERS
The users of this proposed system are required to be well versed in computers’ knowledge
and internet use. The system will fail to perform if it is handed over to a person who is not
too much familiar with computers or where internet is not working properly. The
developer, for this reason, has conducted a research to find out the areas where internet and
computers are very much in use and get a clean statistic reports for that. (Bitrebels, 2013)
The following report describes the approximate number of internet users worldwide:
Figure 9 Internet Users in the world
The above report shows that in Asia region, up to last year’s survey, the number of internet
users have increased to a great extent. This growth rate is so fast that, by April 2014, the

E-FREELANCING
number of internet users in Asia will touch the 1300 million mark. Thus, the developer
does not have to worry about the computer and internet availability even in distant and
remote areas of India.
Some more research related to internet and social networking site’s users in India:
Country Estimated
Population (Year
2013)
Internet Users
(Year 2000)
Internet Users
(Year 2012)
Facebook
Users
(Year 2013)
INDIA 1,253,873,983 5,000,000 137,000,000 80,566,680
3.6.3 WEB-DEVELOPM ENT PLATFORM
The developer had options to choose the web-development platform which could
be implemented during the system development process. The various options of
web-development platforms were:
1) PHP
2) ASP
3) ASP.NET
4) JSP
ASP.NET with C# is the most suitable language for the system development.
Some of the features availed by ASP.NET with c# are as follows:
Stylish Object oriented design: ASP.NET provides bunch of standard controls and data
controls which enables project developers to design their systems in a very efficient
manner and give the best possible professional appearance to the interface.
Protection and efficiency: Coding behind the pages is easier in ASP.NET which can be
achieved by double clicking the controls over which the command is to be applied. This
provides fast coding facility and security related problems can easily be identified and
safeguarded. This increases the efficiency of the system and makes it error free to a great
extent.
Exception handling: Exceptions can be handled very well in ASP.NET and it is not a
tough task for an efficient developer to identify the exceptions in a program and apply

E-FREELANCING
exception handling concepts to it.
Easy error elimination: During the development process, the on time debugging facility
can be used to identify the errors in the program and resolve them.
Flexibility and power: ASP.NET supports most of the languages. So, working on this
platform is comparatively easier than others mentioned above. The developer can design
the system and do the programming in the language most preferred by them. This makes
ASP.NET the most flexible web-development platform.
3.6.4 DATABASE ENGINE SELECTION
Though the IT industry has provided lots of database engines which can be efficiently
attached to any kind of systems, the security level and their utility differs at some points.
The database engines that can be used for the proposed system are:
1) Microsoft Access
2) Oracle
3) MySQL
4) SQL Server 2008
The developer has undergone a detailed research and has decided to implement SQL
Server 2008 in the proposed system. SQL Server 2008 is able enough to provide more
reliability, data integrity, smooth performance, and vast scalability as compared to other
database systems. Also, apart from these, this is very secure and protection of data is
promised in SQL Server 2008.

E-FREELANCING
CHAPTER 4- RESEARCH METHODS
4.1 PRIMARY RESEARCH
To gather the preliminary information in order to complete the requirement’s analysis and
give a start to the system designing, the developer conducted a primary research. Even
though the literature review and the academic research provided sufficient points favoring
the technical and domain study, it is necessary to get the end-users involved during the
development of the system.
For primary research, two different fact-finding techniques such as questionnaire and
interview were incorporated. The developer prepared a questionnaire to get required
answers to few questions which could be analyzed later. An interview was also conducted
to explore and analyze in detail the response of people belonging to a selected group.
Figure 10 Research Plan.
4.1.1 QUESTIONNAIRE
Formally, a Questionnaire can be defined as: “A form containing a set of questions,
especially one addressed to a statistically significant number of subjects as a way of
gathering information for a survey”. It consists of a list of a research or survey questions
which are asked to respondents, and designed to extract specific information. It serves four
basic purposes:
 Collect the appropriate data
 Make data comparable and amenable to analysis
 Minimize bias in formulating and asking questions

E-FREELANCING
 Make questions engaging and varied
Questionnaires are restricted to two basic types of questions:
Closed ended- the researcher provides a list of suitable responses or options for the
respondent to choose from.
Open ended- the researcher doesn’t provide the respondents with any answer set from
which to choose. Rather the respondents are asked to answer in their own words.
The developer has decided to use only closed-ended questions so that this won’t require
much time of the respondents and data collection will be easier and faster. The prepared
questionnaire was distributed to 10 individuals for accessing varying views about the
system. The questions were prepared keeping in consideration the system functionalities
and user requirements.
Note: The prepared questionnaire has been put inside the appendices. Please refer to
APPENDICES SECTION A for the prepared questionnaire with justification.
4.1.2 INTERVIEW
Face -to -face interviews have a distinct advantage of enabling the researcher to establish
rapport with potential participants and therefore gain their cooperation. These interviews
yield highest response rates in survey research. They also allow the researcher to clarify
ambiguous answers and when appropriate, seek follow-up information.
The main motive of the developer behind conducting the interview is to obtain a detailed
understanding about the current system and the technology that are currently being used in
system development so that he can develop the proposed system in a more efficient
manner for the target audience and fulfill their requirements.
Note: The prepared interview question set along with proper justification to all questions
has been put under APPENDICES SECTION B. Please refer appendices for more
details.

E-FREELANCING
4.1.3 OBSERVATION
 Observe how people make calculations and answer selection during an online test.
Justification: There are lots of people of preparing for online tests either for some exams
or they just do it for gaining knowledge. That group of people can be observed facing
different levels of questions and their reaction to every question either simple or hard will
be observed and the developer can analyze those observations to frame the questions he is
planning to put in the system’s online test procedure.
 Observing the features and technologies that IT professionals use to implement advanced
features in their systems.
Justification: The developer will be able to keep himself updated with the latest trend of
technologies and hence, it will be helpful to him in developing the desired system properly.
 Observing various bidding process going around in the market, either it be governmental
or private.
Justification: This will help the developer to understand how bidding process goes on and
what necessary rules are to be followed while implementing the bidding process in the
website.
4.2 SECONDARY RESEARCH
In academic research, the developer had to undergo passive studies which were conducted
from the available resource such as books, internet, journals based on web-technology and
the project related topics.
4.2.1 TECHNICAL RESEARCH
4.2.1.1 SYSTEM DEVELOPMENT METHODOLOGY
A system development methodology refers to the framework that is used to structure, plan,
and control the process of developing an information system. It can be defined as a
collection of procedures, techniques, tools and documentation aids which will help
developers in their efforts to implement a new system. For the successful implementation
of a project, a well-organized and systematic approach is very essential (Bentley, 2002).

E-FREELANCING
4.2.1.2 NEED FOR A METHODOLOGY
Apart from the above purpose that it achieves, it offers various tools and techniques to
assist in analysis, design and testing in terms of detailed design of software, data flow
charts and database design. It helps to reduce the risks and also helps to minimize the
complexities of the project. It provides the developers a structured approach for project
implementation.
4.2.1.3 METHODOLOGY FOR WEB-BASED SYSTEMS
It is very important to choose the right development process model because the
development of the system and the quality control activities that need to be performed in
project is specified by the system development methodology chosen. The types of system
development methodology are that are:
1) Waterfall Model
2) Spiral Model
3) WISDM
WATERALL MODEL
Project is divided into sequential phases, with some overlap and splash back acceptable
between phases. Emphasis is on planning, time schedule, target dates, budgets and
implementation of an entire system at one time. Tight control is maintained over the life of
the project through the use of extensive written documentation. The waterfall model
ensures complete specification, user involvement and training.
Figure 11 Waterfall model

E-FREELANCING
Disadvantages of Waterfall Model (Bentley, 2002):
 The major weakness of waterfall model is its inflexibility to accommodate varying
requirements.
 Slow, costly and cumbersome due to significant structure and tight controls.
 Difficult to respond to changes.
 Though this model is very helpful in measuring the progress of the system, but it fails to
identify all the problems until the system testing is raged.
 Needs are often discovered during design and coding.
Why this model is not suitable?
This model is very old and its inflexibility does not allow accommodating the new
requirements that erupt during the project development at a later stage. It fails to make
commitment at every stage of project development and also it is very difficult to entertain
any changes in the user requirements as the developer does not have complete set of
requirements prior to the start of the development process.
SPIRAL MODEL
The spiral model acts like an extension to the waterfall model as it introduces prototyping
in it. Spiral model is preferred instead of waterfall model for large and complicated
projects. Apart from that, it addresses to some of the implementation issues which affect
the waterfall methodology.
Therefore, we consider the spiral model to be more effective than any other methodologies.
It is both a prototype and incorporates it into an iterative framework that more reflect the
real world. The requirements are defined in the best possible way and a prototype will be
created to identify the associated risks with the project (WHITTEN J, 2002).
The spiral model has four phases:
1. Planning
2. Risk Analysis
3. Engineering
4. Evaluation

E-FREELANCING
A software project repeatedly passes through these phases in iterations (called Spirals in
this model). The baseline spiral, starting in the planning phase, requirements is gathered
and risk is assessed. Each subsequent spiral builds on the baseline spiral.
 Requirements are gathered during the planning phase.
 In the risk analysis phase, a process is undertaken to identify risk and alternate
solutions. A prototype is produced at the end of the risk analysis phase.
 Software is produced in the engineering phase, along with testing at the end of the
phase.
 The evaluation phase allows the customer to evaluate the output of the project to date
before the project continues to the next spiral.
Figure 12 Boehm-Spiral-Model
REASONS FOR NOT USING WISDM
It is mix of common web development techniques, which emphasizes on graphically
intense hypermedia, together with traditional information system development
competencies in DB and program design. Though WISDM appears to be the best suited
methodology for website development, seeing from the Final Year Project’s point of view,
the developer is not comfortable in using WISDM because prior to the implementation of
the project, the developer will have to conduct various forms of research activities, and

E-FREELANCING
need a proper planning to be done. All this can be only done if the developer follows the
SPIRAL model.
4.2.1.4 COMPARISION OF METHODOLOGIES AGAINST CRITERIA
CRITERIA WATERFALL SPIRAL WISDM
Project Management **** ***** ***
Risk Management *** **** ***
Web Framework Support *** ***** **
Object Oriented Programming **** **** **
Testing **** ***** *****
Heavy Documentation *** **** *****
Outcome at each stage **** ***** **
Table 3 Comparison between methodologies
4.2.1.5 CONCLUSION OF METHODOLOGY SELECTION RESULT
The developer had to undergo a lot of research work and after that he came to the
conclusion that
Spiral Model has been the most suitable model for the project development. The above
comparison between the methodologies clearly shows that spiral model is the best
methodology that can be applied in the project development process.
4.2.1.6 WEB-DEVELOPMENT PLATFORM SELECTION
The developer had several options of programming languages to choose from for the
development of the system. This also required a research so that the most suitable language
should be selected and implemented at the time of project development.
PHP
PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. PHP code is interpreted by a web server with a

E-FREELANCING
PHP processor module, which generates the resulting web page: PHP commands can be
embedded directly into an HTML source document rather than calling an external file to
process data. It has also evolved to include a command-line interface capability and can be
used in standalone graphical applications. PHP provides extensive database support.
Programmers can leverage this body of existing code to quickly put together advanced
applications.
Disadvantages of using PHP:
PHP suffers certain security flaws due to unknown vulnerabilities.
ASP.NET
ASP.NET stands for Active Server Pages .NET and is developed by Microsoft. ASP.NET
is used to create web pages and web technologies and is an integral part of Microsoft's
.NET framework vision. As a member of the .NET framework, ASP.NET is a very
valuable tool for programmers and developers as it allows them to build dynamic, rich web
sites and web applications using compiled languages like VB and C#.
It allows developers to build very compelling applications by making use of Visual Studio,
the development tool provided by Microsoft. ASP.NET is purely server-side technology.
Advantages that ASP.NET offers over other web development models:
 ASP.NET reduces the amount of code required to build large applications.
 It provides efficient performance by providing early binding, just in-time compilation,
native optimization, and caching services right out of the box.
 ASP.NET is a purely server-side technology. Thus, the codes generated by ASP.NET
get executed on the server before it is sent to the browser.
 The web server continuously monitors the pages. Components and application running
on it. If any memory leak or infinite loops are noticed, it immediately destroys those
activities and restarts itself.

E-FREELANCING
 ASP.NET is language independent. Thus, it allows choosing the language that best
applies to the system development.
 Rich controls. ASP.NET comes with the huge collection of rich server and client side
controls that you can use to develop interactive grids, wizards, calendars, etc. What’s
great about these controls is that most of them can be used right away.
 ASP.NET pages are compiled.
 Code-behind logic
 It is browser independent
 Web-forms can be created very easily
ASP.NET with c# (DIETEL, 2011)
C# was intended by Microsoft to be a part of the ASP.NET framework. C# is suitable for
writing applications for both hosted and embedded systems, ranging from the very large
that use sophisticated operating systems, down to the very small, having dedicated
functions. C# is one of the programming languages designed for the Common Language
Infrastructure.
Some of the features availed by ASP.NET with c# are as follows:
 Stylish Object oriented design
 Protection and efficiency
 Data types
 Namespaces
 Exception handling
 Easy error elimination
 Flexibility and power

E-FREELANCING
4.2.1.7 COMPARISION BETWEEN WEB-DEVELOPMENT PLATFORMS
Features ASP.NET ASP PHP JSP
Platform Windows Windows Any JSP
Platform to run IIS IIS PHP5 Apache
Response Time High Low High High
Multiple Language Support Yes No No Yes
Execution of pages Compiled Interpreted Interpreted Interpreted
Object oriented features Yes No Yes Yes
Advanced tool support Yes No No Yes
Code cleanness Yes No No Yes
Execution time High Low Low High
Debugging Easy Difficult Difficult Easy
HTML/XHTML Easy Easy Easy Easy
Implementation of AJAX Easy Low Easy Easy
AML Easy Difficult Easy Easy

Table 4 Comparison between Web Development Platforms
4.2.1.8 WEB DEVELOPMENT LANGUAGE CHOICE
The developer has decided to use ASP.NET with c# as the web development platform that
would be implemented during the system development process.
4.2.1.9 DATABASE MANAGEMENT SYSTEM RESEARCH
The reason behind conducting this research is to decide to choose the better database
system so that the developer feels comfortable in providing complete data integrity and
security. This gives a satisfaction to the developer as well as to the other users of the
system too. For conducting this research, the developer has selected database systems like
Microsoft Access, MySQL, Microsoft SQL Server and Oracle. Their implementation,
advantages and disadvantages has been taken into consideration so that selection of the
most suitable DBMS becomes easier.

E-FREELANCING
Microsoft SQL Server
Microsoft SQL server is the most stable, fast, and extremely popular but affordable
database engine. This is tightly integrated with the Windows Server security settings. This
allows the database engine to get installed quickly over the existing server. It also
facilitates easy configuration of maintenance plans and backups for which no custom
scripts are required. (CONNOLLY, 2004)
Due to these reasons, people consider MS SQL Server to be the most secure database
platform.
Benefits for using Microsoft SQL Server 2008 over other database engines:
 Reliability: Unlike MS Access, with SQL Server, the clients do not deal with the tables
directly but with an intelligent data manager on the server. This in turn reads and writes
data from and adds to the tables. Data do not get hampered or affected in any way due to
power supply disconnection or network failure.
 Data Integrity: The concept of using “triggers” in SQL Server has enhanced the data
integrity parameter. Triggers can be added whenever a record is added, updated or deleted.
This occurs at the table level and thus, cannot be forgotten about, ignored by the client
machine.
 Performance: Being highly optimized, SQL server can usually perform the required data
filtering much more quickly than any other database engine.
 Network traffic: SQL Server greatly reduces the network traffic in a client/server
scenario, often by many orders of magnitude. This not only improves network reliability
but also improves the performance of other software, as there is less traffic on the network.
 Scalability: MS Access, being a file server system, has been designed for small work
groups and in scalable to perhaps 10 concurrent clients. With SQL Server client/server
architecture, thousands of concurrent users can be supported without significant
performance degradation.

E-FREELANCING
Conclusion: Seeing the facts about the Microsoft SQL Server, the developer has decided
to use this database engine for the system development.
4.2.1.10 CLIENT SERVER ARCHITECTURE RESEARCH
(AGGARWAL, 2004) Client-server architecture can be referred to as a computer network
architecture in which many clients (remote processors) request and receive service from a
centralized server (host computer). The proposed system is using a client-server
architecture where one system will be acting like a client and the other connected PC will
be the server.
One-tier Client Server Architecture
If the developer uses this architecture form, he will have to install the database on every
client machine and hence, data integrity will be lost completely. Therefore, the developer
denies using this architecture system.
Two-tier client server architecture
In two-tier client/server architecture, users execute the activities on a local client which
connects over a network to the server. The client application can learn both business logic
as well as the code to display the result to the user.
Three-tier Client Server Architecture
By adding an intermediate tier to the client/server architecture, one can easily create a
three-tier architecture where the clients implements the presentation logic and the servers
implement the business login for the system.
Figure 13 Three Tier Client Server Architecture
The developer has decided to use the three-tier client-server architecture.

E-FREELANCING
4.2.1.11 MODELLING LANGUAGE RESEARCH
UML (UNIFIED MODELLING LANGUAGE)
The UML is a standardized, general-purpose modeling language in which the behavior or
functions of any system can be modeled using this language. It includes a set of graphic
notation techniques which can be used to create visual models of Object-oriented software
intensive systems. UMLs provide a very standardized way to visualize a system’s
architectural blueprints. (BOOCH, 1998)
It can be used throughout the SDLC and across different technologies. This language
specifies, visualizes, constructs, and documents the artifacts of software systems.
4.2.2 DEVELOPMENT PLAN
This project will be done using the SPIRAL methodology where the whole project will be
broken down into different modules and will be done according to the different phases of
the methodology.
Project Start date: 16th
August 2013
Project end date: 30th
April 2014
Total Duration for project completion: 36 Weeks 4 days
1. Project Definition
Duration: 2 week
Tasks: The project definition includes the following tasks to be completed:
 Generation of idea related to the project
 Selection of the project’s title
 Feasibility Studies
 Draft Proposal Form
2. Project Planning
Duration: 4 weeks
Tasks: Project planning requires the following tasks to be covered one after the other:
 Schedule and Time Estimation
 Gantt Chart
 Project Proposal Form

E-FREELANCING
3. Requirement Analysis
Duration: 6 weeks
Tasks: The Requirement Analysis phase is to be completed in order to specify thee goals,
resources to be contacted, provide specifications related to the techniques and
functionalities and a detailed analysis of all types of associated risks.
 Identify project specifications
 Project Background
 Resources required
 Techniques to be learnt
 Goals and Objectives
 Determine System Functionalities
 Identify scope of research
 Project Specification Form
 Investigation ad Research
 Analysis
 User Modeling and Profiling
 Domain analysis
 System analysis
 Risk analysis
4. System Design
Duration: 4 weeks
Tasks: This phase is the start of the implementation phase where the system’s design and
its work flow is decided and the interface, functionality and interactivity is being specified.
 Abstract Interface Design
 Screen layout
 Content Design
 Interactivity Design
 Functionality Design
5. Prototyping
Duration: 5 weeks
 Creating Prototypes
 Evaluate Prototype feedbacks
6. Production and Implementation
Duration: 5 weeks
 Coding for several functions
 Payment gateway Integration

E-FREELANCING
 Implementation of online test
 Implementation of Discussion Board
 Implementation of chatting facility
 Implementation of Online bidding and project allocation to freelancer
7. Testing and Evaluation
Duration: 6 weeks
 Prototype Evaluation
 Test Plans
 Unit Testing
 Integration Testing
 System Testing
 Critical Evaluation
8. End of the Project
Duration: 4 weeks
Tasks: This involves only two tasks which lead to the project completion and its end.
 Submission of the finished product
 Presentation of the project to the Project Supervisor and Advisor.
4.2.3 GANTT CHART
[Note: The Gantt chart is attached in the appendices. Please refer to Appendix K for the
Gantt chart of the project]

E-FREELANCING
CHAPTER 5- ANALYSIS
For conducting the primary research, the developer has used the two fact-finding
techniques:
1) Questionnaire
2) Interview
3) Observation
5.1 CONCLUSION FROM ANALYSIS OF QUESTIONNAIRE
1. People have sufficient idea of online bidding of products either it be any project or any
property. Only few persons were found who knew nothing about this process but had
computer related basic knowledge.
2. It was found that nowadays people from all age group starting from 13 yrs of age are active
on social networking sites.
3. The teenagers of present and the youngsters both working in private/governmental jobs
often face online exams and objective questions are preferred by most of the users.
4. People have trust in project outsourcing as it saves a lot of time which can further be
implied to other important activities. For this people look for domain specific and skilled
developers and freelancers who can make their project in the lowest possible amount.
5. Clients mainly give their minor projects in outsourcing and concentrate on their major
projects by themselves or hire developers personally without going for open project
bidding. In most of the scenarios, web and database related projects are given for
outsourcing.
6. Instant messaging and text chatting are used mostly for better communication. Email is not
used as a mode of communication but heavily used as file transfer medium.
7. Online project bidding should not be open for longer duration. It should last for a
maximum of two days and not less than that.

E-FREELANCING
8. Questions asked in online test should be concise and clear. It should not be tough and no
one prefers to do lengthy calculations during an online test.
9. Online payment using debit/credit card is the most preferred mode of payment by most of
the users. Very few prefer cheque or cash payments.
[Note – Detailed Analysis of Questionnaire can be referred from Appendix-C]
5.2 CONCLUSION FROM ANALYIS OF INTERVIEW
1) Interviewees were found to be more inclined towards having less duration for a bidding
process to continue. It can be easily concluded from their response that they wanted bid on
projects to be closed by the completion of the first two days of posting of the project.
Longer duration may lead to lack of interest and time consuming.
2) Clients basically look for freelancers who can develop their minor level projects and those
mainly fall in the range of low bid projects. IT companies look for projects which can be
completed in short time duration.
3) A project developer should be highly skilled and having good knowledge about the
technology that is to be used in developing the project. Clients look for freelancers having
good knowledge of web designing and database is the most essential requirement by all
clients.
[Note – Detailed Analysis of Interview Questions can be referred from Appendix-D]
5.3 CONCLUSION FROM ANALYSIS OF OBSERVATION
1) The developer observed that people sitting for online test have to make quick decisions in
selecting the correct answer out of the options provided. Online exams mainly follow the
pattern of objective type questions and not subjective questions because lengthy
calculations or subjective work leads to time scarcity by the end of the exam.
2) IT professionals are highly skilled and trained to work on a particular type of software
development tools. Sometimes they even add plug-ins to their tool to use enhanced
features.

E-FREELANCING
3) Bidding process in private companies is similar to that of tender release and acceptance in
the government and semi-government sectors. The process has certain rules already
defined which are mandatory to be followed by the participants of the bidding.
[Note – Detailed Analysis of Observation can be referred from Appendix-E]
5.4 RISK ANALYSIS
(HERTZ D. B., 1983)
IMPACT CATEGORIES PROBABILITY CATEGORIES
Level Of Consequences Range Probability Range
Negligible 0.0-3.0 Low 0.0-0.3
Marginal 3.1-7.0 Medium 0.3-0.7
Critical 7.1-9.0 High 0.7-0.9
Catastrophic 9.1-10.0 Very High 0.9-1.0
Calculation of Risk Exposure to the project:
Risk Exposure = Impact of Consequences * Probability
RISK PRIORITY CHART
Table 5 Risk Analysis
0
1
2
3
4
5
6
7
8
Requirement
Change
Hardware Failure New Technology Developer's Health
Issues
Unclear
Requirements

E-FREELANCING
RISK ASSESSMENT RISK CONTROL
No. Risk
Identification
Risk Analysis Risk
Priority
Risk Management
Probability Impact Exposure
1 Due to New
Technology
0.7 7 4.9 1 A proper training should be conducted
prior to development phase
2 Requirement
Changes
0.5 8 4.0 2 Proper procedure should be defined to
handle requirement changes
3 Unclear
Requirements
0.4 7 2.8 3 Requirement analysis should be done
and performed well
4 Hard/Softwar
e Failure
0.4 9 3.6 4 Back up of data should be maintained
regularly.
5 Developer’s
Health Issues
0.3 9 2.7 5 Weekends can be utilized for overtime
work. Working conditions should be
comfortable since beginning.
Table 6 Risk Assessment & Control

E-FREELANCING
CHAPTER 6 - SYSTEM DESIGN
After analysis developer has gathered sufficient information to model the system. It
provides an appropriate guidance to system implementation. The main purpose of system
design is to precisely build the system based on design requirements.
6.1 DESIGN METHODOLOGY SELECTED
There are basically two design methodologies:-
1. Function Oriented Design
2. Object Oriented Design
6.1.1 JUSTIFICATION FOR SELECTION OF OBJECT ORIENTED DESIGN
From the requirements gathered by the developer, it is clear that system needs to be
modeled in the form of classes and objects in order to achieve the technical goals for this
project. As a result, the developer concludes that E-Freelancing needs to be designed using
object oriented design principles. In order to implement it the developer opted to make use
of UML (Unified Modeling Language 2.0). (BOOCH, 1998)
6.2 DESIGN STRATEGY USED
Requirement Analysis & Modelling
Use Case Diagram Activity Diagram Sequence Diagram
Actual Design & Modelling
Class
Diagram
Architecture
Design
Interface
Design
Navigation
Design
Database
Design
Figure 14 Design Strategy Used

E-FREELANCING
6.2.1 USE CASE DIAGRAMS
USE CASE DIAGRAM AND SPECIFICATION: E-FREELANCING
Admin
Register/Login
*
*
Reports Management
Payment
*
*
*
*
Project
Creation/Updation/Deletion
*
*
Online
Certification Exam
Online Project
Binding
Chat
*
*
*
*
Client
*
*
*
*
*
*
*
*
*
*
Freelancer
*
*
*
*
*
*
*
*
*
*
Discussion Forum
*
*
*
*
*
*
Figure 15 Use Case - E-Freelancing

E-FREELANCING
Use Case Name: Client
Client
Post Project
*
*
Payment via Credit
Card
View Reports
*
*
*
*
Login
*
*
View Project
Register
Payment via Debit
Card
«extends»
Payment
«extends»
*
*
<<include>>
<<include>>
<<include>>
Select report type
View Bid Details
*
*
Chat with
Freelancer
«extends»
Check notification
*
*
«uses»
Read
Delete
«extends»
«extends»
Figure 16 Use Case- Client

E-FREELANCING
USE CASE NAME: FREELANCER
Freelancer
View Project
*
*
Browse Project
View Reports
*
*
*
*
Login
*
*
View Profile
Register
Complete
Certification Test
Bid on Project
«extends»
*
*
<<include>>
<<include>>
<<include>>
Select report type
See project
allotment report
*
*
Chat with Client
«extends»
Check notification
*
*
Read
Delete
«extends»
«extends»
<<include>>
<<include>>
Figure 17 Use Case- Freelancer

E-FREELANCING
6.3.1 SUB USE CASES
Use Case Name: Registration Use Case ID: UC- eF1
Scope: E-Freelancing
Level: User Goal
Primary Actors: Clients, Freelancers
Actors and description
Clients Clients register into the system so that they can post projects and
set them to online bidding.
Freelancers Freelancers register into the system so that they can browse for
projects available and place Bid on them and get the contract of
that project upon bid completion corresponding to the lowest
bid amount they placed.
Precondition  The users should have am email ID which will be used to send
password upon registration.
 The system should be connected to internet.
Post Condition Registration is performed and the user details are stored in the
database of this system.
Success Guarantee: The users can use the Login ID and password sent to their
email account to log in to the system.
Main Success Scenario(Basic Flow):
1. 1. The client/freelancer opens the Registration page of this web based application.
2. The primary actors then enter their details and other credentials.
3. The details provided by the user are validated by the system.
4. After successful details entry and subsequent validations, the system creates the account of
the users
5. The users receive their password via email at the same time which can be used to login to
the system.
Alternate Flows/Extensions:
At any instance, if system fails:
1. The user will have to restart the system and open the registration page of the system.
2. In case, system fails, the user will lose all the registration details provided by him/her and the
details have to be entered again.
At any instance, if the server in which the web based application is stored fails:

E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION

E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION

Similar to E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION (20)

Recently uploaded

Recently uploaded (20)

E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATION