Real-Time Currency Converter

By
1. Abdullah Shakeel 42742
2. Mateen Ahmed 42723
3. Sharjeel Shah 42718
4. Ubaid Ullah 42739
5. M.Qasim 42766

A Project report submitted in partial fulfillment

of the requirement for the degree of
DAE Computer Information Technology

Department of Computer Information Technology

Askari Institute of Technology,

Rawat, Islamabad

2025

1
 Real-Time Currency Converter
By
1. Abdullah Shakeel 42742
2. Mateen Ahmed 42723
3. Sharjeel Shah 42718
4. Ubaid Ullah 42739
5. M.Qasim 42766

____________________________________
Ms. Tabinda Saqib
(Research Supervisor)

____________________________________
Mr. Farrukh Mehmood
(HOD, Computer Information Technology)

Department of Computer Information Technology

Askari Institute of Technology,

Rawat, Islamabad

2
 CERTIFICATE

It is certified that the contents and form of project entitled “Real-Time Currency Converter”
submitted by Abdullah Shakeel (42742), Mateen Ahmed (42723), Sharjeel Shah (42718), Ubaid
Ullah (42739), M. Qasim (42766) have been found satisfactory for the requirement of their
degree.

Supervisor: ______________________________

(Ms.Tabinda Saqib)

3
 DEDICATION

To Allah the Almighty

&

To our Parents and Faculty

4
 ACKNOWLEDGEMENTS

We are deeply thankful to our supervisor Ms. Tabinda Saqib for helping us throughout the course
in accomplishing our Final Year Project. Her guidance, support and motivation enabled us in
achieving the objectives of the project.

5
 Table of Contents
ABSTRACT ................................................................................................................................................. 7
1. INTRODUCTION............................................................................................................................... 9
1.1. Problem Background ...................................................................................................................... 9
1.2. Project Scope ................................................................................................................................... 9
1.3. Objective ........................................................................................................................................ 10
1.4. Report Organization ..................................................................................................................... 10
2. REQUIREMENTS & DESIGN ....................................................................................................... 12
2.1. Functional Requirements ......................................................................................................... 12
2.2. Non-Functional Requirements ................................................................................................. 12
2.2.1. Performance requirements............................................................................................... 12
2.2.2. Security requirements....................................................................................................... 12
2.2.3. Reliability measure ........................................................................................................... 13
2.2.4. Maintainability .................................................................................................................. 13
2.2.5. Usability ............................................................................................................................. 13
2.2.6. Portability .......................................................................................................................... 13
2.2.7. Correctness ........................................................................................................................ 13
2.2.8. Efficiency ........................................................................................................................... 14
2.2.9. Flexibility ........................................................................................................................... 14
2.3. Flow Chart ................................................................................................................................. 14
3. IMPLEMENTATION ...................................................................................................................... 16
3.1. Name of Website ....................................................................................................................... 16
3.1.1. Working ............................................................................................................................. 16
3.1.2. Database design ................................................................................................................. 17
4. RESULT & DISCUSSION ............................................................................................................... 20
4.1. Module1 Name .......................................................................................................................... 20
4.2. Module2 Name .......................................................................................................................... 20
5. CONCLUSION & RECOMMENDATION.................................................................................... 22
5.1. Recommendations ..................................................................................................................... 22
5.2. Conclusion ................................................................................................................................. 22

6
 ABSTRACT

The Real-Time Currency Converter is a web-based application designed to provide users with an
efficient and accurate way to convert currencies. Utilizing up-to-date exchange rates, this
application enables individuals and businesses to effortlessly calculate currency conversions for
international transactions.

7
CHAPTER 01
INTRODUCTION

8
 1. INTRODUCTION

1.1. Problem Background

In today's globalized economy, international transactions have become increasingly

common. Individuals and businesses frequently exchange currencies for travel, trade, and
investment purposes. However, manual currency conversion methods are often time-consuming,
prone to errors, and lack real-time accuracy.

1.2. Project Scope

 Scope Statement:-

