The document discusses reliability testing for a realtor management system (RMS) software. It defines the necessary reliability, develops an operational profile, and prepares for testing. Key points include: - The RMS failure intensity objective is set at 15 failures per 1 million transactions. - The operational profile identifies common user operations like property searches and defines their expected occurrence rates. - Approximately 148 test cases will be developed and allocated among different user types and subsystems. Over 500 hours of testing is planned to meet the failure objective.

1. Realtor Management System (RMS) (Project Presentation) Software Reliability and Testing Created By: Md. Fazlul Alam Chowdhury

4. RMS Workflow

5. Sample Screen Snapshots (Home Page)

6. Sample Screen Snapshots (Login Page)

7. Sample Screen Snapshots (Admin Main Page)

8. Sample Screen Snapshots (Realtor Main Page)

9. Sample Screen Snapshots (Custom Property Search)

10. Sample Screen Snapshots (Property Listing Page)

11. Define Necessary Reliability of RMS Reliability is a measure of continuous delivery of the correct service or equivalently, of the time to failure. In other words, it is the probability that the software will work without failure for a specified period of time (Far, 2005).

23. Development Platform Type Platform Language C# Platform .NET Framework 1.2 Database SQL Server 2000 Server System Windows 2000 Server Database SQL Server 2000 Server System Windows 2000 Server Web Server Internet Information Server (IIS) Mail Server SMTP Mail Server

24. Hardware Specification Web server SQL server CPU: 2 x 2.8 GHz Pentium 4 Memory: 2 GB Disk: 80 GB Network: 100BaseT CPU: 4 x 2.8 GHz Pentium 4 Memory: 4 GB Disk: 4 x 40 GB RAID 0 Network: 100BaseT

25. Availability of Hardware Platforms Source: ( http://www.microsoft.com/technet/itsolutions/citsrv/ib/msib2tca.mspx ) Cluster One week One month Internet-facing firewall NLB cluster 0.998867 0.999735 Web NLB cluster 0.999092 0.999788 Search NLB cluster 0.999498 0.999883 Internal firewall NLB cluster 0.999197 0.999813 SQL Server cluster 0.999504 0.999884 Total availability 0.996164 0.999103

26. Standard Availability vs Downtime Ratio Source: ( http://www.microsoft.com/technet/itsolutions/citsrv/ib/msib2tca.mspx ) Uptime Percentage Downtime /Day Downtime /Month Downtime /Year 95 72.00 minutes 36 hours 18.26 days 99 14.40 minutes 7 hours 3.65 days 99.9 86.40 seconds 43 minutes 8.77 hours 99.99 8.64 seconds 4 minutes 52.6 minutes 99.999 0.86 seconds 26 seconds 5.26 minutes

28. Failure Intensity of Hardware Systems 1 – A 1 – 0.996164 0.000897  = = = = 0.00256 / Week A t m 0.996164 X 0.35 0.35 1 Week = 1,22,000 Transactions = 0.02 Failure/1,000,000 Transactions So,  HW = 0.02 Failure/1,000,000 Transactions

29. Calculate Total Failure Intensity Source: http://www.enel.ucalgary.ca/People/far/Lectures/SENG635/ System/Platform Failure Intensity (  ) / 10 Million Transaction Hardware -  HW 0.2 Email Server-  EML 20 Other Systems -  OTH 30 Total Failure Intensity – (  SYS )  SYS = (  HW +  EML+  OTH ) i.e.  SYS  50.20 failure / 10 million transactions or 5 failure / 1,000,000 transactions

34. Developing Operational Profile of RMS Developing operational profiles will give us the information about how users will employ the product that we are building so that we can focus our development and test resources. Operational profile is the set of operations (operation names and frequencies) and their probabilities of occurrences

41. Operational Profile of Realtor Management System (RMS) Operations Occurrence Rate (Transactions) Occurrence Probability (%) Search Properties by Customers 40,000 40 Search Properties by Realtors 30,000 30 Take printout of Properties 5,000 5 Email Property 2,000 2 Upload Property Information 20,000 20 Update Property Specific Information (Require Administrative Login) 1,500 1.5 Update Realtor Profile (Require Realtor/Administrative Login) 500 0.5 Auto Email Notification to Realtor 1,000 1 Total 1,00,000 100

44. Preparing for Test In preparing for test, we apply the operational profile information that we have developed to planning for an efficient test. Our failure intensity should meet the FIO (Failure Intensity Objective) of RMS which is 15 failures / 1000,000 Transaction.

51. Test profile for one of the operational modes (Realtor) Test Case Description Startup Realtor operates startup page Update Profile Realtor updates profile Search Property by Listing Number Realtor searches property by listing number View Today’s Listing Realtor can see today’s listed properties Search Property Realtor searches property Show Property Realtor receives selected property information

54. Hours devoted to feature, regression, and load test for the product (II) Testing Type Hours Percentage Feature Testing 24 4.15% Load Testing 528 91.7% Regression Testing 24 4.15%

57. Execute Test Realtor Management System (RMS) is at the final phase. Development is completed and ready for Reliability Testing.

61. Initial System State

62. Actual Output

68. Table1: Certification Graph Value Failure Number Measure (million transactions) Normalized Measure (MTTF) 1 0.1 1.5 2 0.2 3 3 0.3 4.5 4 0.4 6 5 0.5 7.5 6 0.6 9 7 0.7 10.5 8 0.8 12 9 0.9 13.5 10 10.0 15

69. Certification Graph: Figure 1 Failure Number Normalized Measures (MTTF) Reject Accept Continue

73. Thank you all for watching this presentation