University of Central Punjab

BSCS FINAL PROJECT

Software Design Specification

URDU BOLI

Project Advisor

Mr. Asim Raza

Presented by:
Group ID: F19BS058

Student Reg#: Student Name:

L1S15BSCS0071 ZeeshanAmjad
L1F15BSCS0178 Ahmed Sohail
L1S16BSCS0092 Haseeb Bin Talat

Faculty of Information Technology

University of Central Punjab

 University of Central Punjab

Design and Test Specification

SDP Phase IV

URDU BOLI
Advisor: Mr. Asim Raza
Team F19BS058

Member Name Primary Responsibility

ZeeshanAmjad Integration between the
environment and
character or objects
Ahmed Sohail Creation of
environments of the
game
Haseeb Bin Creation of characters
Talat and objects
 URDU BOLI

Table of Contents
Table of Contents............................................................................................................................i
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Product.......................................................................................................................................1
1.2 Background................................................................................................................................1
1.3 Objective(s)/Aim(s)/Target(s)....................................................................................................1
1.4 Scope..........................................................................................................................................2
1.5 Business Goals...........................................................................................................................2
1.6 Document Conventions..............................................................................................................2
1.7 Miscellaneous.............................................................................................................................2
2. Technical Architecture............................................................................................................5
2.1 Application and Data Architecture.............................................................................................6
2.2 Component Interactions and Collaborations.............................................................................10
2.3 Design Reuse and Design Patterns...........................................................................................10
2.4 Technology Architecture..........................................................................................................13
2.5 Architecture Evaluation............................................................................................................13
3. Detailed/Component Design..................................................................................................14
3.1 Component-Component Interface.............................................................................................14
3.2 Component-Human Interface...................................................................................................14
4. Screenshots/Prototype...........................................................................................................15
4.1 Workflow.................................................................................................................................15
4.2 Screens.....................................................................................................................................16
5. Test Specification and Results..............................................................................................19
5.1 Test Case Specification............................................................................................................19
6. Revised Project Plan..............................................................................................................25
7. References...............................................................................................................................27
Appendix A: Glossary..................................................................................................................28
Appendix B: IV & V Report.......................................................................................................29

F19BS058 SDP Phase IV (DTS) Page i

 URDU BOLI

Revision History
Name Date Reason For Changes Version

F19BS058 SDP Phase IV (DTS) Page ii

 URDU BOLI

1. Introduction

1.1 Product

The application being developed is a game to facilitate the learning of Urdu. It is different from

teaching software in many different ways and takes an indirect approach towards the teaching of

language. The game would follow a storyline and integrate language into it. There would be levels

with rising difficulty and would contain a number of things such as alphabets, counting.

There exist much software for English language and each of these is quite elaborate in its

methods and has been rigorously developed. However, there has been no proper software based

learning system for learning the Urdu language. Those which exist have a very limited and small scope

and do not cope with the basic necessities of teaching a child. A game based learning system is hence

required in this field.

1.2 Background

Urdu Boli is an enhanced form of interactive learning systems for children. It integrates a 3D game and

interactive learning software. However, its sole purpose is to teach Urdu in a world where it is

declining at a rapid rate and may as well in a few decades. Keeping in consideration the present

interaction with gadgets it is necessary to make use of these devices to revive the lost or dying

traditions. As is clear that children are most interested in games, it calls for a creation of such

mechanism. Thus, the background of the development of this game is explained.

1.3 Objective(s)/Aim(s)/Target(s)

The objectives of the game as listed before are quite concrete and clear. These being: to create

considerable and sufficient software meeting the prevalent standards in the pedagogical and learning

fields. Another, rather particular objective is focus on the Urdu language i.e. teaching a child to

F19BS058 SDP Phase IV (DTS) Page 1

 URDU BOLI
identify the objects in his natural surrounding with words of his own language. Moving forward

another aim is to promote culturally responsible use of gadgets, making the targeted users socially and

culturally responsible as a consequence. Improving the skills of the developing team as a financial

responsibility and for the creation of such software for other local languages is also intended. A target

of the software is to generate revenue for the developers.

1.4 Scope

The creation of an educational product to meet the demands of the professional world and to

