Apply the following procedure for solving the TMA problem.

A$.$ Read and analyze the problem

statement.

B$.$ Formulate the algorithm using pseudocode and assume any required

missed data reasonably.

C$.$ Write a C# application.

D$.$ Write a comment for each line of code using your own words.

E$.$ Test, debug and execute the C# application.

F$.$ Copy and paste your code from Visual Studio to the Answer Booklet $($Don$\text{'}$t

put your code as a screenshot$).$

G$.$ Provide Screenshots for both the input and output of ALL cases of each

problem. DO NOT submit sample of screenshots.

H$.$ Your TMA Answer Booklet should be structured as follows:

Problem: To$-$Do List Application:

$1\mathrm{.}1$ Algorithm pseudocode

$1\mathrm{.}2$ Complete problem's application code $($Copied$)$

$1\mathrm{.}3$ Screenshots of both input and output for ALL cases of the problemTo$-$Do List Application $(60$ marks$)$

Create a console application that simulates a To$-$Do List. The application should allow

users to manage their tasks by performing various operations such as adding tasks, listing

tasks, editing tasks, marking tasks as completed, deleting tasks, and setting task priorities.

Requirements:

$1-$ When the application starts, display a welcome message to the user.

$2-$ Implement a menu system that allows the user to select different options.

$3-$ The following options should be available:

$3\mathrm{.}1$ "add": Allow the user to add a new task to the list, including a title,

description, and due date.

$3\mathrm{.}2$ "list": Display all the tasks in the list, including their titles, due dates, priorities,

and completion status. The tasks should be sorted by priority, with high priority

tasks displayed first, followed by medium and low priority tasks.

$3\mathrm{.}3$ "edit": Allow the user to edit an existing task by specifying the task ID$.$ They

should be able to modify the title, description, due date, and priority of the task.

$3\mathrm{.}4$ "complete": Allow the user to mark a task as completed by specifying the

task ID$.$

$3\mathrm{.}5$ "delete": Allow the user to delete a task from the list by specifying the task ID$.$

$3\mathrm{.}6$ "set priority": Allow the user to set the priority of a task by specifying the task

ID and the new priority $($high$,$ medium, or low$).$

$3\mathrm{.}7$ "exit": Quit the application.

$4-$ Implement validation for user inputs to ensure correct data entry. For example,

validate that due dates are in the correct format $($YYYY$-$MM$-$DD$),$ task IDs exist in

the list before performing edit, completion, deletion, or priority setting operations,

and prioritize tasks with valid priority levels $($high$,$ medium, or low$).$

$5-$ Provide appropriate feedback messages to the user after each operation. Display

an error message if the user enters an invalid option.

$6-$ Store the tasks in memory during the runtime of the application. Do not

implement any permanent data storage.

$7-$ Ensure that the code is clean, well$-$structured, and easy to understand. Use proper

naming conventions and meaningful comments where necessary.