0% found this document useful (0 votes)
8 views5 pages

FXHFGJ

Uploaded by

keshavpatel2287
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views5 pages

FXHFGJ

Uploaded by

keshavpatel2287
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

SREENIDHI UNIVERSITY

MINI PROJECT
TEMPERATURE CONVERTER

PROJECT TITLE:

Temperature Converter: Write a program to convert temperatures between


Celsius ,Fahrenheit, and kelvin based on the user’s input.

PROBLEM STATEMENT:

You are tasked with developing an advanced temperature conversion system to


cater to diverse user requirements across scientific, industrial, and everyday use
scenarios. The system should allow users to seamlessly convert temperatures
between the Celsius, Fahrenheit, and Kelvin scales based on the following
functionality:

1. User-Friendly Input:

o Users should be prompted to select the input temperature scale


(Celsius, Fahrenheit, or Kelvin) and provide the temperature value.

o They should also specify the target scale for conversion or opt to
convert to all other available scales.

2. Conversion Accuracy:

o The program must handle conversions accurately to at least two


decimal places, ensuring precision for scientific applications.

o Use the following conversion formulas:

▪ Celsius to Fahrenheit: F=(C×95)+32F = (C \times \frac{9}{5})


+ 32

▪ Fahrenheit to Celsius: C=(F−32)×59C = (F - 32) \times \frac{5}


{9}

▪ Celsius to Kelvin: K=C+273.15K = C + 273.15

▪ Kelvin to Celsius: C=K−273.15C = K - 273.15


▪ Fahrenheit to Kelvin: K=(F−32)×59+273.15K = (F - 32) \times \
frac{5}{9} + 273.15

▪ Kelvin to Fahrenheit: F=(K−273.15)×95+32F = (K - 273.15) \


times \frac{9}{5} + 32

3. Error Handling and Validation:

o Validate user inputs to ensure the temperature value is a valid number


and within acceptable ranges for physical relevance (e.g., Kelvin
cannot be negative).

o Handle invalid scale selections gracefully by providing clear error


messages and retry options.

4. Extended Features:

o Batch Processing: Allow users to input multiple temperature values


for conversion in one session.

o Reverse Conversion: Provide users an option to view the reverse


calculation for verification.

o History Tracking: Maintain a session-based log of all conversions


performed and allow users to review them.

5. Program Scalability:

o Ensure the system is modular, making it easy to extend to include


other temperature scales (e.g., Rankine) in the future.

o Allow the user interface to be adaptable for both command-line and


GUI implementations.

Deliverables:

● A fully functional program meeting the above requirements.

● Test cases to demonstrate the system's accuracy, validation, and error


handling.

● Documentation explaining the program's usage and structure.

Evaluation Criteria:
Your program will be evaluated based on:

● Functionality and correctness of conversions.

● Handling of edge cases and invalid inputs.

● User experience and interface design.

● Code quality, readability, and modularity.


This problem statement pushes you to build more than just a basic converter,
incorporating elements like user experience, error handling, and potential future
scalability.

SREENIDHI UNIVERSITY
MINI PROJECT
TEMPERATURE CONVERTER

PROJECT TITLE:

Temperature Converter: Write a program to convert temperatures between


Celsius ,Fahrenheit, and kelvin based on the user’s input.

PROBLEM STATEMENT:

You are tasked with developing an advanced temperature conversion system to


cater to diverse user requirements across scientific, industrial, and everyday use
scenarios. The system should allow users to seamlessly convert temperatures
between the Celsius, Fahrenheit, and Kelvin scales based on the following
functionality:

6. User-Friendly Input:

o Users should be prompted to select the input temperature scale


(Celsius, Fahrenheit, or Kelvin) and provide the temperature value.

o They should also specify the target scale for conversion or opt to
convert to all other available scales.

7. Conversion Accuracy:

o The program must handle conversions accurately to at least two


decimal places, ensuring precision for scientific applications.

o Use the following conversion formulas:


▪ Celsius to Fahrenheit: F=(C×95)+32F = (C \times \frac{9}{5})
+ 32

▪ Fahrenheit to Celsius: C=(F−32)×59C = (F - 32) \times \frac{5}


{9}

▪ Celsius to Kelvin: K=C+273.15K = C + 273.15

▪ Kelvin to Celsius: C=K−273.15C = K - 273.15

▪ Fahrenheit to Kelvin: K=(F−32)×59+273.15K = (F - 32) \times \


frac{5}{9} + 273.15

▪ Kelvin to Fahrenheit: F=(K−273.15)×95+32F = (K - 273.15) \


times \frac{9}{5} + 32

8. Error Handling and Validation:

o Validate user inputs to ensure the temperature value is a valid number


and within acceptable ranges for physical relevance (e.g., Kelvin
cannot be negative).

o Handle invalid scale selections gracefully by providing clear error


messages and retry options.

9. Extended Features:

o Batch Processing: Allow users to input multiple temperature values


for conversion in one session.

o Reverse Conversion: Provide users an option to view the reverse


calculation for verification.

o History Tracking: Maintain a session-based log of all conversions


performed and allow users to review them.

10. Program Scalability:

o Ensure the system is modular, making it easy to extend to include


other temperature scales (e.g., Rankine) in the future.

o Allow the user interface to be adaptable for both command-line and


GUI implementations.

● BiA fully functional program meeting the above requirements.

● Test cases to demonstrate the system's accuracy, validation, and error


handling.

● Documentation explaining the program's usage and structure.

Evaluation Criteria:
Your program will be evaluated based on:

● Functionality and correctness of conversions.


● Handling of edge cases and invalid inputs.

● User experience and interface design.

● Code quality, readability, and modularity.

This problem statement pushes you to build more than just a basic converter,
incorporating elements like user experience, error handling, and potential future
scalability.

PROJECT PREPARED BY:

1)24011CSEAI0064

KESHAV PATEL.

2)24011CSEAI0094

KARTHIK SAIDE.

3)24011CSEAI0058

BOGA CHARANI.

You might also like