1- Draw a use case diagram for the following narrative:

Case Study: Real Estate Multiple Listing Service System

The Real Estate Multiple Listing Service System (REMLSS) supplies information that local real estate agents
use to help them sell houses to their customers. During the month, agents list houses for sale (listings) by
contracting with homeowners. The agent works for a real estate office, which sends information on the listing to
the multiple listing service (MLS). Therefore, any agent in the community can get information on the listing.

Information on a listing includes the address, year built, square feet, number of bedrooms, number of
bathrooms, owner name, owner phone number, asking price and status code.

At any time during the month, an agent might directly request information on listings that match customer
requirements, so the agent contacts the MLS with the request. Information on the house, on the agent who listed
the house, and on the real estate office the agent works for is provided. For example, an agent might want to
call the listing agent to ask additional questions or call the home owner directly to make an
appointment to show the house.

Twice each month (on 15th and 30) the MLS produces a listing book that contains information on all listings.
These books are sent to all of the real estate agents. Many real estate agents want the books, so they are
provided even though the information is out of date. Sometimes agents and owners decide to change
information about a listing, such as reducing the price, correcting previous information on the house, or
indicating that the house is sold. The real estate office sends in these change requests to the MLS when the agent
asks the office to do so.

Answer:

1
 2. Develop a fully developed use case description, activity diagram, and class diagram
(abbreviated) for the first use case Add New Listing.

Full Use Case Description for Add a Listing use case

Use Case Name: Add new listing

Scenario: Add a single listing
Triggering Event: Agent and/or Clerk adds a new listing to the database
Brief Description: Agents list houses for sale (listings) by contracting with homeowners. The agent
works for a real estate office,
which sends information on the listing to the multiple listing service (MLS).
Information on a listing includes the
address, year built, square feet, number of bedrooms, number of bathrooms,
owner name, owner phone
number, asking price and status code.
Actors: Real Estate Office Agent and/or Clerk
Stakeholders: Real Estate Office Agent(s) and Clerk(s)
Preconditions: Real Estate Agent and/or Clerk, and homeowner information must exist

Postconditions: New listing object must exist

Flow of Events: Actor ( ) System

1. Enter Agent info 1. Verify agent – find and display status

2. Enter new listing 2. Create new listing, display it
information on a property 4. Terminate session
3. Verify Listing
4. Quit session

Exception Conditions:
1. If agent not found in database, terminate session
3. If errors in listing, edit listing

2
3- Draw the activity diagram for “add new listing” use case:

3
4- Draw the System Sequence Diagram (SSD) for “add new listing” use case:

4
5