Team moogle group project 1

Mobile Home Finding APPLICATION
Software Requirements Document
Version 1.0
Moogle, Incorporated
9000 North Torrey Pines Road
La Jolla, California 92037

Home Finder Application Software Requirements Document V1.0
Moogle, Inc. Proprietary Information Page 1 of 50
Table of Contents
1. Introduction ........................................................................................................................................................1
2. Acronyms ............................................................................................................................................................2
3. Need Statement..................................................................................................................................................3
4. Requirements list ................................................................................................................................................4
4.1. Concept Requirement List............................................................................................................................4
4.2. Derived Requirements .................................................................................................................................8
4.3. Key Performance Parameters (KPPs) ........................................................................................................ 12
4.4. Requirement Validation............................................................................................................................ 13
5. Function List......................................................................................................................................................17
6. System Diagrams...............................................................................................................................................20
6.1. Context Diagram ....................................................................................................................................... 20
6.2. System Hierarchy Block Diagram (SBD) .................................................................................................... 21
6.3. Function Block Diagram (FBD)................................................................................................................... 22
6.4. Physical Block Diagram (PBD).................................................................................................................... 23
7. Interface Details................................................................................................................................................24
8. Requirement Analysis Sheets (RAS)..................................................................................................................25
9. Requirement Traceability Matrix......................................................................................................................30
10. Risk Analysis Sheets..........................................................................................................................................34
11. Summary...........................................................................................................................................................44
12. References........................................................................................................................................................45
13. Team schedule..................................................................................................................................................46

List of Tables
Table 1: Home Search Apps Primitive Requirements List ..........................................................................................7
Table 2: Home Search SW Apps KPPs...................................................................................................................... 12
Table 3: Home Search SW Apps Requirements Validation ..................................................................................... 16
Table 4 : Home Search SW Apps Interfaces Details................................................................................................. 24
Table 5: Requirement Traceability Matrix............................................................................................................... 33

List of Figures
Figure 1:Context Diagam for Home Finder Apps..................................................................................................... 20
Figure 2: Home Finder Application System Block Diagram..................................................................................... 21
Figure 3: Home Search SW apps FBD ...................................................................................................................... 22
Figure 4: Home Search SW apps PBD...................................................................................................................... 23

1
1. Introduction
Moogle was formed in the early days of the mobile era shortly after the introduction of the first true smart
phone the Apple iPhone. The core leadership of our team is composed of seasoned lifestyle and software
development experts:
Ahmed Saeed Alqahtani, Saudi Arabia, Ministry Of Defense - Payroll Accountant
Jignesh Doshi, Embedded Software Architect
Daniel Madson, Lifestyle Consultant to the Time Challenged Professional
Hangkawi Pun, Technical Director
This document presents the software requirements for the Home Finder Application, an innovative application
that injects an individual’s lifestyle need into the tedious, time consuming search for the perfect abode.

2
2. Acronyms
- MLS® Server – Multiple Listing Services server
- GPS – Global Positioning System
- OS – Operating system
- HLOS – High Level Operating System
- API – Application Programming Interface

3
3. Need Statement
Both today’s market and today's information hungry home shoppers demand a home searching tool that not
only will find homes based on an individual’s physical needs (e.g. number of bedrooms), but also on their
lifestyle needs as well. This quality of life needs include:
1. Lifestyle factors (e.g., shopping interests, restaurants, school rating)
2. Proximity to particular locations (e.g., school districts, neighborhoods)
3. Location crime statistics
4. Location demographics
Homebuyers in today’s market have many properties available to them but increasingly less time to find the one
that is ideal to them. The Home finder software will be available to user on desktop PCs, tablets devices and
smartphones tool will provide a solution on fingertip – from searching and alerting new listings to scheduling a
visit, assisting in preparation of offers, and submitting offers directly with realtors.

4
4. Requirements list
4.1. Concept Requirement List
CRL-001
10 December 2012
CONCEPT REQUIREMENTS LIST
FOR
HOME FINDER APPLICATION
Prepared By: ________________________________
Harry Requirements
Requirements Analysis
Approved By: ________________________________
Mogie Headguy
Mobile Lifestyle Applications
Chief Engineer/PIT Manager
Requirement
Number
Attribute Relation Value & Units
Hardware Requirements
1. Supported OS Is Windows, Mac, iOS and Android.

5
2. UI supported orientation for tablets
and smartphones
Is Landscape and Portrait.
3. Search function Requires Internet connectivity.
4. Cached search results >= 5 map containing search results.
5. Search by current location Requires GPS connection.
6. Point of sale Has App store.
7. Selling price of advertisement
supported version of the application
Is US $0.00 (Free).
8. Selling price of no-advertisement
version of the application
Is US $5.00 (one time charge).
9. Charge of realtors listing inside the
application
Is US $100 (per property).
10. Cost of downloading app updates Is US $0.00 (Free).
Functional Requirements – Search Functions
11. Home Search database Is Local MLS® server.
12. The homepage of the app Is A map displaying the users’ approximate
locations and tools for search properties.
13. Search tool Has Free-text search.
14. Keyboard tool Is Loaded automatically for the free-text
search tool
15. Support locale Is American English.
16. Search criteria Has Range of year the property was built in.
17. Search criteria Has Range of prices in US dollars.
18. Search criteria Has Search by address.
19. Search criteria Has Range of distance from target location in
miles.
20. Search criteria Has Minimum number of bedrooms desired.