teach a sufficient amount of language is the basic purpose. An introductory phase of a bigger project

which teaches up to 500 words to children.

1.5 Business Goals

The underlying business goals are to generate an income from the finished product through its

sale online (locally and globally). Other business goals include the creation of a company for the

development of such software for people of all ages.

1.6 Document Conventions

Times new Rome, Italicized, Bold with a text font size of 12 and heading with font size of 14

and main heading with the font size of 18.

1.7 Miscellaneous

There exists only a small number of software for teaching Urdu language. Most of these are

based on the methods used to teach adults. A project by the acclaimed Urdu hub Rekhta.org by the

name of Aamozish offers video lectures which are for intermediate to advanced learners. Another

software sponsored by the Government of the United States of America, by the name TLO

(Transparent Language Online) is a web delivered language learning platform. It offers a variety of

ways to teach language including puzzles, sound to word identification, word of the day etc. Any
F19BS058 SDP Phase IV (DTS) Page 2
 URDU BOLI
existing software lacks the capability to deliver the purpose of natural learning. Urdu Boli is an attempt

at teaching language using 3D games with the help of aesthetics however; it is limited to teaching

Urdu.

F19BS058 SDP Phase IV (DTS) Page 3

 URDU BOLI

2. Technical Architecture

The system is custom built which provides the user with real time processing. The game uses

multi-processing. The major components of the game are as follows:

1. Physics (collision detection, actual forces, etc.)

2. Animation management.

3. Scene management.

4. Camera (make sure not to render everything that is in the scene)

The game collects the user’s progress data and saves it on the local drive. It is an offline

stand-alone game which needs to be installed in order to play. The game uses Unity game

engine and C#. The supported platforms are Windows and Android. Files would be saved in the

installation directory. The game would generate metadata files to save data. Thus, it does not

require a database platform. The game has an end-user interface. This is a simple interface

similar to any RPG. It includes the main menu screen, the game world i.e. the scenes in the

game, and submenus. The game uses joystick controllers like mouse and keyboard.

2.1 Application and Data Architecture

Component Diagram:
F19BS058 SDP Phase IV (DTS) Page 4
 URDU BOLI

Fig 3.2-a

Fig 2.1-a Show Flow of events/data between different components of the system

Class-Diagram:

F19BS058 SDP Phase IV (DTS) Page 5

 URDU BOLI

Fig2.1-b
Fig 2.1-b represent the classification and breakdown of the current system.

ER-Diagram 1:

F19BS058 SDP Phase IV (DTS) Page 6

 URDU BOLI

Fig2.1-c

Fig 2.1-c represent the relation between different entities and databases.

Use case Diagram:

F19BS058 SDP Phase IV (DTS) Page 7

 URDU BOLI

Fig2.1-d

Fig 2.1-d represent the use/application of the current system.

2.2 Component Interactions and Collaborations

Sequence Diagram:
F19BS058 SDP Phase IV (DTS) Page 8
 URDU BOLI

<Provide interactions and collaborations between your system components/processing units.

Diagrams/Tools that may be provided in this section include Design Level Sequence Diagram,
Collaboration Diagram, Event Traces, Detailed DFD, Activity Diagram etc. All these diagrams should
have more details than the details provided in Phase 1 of the SDP. Describe each diagram briefly.>

2.3 Design Reuse and Design Patterns

<Identify and state any reuse during development of the system>
Fig 3.3-a

Fig 2.2-a represent the Sequence in which different events are executed.

Data Flow Diagram:

F19BS058 SDP Phase IV (DTS) Page 9

 URDU BOLI

Fig 2.2-b

Fig 2.2-b represent the data flow between different entities and databases/storage.

Activity Diagram:

F19BS058 SDP Phase IV (DTS) Page 10

 URDU BOLI

Activity Diagram

a
Act

Fig3.2-f
Fig 3.2-f represent the flow of events through different activates and tasks

F19BS058 SDP Phase IV (DTS) Page 11

 URDU BOLI
2.4 Technology Architecture

Fig 2.4-a
Fig 2.4-a represent how different objects/components collaborate with each other.

2.5 Architecture Evaluation

The game would require Unity game engine version 2019.3.9f1 (64-bit). Primarily the

operating system would be Android. Unity has a large community of developers and users

