Development of Web based Business Environment for Testing outsourcing

(Test4Value)

ABSTRACT

This is B2B web based application, which is focusing on new method of out sourcing the testing
services business. This application focus on “pay per bug” model. In this model customer pays to
testing services organization per bug basis. The focus is towards the development of Business
environment, which will be an interface between developer and tester.

To improve quality when building a software system and ensure the delivered
product satisfies business user’s operational needs, independent verification and validation is
being recognized as an important step in the software development process. The verification and
validation is a series of technical, managerial and financial activities performed by resources
independent of the project team to provide management with an assessment of the on-going
health of a project.
SYSTEM ANALYSIS

INTRODUCTION

After analyzing the requirements of the task to be performed, the next step is to analyze the
problem and understand its context. The first activity in the phase is studying the existing system
and other is to understand the requirements and domain of the new system. Both the activities are
equally important, but the first activity serves as a basis of giving the functional specifications
and then successful design of the proposed system. Understanding the properties and
requirements of a new system is more difficult and requires creative thinking and understanding
of existing running system is also difficult, improper understanding of present system can lead
diversion from solution.

EXISTING SYSTEM:

In the traditional way, the Development organization gives project to the Testing organization.
Here the Testing organization sets an amount for that project, and finds out each bug with in the
time limit.

LIMITATION OF EXISTING SYSTEM

In case, the Development organization give one project to Testing organization, The Testing
organization fix an amount for that project and finds out the bug. Even if they don’t find any bug
still the Development organization should pay the amount for that desired project.
PROPOSED SYSTEM:

In this “TEST4VALUE” the customer, i.e. Development organization will pay the amount per
bug basis. That means, After getting a project from Development organization, the Testing
organization find out the bug. At the same time the testers raise the bugs into their corresponding
fields in this application. And the Development organization can approve (or) reject the bug. And
give the amount for the approved bugs only.

ADVANTAGES OF PROPOSED SYSTEM

 It provide independence, specialization, resource leverage and cost benefits.

 Customer pay the money per bug basis.

 Customer can easily to understand, which type of errors are in that project.

 Customer can approve (or) reject the bug through online.

 Testing organization can set different cost for each type of bugs and

their priority like low, medium and high, and also set the “Re-Testing” cost.

 Tester can upload the full description of the bugs.

SYSTEM DESIGN:

INTRODUCTION

Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first step
in the development phase for any engineered product or system. The designer’s goal is to
produce a model or representation of an entity that will later be built. Beginning, once system
requirement have been specified and analyzed, system design is the first of the three technical
activities -design, code and test that is required to build and verify software.
 Fig 1. Overall View of the modules

MODULES

TEST4VALUE contains 5 modules.

1. Delivery Manager.

2. Project Manager.

3. Tester.

4. Customer.

5. Customer Developer.

Fig 2: Login form

Fig 3: Delivery Manager
Fig 4: Project manager

Fig 5: Tester

Fig 6: Customer
 Fig 7: Customer Developer

E-R DIAGRAMS

• The relation upon the system is structure through a conceptual ER-Diagram,

which not only specifics the existential entities but also the standard relations
through which the system exists and the cardinalities that are necessary for the
system state to continue.

• The entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling activity
the attributes of each data object noted is the ERD can be described resign a data
object descriptions.

• The set of primary components that are identified by the ERD are

 Data object  Relationships

 Attributes  Various types of indicators.

 VERIFIED
DETAILS

F ProjectId
K The primary purpose of the ERD is to represent data
F DefectID objects and their relationships
K
VERIFIED VALUE

Severity PK SI.No
USER LOGIN
Type ProjectID
P Username
K FK
Approved
Password Cost
ApprovedDate
Role Verified1
Name Verified1Date
Email Verified2
Phoneno Verified2Date BUGTYPE
Status Verified3 FK SI.No

Verified3D BugType
COMPANY

P CompanyID Sort
K