6
21. Search criteria Has Minimum number of bathrooms desired.
22. Search criteria Has Minimum home (in square feet) desired.
23. Search criteria Has Minimum lot (in square feet) desired.
24. Search criteria Has Maximum property tax rate imposed.
25. Search criteria Has Property type desired.
26. Search Has >=1 search criteria.
27. Search tool Has Input validation function.
28. Search criteria Has Users’ current locations.
Functional Requirements – Display of Search Results
29. Display of search results Has List view and map view.
30. Display of search results Has Sorting option.
31. Display of search results in list view Is 20 search results initially.
32. Display of search results in map view Has An icon representing the property and the
asking price.
33. Blurb of property Is Displayed when tapping/hovering mouse
over the icon of the property.
34. Fill description of property Is Displayed when double tapping/double
clicking the icon of the property.
35. Contacts of realtors Has Phone numbers or email address.
App Tools Customization
36. The application Has A means of saving search criteria.
37. The application Has A means of saving >=1 search results.
38. The application Has Alerts for new listings matching user
preferences.
39. Starting page of the application Is The page where users last leave off.
User registration

7
Table 1: Home Search Apps Primitive Requirements List
40. Information required to register = Username, password, and e-mail address.
41. User profile page Has Settings for user information update.
42. The application Has Automatic login function.
43. The application Has Password retrieval function.

8
4.2. Derived Requirements
Hardware requirement
1. The application shall run on the following devices:
 Apple iPhone 4 and iPhone5
 Apple iPad and iPad2
 Android devices of 130mm – 190mm (length) x 70mm – 120 mm (width) of screen size
Blackberry
 Windows 7 or Mac OS X Snow Leopard system running on desktop or laptop computers.
Operation requirements
2. The application shall support portrait and landscape orientations in tablet and smartphone devices.
3. The application shall require an Internet connection when users perform a search operation.
4. The application shall be able cache between five and twenty map areas with search results.
5. The application shall require a GPS connection if the search criteria specifies to consider the users’
current locations.
Business Model Requirements
6. The application shall be downloadable through Android Play Store, Apple App Store and direct
download via tool website.
7. The ad supplemented version shall display one full screen ad on application startup
8. The ad supplemented version shall devote 10% of the screen to advertisements that the user will be
allowed to dismiss after three seconds.
9. The paid version will not display any advertisements and will not display an advertisement during the
application execution.
10. When updates of the tool are available, users shall receive a notification via their device and users shall
decide to download the updates or not.

9
Functional Requirements
Search functions
11. The application shall access data from a MLS® servers maintained by realtors.
12. The application shall display the home page upon the first visit, which shall show a map displaying the
users’ current locations with navigation tools and search tools.
13. The application shall provide a keyword search option by allowing users to input free-text.
14. For tablet devices and smartphones, the application shall automatically call the keyboard tool when the
cursor is placed into a free-text search box.
15. The application shall support the American English language only but nothing in the design should
prevent the application from using other languages in the future.
16. The application shall allow users to search by a range of years the property was built. The years allowed
shall be 1880 to the current year.
17. The application shall allow users to search by price range. The price range shall be represented by a
minimum and a maximum values in US dollars. The minimum is $40,000 and the maximum is
$1,000,000.
18. The application shall allow users to search the target location by street address, zip code, landmark, or
their current position.
19. The application shall allow the users to input integers representing a minimum and maximum distance
in miles from the defined target location. The minimum shall be 0.1 miles and the maximum shall be
100 miles.
20. The application shall allow the users to define the minimum number of bedrooms desired. The
minimum is 1 and the maximum is 10.
21. The application shall allow the users to define the minimum number of bathrooms desired. The
minimum is 0 (studio) and the maximum shall be 10.
22. The application shall allow the users to define the minimum home square feet desired. The minimum is
500 and the maximum is 15,000.
23. The application shall allow the users to define the minimum lot square feet desired. The minimum is 0
(condo) and the maximum is 1,000,000 (approximately 25 acres)
24. The application shall allow the users to define the maximum property tax rate imposed. The minimum
is 0 and the maximum is 99.9%

10
25. The application shall allow the users to define the property type desired (i.e. homes, condos, lofts,
townhomes, land only, recently sold, foreclosures).
26. Users shall be able to apply multiple search criteria in one search, and each search criterion can be
designated as “AND” or “OR” search.
27. The application shall inform the users if invalid input is attempted, and prompt the users to provide
data within the accepted limits.
28. When the users request home data in their current physical proximity, the application shall indicate
where the users are on the map, and return search results of properties for sale in their current
locations.
Display of Search Results
29. The application shall display search results in either a list or map view, as defined by the users.
30. The application shall provide sorting options for the search results, including:
 Sort by price
 Sort by distance from target, smallest to greatest distance