The project scope includes the design, development, testing, and deployment of a currency
converter application with the following features.

 In-Scope:

1. User-friendly interface for currency selection and amount input

2. Real-time exchange rate updates from reliable APIs (e.g., ExchangeRate-API, Open
Exchange Rates)

3. Support for 180+ currencies

4. Automatic calculation and display of converted amount

5. Conversion history storage and display

6. Favorites list for frequently used currencies

7. Responsive design for mobile and desktop devices

8. User testing and feedback incorporation

9
  Out-of-Scope:

1. Integration with payment gateways or financial institutions

2. Advanced analytics or charting features

3. Support for cryptocurrency conversions

4. Offline mode or desktop application development

1.3. Objective

Develop a web-based currency converter application that provides accurate, up-

to-date, and secure currency conversions for individuals and businesses.

1.4. Report Organization

This report is organized into 5 chapters.

Chapter 2 gives a detailed overview of functional requirements, non-functional

requirements, design and architecture of the system.

Chapter 3 discusses the technical aspects for implementation of the system. It describes
methodology that is used for development system.

Chapter 4provides the results and discussion.

Chapter 5 is about the conclusion and recommendation.

10
CHAPTER 02
REQUIREMENTS & DESIGN

11
 2. REQUIREMENTS & DESIGN

This chapter describes the system in terms of functional requirements and non-functional
requirements.

2.1. Functional Requirements

Some requirements are mentioned below, take these as a sample and update or remove according
to your application.
FR-1. Website must allow user to login to the website. It will contain a login/signup
page. So the user can authorize.
FR-2. Once the user is logined/signed in , then user can get access of desired courses.
FR-3. User can watch and download the enrolled content.

2.2. Non-Functional Requirements

2.2.1. Performance requirements

For efficient working of this application, time and speed are a most important factor. Crimes
should be immediately reported at the police station to take corrective and safety actions.

NFR-1. The system should have minimum response time.

NFR-2. The user should be able to stream video with the police station spontaneously so
that some of the information may not pass over (be ignored).
NFR-3. SOS signals should be sent immediately when the user tap/click on “SOS” button.
NFR-4. At a time, only 2 live streaming can be viewed in the police station application. If
the number of streams exceeds, the exceeding ones will not be displayed but will be
saved.

2.2.2. Security requirements

NFR-5. All the data regarding crimes should be properly maintained and kept
confidential.
NFR-6. Data record of citizens should be kept safe.

12
 NFR-7. The IP addresses and port number of the police stations which are kept at the
server side should be protected and encoded.

2.2.3. Reliability measure

NFR-8. The product should be reliable enough to sustain in any condition.

NFR-9. If internet is not connected, application should not crash.

2.2.4. Maintainability

NFR-10. Different versions of the product should be easy to maintain.

NFR-11. For development, it should be easy to add code to existing system, should be easy
to upgrade for new features and new technologies time to time.
NFR-12. Maintenance should be cost effective and easy.

2.2.5. Usability

This can be measured in terms of ease of use.

NFR-13. Application should be user friendly.
NFR-14. Application should be easy to learn.
NFR-15. Navigation should be simple.
NFR-16. The system at the police station saves data in tabular form which aids in providing
user friendly environment.
NFR-17. Proper error message should be displayed to user.

2.2.6. Portability

NFR-18. The application for the local people will run on smart phone with the GPS
application and Android operating system.
NFR-19. The application for the police station will be installed as desktop application with
windows operating system.

2.2.7. Correctness

13
 NFR-20. The application should be correct in terms of its functionality, calculations used
internally, and the navigation should be correct. This means application should adhere to
the functional requirements.
NFR-21. The web server should correctly select the police station for a particular location
NFR-22. Data taken as input from the user should be validated (for e.g. CNIC should be 13
digits long).

2.2.8. Efficiency

NFR-23. Applications should not take all the RAM /hard-disk of mobile or computer
system.
NFR-24. The citizen android application size should be less than 100MB.

2.2.9. Flexibility

NFR-25. Product should be easy to interface with the server.

2.3. Flow Chart

14
CHAPTER 03
IMPLEMENTATION

15
 3. IMPLEMENTATION

This chapter discusses the technical aspects of the system from development point of view.

3.1. Name of Website Application

3.1.1. Working

Citizen application is an android based application written in Java and xml. It is supported
by android version 4.1 or greater. The intended audience of Citizen Android application are the
citizen of Pakistan. It requires permissions of location, camera, Microphone, Contacts, SMS and
Storage.

PERMISSION PURPOSE
Location To get connected to the police station, location of the user is required.
Camera For live streaming, camera is required.
Microphone For live streaming, microphone is required.
Contacts For Sending SOS signals to the selected contacts.
SMS For Sending SOS signals to the selected contacts.
Storage Saving user’s data in the database.

As the application is installed and launched for first time, it displays a disclaimer to the
user. Once user agrees with the disclaimer, registration screen is viewed. User must get registered
with the application. The registration Form consists of field including Name, CNIC, Phone
number, Email. Once the user fills the registration form, the data is sent to the server. Data is
recorded on the server database as well as in the local SQLite database.

Whenever the user starts the application, the location is fetched from the GPS. The
application makes an HTTP request to the webserver to provide the relevant police station data for
the user’s location. This location is send to the web server irrespective of whether the user has

16
started the live streaming or not. The web server, then returns the data to the user, and that data is
saved locally for future use. The data returned by server provides the details of relevant police
station with which the application can connect to the police station. The data of police station is
encrypted which is decrypted by the application. The application will keep this data as soon as the
application is opened. As the application gets closed, the data will be lost.

For F.I.R submission, the website is displayed in web view, where user can fill the F.I.R
form. A submitted F.I.R will be saved in the web server database. For checking F.I.R status,
application make HTTP request to webserver with the F.I.R number and server returns the F.I.R
status. SMS service is used for sending SOS signal to the selected contacts. The signal contains a
google map hyperlink which displays current location of user. For live streaming and sending
SOS signal to the police station, firstly, essential data to get connected with relevant police station
is requested from server. In next step, the application makes a TCP request to the police station
desktop application. In this request, the data of user and current location is sent to the police
station. If the request is for live streaming, the police station desktop application will respond to
the request. In response, the police station desktop application will make RTSP request to the
citizen android application, to fetch the live stream.
For live streaming, RTSP protocol is used. Citizen android application acts as RTSP
server. It captures camera and displays it in a preview where camera is encoded through H.246
compression techniques and microphone audio is encoded through Advanced Audio Coding
(AAC).

3.1.2. Database design

Attribute Description Type Examples

Name Alphabets only - It stores the String XYZ

name of citizen who have
registered with the application.

CNIC Digits Only- It stores the CNIC String 3840120002350

of citizen who have registered

17
 with the application.

Phone Digits- It stores the phone String 03064000000

number of citizen who have
registered with the application.

Email It stores the email of citizen who String [email protected]

have send crime video or SOS
signal.

18
CHAPTER 04
RESULT & DISCUSSION

19
 4. RESULT & DISCUSSION

In this chapter the functionality of different modules of the system is demonstrated. It is

illustrated with the help of screenshots of developed system.

Add functionality and screenshot of each module of your application.

4.1. Module1 Name

4.2. Module2 Name

20
CHAPTER 05
CONCLUSION &
RECOMMENDATIONS

21
 5. CONCLUSION & RECOMMENDATION

5.1. Recommendations
1. Optimize loading times (<3 seconds).

2. Ensure 99.9% uptime and scalability.

3. Use caching mechanisms (e.g., Redis, Memcached).

4. Regularly monitor and analyze performance metrics.

5. Implement Content Delivery Networks (CDNs).

5.2. Conclusion
The real-time currency converter web development project aims to provide an efficient,
secure, and user-friendly application for individuals and businesses to convert
currencies accurately.

22