Note: to answer this question, you need to manually draw three diagrams on a piece of paper. When done, you need to take a picture of each of your diagrams and then submit the pictures to the Blackboard.

Consider a Multiple Listing Service (MLS) system with the following detail description for Update real estate agent use case, domain model class diagram, and a system sequence diagram for Update real estate agent use case.

Use case name: Scenario: Update real estate agent MLS clerk updating real estate agent Real estate agent information changes Revised real estate agent information is entered into the system. Triggering event: Brief description: Actors: MLS clerk Related use cases: Stakeholders: Preconditions: Postconditions: Revised real estate agent information is entered into the system (Web based version scenario Real estate office, real estate agent The real estate office must exist Revised real estate agent information is updated Actor System 1. Find real estate agent 1.1 Display agent and office information 2.1 Update agent record, including its 2. Enter revised agent information relationship to real estate office. Display results. Flow of activities Exception conditions: 1.1 No real estate agent found for requested idame. Display not found message. RealEstateOffice RealEstate Agent Listing 1 1.. 1 0... officeNumber name officeManager address phone agent Number name officePhone cellphone emailAddress listingNumber address yearBuilt squareFeet numberBedrooms numberBathrooms owner Name owner Phone asking Price statusCode Completion Status: System MLS Iclerk findAgent (officeNo, agentNo) Office WithAgent Information 1 update Agent(name, officePhone, ...) Office With Revised AgentInformation %) Your first task is to create a first-cut design class diagram for the Update real estate agent use case by extending the domain model class diagram. This requires three steps: (1) Add a controller class. (2) Elaborate each attribute in e hat is, identify the visibility, data type, initial value if applicable, and {key} property if applicable of each attribute in each class. Moreover, add a third compartment to each class as a placeholder for method signature(s). (3) Identify navig sibility. %) Your second task is to create a sequence diagram for the Update real estate agent use case (domain classes and controller class only) by extending the system sequence diagram. 5%) Your third task is to create final design class diagram. oolbar, press ALT+F10 (PC) or ALT+FN+F10 (Mac). and Submit to save and submit. Click Save All Answers to save all answers. Save All Answers S: Use case name: Scenario: Update real estate agent MLS clerk updating real estate agent Real estate agent information changes Revised real estate agent information is entered into the system. Triggering event: Brief description: Actors: MLS clerk Related use cases: Stakeholders: Preconditions: Postconditions: Revised real estate agent information is entered into the system (Web based version scenario Real estate office, real estate agent The real estate office must exist Revised real estate agent information is updated Actor System 1. Find real estate agent 1.1 Display agent and office information 2.1 Update agent record, including its 2. Enter revised agent information relationship to real estate office. Display results. Flow of activities Exception conditions: 1.1 No real estate agent found for requested idame. Display not found message. RealEstateOffice RealEstate Agent Listing 1 1.. 1 0... officeNumber name officeManager address phone agent Number name officePhone cellphone emailAddress listingNumber address yearBuilt squareFeet numberBedrooms numberBathrooms owner Name owner Phone asking Price statusCode Completion Status: System MLS Iclerk findAgent (officeNo, agentNo) Office WithAgent Information 1 update Agent(name, officePhone, ...) Office With Revised AgentInformation %) Your first task is to create a first-cut design class diagram for the Update real estate agent use case by extending the domain model class diagram. This requires three steps: (1) Add a controller class. (2) Elaborate each attribute in e hat is, identify the visibility, data type, initial value if applicable, and {key} property if applicable of each attribute in each class. Moreover, add a third compartment to each class as a placeholder for method signature(s). (3) Identify navig sibility. %) Your second task is to create a sequence diagram for the Update real estate agent use case (domain classes and controller class only) by extending the system sequence diagram. 5%) Your third task is to create final design class diagram. oolbar, press ALT+F10 (PC) or ALT+FN+F10 (Mac). and Submit to save and submit. Click Save All Answers to save all answers. Save All Answers S