31. When the properties are viewed in the list view, the application shall display 20 search results at time.
The application shall display additional results when the users scroll to the end of the current list. The
maximum search results list shall be limited to 100.
32. When displaying search results in the map view, the application shall display each home for sale with
an icon and the asking price. The maximum search results on the map view shall be limited to 20,
33. When displaying search results in the map view, the application shall display a blurb about the property
when the users taps (for tablet/smartphone devices) or hovers the cursor over (for desktop computers)
the target icon. The blurb will consist of the address, selling price, square footage, number of
bedrooms, and listing agent,
34. When displaying search results in the map view, the application shall display full property details when
the users double-tap (for tablet/smartphone devices) /double-click (for desktop computers) the icon
representing the property.
35. The application shall provide a means of contacting the listing realtors by phone or email.
App Tools Customization
36. The application shall provide a means of saving search criteria for registered users. A maximum of 20
search criteria will be saved.

11
37. The application shall provide a means of saving search results for registered users. The maximum
number of listings in the saved search results shall be no more than 100.
38. The application shall provide a means of defining property alerts for new listings matching user
preferences for registered users.
39. If the users navigates away from the app, the application shall continue from the same page where the
users left off when they re-run the app.
User Registration
40. The application shall allow the users to register through the app. The registration process shall require
a username, password, and e-mail address. The users may optionally provide a phone number.
41. The application shall provide the users with a profile page for personal information updates.
42. The application shall encrypt and store the user log-in information in uses’ devices so that the users are
logged in automatically upon subsequent visits.
43. The application shall allow password retrieval via e-mail.

12
4.3. Key Performance Parameters (KPPs)
Requirement
number
Requirement Statement
13 The application shall provide a keyword search option by allowing users to input free-
text.
29 The application shall display search results in either a list or map view, as defined by the
users.
34 When displaying search results in the map view, the application shall display full
property details when the users double-tap (for tablet/smartphone devices) /double-
click (for desktop computers) the icon representing the property.
37 The application shall provide a means of saving multiple search results for registered
users. The maximum number of listings in the saved search results shall be no more
than 100.
40 The application shall allow the users to register through the app. The registration
process shall require a username, password, and e-mail address. The users may
optionally provide a phone number.
43 The application shall allow password retrieval via e-mail.
Table 2: Home Search SW Apps KPPs

13
4.4. Requirement Validation
Evaluation Verification Manage
Requirement
number
Necessity
Complete
Correctness
Additional
meanings?
Rewrite
Discard
Formal
Validation?
Test
Demo
Inspection
Analysis
Howto
Manage
1. Yes No Yes No Yes No No  Stored
in SAP
2. Yes Yes Yes No Yes No No  Stored
in SAP
3. Yes No Yes Yes Yes No No   Stored
in SAP
4. Yes Yes Yes Yes Yes No No   Stored
in SAP
5. Yes Yes Yes No No No No  Stored
in SAP
in SAP
in SAP
8. Yes Yes Yes No No No No   Stored
in SAP
in SAP
10. Yes Yes Yes No No No Yes   Stored
in SAP
11. Yes No Yes Yes Yes No Yes  Stored
in SAP

14
12. Yes No Yes Yes Yes No Yes  Stored
in SAP
in SAP
14. Yes Yes Yes Yes Yes No No  Stored
in SAP
15. Yes No Yes Yes Yes No No  Stored
in SAP
in SAP
in SAP
18. Yes No Yes No Yes No Yes    Stored
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP

15
in SAP
28. Yes No Yes No Yes No Yes   Stored
in SAP
in SAP
in SAP
in SAP
32. Yes Yes Yes Yes Yes No No  Stored
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP
in SAP

16
in SAP
in SAP
Table 3: Home Search SW Apps Requirements Validation

17
5. Function List
1. Search properties
1.1. Accept user’s search criteria
1.2. Perform input data integrity checking
1.3. Access multiple listing services (MLS®) Server
1.4. Retrieve property information
2. Display properties information
2.1. List search results, 20 on one page
2.2. Display 20 more search results as user scroll to the end
2.3. Sort search results. Sorting options include sort by price and sort by distance
2.4. Switch to map views from list view, and vice versa
2.5. Render search result on map
2.6. Show property information in brief
2.7. Show property information in detail
2.8. Show contact information of realtors
3. Location centric searches
3.1. Request user’s location through GPS.
3.2. Use location information for quick local search functions.
3.3. Alert user when user preferences are met at a particular location.
4. Lifestyle criteria searches
4.1. Connect to demographic data server.
4.2. Connect to crime statistics server.
4.3. Connect to commercial services server.
4.4. Connect to local government information server.

