April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 11
Home Inventory Matching and Management SystemHIMMS
Prototype Presentation
Prepared by:Prepared by: Red Team Red Team
April 27April 27thth , 2007 , 2007
Location: E&CS Conference RoomLocation: E&CS Conference Room
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 22
Group MembersGroup Members Daniel BuhrmanDaniel Buhrman
– Project ManagerProject Manager David PrattDavid Pratt
– Financial Manager and Risk ManagerFinancial Manager and Risk Manager Marnie QuerimitMarnie Querimit
– Research Manager and Prototype TesterResearch Manager and Prototype Tester Samuel LamborginiSamuel Lamborgini
– Marketing Manager and Prototype DeveloperMarketing Manager and Prototype Developer Youssef TaghlabiYoussef Taghlabi
– Technical Manager, Prototype Developer, and Technical Manager, Prototype Developer, and WebmasterWebmaster
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 33
OverviewOverview
Part I Part I Problem and BackgroundProblem and Background Product ComponentsProduct Components Product and Prototype RisksProduct and Prototype Risks
Part IIPart II Prototype DemonstrationPrototype Demonstration Test CasesTest Cases
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 44
If this was your house…If this was your house…
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 55
……what can happen to it?what can happen to it?
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 66
Problem StatementProblem Statement
The insurance process is time The insurance process is time consuming and open to inaccuracies.consuming and open to inaccuracies.– Inadequate insurance coverageInadequate insurance coverage– Time it takes to complete and file a Time it takes to complete and file a
claim formclaim form– Lack of a home inventory Lack of a home inventory
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 77
Inadequate Insurance Inadequate Insurance CoverageCoverage
74 million homeowners in US 74 million homeowners in US 11
96% of homeowners have insurance 96% of homeowners have insurance 22
59% of American homes are 59% of American homes are underinsured underinsured 22
1 US Census Bureau
2 Insurance Information Institute
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 88
Why Homeowners Don’t Why Homeowners Don’t Increase CoverageIncrease Coverage
Insurance Information Institute
Don't want rates to go
up14% Too
expensive4%
Agent said I'm covered
21%
Didn't know I needed to
21%
Other15%
Didn't have time25%
survey of 1,154 homeowners:Don't want rates to go
up14% Too
expensive4%
Agent said I'm covered
21%
Didn't know I needed to
21%
Other15%
Didn't have time25%
survey of 1,154 homeowners:
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 99Federal Emergency Management Agency
Disaster DeclarationsDisaster DeclarationsBy TypeBy Type
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1010
Inventories and Claim FormsInventories and Claim Forms
State Farm Insurance
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1111
GoalGoal
Provide a tool that maintains a Provide a tool that maintains a homeowner’s inventory, matches homeowner’s inventory, matches him with the Best-Fit coverage, and him with the Best-Fit coverage, and assists in filling out insurance claim assists in filling out insurance claim forms forms
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1212
CustomerCustomer
PrimaryPrimary– Insurance CompaniesInsurance Companies
SecondarySecondary– HomeownersHomeowners
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1313
ObjectivesObjectives
Inventory with UPC matchingInventory with UPC matching Best-Fit algorithmBest-Fit algorithm Claim form generationClaim form generation Accessible online via loginAccessible online via login
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1414
Product ComponentsProduct Components
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1515
Phase 2: Critical Phase 2: Critical Design Design
Work Breakdown Schedule
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1616
Phase 2: Critical DesignPhase 2: Critical DesignOrganizational Chart
Project Manager
Financial Manager Software Engineer (2)
Technical Writer Webmaster
Test Engineer (2) Network Engineer
Database Programmer
Data Entry Clerk (2)
Customer Service Representative (2)
Security Expert Information Tech.
ManagerInsurance Expert
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1717
Phase 2: Critical DesignPhase 2: Critical Design Budget: Hardware, Software and Personnel Resources
Description Quantity CostHardware Barcode Scanner 1,000 n/a $49 $49,000
Server 4 n/a $3,799 $15,196Workstation Computers 15 n/a $749 $11,235Microsoft Office Small Business 15 n/a $449 $6,735Total $82,166
Personnel Project manager 1 360 $66,362 $91,534Database programmer 1 65 $52,242 $13,010Software engineer 2 475 $53,122 $96,678Webmaster 1 222 $67,090 $57,065Technical writer 1 90 $42,130 $14,528Test engineer 2 373 $52,277 $74,710Network engineer 1 104 $57,682 $22,984Customer service rep. 2 148 $30,307 $17,186Data entry clerk 1 40 $25,212 $3,864Information technology manager 1 42 $104,827 $16,869Financial manager 1 22 $89,797 $7,569Total $415,997
40% Overhead $166,399
Total $664,561
Phase 2Note: Phase duration is 360 days
Duration (days)
Salary/Price
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1818
Risk Probability/ImpactRisk Probability/Impact
Pro
bab
ilityPro
bab
ility
55
44 11
33 55 3,43,4 22
22 99 77 66
11 88
11 22 33 44 55
ImpactImpact
1. Competition 1. Competition improving our improving our productproduct
2. Insurance 2. Insurance companies companies making a similar making a similar productproduct
3. Security and 3. Security and privacyprivacy
4. No growth area4. No growth area
5. Liability for 5. Liability for keeping keeping inventoriesinventories
6. Customer non-6. Customer non-useuse
7. Database 7. Database failure failure
8. Difficulty of use8. Difficulty of use
9. Potential 9. Potential misuse to commit misuse to commit fraudfraud
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 1919
RisksRisks
RiskRisk Risk DescriptionRisk Description Mitigation ActionsMitigation ActionsCompetitioCompetition n improving improving our our productproduct
Another company Another company improving on our concept improving on our concept releasing their product releasing their product before or near our product’s before or near our product’s release date release date
Research into acquiring a Research into acquiring a patent, make the product patent, make the product before the competition or before the competition or improve on the competition improve on the competition
Insurance Insurance companies companies creating a creating a similar similar projectproject
Insurance companies doing Insurance companies doing their own version of our their own version of our product where they control product where they control all of the aspects all of the aspects
Maintain enough of the Maintain enough of the project ourselves that project ourselves that insurance companies would insurance companies would not attempt to phase out our not attempt to phase out our company company
Security Security and and privacyprivacy
There is personal There is personal information that will be sent information that will be sent by our program to the by our program to the insurance company’s insurance company’s databasedatabase
Use secure methods of Use secure methods of transferring data across the transferring data across the internet to the insurance internet to the insurance company’s databasecompany’s database
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2020
RisksRisks
RiskRisk Risk DescriptionRisk Description Mitigation ActionsMitigation ActionsNo growth No growth area for area for our projectour project
Our project not being able Our project not being able to progress further than the to progress further than the first version in terms of first version in terms of major steps in developmentmajor steps in development
Research and develop new Research and develop new features, which our product features, which our product could incorporatecould incorporate
Liability for Liability for keeping keeping inventoriesinventories
Legal issues associated Legal issues associated with holding databases with with holding databases with personal inventoriespersonal inventories
Consult a lawyerConsult a lawyer
Customer Customer non-usenon-use
Customers will need to Customers will need to continually keep their continually keep their insurance information up to insurance information up to date date
Insurance companies can Insurance companies can provide incentives for provide incentives for customers who use our customers who use our product product
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2121
RisksRisks
RiskRisk Risk DescriptionRisk Description Mitigation ActionsMitigation ActionsDatabase Database failurefailure
We will be maintaining the We will be maintaining the database of inventories of database of inventories of items, which needs to be items, which needs to be preserved preserved
Keep a backup database and Keep a backup database and keep a database support keep a database support specialist on staff 24/7 in specialist on staff 24/7 in three shifts three shifts
Difficulty Difficulty of useof use
This product needs to be This product needs to be able to be used by able to be used by homeowners who are not homeowners who are not computer literatecomputer literate
Inputting of items should be Inputting of items should be quick and simple, so as not to quick and simple, so as not to become tedious become tedious
Potential Potential misuse to misuse to commit commit fraudfraud
Our product should not be Our product should not be able to be used to better able to be used to better facilitate insurance fraud facilitate insurance fraud
Find out from an insurance Find out from an insurance expert what measures can be expert what measures can be used (or are used) to prove used (or are used) to prove ownership ownership
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2222
No growth area for HIMMSNo growth area for HIMMS– Many features of HIMMS can be Many features of HIMMS can be
expanded and developedexpanded and developed Difficulty of useDifficulty of use
– UPC auto-entry makes inventory UPC auto-entry makes inventory creation easiercreation easier
Risks Addressed by the Risks Addressed by the PrototypePrototype
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2323
Part IIPrototype Test Plan Procedure
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2424
Group Members & Test Group Members & Test ResponsibilitiesResponsibilities
Youssef Taghlabi: Test plan presenterYoussef Taghlabi: Test plan presenter Sam Lamborgini : Administrator test casesSam Lamborgini : Administrator test cases Homeowner 1 test cases Daniel Daniel Buhrman : Homeowner 2 test casesHomeowner 2 test cases David Pratt : DatabaseDavid Pratt : Database Marnie Querimit : SlidesMarnie Querimit : Slides
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2525
PrototypePrototype RoomRoom LayoutLayoutTV1: Database Database Projector Screen 1:Projector Screen 1: Presentation Slides Presentation SlidesTV2: Database Database Projector Screen 2:Projector Screen 2: Prototype Demonstration Prototype Demonstration
Room LayoutRoom Layout
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2626
Test Plan OutlineTest Plan OutlineSelected Test CasesSelected Test Cases
Administrator: 1.1.2 Administrator LoginAdministrator: 1.1.2 Administrator Login 2.1 Add Homeowner2.1 Add Homeowner 2.3 Delete Homeowner2.3 Delete Homeowner 3.1.1 Add Policy3.1.1 Add Policy 3.1.2 Add Rider3.1.2 Add Rider 4.1 Add UPC Item4.1 Add UPC Item 1.3.1 Administrator Logout1.3.1 Administrator Logout
Homeowner: 1.2.1 Valid Homeowner LoginHomeowner: 1.2.1 Valid Homeowner Login 5.1.1 Add Item with Known UPC to Inventory5.1.1 Add Item with Known UPC to Inventory 5.1.2 Add Item with Unknown UPC to Inventory5.1.2 Add Item with Unknown UPC to Inventory 5.2 Add Item with No UPC to Inventory5.2 Add Item with No UPC to Inventory 8.1 Concurrent Homeowners8.1 Concurrent Homeowners 5.5.1 View Inventory5.5.1 View Inventory 5.5.2 Sort Inventory5.5.2 Sort Inventory 5.3 Modify Item in Inventory5.3 Modify Item in Inventory 6.1 Best-Fit Policy6.1 Best-Fit Policy 7 Loss7 Loss 1.2.1 Homeowner Logout1.2.1 Homeowner Logout
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2727
1.1.2 Administrator Login1.1.2 Administrator Login Test ID: 1.1.2
Test Name: Administrator Login
Description: A number of invalid username and password combinations will be entered into the Administrator Welcome Screen to ensure that it handles invalid data entry. Afterwards, an administrator login is used to ensure the system accepts administrator logins and displays the Administrator Main Menu
Test Initialization: The GUI must be complete. Administrator Welcome Screen is displayed in the Internet browser. The username, “Bob”, and password, “Bad Password”, are invalid entries. The administrator account “admin” exists
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.1, Test ID: 1.1.2
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2828
2.1 Add Homeowner2.1 Add Homeowner Test ID: 2.1
Test Name: Add Homeowner Description: A homeowner will be added to the system
Test Initialization: The GUI and Inventory functional components must be complete. The Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.2, Test ID: 2.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 2929
2.3 Delete Homeowner2.3 Delete Homeowner Test ID: 2.3
Test Name: Delete Homeowner Description: The homeowner “Kevin Smithsonian” is
deleted from the system
Test Initialization: The GUI and Inventory functional components must be complete. The Homeowner Display is displayed in the Internet browser. The homeowner account for “Kevin Smithsonian” exists
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.2, Test ID: 2.3
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3030
3.1.1 Add Policy3.1.1 Add Policy Test ID: 3.1.1
Test Name: Add Policy Description: A Policy will be added to the system
Test Initialization: The GUI and Inventory functional components must be complete. The Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.3, Test ID: 3.1.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3131
3.1.2 Add Rider3.1.2 Add Rider Test ID: 3.1.2 3.1.2
Test Name: Add Rider Description: A Rider will be added to the system
Test Initialization: The GUI and Inventory functional components must be complete. The Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.3, Test ID: 3.1.2
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3232
4.1 Add UPC Item4.1 Add UPC Item Test ID: 4.1
Test Name: Add UPC Item Description: Adds a UPC to an item
Test Initialization: The GUI and Inventory functional components must be complete. The UPC Display is displayed in the Internet browser. The item with a name of “DVD” and description of “Cars” does not have an UPC assigned to it.
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.4, Test ID: 4.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3333
1.3.1 Administrator Logout1.3.1 Administrator Logout Test ID: 1.3.1
Test Name: Administrator Logout Description: An administrator account will be logged out.
Then the tester will try to access the system without logging back in.
Test Initialization: The GUI must be complete. Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.1, Test ID: 1.3.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3434
1.2.1 Valid Homeowner 1.2.1 Valid Homeowner LoginLogin
Test ID: 1.2.1
Test Name: Valid Homeowner Login Description: A number of invalid username and password
combinations will be entered into the Homeowner Welcome Screen to ensure that it handles invalid data entry. Afterwards, a homeowner’s login is used to ensure that the system accepts valid logins in the database and uses the correct homeowner’s inventory
Test Initialization: The GUI and Inventory software components must be complete. Homeowner Welcome Screen is displayed in the Internet browser. The username, “Bob”, and password, “Bad Password”, are invalid entries. A homeowner account exists for the username, “Jsmith”.
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.1, Test ID: 1.2.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3535
5.1.1 Add Item with Known 5.1.1 Add Item with Known UPC to InventoryUPC to Inventory
Test ID: 5.1.1
Test Name: Add Item with Known UPC to Inventory Description: An item will be added to a homeowner’s
inventory by entering the items known UPC
Test Initialization: The GUI and Inventory functional components The GUI and Inventory functional components must be complete. A barcode scanner is connected to the must be complete. A barcode scanner is connected to the computer the tester is using. The tester is logged into the system computer the tester is using. The tester is logged into the system as John Doe and the Homeowner Main Menu is displayed in the as John Doe and the Homeowner Main Menu is displayed in the Internet browser. John Doe does not have “The Great Escape” in Internet browser. John Doe does not have “The Great Escape” in his inventory his inventory Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.5, Test ID:
5.1.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3636
5.1.2 Add Item with Unknown 5.1.2 Add Item with Unknown UPC to InventoryUPC to Inventory
Test ID: 5.1.2
Test Name: Add Item with unknown UPC to Inventory Description: An item will be added to a homeowner’s
inventory by entering the items unknown UPC.
Test Initialization: The GUI and Inventory functional The GUI and Inventory functional components must be complete. A barcode scanner is components must be complete. A barcode scanner is connected to the computer the tester is using. The tester is connected to the computer the tester is using. The tester is logged into the system as John Doe and the Homeowner logged into the system as John Doe and the Homeowner Main Menu is displayed in the Internet browser. There is no Main Menu is displayed in the Internet browser. There is no item in the system with the name of “DVD” and description item in the system with the name of “DVD” and description of “I Robot” of “I Robot”
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.5, Test ID: 5.1.2
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3737
5.2 Add Item with No UPC to 5.2 Add Item with No UPC to InventoryInventory
Test ID: 5.2
Test Name: Add Item with No UPC to Inventory Description: An item is added to a homeowner’s inventory
that has no UPC.
Test Initialization: The GUI and Inventory functional The GUI and Inventory functional components must be complete. components must be complete. The tester is logged into the system as John Doe and the Homeowner Main Menu is displayed in the Internet browser. John Doe does not have “Coffee Cup” in his inventory
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section 5.5, Test ID: 5.2
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3838
8.1 Concurrent Homeowners8.1 Concurrent Homeowners Test ID: 8.1
Test Name: Concurrent Homeowners Description: Two homeowners are logged into the system Two homeowners are logged into the system
at the same timeat the same time
Test Initialization: All components of the prototype are All components of the prototype are complete. Two computers and two testers are needed for complete. Two computers and two testers are needed for the test case. The Homeowner Welcome Screen is the test case. The Homeowner Welcome Screen is displayed in the Internet browser of both computers. The displayed in the Internet browser of both computers. The homeowner accounts for John Doe and Kevin Smith are homeowner accounts for John Doe and Kevin Smith are both exist both exist
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section 5.8, Test ID: 8.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 3939
5.5.1 View Inventory5.5.1 View Inventory Test ID: 5.5.1
Test Name: View Inventory Description: An item is removed from an homeowner’s
inventory
Test Initialization: The GUI and Inventory functional The GUI and Inventory functional components must be complete. The tester is logged into components must be complete. The tester is logged into the system as John Doe and the Homeowner Main Menu is the system as John Doe and the Homeowner Main Menu is displayed in the Internet browser displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.5, Test ID: 5.5.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4040
5.5.2 Sort Inventory5.5.2 Sort Inventory Test ID: 5.5.2
Test Name: Sort Inventory Description: A homeowner’s inventory is sorted by name,
description, and category
Test Initialization: The GUI and Inventory functional components must be complete. The Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.5, Test ID: 5.5.2
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4141
5.3 Modify Item in Inventory5.3 Modify Item in Inventory Test ID: 5.3
Test Name: Modify Item in Inventory Description: Information about an item is modified
Test Initialization: The GUI and Inventory functional components must be complete. The tester is logged into the system as John Doe and the Display Inventory Screen is displayed in the Internet browser. John Doe has “Coffee Cup” in his inventory
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.5, Test ID: 5.3
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4242
6.1 Best-Fit Policy6.1 Best-Fit Policy Test ID: 6.1
Test Name: Best-Fit Policy Description: The Best-Fit algorithms are tested to ensure
that they would correctly
Test Initialization: The GUI, Inventory, and Best-Fit The GUI, Inventory, and Best-Fit algorithms must be complete. The tester is logged into the algorithms must be complete. The tester is logged into the system as John Doe and the Homeowner Main Menu is system as John Doe and the Homeowner Main Menu is displayed in the Internet browserdisplayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.6, Test ID: 6.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4343
7.0 Item Loss7.0 Item Loss Test ID: 7.0
Test Name: Item Loss Description: A claim form is generated for a total loss and
a partial loss
Test Initialization: All components of the prototype are All components of the prototype are complete. The tester is logged into the system as John Doe complete. The tester is logged into the system as John Doe and the Homeowner Main Menu is displayed in the Internet and the Homeowner Main Menu is displayed in the Internet browser. browser.
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.7, Test ID: 7.0
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4444
1.2.1 Homeowner Logout1.2.1 Homeowner Logout Test ID: 1.2.1
Test Name: Homeowner Logout Description: A homeowner will be added to the system
Test Initialization: The GUI and Inventory functional components must be complete. The Administrator Main Menu is displayed in the Internet browser
Note: For more details about this test case , please refer to Prototype Test Plan Procedure, Section: 5.1, Test ID: 1.2.1
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4545
ConclusionConclusion
Our solution will assist homeowners Our solution will assist homeowners in maintaining a home inventory and in maintaining a home inventory and determining the “Best-Fit” coveragedetermining the “Best-Fit” coverage
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4646
Questions ?Questions ?
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4747
References:References:
HIMMS Product Description HIMMS Prototype Product Specification HIMMS Prototype Test Plan Procedure HIMMS Prototype User Manual HIMMS SBIR Phase 2 HIMMS WBS
April 27, 2007April 27, 2007 HIMMS Prototype PresentationHIMMS Prototype Presentation 4848
ReferencesReferences
Federal Emergency Management Federal Emergency Management AgencyAgency
http://www.fema.gov/pdf/hazard/map/declarationsmap2000_07.pdfhttp://www.fema.gov/pdf/hazard/map/declarationsmap2000_07.pdf
Insurance Information Institute Insurance Information Institute http://www.iii.org/media/presentations/pcoverview/http://www.iii.org/media/presentations/pcoverview/
US Census BureauUS Census Bureauhttp://factfinder.census.gov/servlet/STTable?_bm=y&-geo_id=01000US&-http://factfinder.census.gov/servlet/STTable?_bm=y&-geo_id=01000US&-
qr_name=ACS_2005_EST_G00_S2504&-qr_name=ACS_2005_EST_G00_S2504&-ds_name=ACS_2005_EST_G00_ds_name=ACS_2005_EST_G00_
Top Related