Kindly answer this as soon as possible. Need Urgently. Thanks
While making a diagram must use Modle, View, and Controller.
The following classes are partially designed for a University Management System where the University is the only entity allowed to fire a faculty. dismiss a student, and eliminate a room. A Person can be a Student or Faculty. A faculty can teach up to 6 sections. A student can be enrolled in several courses. A section, besides the attributes listed, has a room and a course assigned. Connect the classes using the appropriate UML relationships and multiplicities. Student and Faculty are missing at least one attribute, and Section is missing at least two fields.
Extracted text: Person |- name : String - ssn : int + Person() Student |- ID : String - Student() Faculty |- ID: String UniversityMS |- name : String Faculty) - UniversityMSO Course |- name : String |- ID: String + Course() Section |- ID : String |- day : DateTime |- time : DateTime Room + Section() |- number : String |- capacity : int + Room)
Extracted text: Design a Mini-Kindle App that conforms with the MVC pattern. At this time, the Mini-Kindle App only has two views, the Library view and the Book view. • In the Library view the user can (i) synchronize the book library with the library in the cloud, and (ii) select (open) a book to read • When the library is synchronized, the library view is updated with the new conten (if any) from the cloud library • In the Book view, the user can (i) flip pages back and forward, (ii) set/remove bookmarks (up tp 5 bookmarks per book), (iii) go to a specific page (by providing a page number) • When the user selects/opens a book, the latest/current page is displayed • You may use enums with different statates to update the views The user can execute the commands from a GUI. You can assume that there are contorls in the GUI for each of the operations mentioned above. Your class diagram must follow the MVC version 3 as we discussed in class. In each class include the minimum attributes and methods needed to satisfy the requierements descibed above. It is expected full method signatures, appropiate visibility modifiers, descriptive naming convention for classes, attributes, methods, and delegates. All relationships that accept multiplicity must be depicted in the diagram.