18
4.5. Retrieve information matching user lifestyle preferences.
4.6. Determine proximity of the matched results.
4.7. Filter home search listing based on matching lifestyle criteria.
5. Register user
5.1. Read username and password from user
5.2. Encrypt user login information
5.3. Send registration to database
5.4. Validate registration information
5.5. Send registration confirmation message to user
5.6. Store user login information in device
6. Customize functions (for registered users)
6.1. Save search criteria
6.2. Save search results
6.3. Cache more than or equal to five map areas with search results
6.4. Create alerts for new listings that match users’ preference
7. Show advertisements
7.1. Charge realtors for posting advertisements
7.2. Fetch advertisements from realtors
7.3. Determine if user has a paid or free account
7.4. Display advertisements
8. Manage application via device portal (iTunes, PlayStore, etc.)
8.1. Install application on target device via the device portal
8.2. Update the application on the target device via the device portal
8.3. Uninstall the application on the target device via the device portal
9. Maintain user entered notes/pictures

19
9.1. Add pictures to home entry
9.2. Add text notes to home entry
9.3. Add voice notes to home entry
10. Display recent sold or foreclosed properties
10.1. Display recently sold properties including price and sale date
10.2. Display properties that have recently entered into foreclosure
11. Socialize the search results
11.1. Add pictures, notes, and location of selected homes to Facebook
11.2. Add pictures, notes, and location of selected home to email message

20
6. System Diagrams
6.1. Context Diagram
Mobile Application Software
User
Device,
Operating
System, and
Local Database
Realtor
Add reputation and Online presence
Listing Agent
Contact Notification
Request Resource
Allocation
Provide
Operating Platform Return Optimal
Search Results
App store and Market Place
Visual Responses
Commands (e.g., request alerts,
request showings, etc.)
Input Search Criteria
Provide Registration
Information
Map Data
Request for
Map Data
Response with
Map Data
Saving Favorites
Retrieving Favorites
Multiple Listing
Service
Database
Home Listings
Home Query
Figure 1:Context Diagam for Home Finder Apps

21
6.2. System Hierarchy Block Diagram (SBD)
Home Finder
Application
(Moogle) - 0
Operating System
Interfaces – 0.1 Local Database – 0.2
User
Interface – 0.3
Server
Interractions – 0.4
Publishing
Management – 0.5
Monitization
Management – 0.6
Search
Listing Cache
2.1
Downloaded
Maps
2.2
Application
Configuration
2.3
User
Preferences
2.4
IOS API
1.1
Android API
1.2
Windows API
1.3
GPS Interface
1.4
File System
Interface
1.5
Network
Interface
1.6
Orientation
Management
3.1
Home
Search
Screen
3.2
Home
Listing
Screen
3.3
Map Screen
3.4
Realtor
Contact
Screen
3.5
Aplication
Config. Screen
3.6Sensor
Interface
1.6
Home Listing
Server
Communication
4.1
Advertising
Server
Communicaton
4.2
Map Server
Communication
4.3
App. Store
Server
Communication
4.4
Website
Download
5.1
App Store
Download
5.2
Purchase
Options
6.1
Advertisement
Placement
6.2
Preferred
Realtor
Listing
6.3
Home Finder Mobile App (Moogle)
System Block Diagram
Figure 2: Home Finder Application System Block Diagram

22
6.3. Function Block Diagram (FBD)
User
MLS Server
Local Database
Operating
System
Advertisement
Management
Server
Public
Databases
( Crime Statistics
Demographic
info.)
Map Server
Display Properties
Location Centric
Searches
Register User
Advertisement
Placement
Publishing Management
Maintain User Notes,
interest lists
Display recent sold and
history of property and
locality
Registration Details Registration DetailsSearch Properties
Lifestyle
Preferences
Home
Search
Query
New Lifestyle
Preference
Based Query
Map
Query
Property
List
Property Filter
Information
Map Image
Location
Query
Location
Response
Map Query
Saved
Porperties,
Notes. Local User
Information
Registration Status
User Configurations
More
Details
Detail
Query
Download Application Request
Application
Executable
Purchase Application Transaction
Advertisements
Advertisements
Purchase Status
Query
Request Advertisement
Purchase status
Moogle Home Search SW Application – Functional
Block Diagram (FBD)
Figure 3: Home Search SW apps FBD

