Continuing Education Program

Centre for Computing and Information Technology

Faculty of Engineering – University of Indonesia
Tel: 021-7863508 Mail: ccit.@eng.ui.ac.id

VMobil

Created By:
Anjani Muhamad Sodik
Muhammad Rayi Hafiza

Class:
4SC3

Faculty:
Mr. Riza Muhammad N
 PROJECT ON
VMobil

Prepared by:

Name:
1. Anjani Muhamad Sodik
2. Muhammad Rayi Hafiza
 VMobil
(Project Title)

Batch Code : 4SC3

Start Date : June 27th, 2016
End Date : July 14th, 2016
Name of Coordinator : Riza Muhammad N
Name of the Testers :
1. Anjani Muhamad Sodik
2. Muhammad Rayi Hafiza

Date of Submission : July 14th, 2016

 CERTIFICATE

This is to certify that this report titled VMobil embodies the original work done by

Anjani Muhamad Sodik and Muhammad Rayi Hafiza, in partial fulfillment

of their course requirement at NIIT.

Coordinator:
Riza Muhammad N
 INTRODUCTION

VMobil is traditional game. This game should avoid the vehicle from the opposite
direction. This game will continue to run until the player hit the other car from the other
direction. Our project is a Windows Form game that should enable Player to:
 Play Game
 Check High Score
 Change Color of the Car.
In completing this project, the developer have benefited a lot from the feedback and
suggestions that given to us by Mr. Riza Muhammad N and others.
 IDEAL TEST ENVIRONMENT FOR VMobil

Describe the ideal software and hardware requirements to test the VMobil. The
details of the test environment is attached.
 TESTING TECHNIQUES IMPLEMENTED IN
VMobil

Describe different types of testing techniques that can be implemented to test the VMobil.
The suitable testing techniques can be selected from the following techniques to test the
website application:
 Structural Testing Technique(White box):
 Load/Stress Testing (demands resource in quantity, frequency, or volume)

 Compliance Testing (accordance with IT standards, procedures, and

guidelines)

 Functional Testing Technique(Black box):

 Requirements Testing (performs correctly over a continuous period of time)
 Regression Testing (a change in one segment, affect the other segment)
 Error-handling Testing (anticipate what can go wrong with the system)
 Intersystem Testing (ensure interconnection between apps function
correctly)

The tables of the testing techniques are attached.

 TYPE OF TESTING TOOLS FOR VMobil

Efficient testing of an application necessities the use of some testing tools. These tools
perform various activities and are applicable in all the phases of the system development
life cycle. Describe the testing tools applicable for VMobil that can be selected from
the Unit testing tools and Manual testing tools.
Unit testing tools is a test which is using a Test project in visual studio. The idea of unit
testing tools is to compare between the expected output and the actual output from the
software. If the both output is not match, then it will be count as a defect.
 RISKS TO VMobil DURING TESTING

Identify and describe the risks from the following types of risks that may affect the
Gobak Sodor:
 Software Risks (associated when application is being developed)
 Business Risks (market, tech change, product competition, management,
budget)
 Premature Release Risks (release the software before it is complete)
 Testing Risks (affect the process of testing a software)

The tables of the risks are attached

 TYPICAL COMPONENTS OF A TEST PLAN FOR
VMobil

A typical test plan should describe the purpose of the test plan align with the intended
audience for the test plan. The test plan should describe the following components
based on the VMobil:

 Scope of test (specifies the features)

 Test objectives (goals of testing)
 List of assumptions (assumptions for creating a test plan)
 Result of risk analysis (documents the risks identified)
 Resource allocation (details of the resource requirements for the testing
activity)
 Test schedule (information on the timelines for the test activities)
 Test design (describes various types of test to be conducted)
 Test environment (describes the environment requirements for various types of
testing)
 Testing tools and techniques (which is required for testing)
 Test completion criteria (specifies the conditions which must be evaluated
after testing is completed)

The tables of the typical component of a test plan are attached.

 TEST METRICS RELEVANT TO VMobil

Describe the need for designing test metrics and the types of test metrics that should
be grateful to test the VMobil.

The tables of the test metrics are attached.

TEST ENVIRONMENT

The suggested hardware and software requirements for VMobil Game include:

 Hardware:
- Processor Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz , 4.00GB RAM and
CDROM
- Processor Intel(R) Core(TM) i5 CPU M460 @ 2.53GHz, 4.00GB RAM and
CDROM
 Operating System:
- Microsoft Windows 8.1 Professional
- Microsoft Windows 10 Professional
 Software:
- Visual Studio 2010 and 2015 Professional, SAP Crystal Report.
Review Checklist

Software Requirements Review Checklist

