Undergraduate

Activity
Amira Fatiha binti Baharudin
KCT15005

Software Quality
Assurance
Booking Badminton Court from Sports
Complex

Overview
The student define the problems in the methods
of booking badminton court process.
Methods of booking:

1)Walk-in

2)Through UMP E-Community portal

The students have been assigned for their

respective process areas in CMMI by their
group leader.
They use the existing system in E-Comm as
benchmark.

Individual Tasks
CMMI Process Area
Member

CMMI Process Area

Tan Jia Chin

Amin Muzafar
Nasihah

L2 CM, L5 OID, L5 CAR

L2 REQM, L4 OPP, L4 QPM
L2 SAM, L3 OPF, L3 OPD, L3
OT
L2 PPQA, L3 PI, L3 VAL, L3
VER
L2 MA, L3 DAR, L3 RSKM, L3
IPM
L2 PP, L2 PMC, L3 RD, L3 TS

Ilykaviron Isal
Nadiya Syafiqah

Nur Adiella

Interview Process
They have interview few staffs in UMP Sports Complex.

Now, Sports Complex only use the Walk-in method to booking badminton
court.
The staffs gave up to use the E-Comm since the system have many
shortcomings in the process of booking badminton court.
For example,
1) Cannot make online payment.
2) If 1 student book all the badminton court, other student cant play
badminton.

Significant Process Areas for Improving

Booking Badminton Court Process

Nadiya: Measurement & Analysis (MA)

Adiela: Project Planning (PP)

Nasihah: Organizational Process Focus (OPF)
Amin: Requirement Management (RM)
Ilykaviron: Process & Product Quality Assurance (PPQA)
Jerry: Causal Analysis & Resolution (CAR)

Summary of Project
Currently, the E-Comm system have many problems, so they

use walk-in booking method. But this walk-in method is not

so convenience for staffs and students.
Staffs prefer to use the online system if the system is better to
use, prefer to develop a new system for Sports Complex.
With the CMMI process, they can define and suggest how to
make the system alive and useful for UMP staffs and students.
From their findings, they stated that process areas in level 2 in
CMMI is the most significant areas, since these areas are
essential in order to understand the process and detecting the
problems or weaknesses in managing booking badminton
court process.

Software Testing
ATM Machine (Audacity)

Overview
The test object is the ATM system, ATMS.
The company name is Audacity.
Each members are assigned on one features
of the system by their group leader.
Each member need to commit their part
(features) in the deliverables.
They follow the IEEE standard in
completing the project.

Deliverables
The deliverable of this project consists of:
1) Test Item Transmittal Report
2) Test Plan
3) Test Design Specification
4) Test Case Specification
5) Test Procedure Specification
6) Test Log
7) Test Summary Report

Individual Tasks
Features
Member

Features

Chan Mun Kit

Tan Jia Chin

F007 Transfer
F001 Start Up
F002 Shut Down
F003 Session Verification
F004 Transaction Menu
F005 Withdrawal
F006 Cash Deposit
F008 Balance Inquiry

Lam Yu Jie
Gan Jit Fook
Foong Meng Wei
Leong Chin Jian

Techniques
Test cases for ATMS were designed using five techniques:

Equivalence Partitioning
Boundary Value Analysis
Decision Table Testing
State Transition Testing
Use Case Testing

According to the documents,

1) Test Plan: Briefly introduce the testing plan such as
purpose, scope, test traceability, features, planned test
activities, test team roles.

2) Test Item Transmittal Reports: Specify the hardware

and software.

3) Test Design Specification: Find BV, EP, design state

diagram, decision table, use case testing and find out the
coverage of each test case.

According to the documents,

4) Test Case Specification: Design test case according to
feature based from test coverage.

5) Test Procedure Specification: Describes the steps

necessary to perform the test for each test case.

6) Test Log Report: Test case is performed and result is

recorded in this log.

7) Test Summary Report: Provide summary from the

findings in Test Log report.

Summary of Project
The project is about breaking the testing process into few phases.
Test Design Specification to find out the coverage.
Test Case Specification based on coverage to determine whether a system under
test satisfies system requirements and works correctly.
Test Procedure Specification after identify input, expected result, and procedures
to execute.
Record all test result in a Test Log.
Test Summary Report is then made from the result collected in the Test Log.
The testing process is completed after all test cases have been executed.