23
6.4. Physical Block Diagram (PBD)
Mobile Home Search Application
(Moogle)
Apple iOS
User
Demographics Server Crime Statistics Public Server
Windows OS
Android OS
Application Website Host
GPS Receiver
File System
(Local Database)
Multiple Listing Server (MLS)
Map Server
Google Play Store
AppStore
Windows Store
Advertisement
Server
Authorization
Server
iOS API
module
Android API
module
Windows API
module
Mobile System
User Interface
Touchscreen
Display
Core Search
Engine
Lifestyle
Search
Preferences
Matched
Properties
Download
Application
Request
Application
Executable
Result Filters
Lifestyle Search
Prefrences
Demographic Query
Crime Stats Query
Search Query
Context / Location Relevant
Advertisement Request
Map
Image
Location Map Request
Filtered
Property List
Install Apple OS version
Install
Android OS
version
Query
Response
Apple iOS specific
Interactions
Android OS specific Interactions
Windows OS
intereactions
Free
User?
Query
Context / Location Relevant
Advertisements
Local Storage
& Retrieval
Local
Storage &
Retrieval
Local
Storage
&
Retrieval
Install
Windows OS version
Location Request
&
Response / Alerts
Location Request
&
Response / Alerts
Location Request
&
Response / Alerts
OS
Resources
Figure 4: Home Search SW apps PBD

24
7. Interface Details
Interface Function Interface Media Constraint Interface Value Comment
Orientation
Management
Operating
system
capabilities
iOS API, Android
API, Windows API
Realtor, Google
Map, GPS satellite
Graphical resolutions Realtor must
capable with
operating system
Home search
Screen
Display server
interaction
Advertising server,
Home listing,
Mapping server
Advertising server
communication
Home search Size
between 3" to 5".
Home listing
screen
Display
recorded
realtors
Sorting properties Home listing
communication
Alerts, Labels,
Placeholders, Tab bar
text, and Segmented
Controllers
Map Screen Display realtor
information
Touch screen Map server
communication
Accelerometer sensor
will used in navigate
engine
Realtor Contact
Screen
Registration
realtor contact
and Price
File system
interfaces
App. Store server
communication
Labels to filling
contacts details.
Realtor must
have at least,
Name, Number,
Price range
Application
Configuration
Screen
Configure
displaying
items
Application
configuration, User
preferences
App. Store server
communication
Advertisement
Placement
Table 4 : Home Search SW Apps Interfaces Details

25
8. Requirement Analysis Sheets (RAS)
Requirements Analysis Sheet
Function ID 1
Function Name Search properties
Description
Obtain search criteria such as properties information, community
demographics, and/or users’ current locations. Access the home listing
server and map server’s databases to retrieve the properties which
information match the search criteria.
Initial Event
User starts a search section by inputting the search criteria, which
include:
- Picking preferences from search criteria presented in pick lists
(such as range of size of properties).
- Inputting free text.
- Panning and zooming to areas of interest on map.
Terminal Event The application fetches search from the backend databases.
Time Duration 3.1 seconds -9.3 seconds
Mean 5.5 seconds
Variance 0.3 second
Requirement Attribute Time in executing the search function
Value/Units
Target 4
secondsMargin 10
Achieved 5.5
Requirement Statement(s) (Refer to requirements 11-28)
Paragraph Title N/A
Paragraph Number N/A Requirement Number 11-28

26
Architecture Item Allocation
Name Signature Date
Analyst Moogle 30th
Nov2012
Principal Eng. Moogle 1th
Dec2012

27
Function ID 2
Function Name Display property information
Description
List property information returned from search function, and presents
the information on a map. Display the information in 2 levels of details,
and display the contact information of the realtor.
Initial Event Search result returned from databases.
Terminal Event Search results presented in list view and map view.
Time Duration 0.5 seconds -2 seconds
Mean 1.1 seconds
Variance 0.1 second
Requirement Attribute Time in displaying the results and rendering them on map
Value/Units
Target 0.5
secondsMargin 4
Achieved 1.1
Paragraph Title N/A
Name Signature Date
Analyst Moogle 30th
Nov2012
Dec2012

28
Function ID 3
Function Name Register user
Description
Accept login information from user and validate the information. Save
the encrypted login information in database and in user’s device.
Initial Event
Users request the application to send the registration information to
server.
Terminal Event Login information stored in users’ device
Time Duration 9.8-10.5seconds
Mean 10seconds
Variance 0.1second
Requirement Attribute Time in registering a user
Value/Units
Target 8
secondsMargin 11
Achieved 10
Paragraph Title N/A
Name Signature Date
Analyst Moogle 30th
Nov2012
Dec2012

29
Function ID 4
Function Name Show advertisements
Description
Fetch advertisements from realtors’ databases, and display them on
users’ devices for free account, and do not display advertisements for
paid accounts.
Initial Event Application loaded up and user account type determined.
Terminal Event Advertisements displayed on screen for free accounts.
Time Duration 1.8seconds – 3seconds
Mean 2.2 seconds
Variance 0.2 seconds
Requirement Attribute Time in displaying advertisements
Value/Units
Target 1.5
secondsMargin 3.2
Achieved 2.2
Paragraph Title N/A
Name Signature Date
Analyst Moogle 30th
Nov2012
Dec2012