CompanyName

Address
PROJECT
City
P ProjectID
DEFECT
State K TEST VALUE
F ProjectId
Country ProjectName FK ProjectID
K
PinCode CompanyID Type
P DefectID
K Domain
Severity
Type Pname
Cost
Summary Pemail
Severity Pphone
Description Pmobile USER IN
PROJECT
Comments Pfax
Username
Status Sname
Role
ReportedOn Semail
FK ProjectID
Attachment Sphone
FileSize Smobile
ContentType Sfax
FileName
CLASS DAIGRAMS:
DATABASE DESIGN:

A database management system consists of interrelated data and set of programs to access that
data. The collection of record usually referred to as the database. In this project the primary goal
of a “SQL SERVER 2008” is to provide an environment that is both convenient and efficient to
use in retrieving and storing database information.

USER LOGIN:

S.No COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. Username Varchar 50 NO
(primary key)

2. Password Varchar 50 NO

3. Role Varchar 20 NO

4. Name Varchar 100 NO

5. Email Varchar 30 NO

6. Phoneno Varchar 30 NO

7. Status Bit - NO

VERIFIED DETAILS:
S.NO COLUMN NAME DATA TYPE SIZE ALLOW
NULLS
1. ProjectID Int - NO
2. DefectID Int - NO
3. Severity Varchar 50 NO
4. Type Varchar 20 NO
5. Approved Bit - YES
6. ApprovedDate Datetime - YES
7. Verified1 Bit - YES
8. Verified1Date Datetime - YES
9. Verified2 Bit - YES
10. Verified2Date Datetime - YES
11. Verified3 Bit - YES
12. Verified3Date Datetime - YES

VERIFIED VALUE:
S.NO COLUMN NAME DATA TYPE SIZE ALLOW
NULLS

1. Slno Int - NO

2. ProjectID Int - NO

3. Cost Float - NO

BUG TYPE:

S.NO COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. Slno Int - NO

2. BugType Varchar 50 NO

3. Sort Int - NO

COMPANY:

S.NO COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. CompanyID BigInt - NO
(primary key)
2. CompanyName Varchar 100 NO

3. Address Varchar MAX NO

4. City Varchar 50 YES

5. State Varchar 50 YES

6. Country Varchar 50 YES

7. PinCode Varchar 20 YES

DEFECT:

S.NO COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. ProjectID Int - NO

2. DefectID Int - NO
3. Type Varchar 10 NO

4. Summary Varchar MAX NO

5. Severity Varchar 50 NO

6. Description Varchar MAX YES

7. Comments Varchar MAX YES

8. Status Varchar 50 NO

9. ReportedOn Detetime - NO

10. Attachment Image - YES

11. FileSize BigInt - YES

12. ContentType Nvarchar 100 YES

13. FileName Nvarchar 50 YES

PROJECT:

S.NO COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. ProjectID(prim. Key) Int - NO

2. ProjectName Varchar 100 YES

3. CompanyID Int - YES

4. Domain Varchar 20 YES

5. Pname Varchar 100 YES

6. Pemail Varchar 50 YES

7. Pphone Varchar 50 YES

8. Pmobile Varchar 50 YES

9. Pfax Varchar 50 YES

10. Sname Varchar 50 YES

11. Semail Varchar 50 YES

12. Sphone Varchar 50 YES

13. Smobile Varchar 50 YES

14. Sfax Varchar 50 YES

TEST VALUE:

S.NO COLUMN NAME DATA TYPE SIZE ALLOW

NULLS

1. ProjectID Int - YES

2. Type Varchar 20 YES

3. Severity Varchar 20 YES

4. Cost Float - YES

USER IN PROJECT:
S.NO COLUMN NAME DATA TYPE SIZE ALLOW
NULLS

1. Username Varchar 50 NO
2. Role Varchar 50 NO

3. ProjectID Int - NO

DATABASE TABLES: