0% found this document useful (0 votes)
2 views1 page

CREDITSERVICE Project H

The document outlines the requirements for a currency conversion web application that uses exchange rates from the National Bank of Georgia. It specifies the form fields needed for user input, the output expected, and constraints regarding external data dependencies. Additionally, it details the tech stack to be used, including MSSQL for the database and .NET Core for the framework.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views1 page

CREDITSERVICE Project H

The document outlines the requirements for a currency conversion web application that uses exchange rates from the National Bank of Georgia. It specifies the form fields needed for user input, the output expected, and constraints regarding external data dependencies. Additionally, it details the tech stack to be used, including MSSQL for the database and .NET Core for the framework.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

For our application we sometimes need to convert a monetary amount from one currency to another.

To do this, we want to use the conversion rates published (almost) daily by the National Bank of Georgia
(NBG). These exchange rates are open to the public and available at their site:
https://nbg.gov.ge/gw/api/ct/monetarypolicy/currencies/ka/json

The idea is to create a simple webpage where we can convert currencies from one currency to another.
A form should be present where you can select:

 ClientName
 PersonalNumber
 Origin Currency
 Destination Currency
 Date
 Amount

And the output should contain:

 Converted Amount
 Actual date of the exchange rate used for conversion

There is however one constraint with this application. We do not want the form to depend directly on
the external datasource. If that service is down, we want to see the exchange rate of that day or the
closest day in the past that is available to us in our database. A table ‘exchange_rate’ should be created
where exchange rates are stored. Data should be stored in MSSQL. When and how you store this data is
up to you. Dynamically storing and updating data from provided URL, is not compulsory. Form
validation is requested, ClientName should be string containing two words, not more or less.
PersonalNumber should contain numeric values, by default it has length 11. Origin and destination
currency should be in Dropdownlist. Bear in mind that we don’t have cross rates, which means that on
one side of currency should be Georgian Lari. Date should be choosable by datepicker. Amount should
contain decimal data type. On the current page to the downside, we’d like to have an operations’ table
with columns: Id, ClientName, PersonalNumber, FromCurrency, ToCurrency, Rate, Date.

Note:

List of currencies we want to convert: USD, EUR, GBP, RUB

Tech stack:
Database: MSSQL
Framework: .NET Core
ORM: Entity Framework, ADO.NET, Dapper or up to you

You might also like