30
9. Requirement Traceability Matrix
Requirement Traceability Matrix
Project Name:
Home Finder Application (Moogle)
Project Number:
HFA-61725022
Author:
Moogle
Date Version Revision Description Revision Author
2Nov012 0.1 First draft of RTM prepared Moogle
11Nov2012 0.2 Submitted for approval Moogle
16Nov2012 1.1 Updates from stakeholder Moogle
Unique
Require-
ment
ID
Requirement Description
Source of
requirement
Program or
software
module
containing the
requirement
Test specification
containing the
requirement test
Date of
Successful
Test
Verification
conducted
Changes made to the
requirement
Status
1.
Support Apple iPhones, iPad; Android devices,
and Windows7 Mac laptop/desktop computers CLR1 of 1Nov2012
SYS#001 TSpec- 001-Fc 22Nov2012 N/A Green
2. Support portrait and landscape orientation CLR2 of 1Nov2012 SYS#003 TSpec- 001-Fc 22Nov2012 N/A Green
3. Connect to the internet for searching function CLR3 of 1Nov2012 SEAR#DB001 TSpec- 002-Fc 22Nov2012 N/A Green
4.
Cache more than or equal to five areas of
interest CLR4 of 1Nov2012
SYS#008 TSpec- 001-Fc
22Nov2012 N/A Green
5. Support search by current location CLR5 of 1Nov2012 SEAR#SEA018 TSpec- 002-Fc 22Nov2012 N/A Green
6.
Application is downloadable from Android Play
Store, Apple App Store or tool website CLR6 of 1Nov2012
SYS#002 TSpec- 001-Fc
22Nov2012 N/A Green
7. Shows advertisements CLR7 of 1Nov2012 SYS#ADV003 TSpec- 002-Fc 22Nov2012 N/A Green

31
8.
Application is advertisement free when users pay
a one-time charge CLR8 of 1Nov2012
SYS#ADV004 TSpec- 001-Fc
22Nov2012 N/A Green
9. Charge realtor $100 USD per listed property CLR9 of 1Nov2012 SYS#007 TSpec- 001-Fc 22Nov2012 N/A Green
10. Notify users for updated versions CLR10 of 1Nov2012 SYS#ADV012 TSpec- 001-Fc 22Nov2012 N/A Green
11. Access MLS® database maintained by realtors
CLR11 of 1Nov2012
SEAR#DB003
TSpec- 002-Fc,
TSpec- 002-
NonFc
22Nov2012 (14Nov2012) Add support of
access to government’s public
database with demographic
information
Green
12.
Display home page with a map and property
search tools CLR12 of 1Nov2012
SEAR#DIS012 TSpec- 002-Fc
22Nov2012 N/A Green
13. Provide free text search option CLR13 of 1Nov2012 SEAR#SEA003 TSpec- 002-Fc 22Nov2012 N/A Green
14.
Display keyboard tool when the free text search
box is selected CLR14 of 1Nov2012
SEAR#SEA004 TSpec- 002-Fc
22Nov2012 N/A Green
15. Locale supports American English only CLR15 of 1Nov2012 SYS#005 TSpec- 001-Fc 22Nov2012 N/A Green
16. Support search by year range CLR16 of 1Nov2012 SEAR#SEA005 TSpec- 002-Fc 22Nov2012 N/A Green
17. Support search by price range CLR17 of 1Nov2012 SEAR#SEA006 TSpec- 002-Fc 22Nov2012 N/A Green
18. Support search by location CLR18 of 1Nov2012 SEAR#SEA007 TSpec- 002-Fc 22Nov2012 N/A Green
19.
Support search by distance range from target
location CLR19 of 1Nov2012
22Nov2012 N/A Green
20.
Support search by minimum number of
bedrooms CLR20 of 1Nov2012
22Nov2012 N/A Green
21.
Support search by minimum number of
bathrooms CLR21 of 1Nov2012
22Nov2012 N/A Green
22. Support search by minimum home square feet CLR22 of 1Nov2012 SEAR#SEA0011 TSpec- 002-Fc 22Nov2012 N/A Green
23. Support search by minimum lot square feet CLR23 of 1Nov2012 SEAR#SEA0012 TSpec- 002-Fc 22Nov2012 N/A Green

