Chapter 2 RAD Usecase and Scenario Done

Chapter 2: Requirement Analysis
2.1 Introduction
This chapter delves into the current state of property management and showcase systems within
the real estate industry, pinpointing existing challenges and outlining the comprehensive
requirements for the proposed Property Management and Showcase System for Brokers. This
analysis will serve as a blueprint for designing and developing a solution that effectively
addresses the identified needs and offers substantial improvements for real estate professionals
and their clients.
2.2 Current System Description
2.2.1 Problems of the Existing System
The traditional methods currently employed by real estate professionals often involve a
fragmented array of tools and platforms, leading to several key issues:
 Inefficiency and Redundancy: Information is scattered across disparate systems,

resulting in wasted time, increased risk of errors, and a lack of automation for repetitive
tasks.
 Ineffective Listing Showcase:
o Listings are presented inconsistently across platforms, hindering visibility and
appeal.
o Interactive features and virtual tours are often limited, reducing engagement.
 Poor Client Engagement: Communication channels are fragmented, leading to potential
miscommunication and frustration.
o Centralized collaboration platforms are often absent, hindering information
sharing.
o Client access to property information and updates is often limited, impeding
transparency.
 Lack of Data-Driven Insights: Valuable data is siloed across systems, making it
challenging to analyze and leverage for strategic decision-making.
o Reporting and analytics tools are often inadequate, hindering performance
tracking and optimization.
2.3 Requirement Gathering
2.3.1 Requirement Gathering Methodology
To meticulously gather comprehensive requirements for the proposed system, a blend of the
following methodologies will be employed:
 Interviews: In-depth discussions with real estate brokers and property managers will
uncover their pain points, challenges, and desired functionalities.
1
 Observation: Direct observation of workflows and practices within real estate offices
will reveal inefficiencies and areas for improvement.
 Document Analysis: A thorough review of industry reports, literature, and best practices
will provide insights into technological trends and solutions.
2.4. Proposed System
2.4.1. Overview of proposed system
A property listing system is a software platform that makes it easier to advertise

and find properties for sale or rental purposes online. It serves as a bridge between
property owners/managers and potential tenants/buyers, streamlining the search
and connection process The system will offer a centralized, standardized listing of
available properties with complete details and up-to-date listings, catering to the
needs of both consumers and brokers. Brokers will primarily be able to manage
property owners, list properties, sell or rent out properties, and report on the
earnings they made for each category using an organized interface.
2.4.2. Functional Requirements
Functional requirements define a function of a system or its components, where these

functions are described as a set of inputs, the behavior, and outputs. And the expected
Bridge system shall have the following set of functional requirements:
FR-1: The system shall let admin show current listing in different categories.
FR-2: The system shall let admin view the total users.
FR-3: The system shall let admin view total Sales in different categories.
FR-4: The system shall let admin and user login and register.
FR-5: The system shall let admin create Property.
FR-6: The system shall let admin update Property
2
FR-7: The system shall let admin delete Property.
FR-8: The system shall let admin Feature Property.
FR-9: The system shall let admin Search Property.
FR-10: The system shall let admin create Owner.
FR-11: The system shall let admin updated Owner.
FR-12: The system shall let admin delete Owner.
FR-13: The system shall let admin search user.
FR-14: They system shall let admin deactivate user.
FR-15: They system shall let admin view users favorited properties.
FR-16: They system shall let admin Create Advertiser Client info
FR-17: They system shall let admin Create Advertisement
FR-18: They system shall let admin View Featured Properties Table
FR-19: They system shall let admin Add Site information
FR-20: They system shall let admin Update Site information
FR-21: They system shall let admin Update Account information
FR-22: They system shall let admin Add Sub Admin
FR-23: The system shall let clients View Featured Property Listings.
FR-24: The system shall let clients View Property Listing for Sale only or Rent Only
FR-25: The system shall let clients Search Properties
FR-26: The system shall let clients Advance Property Listing search
FR-27: The system shall let clients View Property Details
3
FR-28: The system shall let clients List favorited listing
FR-29: The system shall let clients View Broker Contact Details
2.4.3. Non-Functional Requirements
Non-functional requirements are requirements that specify criteria that can be used to
criticize the operation of a system, rather than specific behaviors. In general, they are
quality attributes of certain software system, for our system, we have selected the
following attributes to be our guides in the development process.
Here are the key characteristics of NFRs:
Not directly related to specific functionalities: They don't specify particular features or
functions, but rather the overall qualities that those features should possess.
Often cross-cutting: They often affect multiple parts of the system, as opposed to functional
requirements that typically focus on individual features.
Measured and tested: They can be measured and tested to ensure they are met, although
measuring them may be more subjective than measuring functional requirements.
Essential for system success: They are crucial for user satisfaction and system adoption, as
they impact the overall user experience and trust in the system.
1. Performance and Scalability:
Page load times: Listings and search results must load within few seconds to ensure a smooth
user experience and keep brokers productive.
High availability: The site must be available 99.5% of the time to avoid any downtime that could
disrupt broker activity and potentially lead to missed deals.
Scalability: The system should be able to handle growing volumes of listings and user
traffic without performance degradation.
2. Security and Data Privacy:
4
Data encryption: Sensitive user and property data must be encrypted at rest and in transit to
ensure confidentiality and prevent unauthorized access.
Authentication and access control: Robust authentication mechanisms and granular access
control levels are crucial to protect sensitive information and restrict unauthorized interactions.
3. Usability and Accessibility:
Intuitive interface: The user interface should be intuitive and easy to navigate for brokers with varying
levels of technical experience.
Mobile responsiveness: The site must be fully responsive and optimized for mobile devices, as
brokers often access it on the go.
4. Error Handling and Extreme Conditions: The system shall examine all inputs before
performing tasks.
5
2.5 System Model
2.5.1 Use Case Model
2.5.1.1 Use Case diagram
6
2.5.1.2 Description of Use-Case Model
This table format presents the use cases, the actors involved, and a brief description of each use case. It
provides a concise overview of the different actions that can be performed by users and administrators on
the real estate broker website.
Use Case ID 001
Use Case Name Show property listing

