Introduction

Make $($and not qnake$)$ when setting up your assignment project.

Qt Designer should not be used to design user interfaces, and you are expected to manually set up

GUls to ensure that you properly handle memory using Ql$\text{'}$s parent$-$child functionality.

Good programming practices should be followed.

Follow standard naming coavemions: class names start with a capital leter, variable and function names start with a lowercase letter, using camelCase for names made up of multiple words. Ensure consistent code layout and use of blank lines. Use forward class declarations in beader files. Use initialiser lists in constructori.

Have proper GUI managenent: setting cursor focus, sequential tabbing, clearing input widget $($like text input fields being cleared and spin boxes being returned to some default value$),$ and enabling and disabling buttons as appropriate. Provide appropriate user feedhack.

Your code should build and run without any wamings.

$2.$ Questions

The UML class diagram is an initial design of classes for a conference registration application.

There are three types of registration allowed for the conference: standard registration student registration and invited guests registration. The standard registration fee is the standard tee $($stored in STANDARD$\_$FEE$).$ For those registered as students, the conference fee is half the price of the standard registration fee. For those registered as guests, the conference fee is $10\%$ of the standard registration fee.

An instance of RegistrationList contains a list of Registration$*.$ No two registrations are allowed to have attendees with the same e $-$mail addresses, unless the names are different. You should be able to query a RegistrationList whether a person $($by the name$)$ is already registered for the conference. A RegistrationList can also retum the number of attendees that are registered for the conference from an institution. Similarly, you can request the total registration fees for a type $("$Registration$"$; "StudentRegistration", "GuestRegistration" or "All"$)$ of registration. You are expected to use ar's metaobject system to access the type of a Registration in RegistrationList

Write a GUI application that allows users to register for a conference. The GUI should display the current list of registrations, including the respective registration fees, in the RegistrationList at all times, using a table widget. The interface should also allow users to request and view the results of the various operations supported by the RegistrationList class.

You are allowed to add new features to the classes given in the UML diagram, although you are not allowed to delete or change the given functions. You can decide on the desig of the GUI, and it can be done manually or using Qt Designer. You are expected to follow good programming principles.

Question $2$

Extend the solution in Question $1,$ to add another class named RegistrationListWriter that produces an XML$-$formatted RegistrationLis: using DOM as follows:Modify the GUI in Question $1,$ to give the user an option to save the registration list. Allow the user to choose the file, using the standard file dialog, where the XML$.$ formatted registration list should be saved.