32
24. Support search by maximum tax rate CLR24 of 1Nov2012 SEAR#SEA0013 TSpec- 002-Fc 22Nov2012 N/A Green
25. Support search by property type CLR25 of 1Nov2012 SEAR#SEA0014 TSpec- 002-Fc 22Nov2012 N/A Green
26. Support multiple search criteria CLR26 of 1Nov2012 SEAR#USR020 TSpec- 002-Fc 22Nov2012 N/A Green
27. Prompt user to correct invalid data CLR27 of 1Nov2012 SEAR# SEA002 TSpec- 002-Fc 22Nov2012 N/A Green
28.
Search properties based on users’ current
location CLR28 of 1Nov2012
22Nov2012 N/A Green
29. Display search result in a list or on map CLR29 of 1Nov2012 DISP#002 TSpec- 003-Fc 22Nov2012 N/A Green
30. Provide sporting option for search results CLR30 of 1Nov2012 DISP#LST004 TSpec- 003-Fc 22Nov2012 N/A Green
31. Display 20 initial search results in list view
CLR31 of 1Nov2012
DISP#LST002
TSpec- 003-Fc,
TSpec- 003-
NonFc
22Nov2012 N/A Green
32.
Render properties using icons and asking prices
in map view CLR32 of 1Nov2012
DISP#MAP003 TSpec- 003-Fc
22Nov2012 N/A Green
33.
Display blurb about the property when a
property icon is highlighted CLR33 of 1Nov2012
22Nov2012 N/A Green
34.
Display full details of properties when a
property’s icon is selected CLR34 of 1Nov2012
22Nov2012 N/A Green
35. Provide contact information of realtors CLR35 of 1Nov2012 DISP#005 TSpec- 003-Fc 22Nov2012 N/A Green
36. Save search criteria CLR36 of 1Nov2012 USER#NOT003 TSpec- 004-Fc 22Nov2012 N/A Green
37. Save search results CLR37 of 1Nov2012 USER#NOT004 TSpec- 004-Fc 22Nov2012 N/A Green
38.
Alert users for new listings that match users’
preferences CLR38 of 1Nov2012
USER#NOT008 TSpec- 004-Fc
22Nov2012 N/A Green
39.
Continue from last opened page when
application restarts CLR39 of 1Nov2012
USER#001 TSpec- 004-Fc
22Nov2012 N/A Green
40. Register user CLR40 of 1Nov2012 USER#REG004 TSpec- 004-Fc 22Nov2012 N/A Green

33
41. Allow user to update personal information CLR41 of 1Nov2012 USER#REG009 TSpec- 004-Fc 22Nov2012 N/A Green
42.
Stored encrypted user log-in information in
device CLR42 of 1Nov2012
USER#REG012 TSpec- 004-Fc
22Nov2012 N/A Green
43. Provide password retrieval tools CLR43 of 1Nov2012 USER#REG015 TSpec- 004-Fc 22Nov2012 N/A Green
Table 5: Requirement Traceability Matrix

34
10. Risk Analysis Sheets
RISK TITLE: Unable to obtain sufficient funding for the project.
RISK NUMBER: Impl-01 DATE: 11/6/12
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Assessment Cube Initial Assessment <date>
Likelihood
E
D 1
C
B
A
1 2 3 4 5
Consequence
Assessment Cube Goal: Final Assessment As of <date>
Likelihood
E
D 1
C 3 2
B
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: Moogle is unable to make sufficient profit to sustain the cost of
maintenance of the Home Finder Application.
CONSEQUENCE IF REALIZED: The Home Finder project will terminate until additional funding is
obtained.
RISK LIKELIHOOD EXAPLANATION: (D): As a new product, the Home Finder Application is still
gaining popularity from the public. At the current stage the project cannot maintain itself all by
the profit that the application makes without funding from Moogle.
RISK CONSEQUENCE SEVERITY EXPLANATION: (4): The consequence will be severe as the risk
may lead to termination of the project. However, based on the current financial status of
Moogle, the risk would only cause the company to lose about 1% of the annual profit.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking

35
Home Finder application is new to the public
and can’t support itself by the profit.
11/18/12 - D,4
Offer a discount to realtors for posting the first
5 properties.
2/06/12 11/06/13 C,3
Posting advertisements for the home finder
applications on computer magazines and
online forums.
11/09/12 11/22/12 C,2

36
RISK TITLE: Insufficient real estates data from data providers
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Likelihood
E 1
D
C
B
A
1 2 3 4 5
Consequence
Likelihood
E
D 1
C 2
B 3
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: Users enables to search for specific home properties, and could not
access in MSL®
server.
CONSEQUENCE IF REALIZED: MLS® server dose not synchronize with home realtor Apps.
RISK LIKELIHOOD EXAPLANATION: (E): Realtor Apps will not get users satisfaction and
performance does not meet user’s needs.
RISK CONSEQUENCE SEVERITY EXPLANATION: (5) Realtor will not meet Users needs and
performance will be lower than standard.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking
Find additional requirements connectivity and
keeps always reviewed.
11/05/12 11/15/12 D,5
Scheduled synchronize and updated with MLS®
server
11/06/12 11/19/12 C,3

37
Added new requirements for connection
purpose.
11/09/12 11/22/12 B,3

38
RISK TITLE: Use information security concern
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Likelihood
E 1
D
C
B
A
1 2 3 4 5
Consequence
Likelihood
E
D 1
C 2
B 3
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: Users could not authenticate login on MSL® server and there are no
response with User name and Password.
CONSEQUENCE IF REALIZED: MLS® server does not allow users to created User Name and
Password.
RISK LIKELIHOOD EXAPLANATION: (E): increase cost of project, and lead software not achieving
stated functions.
RISK CONSEQUENCE SEVERITY EXPLANATION: (5) contacts and price range for the properties
will not appear and may cause to fails in searches for home Apps.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking
Find dialog boxes that allowed users in
realtor Apps to add contacts details and
price range.
11/05/12 11/15/12 D,1
Perform review requirement that required
from users to updated Password and
11/06/12 11/19/12 C,2