Participating Actor Admin
Entry condition Actor must login
Flow of Events 1. User navigates to the Dashboard page.
2. The system displays tables contains property
listing per category
Exit condition Actor views property listing
Use Case ID 002
Use Case Name Show total users

2. The system displays a graph of registered users
and total user count
Exit condition Actor views total number of users
Use Case ID 003
Use Case Name Show total sales

2. The system displays a pie chart and a table
that shows total sales of each category
7
Exit condition Actor views total number of sales
Use Case ID 004
Use Case Name Register

Participating Actor Users
Entry condition None
Flow of Events 1. Actor navigates to the login page.
2. Actor clicks register button
3. The system displays register form
4. Actor fills out username, name, phone number
and password.
5. Actor submits form
Exit condition User is Created.
Use Case ID 005
Use Case Name Login
Participating Actor Users, Admin
Flow of Events 1. Actor navigates to the login page.

2. The system displays Login form
3. Actor fills out login form.
4. Actor submits form
Exit condition Actor is Authenticated and redirected to the main page

based on the actor type.
8
Use Case ID 006
Use Case Name Create Property
Entry condition Actor must login.
Flow of Events 1. Actor navigates to the properties page.

2. The system displays list of properties and an
add button.
3. Actor clicks add button.
4. System displays create property form.
5. Actors fills out form.
6. Actor submits form.
Exit condition New property is created.
Use Case ID 007
Use Case Name Update Property
Entry condition Actor must login and at least one property must be
created.
2. The system displays list of properties..
3. Actor clicks on the property item edit button.
4. System displays populated property form.
5. Actors updates the form.
6. Actor submits form.
Exit condition Property information is update.
9
Use Case ID 008
Use Case Name Delete Property
created.
3. Actor clicks on the property item delete button.
4. System displays a confirmation dialogue.
5. Actors clicks confirm button.
Exit condition Property information is deleted.
Use Case ID 009
Use Case Name Feature Property
created.
3. Actor clicks on the property item feature
button.
4. System displays a form with “from” and “to”
date options.
5. Actor fills out feature date information.
6. Actors submits form.
Exit condition Property information is featured at the top of the home

page.
10
Use Case ID 010
Use Case Name Search Property
created.
3. Actor inserts search key on the search box.
4. System displays list of properties matching
keyword by property name, id, type, owner
name.
Exit condition System display list of properties matching the key
word.
Use Case ID 011
Use Case Name Create Owner