S.No. Area of concern (Yes/No)
1. Are all the requirements traceable? Yes
2. Is there a prototype available for the user? Yes
Are the requirements consistent with the schedule, the resources,
3. Yes
and the budget?
Does data model correctly, reflect data objects, their attributes,
4. Yes
and relationship?
5. Is the analysis of the information domain complete and accurate? Yes
 High-Level Design Review Checklist
S.No. Area of concern (Yes/No)
1. Does the software architecture reflect the software requirements? Yes
2. Are all the modules functionally independent? Yes
Are the interface defined for modules and external system
3. Yes
elements?
4. Is the data structure consistent with the information domain? Yes
5. Is the data structure consistent with the software requirements? Yes

Detailed Design Review Checklist

S.No. Area of concern (Yes/No)
1. Does the algorithm accomplish the desired function? Yes
2. Is the logic of the algorithm correct? Yes
3. Does the interface map to the architectural design? Yes
4. Are the local data structures properly defined? No
5. Are structured programming constructs used throughout the code? No
 Code Review Checklist
S.No. Area of concern (Yes/No)
1. Is the design correctly translated into code? Yes
2. Are there any incorrect spellings or typing errors? No
3. Is the language being used appropriate? Yes
4. Is there compliance with the coding standards? Yes
5. Are necessary comments to be added in the code as per standards? No
6. Are there any incorrect or ambiguous comments? No
7. Are the data types and data declaration correct? Yes
8. Are the physical constraints appropriate? Yes
Software Risk
Project Risk
Probab
Impact Risk Responsi Mitigation Start End
Risk ility
Factor bility Steps Date Date
Conduct
Inadequate training
When
skill session
Project the Within
possessed Low Med Low before
Manager project 1 week
by developme
comme
developers nt of the
nces
project.
When
Till the
Disgruntled Project Give the the
Med High Med end of
employees Manager job project
project
benefits comme
nces
When
Unrealistic Consultati
System the Within
performanc Low Med Low on with
Analyst project 1 week
e standards developer
comme
s
nces
Increase When
Till the
Unrealistic Project budget the
Med High Med end of
Budget Manager with a project
project
new comme
feature nes
When
Till the
Personnel Project Hire a the
Med High M end of
resignation Manager new project
ed project
developer comme
nc es
When
Till the
Insufficient Project Upgrad the
Low High M end of
resource Manager e project
ed project
resourc comme
eRequest nc es
When
for Till the
Insufficient Project the
Med High Med additiona end of
time Manager project
l project
comme
develope
nc es
rs to
work on
the
project
Technical Risk
Risk Probab Impact Risk Responsi Mitigation Start End
ility Factor bility Steps Date Date

Consultati
When the
o
System project Within
Bad design Me Hig Med n with
Analyst expert commenc 1 week
d h
es
system
annalis
Consultatio When the
Bad Develop nt with project Within
Lo Med Low
interface er visual commenc 1 week
w
designe es
8 r
Ensure
Security
restricted When the
risk due to Till the
access to project
confidential Me Hig Med Designer end of
the commenc
ity of data d h project
system es
processed
being
Database is developed
Consultati
o
not Develop n with Within
Me Hig Med When
er expert 1 week
available d h
system
annalis
t
Business Risk
Probab
Impact Risk Responsi Mitigation Start End
Risk ility
Factor bility Steps Date Date
When the
Gain Till the
Lot of Project project
Low Med Lo player’ end of
competitors Manager commen
w s trust project
c es
When the
Training
Technology Project project Within
Low Med Lo the
change Manager commen 2 week
w developer
c es
s
When the
Managemen Training
Project project Within
t team Med Hig Me the
Manager commen 2 week
support h d developer
c es
s

Premature Risk
Risk Probab Impact Risk Responsi Mitigation Start End
ility Factor bility Steps Date Date

Release When the

Till the
before the Project Release the project
Med Hig Me end of
project Manager beta commen
h d project
completed version c es
Testing Risk
Risk Probabi Impact Risk Responsi Mitigation Start Date End
lity Factor bility Steps Date

Incompatibl Low High Med System Update the When the Till
e test Analyst requirement project the
environmen s commence end
t s of
proje
ct
Inexperienc High High High Project Tester When the Withi
ed tester Manager training project n1
commence week
s
Use of a Med High Med Project Training When the Withi
new Manager project n1
technology commence week
s
 Critical Success
Factors of the Test Result
S.No. Acceptance Criteria Software Comments
(Accept/Reject)
(Yes/No)
Allow Player can register
1. Yes Accepted None.
their name for high score
This will make
Allow users to view
2. Yes Accepted the user play the
Highscore game
game again.
If the users want
to change car,
Allow users to change Car can
3. Yes Accepted
Car before game. change before
game.