39
contacts details, to scheduled reminder by
emails.
Adds requirements to user identification
such as Login with LinkedIn.
11/09/12 11/22/12 B,3

40
RISK TITLE: Sensor failure
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Likelihood
E 1
D
C
B
A
1 2 3 4 5
Consequence
Likelihood
E
D 1
C 2
B 3
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: sensor may operate incorrectly and fails to located properties in Maps
Application.
CONSEQUENCE IF REALIZED: navigation systems would require monitoring and tracking the
sensor.
RISK LIKELIHOOD EXAPLANATION: (E): increase cost of project, and lead company to failure.
RISK CONSEQUENCE SEVERITY EXPLANATION: (5) The project will fail.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking
Find out the additional sensor to detected
signals.
11/05/12 11/15/12 D,1
Major schedule slip less than one moth 11/06/12 11/19/12 C,2
Significant mission to design and
engineering team.
11/09/12 11/22/12 B,3

41
RISK TITLE: Unable to connect to servers that fetch advertisements
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Likelihood
E
D
C 1
B
A
1 2 3 4 5
Consequence
Likelihood
E
D 1
C 2
B 3
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: The application cannot display the advertisements that have been
commissioned.
CONSEQUENCE IF REALIZED: Application does not synchronize with server.
RISK LIKELIHOOD EXAPLANATION: (C): Unable to monetize the application will lead to not
being able to satisfy business requirements
RISK CONSEQUENCE SEVERITY EXPLANATION: (2) Cannot charge for advertisements thereby
impact profitability of application.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking
Find additional requirements connectivity and
keeps always reviewed.
11/05/12 11/15/12 D,5
Scheduled synchronize and updated with 11/06/12 11/19/12 C,4

42
advertisement source
Added new requirements for connection
purpose.
11/09/12 11/22/12 B,2

43
RISK TITLE: Unable to test the application through all deice types
RISK
CATEGORY:
Technical

Requirements

Schedule

Cost

Budget

Likelihood
E
D
C
B 1
A
1 2 3 4 5
Consequence
Likelihood
E
D 1
C 2
B
A
1 2 3 4 5
Consequence
DESCRIPTION OF RISK: The application does not pass the published standards for inclusion into
the applicable portal
CONSEQUENCE IF REALIZED: Unable to distribute application.
RISK LIKELIHOOD EXAPLANATION: (B): Software design standards for the applicable portal are
well published and well understood.
RISK CONSEQUENCE SEVERITY EXPLANATION: (2) Being unable to distribute applications via the
portal will the application to fail in its mission.
Mitigation Steps:
Schedule
Start
Schedule
Finish
Actual
End
Risk
Ranking
Create test plans for each portal. 11/05/12 11/15/12 D,5
Include portal testing with each build of the
application
11/06/12 11/19/12 C,3

44
11.Summary
The main lessons that this class/project has brought to light is the importance of a well-crafted requirements
document. The judicious application of the principles learned during this course will most likely mitigate the risk
of any future undertaking. Things may still go wrong with regards to technical, cost, and schedule performance
but likelihood that these trouble would stem from inadequate requirements will definitely be reduced.
Another important lesson learned in this project is that things build on one another. For example, progressing
from high level functions though to derived/allocated functions and creating the diagrams shows the ripple
effect that can happened when you discover that a fundamental requirement was not clearly defined or was
missing. Adding fundamental requirements after much work has been done can cause changes to ripple thought
the document. Consensus and closure is important.

45
12.References
[1]
Smartphone application http://en.wikipedia.org/wiki/Smartphone
[2]
GPS navigation smart phone http://www.zdnet.com/blog/mobile-news/smartphone-for-gps-navigation-is-
better-than-a-dedicated-device/3055
[3]
Design Techniques for User Interface Text in Smartphone Applications Smartphone Applications, Joe Welinske.
Email: joewe@writersua.com
[4]
Smartphone Apps http://www.appiction.com/apps-101-iphone-smartphone-application-development
[5]
HSUPA http://en.wikipedia.org/wiki/High-Speed_Uplink_Packet_Access

46
13. Team schedule
By 11/10 we should nail down the following:
 Need Statement
 Context Diagram
 Function List
 25 Requirements
By 11/17 we should nail down the following:
 SBD
 Derived Requirements
 FBD
 PBD
By 11/24 we should nail down the following (even with Thanksgiving)
 ABD
 IBD
 4 Risks on Risk Analysis Sheet
By 12/1 we should nail down the following
 RTM
 Risks Management
 Team Schedule
 Summary
By 12/3 we start to put it all together for final submission on 12/9.

Team moogle group project 1

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (8)

Similar to Team moogle group project 1

Similar to Team moogle group project 1 (20)

Recently uploaded

Recently uploaded (20)

Team moogle group project 1