Download Document

ANALYSIS SCENARIOS
A scenario is an elaboration on the user case model. A scenario will add more
detail to sub-cases by describing a specific sequence of events. The user cases and the
analysis scenarios together constitute the functional requirements for the system. The
object of the analysis scenario is to provide enough insight to enable the development
team to develop Object Interaction Diagrams. The analysis scenario is also an effective
way to define the requirements of each cycle in terms of which scenarios that must be
implemented.
User Case 1: Buyer Qualification
Scenario 1.1: Client seeks financial qualification for a known amount (Granted)
Assumptions:
 Acceptable debt to income ratio given the interest rate
Outcomes:
 Will return the terms and conditions of the loan
Scenario 1.2: Client seeks financial qualification for a known amount (Denied)
Assumptions:
 Unacceptable debt to income ratio given the interest rate
Outcomes:
 Will return reasons for the denial
Scenario 1.3: Client seeks financial qualification for a maximum loan amount
Assumptions:
 Acceptable debt to income ratio given the interest rate
Outcomes:
 Will return the greatest possible loan amount for the client
User Case 2: Cost Comparisons
Scenario 2.1: Creates a side by side comparison of up to three loan programs
Assumptions:
 Loan specifics known for the three loans
Outcomes:
 Will provide a printable form containing the side by side comparison
User Case 3: P.I.T.I. Calculations
Scenario 3.1: Computes the Principal Interest, Tax and Insurance elements of the total
monthly loan repayment schedule.
Assumptions:
 Real estate taxes, hazard insurance and mortgage insurance known for the
given loan.
Outcomes:
 Returns the additional cost associated with loan.
User Case 4: Loan Comparisons
Scenario 4.1: Compares actual cost for two different loans over a given amount of time
Assumptions:
 Loan specifics for the two loans are known
Outcomes:
 Returns the actual cost for each loan option
User Case 5: Mortgage Refinance
Scenario 5.1: Compares the borrower’s current loan to a proposed one.
Assumptions:
 Know the specifics for the original loan.
 Know the specifics for the new loan.
Outcomes:
 Will return the difference in monthly payments.
 Will return the difference in loan balances given a point in the future.
 Will return the number of months necessary to regain the cost of
originating the new loan.
User Case 6: Amortization Schedules
Scenario 6.1:
Assumptions:
Outcomes:
User Case 7: Fixed Rate Loan vs. ARM
Scenario 7.1: Compares a fixed rate mortgage to an adjustable rate mortgage.
Assumptions:
 Negative amortization allowed.
Outcomes:
 Will return a best and worst case scenario given the number of months a
borrower intends to keep the mortgage
User Case 8: Financial Calculator
Scenario 8.1: The loan officer would like to use the financial calculator
Assumptions:
 The loan officer knows what they are doing
Outcomes:
 Will return the correct answer
User Case 9: Closing Cost Estimate
Scenario 9.1: Calculates the actual cost of obtaining the loan for the buyer.
Assumptions:
 Loan specifics known
Outcomes:
 Will return the monthly PITI
 Will return the APR
User Case 10: Seller’s Net Proceeds
Scenario 10.1: Calculates the cost to the seller for the sales transaction.
Assumptions:
 Loan specifics known
Outcomes:
 Will return the closing costs associated with selling a home and the real
estate commissions.
 Will return an investment schedule should the seller opt to invest some of
the proceeds
User Case 11: Rent vs. Buy
11.1: Compares the cost of renting to home ownership.
Assumptions:
 Loan specifics known.
 Current renting situation known.
Outcomes:
 Will return the estimated appreciation of the property.
 Will return the equity to be gained over time in the home.
 Will return the tax advantages of home ownership.
User Case 12: Saving User Data
12.1: Saves the users data for later retrieval.
Assumptions:
 Accurate user information.
 Complete user information.
Outcomes:
 Accurately saves user data.
User Case 13: Retrieving User Data
13.1: Retrieves User Data from the database.
Assumptions:
 User is in the system.
Outcomes:
 Correctly restores user’s information.
User Case 14: Deleting User Data
14.1: Deletes user profile from the database.
Assumptions:
 User is in the system.
Outcomes:
 User is removed without corrupting other user accounts.
User Case 15: Program Variables
15.1: Mortgage broker will set the initial values for the program.
Assumptions:
 Mortgage broker is familiar with the program.
Outcomes:
 The desired default values are initialized.