2. The system displays list of owners and an add
button.
3. Actor clicks add button.
4. System displays add owner form.
5. Actor fills out owner information and submit
form
Exit condition System Creates Owner
Use Case ID 012
11
Use Case Name Update Owner
Entry condition Actor must login and at least one owner must be
created
2. The system displays list of owners.
3. Actor clicks on the specific owner list item edit
button..
4. System displays populated owner form.
5. Actor updates owner information and submit
form
Exit condition System updates Owner information.
Use Case ID 013
Use Case Name Delete Owner
Entry condition Actor must login and at least one owner must be
created
3. Actor clicks on the specific owner list item
delete button..
4. System displays confirmation dialogue.
5. Actor clicks confirm button.
Exit condition System deletes Owner information.
Use Case ID 014
12
Use Case Name Search Users
Entry condition Actor must login and at least one user must be
registered
Flow of Events 1. Actor navigates to the users page.
2. The system displays list of users.
3. Actor clicks on the search box and inputs
search key
4. System display users that have information that
matches the search key.
Exit condition System displays list of users that match the search key.
Use Case ID 015
Use Case Name Deactivate Users
registered
3. Actor clicks on the specific user list item
deactivate button.
5. Actor clicks confirm button.
Exit condition System deactivates specific user.
Use Case ID 016
13
Use Case Name View User’s Favourite Property
registered and one property must be favorited.
2. The system displays list of users and list of
properties favorited by users.
3. Actor views properties.
Exit condition System displays list of favorited properties by users.
Use Case ID 017
Use Case Name Create Client
Entry condition Actor must login and
Flow of Events 1. Actor navigates to the advertisements page.

2. The system displays an add client button.
3. Actor clicks add client button.
4. System provides add client form
5. Actor fills out client information and submit
form.
Exit condition System creates a client.
Use Case ID 018
Use Case Name Create Advertisement
14
Entry condition Actor must login and at least

2. The system displays an add advertisement
button.
3. Actor clicks add advertisement button.
4. System provides add advertisement form
5. Actor fills out advertisement information and
submit form.
Exit condition System creates an advertisement.
Use Case ID 019
Use Case Name View Featured Properties
Entry condition Actor must login and at least and at least one
property must be feature.
2. The system displays a list of properties that are
featured with feature information.
3. Actor views featured properties
Exit condition System displays featured properties.
Use Case ID 020
Use Case Name Add Site Information
15
Flow of Events 1. Actor navigates to the settings page.

2. The system displays a list of site settings.
3. Actor adds site setting information like Title,
phone number, email and useful links.
Exit condition System saves site information.
Use Case ID 021
Use Case Name Update Site Information
Flow of Events 1. Actor navigates to the settings page.

3. Actor updates site setting information like
Title, phone number, email and useful links.
Exit condition System updates site information.
Use Case ID 022
Use Case Name Update Account Information
Flow of Events 1. Actor navigates to the Accounts page.
16
2. The system displays a list of Account
information like password and email.
3. Actor updates account information.
Exit condition System updates account information.
Use Case ID 023
Use Case Name Add Sub Admin
Flow of Events 1. Actor navigates to the Accounts page.

information and add Admin button.
3. Actor clicks add Admin button.
4. System displays add admin form
5. Actor fills out sub admin information and
submits form.
6. System creates sub admin.
Exit condition System creates sub admin.
Use Case ID 024
Use Case Name View Featured Properties
Participating Actor Admin,Users
Flow of Events 1. Actor navigates to the Home page.

2. The system displays a list of featured
17
properties at the top.
3. Actor views Featured property.
Exit condition System displays featured properties.
Use Case ID 025
Use Case Name Filter listings by property type

2. The system displays a list of properties and
filtering options for sale and rental listings.
3. Actor toggles for sale and for rent button.
4. System filters out properties matching the filter
criteria.
Exit condition System displays filtered properties.
Use Case ID 026
Use Case Name Search for properties

18
search box.
3. Actor inserts search key and submits.
4. System filters out properties matching the
search key.
Use Case ID 027
Use Case Name Advanced search for properties

filter options.
3. Actor updates filter options and submits.
criteria.
Use Case ID 028
Use Case Name View property Detail
Participating Actor Admin, Users
19
2. The system displays a list of properties.
3. Actor clicks on any property.
4. System redirects actor to property detail page
that shows details of the property like full
description, images, all amenities.
Exit condition System displays property details.
Use Case ID 029
Use Case Name Favourite property
Entry condition User must login.

3. Actor clicks on any property favourite button.
4. System saves property as favourite and marks
the property on the UI.
Exit condition System saves user’s favourite property.
Use Case ID 030
Use Case Name View Favourite properties
Flow of Events 1. Actor navigates to the Favourites page.