which make it readily available for learning. Unity has a large number of pre-developed

resources which can be used for free. Another major benefit is that it does not require any third

party software for its functionality, it is a complete package in itself. The game developed

leveraging Unity engine consumes more memory, which in turn creates OOM errors and

debugging issues in the apps.

F19BS058 SDP Phase IV (DTS) Page 12

 URDU BOLI

3. Detailed/Component Design

3.1 Component-Component Interface

Fig 3.1-a
Fig 3.1-a represent how different objects/components collaborate with each other.

3.2 Component-Human Interface

Fig 3.2-a
Fig 3.2-a represent how human and objects/components collaborate with each other.

F19BS058 SDP Phase IV (DTS) Page 13

 URDU BOLI
3.3 Component-Human Interface

3.3a The main menu screen takes input

3.3b The game-play takes input for player movement

F19BS058 SDP Phase IV (DTS) Page 14

 URDU BOLI

3.3c This part takes input to transport to a level

F19BS058 SDP Phase IV (DTS) Page 15

 URDU BOLI

4. Screenshots/Prototype

4.1 Workflow

Fig 4.1-a

F19BS058 SDP Phase IV (DTS) Page 16

 URDU BOLI
4.2 Screens

F19BS058 SDP Phase IV (DTS) Page 17

 URDU BOLI

F19BS058 SDP Phase IV (DTS) Page 18

 URDU BOLI

5. Test Specification and Results

5.1 Test Case Specification

Table 5.1: TC-1

Identifier TC-1
Related
requirements(s) The Game starts and displays the main menu
Short description Display menu
Pre-condition(s) Game files present on the system
Input data Start the game
Detailed steps N/A
A menu with 5 to 6 intractable options with sub-
Expected result(s)
menus opens
Post-condition(s) Sub menus are accessed
Actual result(s) Sub menus were accessed
Test Case Result Pass

F19BS058 SDP Phase IV (DTS) Page 19

 URDU BOLI

Table 5.2: TC-2

Identifier TC-2
Related requirements(s) A valid instance of the game is running
Short description Change graphic settings

Pre-condition(s) Default graphic settings

Input data The values of graphics settings are changed.

Resolution is changed, gamma level is changed, brightness is changed,
Detailed steps
graphics quality is changed.
Expected result(s) The altered options show results after applying
Post-condition(s) The changes are applied and saved
Actual result(s) The changes were applied and saved
Test Case Result Pass

F19BS058 SDP Phase IV (DTS) Page 20

 URDU BOLI

Table 5.3: TC-3

Identifier TC-2
Related requirements(s) A valid instance of the game is running
Short description Start New game
A valid instance of the game is initiated. The player creates a profile
Pre-condition(s)
in the game including first and last name.
Input data Player profile, difficulty settings
Detailed steps N/A
Expected result(s) A new game starts from the first level
Post-condition(s) The game can be played, saved or exited.
Actual result(s) The game starts and can be played and saved at any instant
Test Case Result PASS

F19BS058 SDP Phase IV (DTS) Page 21

 URDU BOLI

Table 5.4: TC-4

Identifier TC-2
Related requirements(s) A valid instance of the game is running
Short description Load Game
A valid instance of the game is running, a valid save-file exists in
Pre-condition(s)
the saved games folder.
Input data Saved game file
Detailed steps N/A
Expected result(s) The game is loaded from the last saved checkpoint
Post-condition(s) The game can be played and saved again
Actual result(s) The game was loaded and was playable
Test Case Result PASS

F19BS058 SDP Phase IV (DTS) Page 22

 URDU BOLI

Table 5.5: TC-5

Identifier TC-2
Related requirements(s) A valid instance of the game is running
Short description Quit game
Pre-condition(s) A valid instance of the game is running.
Input data N/A
Detailed steps N/A
Expected result(s) The game exits to the desktop
Post-condition(s) All instances of the game are closed
Actual result(s) The game successfully closed
Test Case Result PASS

6. Project Completion Status

