PLEASE USE Qt programming

Question 1 Refer to the UML diagram to answer this question. Book -title: QString -authors: String List -isbn: QString -publicationDate: QDate +Book) +Book(t: QString, a: QString List i: QString.p: QDate) +setTitle(t: QString) setAuthors/a: QStringList) +setisbni: QString) +setPublicationDate(p: QDate) +getTitle(): QString +getAuthors() QStringList +getIsbn1. QString +getPublicat on Date(): QDato +obtairBookinfo() +saveBook(b: Book) The Book class is burdened with two additional responsibilities: 1. obtainbookInfo() to get user input on book details (title, authors. ISBN, and date of publication) via a console, and 2. saveBook () to save the state of a book instance into a file. Redesign the Book class so that the concept/process currently included in it is achieved using three different classes: 1. The Book class to represent a book with the necessary functions (as given in the above UML diagram). Remember that a book may have more than one author. 2. A Bookwriter class which saves the state of a book instance (values of the data members of that instance) in a file (you may save it in any sensible format). 3. A Graphical User Interface (GUI) class BookInput, which allows users to enter book information to create book instances, which should also be saved to a file (using the Bookwriter). Note: You can decide when book instance(s) should be saved. Question 1 Refer to the UML diagram to answer this question. Book -title: QString -authors: String List -isbn: QString -publicationDate: QDate +Book) +Book(t: QString, a: QString List i: QString.p: QDate) +setTitle(t: QString) setAuthors/a: QStringList) +setisbni: QString) +setPublicationDate(p: QDate) +getTitle(): QString +getAuthors() QStringList +getIsbn1. QString +getPublicat on Date(): QDato +obtairBookinfo() +saveBook(b: Book) The Book class is burdened with two additional responsibilities: 1. obtainbookInfo() to get user input on book details (title, authors. ISBN, and date of publication) via a console, and 2. saveBook () to save the state of a book instance into a file. Redesign the Book class so that the concept/process currently included in it is achieved using three different classes: 1. The Book class to represent a book with the necessary functions (as given in the above UML diagram). Remember that a book may have more than one author. 2. A Bookwriter class which saves the state of a book instance (values of the data members of that instance) in a file (you may save it in any sensible format). 3. A Graphical User Interface (GUI) class BookInput, which allows users to enter book information to create book instances, which should also be saved to a file (using the Bookwriter). Note: You can decide when book instance(s) should be saved