2. The system displays a list of favourite
20
properties.
3. Actor views properties.
Exit condition System displays list of favourite properties.
Use Case ID 031
Use Case Name View Broker Contact Details
Participating Actor Users, Admin
Flow of Events 1. Actor navigates to the Contact us page.

2. The system displays broker contact details
3. Actor views contact details.
Exit condition System displays broker contact details.
2.5.2 Scenario
Table Scenario
Table scenario registration
Scenario ID S001
Scenario Name Show property listing
Related Use Case 001 - Show Property Listing
Participating Actor Jane as Admin
Pre condition Jane must login
Flow of Events 1. Jane navigates to the Dashboard page.
2. The system displays tables contains property
listing per category
Exit condition Jane views property listing
Scenario ID 002
21
Scenario Name Show total users
Related Use Case 002 - Show total users
Participating Actor John as Admin
Entry condition John must login
Flow of Events 1. John navigates to the Dashboard page.
2. The system displays a graph of registered users
and total user count
Exit condition John views total number of users
Scenario ID 003
Scenario Name Show total sales
Entry condition Jane must login
Flow of Events 1. Jane navigates to the Dashboard page.
2. The system displays a pie chart and a table that
shows total sales of each category
Exit condition Jane views total number of sales
Scenario ID 004
Scenario Name Register

Related Use Case 004 - Register
Participating Actor Mike as User
Flow of Events 1. Mike navigates to the login page.
2. Mike clicks register button
3. The system displays register form
4. Mike fills out username, name, phone
number and password.
5. Mike submits form
Exit condition Mike’s Profile is Created.
Scenario ID 005
22
Scenario Name Login
Related Use Case 005 - Login

Participating Actor John as User, Admin
Flow of Events 1. John navigates to the login page.

2. The system displays Login form
3. John fills out login form.
4. John submits form
Exit condition John is Authenticated and redirected to the main page

based on the actor type.
Scenario ID 006
Scenario Name Create Property
Related Use Case 006 - Create Property

Entry condition Jane must login.
Flow of Events 1. Jane navigates to the properties page.

2. The system displays list of properties and an add
button.
3. Jane clicks add button.
4. System displays create property form.
5. Jane fills out form.
6. Jane submits form.
Exit condition Jane created a New property is created.
Scenario ID 007
23
Scenario Name Update Property
Related Use Case 007 - Update Property

Entry condition John must login and at least one property must be
created.
Flow of Events 1. John navigates to the properties page.
3. John clicks on the property item edit button.
4. System displays populated property form.
5. John updates the form.
6. John submits form.
Exit condition John updated property information.
Scenario ID 008
Scenario Name Delete Property
Related Use Case 008 - Delete Property

Entry condition Jane must login and at least one property must be
created.
3. Jane clicks on the property item delete button.
5. Jane clicks confirm button.
Exit condition Jane delete Property information.
Scenario ID 009
Scenario Name Feature Property
24
Related Use Case 009 - Feature Property
Entry condition John must login and at least one property must be
created.
2. The system displays list of properties.
3. John clicks on the property item feature button.
4. System displays a form with “from” and “to”
date options.
5. John fills out feature date information.
6. John submits form.
Exit condition John has featured Property information at the top of

the home page.
Scenario ID 010
Scenario Name Search Property
Related Use Case 010 - Search Property

Entry condition Jane must login and at least one property must be
created.
2. The system displays list of properties.
3. Jane inserts search key on the search box.
4. System displays list of properties matching
keyword by property name, id, type, owner name.
Exit condition Jane views list of properties matching the key word.
Scenario ID 011
25
Scenario Name Create Owner
Related Use Case 011 - Create Owner

Entry condition John must login

2. The system displays list of owners and an add
button.
3. John clicks add button.
4. System displays add owner form.
5. John fills out owner information and submit
form
Exit condition John Creates Owner
Scenario ID 012
Scenario Name Update Owner
Related Use Case 012 - Update Owner

Entry condition Jane must login and at least one owner must be
created
3. Jane clicks on the specific owner list item edit
button.
4. System displays populated owner form.
5. Jane updates owner information and submit form
Exit condition John updates Owner information.
Scenario ID 013
26
Scenario Name Delete Owner
Related Use Case 013 - Delete Owner

