or the student functionality "Update student information", using the Domain Model Class Diagram and the System Sequence diagram:Draw a First-cut Sequence Diagram Draw a Final-cut Sequence DiagramNOTES: See Process Guidelines for how to draw these diagramsIMPORTANT - Please cut and paste an image of your 2 diagrams in the answer Value: 70%Process GuidelinesDraw the First-Cut Sequence DiagramStart with elements from System Sequence Diagram (SSD) and first-cut Design Class Diagram (or Domain Model Class Diagram)A Sequence Diagram uses all elements of an SSD. System object replaced by all internal objects and messagesReplace the :System object with an appropriately named use case controllerFor each input message Determine all internal messages that result from that inputDetermine its objective, what information is neededIdentify the complete set of classes from the domain model affected by the messageWhat class needs it (destination)What class provides it (source)Whether any objects are created as a result of the inputFlesh out the components for each messageIteration, true/false conditions, return values, passed parametersAdd the controller - use case controller acts as intermediary between outside world and internal system Draw the Final-Cut Sequence DiagramAdd a view layer interface class before the controller either as a single GUI class or as Windows classesAdd a data access class for each problem domain class Data access layer should only support database CRUD – (Create, Read, Update, Delete) operations so classes maintain a high level of cohesion and are loosely coupled with the business layer