PRESENTATION

By AMAN SADANA
SYSTEM ANALYSIS
Event Table
Event Trigger Source Use Case Response Destinatio
n
Customer/
employee
wants to
access
system
System
access
Customer/employe
e
System
Access
Customer
accessed
site
Employee
Customer
wants to
register/up
date an
account
Register/u
pdate
account
Customer Register
/update
account
Customer
requires to
input
details
Employee
Customer
wants to
submit
registratio
n
Submit
registratio
n
Customer Submit
registratio
n
System
Employee
wants to
list new
properties
Create
properties
Employee Add
properties
Property
summary
details
System
Customer
wants to
search
properties
Search
properties
Customer Search
properties
Returns
list of
properties
Employee
Customer
wants to
know
details
about
property
View
property
details
Customer View
property
details
Summary
details of
property
Customer
Employee
want to
search
customers
/sellers
Search
customers
Employee Search
customers
Returns
list of
customers
/sellers
Employee
Employee
wants to
add seller's
contact
Create
sellers
contact
Employee Create
sellers
contact
Contact
summary
details
System
USE CASE DIAGRAM
USE CASE DESCRIPTION
Use case name: System Access
Scenario: Access system
Triggering event: System access
Brief description System detects visit from either customer or
employee
Actors: Customer/ Staff
Related use cases
Stakeholders:
Preconditions: Customer/ staff must exist
System must exist
Postconditions: System is accessed
Flow of activities: Actors System
1.Enters site URL 1.1 Server receives
request
1.2Server answers
request
1.3 Server allows user to
access system
Exception conditions: 1.1 System is down or under maintenance
USE CASE DESCRIPTION
Use case name: Register/update account
Scenario: Register/update account
Triggering event: Actor click on register button
Actor edit account and update
Brief description
Actors: Customer/ Staff
Related use cases
Stakeholders:
Preconditions: Customer/ staff must exist.
Registration must exist.
Update must exist.
Postconditions: Account is registered
Account is updated
Flow of activities: Actors System
1. Request account
2.Enter address
3. View account
4. Edit details
1.1 create customer
2.1 creates address
4.1Update account
Exception conditions:
USE CASE DESCRIPTION
Use case name: Submit registration
Scenario: Submit registration
Triggering event: Actor input complete and submit
Brief description Creates name, address and history
Actors: Customer/ Staff
Related use cases Register/update account
Stakeholders:
Preconditions: Customer/staff must exist
Required field must be filled
Postconditions: Account created
Flow of activities: Actors System
1. Enter registration form
2. Submit registration
form
1.1 Creates customer
2.1 Information saved to
database
2.2 Account created
Exception conditions: 1.1 information inputted are invalid or does not
match
USE CASE DESCRIPTION
Use case name: Add properties
Scenario: Add property for sale
Triggering event: Potential property on sale was not yet listed on the
system
Brief description
Actors: Staff
Related use cases
Stakeholders: Customer, Seller, Agency
Preconditions: Property must exist
Property must be on sale
Property must be new
Postconditions: Account created
Flow of activities: Actors System
1. enter property
2. Assigns property
number
3. enter description
4.enter category
1.1 Creates property
2.1 Create property
number
3.1 Create description
4.1 Create category
Exception conditions: 1.1 Property was already created on the system
USE CASE DESCRIPTION
Use case name: Search properties
Scenario: Search properties for sale
Triggering event: Actor want to look up for property
Brief description Retrieve property description, category and seller
Actors: Customer/ Staff
Related use cases
Stakeholders:
Preconditions: Property must exist
Postconditions: Return list of properties
Flow of activities: Actors System
1. Search property
keyword
2. If property unavailable,
create new property
3. Click property profile
1.1 Returns list of
properties
2.1 System update
property records
3.1 Allows access to
property profile
Exception conditions: 1.1 keyword does not match or exist
USE CASE DESCRIPTION
Use case name: View properties description
Scenario: View properties description
Triggering event: Customer wants to know details of property
Brief description
Actors: Customer
Related use cases Search properties
Stakeholders:
Preconditions: Property must exist
Postconditions: Return property description, category and seller
Flow of activities: Actors System
1. Click property profile
2. If property description
is unavailable, add
description
1.1 Reveals property
description
2.1 System updates
property profile
Exception conditions: 1.1 Property does not exist
USE CASE DESCRIPTION
Use case name: Search Customer
Scenario: Search Customer
Triggering event: Staff wants to search regular or potential customer
Brief description
Actors: Staff
Related use cases
Stakeholders: Customer, Seller and Agent
Preconditions: Customer must exist
Postconditions: Return property description, category and seller
Flow of activities: Actors System
1. Enters customer
number
2. if customer not
available, create
customer profile
1.1 returns customer
profile
2.1 System updates
customer records
Exception conditions: 1.1 Customer does not exist
USE CASE DESCRIPTION
Use case name: Create contact
Scenario: Create contact of potential seller
Triggering event: Staff wants to record contact of potential seller
Brief description Records sellers name, address, contact and property
on sale
Actors: Staff
Related use cases
Stakeholders: Agent, customer
Preconditions: Seller must exist
Seller's property passed the criteria
Postconditions: Seller's contact information is created
Flow of activities: Actors System
1. Enter contact
2. Enter address
3. Enter phone number
1.1 creates contact
2.1 Creates address
3.1 Create phone number
3.2 Update contact
record
Exception conditions: 1.1 Customer does not exist
USE CASE DESCRIPTION
Use case name: Search contact
Scenario: Search contact to request seller for assessment and
details
Triggering event: Staff wants to contact a seller for assessment and
details
Brief description
Actors: Staff
Related use cases Create contact
Stakeholders: Agent, customer
Preconditions: Seller's contact must exist
Seller's property passed the criteria
Postconditions: Seller's contact acquired
Flow of activities: Actors System
1. Search contact
2. If contact available,
staff send message
3. If contact unavailable,
staff create contact
1.1 System returns
contact details
2.1 System record history
3.1 System updates
contact records
Exception conditions: 1.1 Seller's contact unavailable or has been changed
1.1 Seller does not exist
CLASS DIAGRAM