Entry condition Jane must login and at least one owner must be
created
3. Jane clicks on the specific owner list item delete
button.
4. System displays confirmation dialogue.
Exit condition Jane deletes Owner information.
Scenario ID 014
Scenario Name Search Users
Related Use Case 014 - Search Users

Entry condition John must login and at least one user must be
registered
Flow of Events 1. John navigates to the users page.
3. John clicks on the search box and inputs search
key
4. System display users that have information that
matches the search key.
Exit condition John views list of users that match the search key.
Scenario ID 015
27
Scenario Name Deactivate Users
Related Use Case 015 - Deactivate Users

Entry condition Jane must login and at least one user must be
registered
Flow of Events 1. Jane navigates to the users page.
3. Jane clicks on the specific user list item
deactivate button.
Exit condition Jane deactivates specific user.
Scenario ID 016
Scenario Name View User’s Favourite Property
Related Use Case 016 - View User’s Favourite Property

Entry condition John must login and at least one user must be
registered and one property must be favorited.
Flow of Events 4. John navigates to the users page.
5. The system displays list of users and list of
properties favorited by users.
6. John views properties.
Exit condition John views list of favorited properties by users.
Scenario ID 017
28
Scenario Name Create Client
Related Use Case 017 - Create Client

Entry condition Jane must login and
Flow of Events 1. Jane navigates to the advertisements page.

2. The system displays an add client button.
3. Jane clicks add client button.
4. System provides add client form
5. Jane fills out client information and submit form.
Exit condition Jane created a client.
Scenario ID 018
Scenario Name Create Advertisement

Entry condition John must login and at least
Flow of Events 1. John navigates to the advertisements page.

2. The system displays an add advertisement
button.
3. John clicks add advertisement button.
4. System provides add advertisement form
5. John fills out advertisement information and
submit form.
Exit condition John creates an advertisement.
Scenario ID 019
29
Scenario Name View Featured Properties
Related Use Case 019 - View Featured Properties

Entry condition Jane must login and at least and at least one
property must be feature.
Flow of Events 1. Jane navigates to the advertisements page.
2. The system displays a list of properties that are
featured with feature information.
3. Jane views featured properties
Exit condition Jane views featured properties.
Scenario ID 020
Scenario Name Add Site Information
Related Use Case 020 - Add Site Information

Entry condition John must login.
Flow of Events 1. John navigates to the settings page.

3. John adds site setting information like Title,
Exit condition John adds site information.
Scenario ID 021
Scenario Name Update Site Information
Related Use Case 021 - Update Site Information
30
Entry condition Jane must login.
Flow of Events 1. Jane navigates to the settings page.

3. Jane updates site setting information like Title,
Exit condition Jane updates site information.
Scenario ID 022
Scenario Name Update Account Information
Related Use Case 022 - Update Account Information

Flow of Events 1. John navigates to the Accounts page.

information like password and email.
3. John updates account information.
Exit condition System updates account information.
Scenario ID 023
Scenario Name Add Sub Admin
Related Use Case 023 - Add Sub Admin

Flow of Events 1. John navigates to the Accounts page.

31
information and add Admin button.
3. John clicks add Admin button.
4. System displays add admin form
5. John fills out sub admin information and submits
form.
6. System creates sub admin.
Exit condition John creates sub admin.
Scenario ID 024
Scenario Name View Featured Properties
Related Use Case 024 - View Featured Properties

Participating Actor Mike as Admin,Users

2. The system displays a list of featured properties
at the top.
3. Actor views Featured property.
Exit condition Mike views featured properties.
Scenario ID 025
Scenario Name Filter listings by property type
Related Use Case 025 - Filter listings by property type

Participating Actor Mary as Admin,Users
Flow of Events 1. Mary navigates to the Home page.

32
filtering options for sale and rental listings.
3. Mary toggles for sale and for rent button.
criteria.
Exit condition Mary views filtered properties.
Scenario ID 026
Scenario Name Search for properties
Related Use Case 026 - Search for properties

Participating Actor Mike as Admin,Users
Flow of Events 1. Mike navigates to the Home page.

search box.
3. Mike inserts search key and submits.
4. System filters out properties matching the search
key.
Exit condition Mike views filtered properties.
Scenario ID 027
Scenario Name Advanced search for properties
Related Use Case 027 - Advanced search for properties

Participating Actor Mary Admin,Users