Ensure the Player can This will

access the game by increase interest
4. Yes Accepted
windows 8.1 and windows player in playing
10 operating system. game.
Ensure the users can view
5. Yes Accepted None.
Help form.
Data input in a name score
6. form not take more than Yes Accepted None.
30 seconds.
 TEST METRICS
Software Requirements Review Checklist
S.No. Area of concern (Yes/No)
6. Are all the requirements traceable? Yes
7. Is there a prototype available for the user? NO
Are the requirements consistent with the schedule, the resources,
8. Yes
and the budget?
Does data model correctly, reflect data objects, their attributes,
9. Yes
and relationship?
10. Is the analysis of the information domain complete and accurate? Yes

High-Level Design Review Checklist

S.No. Area of concern (Yes/No)
6. Does the software architecture reflect the software requirements? Yes
7. Are all the modules functionally independent? Yes
Are the interface defined for modules and external system
8. Yes
elements?
9. Is the data structure consistent with the information domain? Yes
10. Is the data structure consistent with the software requirements? Yes

Detailed Design Review Checklist

S.No. Area of concern (Yes/No)
6. Does the algorithm accomplish the desired function? Yes
7. Is the logic of the algorithm correct? Yes
8. Does the interface map to the architectural design? Yes
9. Are the local data structures properly defined? No
10. Are structured programming constructs used throughout the code? No
 Stage Discovered Defect Count
Requirements Review 0
Design Review 3
Code Review 4
Testing 3
Acceptance Testing 0
Defects Identified in SDLC

The total size of the software is 17 FP.

The calculation of the DRE and DD for the project and the management analyze data will be
show below.

DRE (Defect Removal Efficiency)

The DRE of the software project is calculated as:
DRE = (Total Number of defects found during development (before delivery)) / (Total Number
of defects found during development (before delivery) + Total Number of defects found
after delivery)
DBD = 0 + 3 + 4 + 3
= 10

DAD = 0 (Acceptance)

DRE = DBD / (DBD + DAD)

= 10 / (10 + 0)
= 10/ 10
=1

*DBD = Defects Before Delivery

*DAD = Defects After Delivery
DD (Defect Density)
DD is the defect density in a software project. This provides a normalized view of the software.
The formula for DD is:
DD = Number of Known Defects / Size (in Line of Code or Function Point)
N=0+3+4+3+0
= 10

DD = 10 / 3 FP
= 3.33
 TESTING TOOLS

Unit Testing Tools

S. No Conditions Output Pass/Failed
Load the Crystal Report (crystalReportViewer1_LoadTest) Pass
1. The result will be load the Crystal
Report

(inputanTest) The result Pass

2. User entered the data name and
sore will data save on txt
User want to view list of (crystalReportViewer1_LoadTest) Pass
3. The result will return Crystal
High score report data
Manual Tools
S. No Conditions Pass Failed
1. The data will be saved if user doing register name and Pass -
score
3. The score will be saved bassed on user play the game Pass -

4. The data of character will be shown before play the game. Pass -
.
The method Button Input () will be worked after user
5. play the gamein the Form2 if user go to Play the game Pass -

The method Label 2 click () will be worked in the

6. Pass -
Tampilan Utama Form if user go to Tampilan Utama Form.
The method Label5 Click () will be worked in the
7. Tampilan Utama Form if user go to Tampilan Utama Form. Pass -

The method Label3 Click () will be worked in the

8. Pass -
Tampilan Utama Form if user go to Tampilan Utama
Form.
The following table describes the components of a test plan

Component Description

Overview

The system to test a Windows form

Project Objectives
application VMobil Game.
It is a Windows form game that enables the
Players to:

 Play the game.

 View the highscore
System Description  Choose the color of the
car.
 Use left and right arrow to controls
the character.

 To ensure that the application meets

or exceeds player’s expectations.
 To ensure that all required functions
Test Objectives operate appropriately.
 To ensure that the system meets
performance, and reliability
requirements.
Scope of Test

 Whether or not the players are able

to view the highscore each level.
 Whether or not the players are able
to use left and right arrow to
Features to be Tested controls the car.
  Whether or not the players are able
to choose the car color.

Plan

 Muhammad Rayi Hafiza (Test

Manager and Tester)
Test Team
 Anjani Muhammad Sodik (Test Lead
and Tester)

Two testers need to be involved to complete

Staffing and Training Needs
Budget
the testing in time.
Testers need to train on Windows Form
Application so that they can perform the
structural testing of the software
0

Software: Windows 10 operating system,

Visual Studio 2010, SAP CrystalReport,
test tools.
Requirements

Personnel: One test manager, one test lead,

and two testers.