The Islamia University of Bahawalpur

Department of Computer Science

SOFTWARE REQUIREMENTS SPECIFICATION

for

<Flappy Bird>

By
Muhammad Shoaib
S22BDOCS1
Session Spring/Fall 2022 – 2026

Supervisor

Bachelor of Science in Computer Science

Revision History....................................................................................................................................
Application Evaluation History.............................................................................................................
Introduction............................................................................................................................................
Purpose...................................................................................................................................................
Scope......................................................................................................................................................
Overall description.................................................................................................................................
Product perspective................................................................................................................................
Operating environment..........................................................................................................................
Design and implementation constraints.................................................................................................
Requirement identifying technique........................................................................................................
Use case diagram...................................................................................................................................
Use case description...............................................................................................................................
Functional Requirements.......................................................................................................................
Functional Requirement X.....................................................................................................................
Non Functional Requirements...............................................................................................................
Usability.................................................................................................................................................
Performance...........................................................................................................................................
References..............................................................................................................................................

2
Revision History
Name Date Reason for changes Version

1
Application Evaluation History
Comments (by committee) Action Taken
*include the ones given at scope time both in doc
and presentation

Supervised by
<Mam Hira Awais>

Signature

2
Introduction
Purpose

This SRS document defines the requirements for the Flappy Bird 2D Game, developed in
Unity 2D for Android. It outlines functional/non-functional requirements, use cases, and
constraints.

Scope
 Core Features: Tap-to-fly mechanics, obstacle generation, scoring, UI screens.
 Future Scope: Leaderboards, skins, monetization.
 Exclusions: Multiplayer mode, iOS support (initially).

Overall description
Product perspective

 A standalone mobile game inspired by the original Flappy Bird.

Operating environment

 Platform: Android (min API level 21).

 Hardware: Moderate GPU for smooth animations.

 Tools: Unity 2D, C#, Git/GitHub, Photoshop/Audacity.

Design and implementation constraints

 CO-1: Must use Unity’s built-in physics engine for collision detection.
 CO-2: Adopt Object-Oriented Methodology (OOM) for modularity.

3
 Requirement identifying technique
For the Flappy Bird 2D game, use case modeling has been chosen as the primary technique
for identifying software requirements. This method is well-suited to interactive applications
where the user directly engages with the system through actions like tapping, navigating, or
responding to feedback.
 Use case modeling is ideal for interactive end-user applications like games, as it helps
capture how users interact with the system.
 Event-response tables are better suited for real-time or hardware control systems, which
are not applicable in this case.
 Storyboarding is typically used for graphically intensive applications such as
animations or media-rich platforms but is not the main technique here.

Use case diagram

Functional Requirements
This section outlines the functional requirements of the Flappy Bird 2D Game system. Each
requirement is described in natural language and organized by core features of the game. The
requirements specify what the system must do to ensure the gameplay experience is
functional, responsive, and user-friendly.

Non-Functional Requirements
Usability
 USE-1: The game shall provide a simple tap interface to control the bird.
 USE-2: UI must be responsive across multiple screen sizes.

Performance

4
 PER-1: The game shall maintain at least 30 FPS on devices with minimum 2 GB RAM.
 PER-2: The game shall load within 5 seconds on supported devices.

References
 Flappy Bird - Wikipedia

 Unity Documentation

 Firebase Leaderboard Integration

 Jetpack Joyride, Helix Jump Gameplay Inspirations

5
6