2. The system displays a list of properties and filter
33
options.
3. Mary updates filter options and submits.
criteria.
Exit condition Mary views filtered properties.
Scenario ID 028
Scenario Name View property Detail
Related Use Case 028 - View property Detail

Participating Actor Mike as Admin, Users
Flow of Events 1. Mike navigates to the Home page.

3. Mike clicks on any property.
4. System redirects Mike to property detail page that
shows details of the property like full description,
images, all amenities.
Exit condition Mike views property details.
Scenario ID 029
Scenario Name Favourite property
Related Use Case 029 - Favourite property

Participating Actor Mary as User
Entry condition Mary must login.
34
3. Mary clicks on any property favourite button.
4. System saves property as favourite and marks
the property on the UI.
Exit condition Mary saves favourite property.
Scenario ID 030
Scenario Name View Favourite properties
Related Use Case 030 - View Favourite properties

Participating Actor Mike as User
Flow of Events 1. Mike navigates to the Favorites page.

2. The system displays a list of favourite
properties.
3. Mike views properties.
Exit condition Mike views list of favourite properties.
Scenario ID 031
Scenario Name View Broker Contact Details
Related Use Case 031 - View Broker Contact Details

Participating Actor Mary as Users, Admin
Flow of Events 1. Mary navigates to the Contact us page.
35
2. The system displays broker contact details
3. Mary views contact details.
Exit condition Mary views broker contact details.
2.5.3 Object Model

2.5.3.1 Data Dictionary
Table
Object Attributes Description

User - Username - Password - Represents a user of the real
Email estate broker website
Property - Property ID - Type - Represents a property listed on

Location - Price - the website
Description - Images -
Contact Information
Administrator - Username - Password Represents an administrator of

the real estate broker website
2.5.3.2 Class Diagram
36
2.5.4 Dynamic Modeling
2.5.4.1 Sequence diagrams
Sequence Diagram 1: Searching for Properties
37
Sequence Diagram 2: Contacting a Broker
38
2.5.4.2 Activity Diagram
39
40

Chapter 2 RAD Usecase and Scenario Done

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 2 RAD Usecase and Scenario Done

Uploaded by

Copyright:

Available Formats

Chapter 2: Requirement Analysis

2.2 Current System Description

2.2.1 Problems of the Existing System

 Inefficiency and Redundancy: Information is scattered across disparate systems,

2.3 Requirement Gathering

2.3.1 Requirement Gathering Methodology

2.4. Proposed System

2.4.1. Overview of proposed system

A property listing system is a software platform that makes it easier to advertise

2.4.2. Functional Requirements

Functional requirements define a function of a system or its components, where these

FR-5: The system shall let admin create Property.

FR-6: The system shall let admin update Property

FR-8: The system shall let admin Feature Property.

FR-9: The system shall let admin Search Property.

FR-10: The system shall let admin create Owner.

FR-11: The system shall let admin updated Owner.

FR-12: The system shall let admin delete Owner.

FR-13: The system shall let admin search user.

FR-14: They system shall let admin deactivate user.

FR-17: They system shall let admin Create Advertisement

FR-19: They system shall let admin Add Site information

FR-20: They system shall let admin Update Site information

FR-21: They system shall let admin Update Account information

FR-22: They system shall let admin Add Sub Admin

FR-25: The system shall let clients Search Properties

FR-27: The system shall let clients View Property Details

2.4.3. Non-Functional Requirements

Here are the key characteristics of NFRs:

1. Performance and Scalability:

2. Security and Data Privacy:

2.5.1 Use Case Model

2.5.1.1 Use Case diagram

Use Case ID 001

Use Case Name Show property listing

Use Case ID 002

Use Case Name Show total users

Use Case ID 003

Use Case Name Show total sales

Use Case ID 004

Use Case Name Register

Use Case ID 005

Use Case Name Login

Participating Actor Users, Admin

Entry condition None

Flow of Events 1. Actor navigates to the login page.

Exit condition Actor is Authenticated and redirected to the main page

Use Case Name Create Property

Participating Actor Admin

Entry condition Actor must login.

Flow of Events 1. Actor navigates to the properties page.

Exit condition New property is created.

Use Case ID 007

Use Case Name Update Property

Participating Actor Admin

Exit condition Property information is update.

Use Case Name Delete Property

Participating Actor Admin

Exit condition Property information is deleted.

Use Case ID 009

Use Case Name Feature Property

Participating Actor Admin

Exit condition Property information is featured at the top of the home