<Show your progress and provide current status of the project in accordance with the plan provided in
project proposal and/or the previous phase. Provide list of modules that have been completed and the
modules that could not be completed. Also provide a list of modules that have been implemented but
were not part of original requirements (additional work). Use table 7.1 for this purpose.>
Table 7.1: Project Completion Status
Status
Module Name (Complete, Partially Implemented, Not
Implemented)
Module 1 (for example Bill
Calculation Module, Speech
Processing Unit
Module 2 …
Module 3 …
Complete System …

<Also add a table to show how many of the objectives/targets (mentioned in section 1.3) have been
met? And to what extent have they been met (whether an objective has not been met, or has been
met partially or fully). Also state the reason if an objective has not been met or has been partially met.
For example see table 7.2>
Table 7.2: Objective(s)/Target(s) Status
Target/Objectiv Status Reason(s)
e (Completed,

F19BS058 SDP Phase IV (DTS) Page 23

 URDU BOLI
Partially Completed,
Not Completed)
Creation of
character and Completed
environment
Creation of
challenges Completed
Usage of Urdu keyboard in MS
Windows Windows is not as convenient. This
compatibility Partially Completed
was the main reason we had to drop
MS Windows support.
The major content of the game left
High Quality
graphics Not completed no time for improve in the quality of
graphics.

Number of
Targets 2
Completed
Number of
Targets Partially 1
Completed
Number of
Targets Not 1
Completed

7. Deployment/Installation Guide
The user can install the game on their Android device. An APK file would be provided which

would enable the user to install the game on Android.

8. User Manual
The user must have some Urdu keyboard installed on their Android device, preferably Gboard.

After installation of the keyboard and the game the user can start the game and change the setting in
‫تت‬
the “‫” ر ی ب ب دلی ں‬option in the main menu. The user can start a new game using the “‫ ”نیا کھیل‬option in

the main menu or can continue a previously saved game using “‫ ”جاری رکھیں‬option in the main menu or

can quit the game using “‫ ”بند کریں‬option. After starting a new game the user can move the character

using the controls displayed on the screen.

F19BS058 SDP Phase IV (DTS) Page 24
 URDU BOLI

9. Revised Project Plan

F19BS058 SDP Phase IV (DTS) Page 25

 URDU BOLI
Table 6.2: Project Completion Status
Status
Module Name (Complete, Partially Implemented, Not
Implemented)
Crossword Puzzles Complete
Matching Complete
Writing Complete
Complete System Complete

F19BS058 SDP Phase IV (DTS) Page 26

 URDU BOLI

10. References

https//:draw.io

F19BS058 SDP Phase IV (DTS) Page 27

 URDU BOLI

Appendix A: Glossary

F19BS058 SDP Phase IV (DTS) Page 28

 URDU BOLI

Appendix B: IV & V Report

(Independent verification & validation)
IV & V Resource

Name Signature

Fix Time
S# Defect Description Origin Stage Status
Hours Minutes
1

Table 1: List of non-trivial defects

This document has been adapted from the following:

 Previous project templates at UCP

 High-level Technical Design, Centers for Medicare & Medicaid Services. (www.cms.gov)

F19BS058 SDP Phase IV (DTS) Page 29

 S06

University of Central Punjab

(Incorporated by Ordinance No. XXIV of 2002 promulgated by Government of the Punjab)

1.1

Faculty of Information Technology

PROJECT OFFICE CERTIFICATE OF APPROVAL FORM

Day Month Year

DATE 0 3 – 0 7 – 2 0 2 0

Project Information:
Group ID: F19BS058 Advisor’s Name: Asim Raza
Thesis / Project Title: URDU BOLI

Advisor’s Approval:
I Prof./Dr./Mr./Ms. _____Asim Raza_____________________ certify
that, I have;
Reviewed the document thoroughly.
Taken mock presentation and demonstration of project.
Verified the smooth working of the project and met the proposed
completion requirements.

Signatures and Date

Asim Raza 3/7/20

Advisor

F19BS058 SDP Phase IV (DTS) Page 30

 S06

University of Central Punjab

(Incorporated by Ordinance No. XXIV of 2002 promulgated by Government of the Punjab)

1.1

Faculty of Information Technology

PROJECT OFFICE CERTIFICATE OF APPROVAL FORM

For Project Office use only

Remarks: Signatures and Date

____________________
Group No Manager Projects

F19BS058 SDP Phase IV (DTS) Page 31