System and Software Architecture Description (SSAD)

Transcription

1 System and Software Architecture Description (SSAD) REAL ESTATE INVESTMENT AND REVIEW TOOL TEAM 02 Venkata Sravanti Malapaka (Project Manager / Software Architect) Yuxuan Chen (Prototyper / Developer/Trainer) Yonghyun Cho (Requirements Engineer / Developer) Md Shadman Rafid (Operational Concept Engineer / Trainer) Shiraksha Rao (Feasibility Analyst, Trainer) Vikram Mudaliar (Life Cycle Planner, Software Architect) Webber Wang (Tester, Quality Focal Point, Developer) Jose Gabriel Vicente Hernandez (IV and V, Tester) SSAD_TRR_F18a_T02_V /02/2018

2 Version History Date Author Version Changes made Rationale 10/11/18 VSM 1.0 Added Introduction and System Analysis 10/22/18 VSM Updated Use Case Diagrams - Updated artifacts and information diagram - completed All document sections 12/02/18 VSM Updated Use cases and developments done - Updated the document taking into consideration comments from the DC Package - Adjusted the document post TRR and learnt the core capabilities implemented and changed the document accordingly Initial draft for DC Package Final document for DC package Final document for As-Built Package SSAD_TRR_F18a_T02_V /02/2018

3 Table of Contents 1. Introduction Purpose of the SSAD Status of the SSAD System Analysis System Analysis Overview System Context Artifacts & Information Behavior Modes of Operation System Analysis Rationale Technology-Independent Model Technology-Specific System Design Design Overview System Structure Design Classes Process Realization Design Rationale Architectural Styles, Patterns and Frameworks 93 SSAD_TRR_F18a_T02_V /02/2018

4 Table of Tables Table 1- Actors Summary 13 Table 2- Artifacts and Information Summary 15 Table 3- Process Description: Sign Up 18 Table 4- Typical course of action: Sign Up 19 Table 5- Alternative course of action: Sign up failed due to incomplete form 19 Table 6- Process description: View all service providers 19 Table 7- Typical course of action: View all service providers 20 Table 8- Process description: Search for service provider 20 Table 9- Typical course of action: Search for service provider 20 Table 10- Process description: View a service provider s profile 21 Table 11- Typical course of action: View a service provider s profile 22 Table 12- Process description: Read reviews 22 Table 13- Typical course of action: Read reviews 22 Table 14- Process description: Share a service provider s profile 23 Table 15- Typical course of action: Share a service provider s profile 23 Table 16- Alternative course of action: Share a service provider fails due to error on social media API 23 Table 17- Process description: Contact Admin 23 Table 18- Typical course of action: Contact Admin 24 Table 19- Process description: Read Blog 24 Table 20- Typical course of action: Read Blog 24 Table 21- Process description: Share Blog 25 Table 22- Typical course of action: Share Blog 25 Table 23- Alternative course of action: Share a service provider fails due to error on social media API 26 Table 24- Process description: Contact service provider 26 Table 25- Typical course of action: Contact service provider 26 Table 26- Process description: Login 27 Table 27- Typical course of action: Login 27 SSAD_TRR_F18a_T02_V /02/2018

5 Table 28- Alternative course of action: Login failed 27 Table 29- Process description: Add a profile 28 Table 30- Typical course of action: Add a profile 28 Table 31- Alternative course of action: Add a profile failed because creation form is incomplete 29 Table 32- Alternative course of action: Add a profile failed because database is not available 29 Table 33- Process description: Share profile 29 Table 34- Typical course of action: Share profile 30 Table 35- Alternative course of action: Share a service provider fails due to error on social media API 30 Table 36- Process description: Add a property 31 Table 37- Typical course of action: Add a property 31 Table 38- Alternative course of action: Add a property failed because creation form is incomplete 31 Table 39- Alternative course of action: Add a property failed because database is not available 32 Table 40- Process description: Compare Property 32 Table 41- Typical course of action: Compare property 33 Table 42- Process description: Track Investment 33 Table 43- Typical course of action: Track Investment 34 Table 44- Process description: Export tracking data 34 Table 45- Typical course of action: Export tracking data 35 Table 46- Alternative course of action: Export tracking data failed because error on operating system 35 Table 47- Process description: Write review 36 Table 48- Typical course of action: Write review 36 Table 49- Alternative course of action: Write Review failed because database is not available 36 Table 50- Process description: Read Review 37 Table 51- Typical course of action: Read Review 37 Table 52- Process description: Start discussion 38 Table 53- Typical course of action: Start discussion 38 Table 54- Alternative course of action: Start discussion failed because database is not available 38 Table 55- Process description: Read discussion 38 Table 56- Typical course of action: Read discussion 39 SSAD_TRR_F18a_T02_V /02/2018

6 Table 57- Process description: Like or dislike reviews 39 Table 58- Typical course of action: Like or dislike reviews 40 Table 59- Alternative course of action: Like or dislike failed because database is not available 40 Table 60- Process description: Comment on blog 40 Table 61- Typical course of action: Comment on blog 30 Table 62- Alternative course of action: Comment on blog failed due to error in database 41 Table 63- Process description: Two-factor Authentication 41 Table 64- Typical course of action: Two-factor Authentication 41 Table 65- Alternative course of action: Two-factor authentication failed due to bad username and password 42 Table 66- Alternative course of action: Two-factor authentication failed due to bad answer to question 43 Table 67- Process description: Recover password/ reset password 43 Table 68- Typical course of action: Recover password/ reset password 43 Table 69- Alternative course of action: Recover password/ reset password failed because link is too old 44 Table 70- Alternative course of action: Recover password/reset password failed because incorrect password 44 Table 71- Process description: Adjust notification 45 Table 72- Typical course of action: Adjust notification 46 Table 73- Alternative course of action: Adjust notification failed because of error in database 46 Table 74- Process description: Check for new notifications 47 Table 75- Typical course of action: Check for new notifications 47 Table 76- Process description: Reply comments for reviews 48 Table 77- Typical course of action: Reply comments for reviews 48 Table 78- Alternative course of action: Reply comments for reviews failed because of error in database 49 Table 79- Process description: Revise personal information 49 Table 80- Typical course of action: Revise personal information 49 Table 81- Process description: Add a profile 49 Table 82- Typical course of action: Add a profile 50 Table 83- Alternative course of action: Add profile failed because of error in database 50 Table 84- Process description: Claim an existing service provider s profile 50 Table 85- Typical course of action: Claim an existing service provider s profile 51 SSAD_TRR_F18a_T02_V /02/2018

7 Table 86- Process description: Write a blog 51 Table 87- Typical course of action: Write a blog 52 Table 88- Alternative course of action: Write blog failed because of error in database 52 Table 89- Process description: Verify user 52 Table 90- Typical course of action: Verify user 53 Table 91- Alternative course of action: Verify user failed because of error in database 53 Table 92- Process description: View statistics 53 Table 93- Typical course of action: View statistics 54 Table 94- Process description: Remove flagged/fake website users 54 Table 95- Typical course of action: Remove flagged/fake website users 55 Table 96- Alternative course of action: Remove flagged/fake users failed because of error in database 55 Table 97- Process description: Delete inappropriate user content 55 Table 98- Typical course of action: Delete inappropriate user content 56 Table 99- Alternative course of action: Delete inappropriate user content failed because of error in database 56 Table 100- Process description:enable/disable write button on review button 57 Table 101- Typical course of action: Enable/disable write button on review button 58 Table 102- Alternative course of action: for unregistered user 58 Table 103: Hardware Component Description 63 Table 104: Software component description 63 Table 105: Architectural Styles, Patterns, and frameworks 95 SSAD_TRR_F18a_T02_V /02/2018

8 Table of Figures Figure 1- System- context diagram 13 Figure 2- Artifacts and Information Diagram 15 Figure 3- Unregistered User Use case diagram 16 Figure 4: Registered User Use Case Diagram 17 Figure 5: Website Administrator Use Case Diagram 18 Figure 6- Conceptual domain model 61 Figure- 7- Hardware Component Class diagram 61 Figure 8- Software Component Class diagram 61 Figure 9- Deployment Diagram 62 Figure 10: Design class diagram 64 Figure 11- UC-1 Sign up Robustness Diagram 65 Figure 12- UC-1 Sign Up sequence diagram 65 Figure 13- UC-2 View all Service Providers Robustness Diagram 66 Figure 14- UC-2 View all Service Providers Sequence Diagram 66 Figure 15- UC-3 Search for Service Provider Robustness Diagram 66 Figure 16- UC- 3 Search for Service Provider Sequence Diagram 67 Figure 17- UC-4 View a Service Provider s profile Robustness Diagram 67 Figure 18- UC-4 View a Service Provider s profile Sequence Diagram 68 Figure 19- UC-5 Read Review Robustness Diagram 68 Figure 20- UC-5 Read Review Sequence Diagram 68 Figure 21- UC-6 Share a Service Provider Profile Robustness Diagram 69 Figure 22- UC-6 Share a Service Provider Profile Sequence Diagram 69 Figure 23- UC-7 Contact admin Robustness Diagram 69 Figure 24- UC-7 Contact admin Sequence Diagram 70 Figure 25- UC-8 Read Blog Robustness Diagram 70 SSAD_TRR_F18a_T02_V /02/2018

9 Figure 26- UC-8 Read Blog Sequence Diagram 70 Figure 27- UC-9 Share Blog Robustness Diagram 71 Figure 28- UC-9 Share Blog Sequence Diagram 71 Figure 29- UC-10 contact Service Provider robustness diagram 71 Figure 30- UC-10 contact Service Provider Sequence diagram 71 Figure 31- UC-11 Login Robustness Diagram 72 Figure 32- UC-11 Login Sequence Diagram 72 Figure 33- UC- 13 Robustness diagram for add a profile 73 Figure 34- UC-13 Sequence Diagram for add a profile 73 Figure 35- UC-14 Robustness diagram for Share a profile 74 Figure 36- UC-14 Sequence diagram for Share a profile 74 Figure 37- UC- 16: Search for Service Provider Robustness Diagram 75 Figure 38- UC-16 Search for Service Provider Sequence Diagram 75 Figure 39- UC-18 Add a property Robustness Diagram 76 Figure 40- UC- 18 Add a property Sequence Diagram 76 Figure 41- UC 19: Robustness diagram for compare property 77 Figure 42- UC-19 Sequence diagram for compare property 77 Figure 43- UC-20 Robustness diagram for Track Investment 78 Figure 44- UC-20 Sequence diagram for Track Investment 78 Figure 45- UC-21 Export Tracking data Robustness Diagram 79 Figure 46- UC-21 Export Tracking data Sequence Diagram 79 Figure 47- UC-22 Write review Robustness Diagram 67 Figure 48- UC-22 Write review sequence Diagram 80 Figure 49- UC-23 Read Review Robustness Diagram 80 Figure 50- UC-23 Read Review Sequence Diagram 81 Figure 51- UC- 27 Like or Dislike reviews Robustness Diagram 81 SSAD_TRR_F18a_T02_V /02/2018

10 Figure 52- UC- 27 Like or Dislike reviews Sequence Diagram 81 Figure 53- UC- 28 Comment on blog robustness diagram 82 Figure 54- UC- 28 Comment on blog sequence diagram 82 Figure 55- UC-29 Robustness diagram for two-factor authentication 83 Figure 56- UC-29 Sequence Diagram for Two-factor authentication 83 Figure 57- UC- 30 Recover Password Robustness Diagram 84 Figure 58- UC-30 Recover Password Sequence Diagram 84 Figure 60- UC- 31 Adjust Notifications Sequence diagram 84 Figure 61- UC- 34- Robustness Diagram for Check for new notifications 85 Figure 62- UC-34 Sequence Diagram for Check for new notifications 85 Figure 63- UC-35 Reply comments for reviews Robustness Diagram 85 Figure 64- UC- 35 Reply comments to reviews sequence Diagram 86 Figure 65- UC-36 Revise personal information Robustness Diagram 86 Figure 66- UC-36 Revise Personal information Sequence Diagram 86 Figure 67- UC- 37 Robustness diagram for add a profile 87 Figure 68- UC-37 Sequence Diagram for add a profile 87 Figure 69- UC- 38 Claim an existing Service Provider Profile Robustness Diagram 87 Figure 70- UC-38 Claim an existing Service Provider Profile Sequence Diagram 88 Figure 71- UC-40 Write a blog robustness diagram 88 Figure 72- UC-40 Write a blog Sequence diagram 88 Figure 73- UC- 41- Robustness Diagram for Verify a user 76 Figure 74- UC- 41- Sequence Diagram for Verify a user 89 Figure 75- UC 42- Robustness Diagram for View Statistics 89 Figure 76- UC-42 Sequence Diagram for View Statistics 90 Figure 77- UC-43 remove flagged/ fake website users Robustness Diagram 90 Figure 78- UC-43 remove flagged/ fake website users Sequence Diagram 90 SSAD_TRR_F18a_T02_V /02/2018

11 Figure 79- UC-44 Delete Inappropriate User content Robustness Diagram 91 Figure 80- UC-44 Delete Inappropriate User content Sequence Diagram 92 Figure 81- UC-45 Enable/disable write button on a review button Robustness diagram 92 Figure 82- UC-45 Enable/disable write button on a review button Sequence Diagram 92 SSAD_TRR_F18a_T02_V /02/2018

12 1. Introduction 1.1. Purpose of the SSAD The purpose of the SSAD is to provide a detailed description of the system architecture and its components. This document aims to identify the key users and their interaction with the system developed, as well as the functions they can perform while using the system based on their given role Status of the SSAD This is the final version of the System and Software Architecture Description document. It includes Updated Use Case Diagrams, Updated artifacts and information diagram, All document sections along with Introduction and System Analysis from the initial draft. 2. System Analysis 2.1. System Analysis Overview Create an online resource to help real estate investors track investments and evaluate resources related to property scouting, acquisition, maintenance, and management through community reviews and referrals. SSAD_TRR_F18a_T02_V /02/2018

13 System Context Table 1- Actors Summary Figure 1- System- context diagram ACTOR DESCRIPTION RESPONSIBILITIES Unregistered User Registered User Investor (A kind of Any random surfer who visits the website. He can also be a person who wants to become a registered user of the website- he must sign up for that A user who is the actual user of the website and can use all functionalities the website provides A registered user, who is interested in investing for - Search for service providers - View a service provider s profile - contact admin - sign up - read blog contents - search for any specific service provider - view all service providers - login - contact admin - read blog contents - search for any specific service provider - adjust notifications - View all properties - Compare properties SSAD_TRR_F18a_T02_V /02/2018

14 Registered User) Service Provider (A kind of Registered User) Administrator properties and can track/compare his properties. He can also store data for his properties like the costs incurred. A person who acts as a point of contact between the investors and their investments A person responsible for maintaining the website for its proper functionality - Track investments using tracking tool - view all service providers - login - contact admin - read blog contents - search for any specific service provider - adjust notifications - view all service providers - login - contact admin - read blog contents - search for any specific service provider - adjust notifications - Login - Write a blog - Verify a registered user - view website utilization statistics - remove flagged users/ fake website users - delete inappropriate user contents Artifacts & Information Figure 2- Artifacts and Information Diagram SSAD_TRR_F18a_T02_V /02/2018

15 Table 2- Artifacts and Information Summary Artifacts ART-1: User Access Level ART-2: Investor Profile Purpose Access level privileges of a given user. This could be one of the following access levels: Admin, Service Provider, Investor, Unregistered User Contains information about a user, including: name, address, password. SSAD_TRR_F18a_T02_V /02/2018

16 ART-3: Investments ART-4: Service Provider Profile ART-5: Reviews Contain information about monthly rent, mortgage, down-payment, interest rate and so on. Contains information about a user, including: name, phone number, address, password. Contains review and rate for a service provider Behavior Figure 3- Unregistered User Use case diagram SSAD_TRR_F18a_T02_V /02/2018

17 Figure 4: Registered User Use Case Diagram NOTE- Investor and Service provider are only the kinds of registered users, they do not have separate functionalities which a registered user does not have. Thus, there are no separate functionality Use-Case diagrams given for Investors and Service Providers. Moreover, a service provider can also be an investor and thus they share functionalities. SSAD_TRR_F18a_T02_V /02/2018

18 Figure 5: Website Administrator Use Case Diagram Sign Up Table 3- Process Description: Sign Up Identifier Purpose Requirements Development Risks Pre-conditions UC- 1 Sign Up User can sign up for creating his own profile in our website WC_4759 Password must be encrypted and stored securely on the server, has security implications when saving the password in the database. User must be on the sign-up page of the website The user should enter all the fields required for sign up correctly SSAD_TRR_F18a_T02_V /02/2018

19 Post-conditions If user has provided all valid information, then he can Sign up and login to the website and get all the privileges of a registered user accessing the website Table 4- Typical course of action: Sign Up 1 Go to Home page 2 Click on Sign Up button to go to the Sign-Up page. 3 Fill out fields in the form: User Name, , Password, Re-type Password". 4 Click on Sign Up button to confirm provided information. 5 Creates a user account in database. 6 If success, the user get access into website (login). Table 5- Alternative course of action: Sign up failed due to incomplete form 1-4 Refer to typical course of action 5 Display error message indicating why the form is considered incomplete View All Service Providers Table 6- Process description: View all service providers Identifier UC- 2: View all service providers Purpose Requirements Development Risks The user can browse through all available registered Service providers in the website WC_4632 None SSAD_TRR_F18a_T02_V /02/2018

20 Pre-conditions Post-conditions Database is initialized properly User is on the service provider s page User can view service provider s list Table 7- Typical course of action: View all service providers 1 Go to Home page 2 Click on Service Providers button to go the list of service providers. 3 Query database and shows all the service providers sorted descending by creation date Search for a Service Provider Table 8- Process description: Search for service provider Identifier UC- 3 Search for service provider Purpose Requirements Development Risks Pre-conditions Post-conditions The user can filter his search to find a specific service provider, based on name, phone number, zip code or Geographical region WC_4762 Searching performance would be significantly low if too many services provider s profiles with same key field existed in database Database is initialized properly User is on the service provider s page User can search for the service provider s profile he wants to navigate to. Table 9- Typical course of action: Search for service provider 1 Follow the typical course of action: View all service providers to go to the list of service providers. SSAD_TRR_F18a_T02_V /02/2018

21 2 Fill out the field Search service provider by with the name, , phone or address of the required service provider. 3 Select the type of service provider from the combo Provider Type. 4 Query the database and shows all the service provider that match the criteria provided by actor View a service Provider s profile Table 10- Process description: View a service provider s profile Identifier UC- 4 View a service provider s profile Purpose Requirements Development Risks Pre-conditions Post-conditions The user can select the service provider he wants to know detailed information about, and that will redirect him to that Service provider s profile WC_4641 Service provider s profile was revised but hasn t been updated in time; Database is initialized properly User is on the service provider s page User can view the service provider s page Table 11- Typical course of action: View a service provider s profile 1 Follow the typical course of action: Search for service provider to filter the service providers and obtain the ones that match actor s criteria. 2 Select the desired service provider from the table. 3 Redirect to the Profile Page of the selected Service Provider. SSAD_TRR_F18a_T02_V /02/2018

22 4 Show detailed information about the selected service provider Read Reviews Table 12- Process description: Read reviews Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 5 Read reviews The user, after sees into the profile of service provider, will be able to check reviews given about him on the review board of his profile WC_4758 Database crash may cause data loss of review information; Bad query on server side may cause too much waiting time or wrong data output; User is on the Profile page of a service provider User is able to read reviews about that particular service provider Table 13- Typical course of action: Read reviews 1 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 2 Show detailed information about the selected service provider. 3 Read reviews from the selected service provider Share a service Provider s profile Table 14- Process description: Share a service provider s profile Identifier UC- 6 Share a service provider s profile SSAD_TRR_F18a_T02_V /02/2018

23 Purpose Requirements Development Risks Pre-conditions Post-conditions The user should be able to share the information of a service provider using social media WC_4760 Integrating modules involves many works and time. We need to understand requirements and API response format User is on the Profile page of a service provider User is able to see the share via social network buttons on the page he visited The Service Provider profile is shared using any of the Social media buttons Table 15- Typical course of action: Share a service provider s profile 1 Follow the typical course of action: View a service provider s profile to go to the profile page of a specific service provider. 2 Click on social media buttons. 3 Trigger sharing API & redirect to external site when clicking on share button. Table 16- Alternative course of action: Share a service provider fails due to error on social media API 1-3 Refer to typical course of action. 4 Display error message indicating that the social media server is not available or it has responded with an error. - Contact Admin (to be developed- beyond scope of semester) SSAD_TRR_F18a_T02_V /02/2018

24 Table 17- Process description: Contact Admin Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 7 Contact Admin The user will be able to contact the Admin by going to the contact us button at the Website footer, to comment or about the Website WC-4641 None as of now (not yet implemented) User is able to see the option to contact the website admin The admin gets contacted by the user Table 18- Typical course of action: Contact Admin 1 Go to Home page 2 Click on Contact link at the bottom of the page. 3 Click on link 4 Opens the default system mail application. - Read Blog(to be developed- beyond scope of semester) Table 19- Process description: Read Blog Identifier Purpose Requirements Development Risks UC- 8 Read Blog The user will be able to read the blog written by Website Admin WC_4761 Blog data may not be associated with admin of main site if we use an NDI for the blog. This will store the blog admin user account on a separate database. SSAD_TRR_F18a_T02_V /02/2018

25 Pre-conditions Post-conditions User is on the blog page of the website User is able to view the blog Table 20- Typical course of action: Read Blog 1 Go to Home page 2 Click on Blogs button. 3 Query the database to get the blogs. 4 Display the Blogs page which contains a table of blogs sorted descending from the most recent. 5 Click on the specific blog to read. 6 Display the specific blog page. - Share Blog(to be developed- beyond scope of semester) Table 21- Process description: Share Blog Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 9 Share Blog The user will be able to share the blog using social media. WC_4760 Social media sharing API may break in the future, since we re depending on several external services. User is on the blog page of the website User is able to see the share via social network buttons on the page he visited The Service Provider profile is shared using any of the Social media buttons Table 22- Typical course of action: Share Blog SSAD_TRR_F18a_T02_V /02/2018

26 1 Follow the typical course of action: Read Blog to go to the blogs page. 2 Click on social media share icon. 3 Trigger sharing API & redirect to external site when clicking on share button. Table 23- Alternative course of action: Share a service provider fails due to error on social media API 1-3 Refer to typical course of action. 4 Display error message indicating that the social media server is not available, or it has responded with an error Contact Service Provider Table 24- Process description: Contact service provider Identifier UC- 10 Contact service provider Purpose Requirements Development Risks Pre-conditions Post-conditions The user could be able to contact the service provider for an extended conversation about buying property WC_4641 Service provider s profile was revised but hasn t been updated in time; Unverified service provider s registration that contains wrong contact info; User is on the service provider profile page of the website User is able to see the option to contact the service provider The Service provider gets contacted by the website user SSAD_TRR_F18a_T02_V /02/2018

27 Table 25- Typical course of action: Contact service provider 1 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 2 Click on contact link from the service provider profile page. 3 Opens the default system mail application Login Table 26- Process description: Login Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 11 Login User login into the system using username and password WC_4633 Multiple scenarios to handle for frontend and backend validation, missing any piece may impact UX. Security implications when dealing with password System database is properly initialized User is on the login page of the Real Estate investment and review tool System website If user is authorized, he/she is login in the system and given access based on his/her assigned access privileges Table 27- Typical course of action: Login 1 Go to home page. 2 Click on Login button at the top of the page. 3 Provide username and password. SSAD_TRR_F18a_T02_V /02/2018

28 4 Click on Login button. 5 Query username and password from database and validate username and password provided by Actor. 6 Display main screen if username and password are valid. Table 28- Alternative course of action: Login failed 1-5 Refer to typical course of action. 6 Display error message indicating that the username or password is incorrect. NOTE- UC-12 is same as UC-1, having the same process description, typical course of action and alternative course of action, the only difference is that the actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided Add a Profile Table 29- Process description: Add a profile Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 13 Add a profile Register for someone else- create account for a Service Provider to portray his profile in the website WC_4637 System could be vulnerable by invalid data. Code injection attack could result in data loss or system malfunction. Database is initialized properly The person accessing the website is a registered user Profile added into the website SSAD_TRR_F18a_T02_V /02/2018

29 Table 30- Typical course of action: Add a profile 1 Follow the typical course of action: View all service providers to go to the list of service providers. 2 Click on the button Add Provider 3 Provide the information required to create a service provider. 4 Click on the button Create 5 Insert the profile in database. Table 31- Alternative course of action: Add a profile failed because creation form is incomplete 1-4 Refer to typical course of action. 5 Display error message indicating the creation form is incomplete. The message must indicate the field that is missing. Table 32- Alternative course of action: Add a profile failed because database is not available 1-4 Refer to typical course of action. 5 Display error message indicating the insertion on database failed Share a profile Table 33- Process description: Share profile Identifier Purpose Requirements Development Risks UC- 14 Share profile The user should be able to share the information of a service provider using social media WC_4641 Not enough cooperation with relative SSAD_TRR_F18a_T02_V /02/2018

30 platform can result in a not readable share content; Sensitive user information loss when sharing the profile; Pre-conditions Post-conditions User is on the service provider profile page of the website User is able to see the share via social network buttons on the page he visited The Service Provider profile is shared using any of the Social media buttons Table 34- Typical course of action: Share profile 1 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 2 Click on social media buttons. 3 Trigger sharing API & redirect to external site when clicking on share button. Table 35- Alternative course of action: Share a service provider fails due to error on social media API 1-3 Refer to typical course of action. 4 Display error message indicating that the social media server is not available or it has responded with an error. NOTE- UC-15 is same as UC-4, having the same process description, typical course of action and alternative course of action, the only difference is that the actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided. NOTE- UC-16 is same as UC-3, having the same process description, typical course of action and alternative course of action, the only difference is that the SSAD_TRR_F18a_T02_V /02/2018

31 actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided. NOTE- UC-17 is same as UC-9, having the same process description, typical course of action and alternative course of action, the only difference is that the actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided Add a property Table 36- Process description: Add a property Identifier Purpose Requirements Development Risks Pre-conditions UC- 18 Add a property The user can add a property to his profile to track his investment using tracking tool WC_4663 The Zillow API has issues picking up the price of the property using the address when the house isn t listed for sale. The price needs to be obtained consistently. User is an Investor only/ Both an investor and a service provider of the website In simpler words, the user is a registered user of the website User is on the properties page of the website There is an option to add property to the website Post-conditions Property added to the page of the Investor Table 37- Typical course of action: Add a property 1 Go to the Home page 2 Click on Investments button to go to the Investments page where the properties table is found. SSAD_TRR_F18a_T02_V /02/2018

32 3 Click on Add Provider button. 4 Provide all the information required to create a property. 5 Click on Create button. 6 Insert the new property into the database. Table 38- Alternative course of action: Add a property failed because creation form is incomplete 1-5 Refer to typical course of action. 6 Display error message indicating the creation form is incomplete. The message must indicate the field that is missing. Table 39- Alternative course of action: Add a property failed because database is not available 1-5 Refer to typical course of action. 6 Display error message indicating the insertion on database failed. 5- Compare Property(to be developed- beyond scope of semester) Table 40- Process description: Compare Property Identifier Purpose Requirements Development Risks Pre-conditions UC- 19 Compare Property He can make a comparison among his properties to evaluate investments/returns WC_4631 The compare feature is not a widely implemented feature. It would require decent amount of custom code, making it more prone to errors and bugs. Also there are less examples to follow, making development more difficult. User is an Investor only/ Both an investor and SSAD_TRR_F18a_T02_V /02/2018

33 a service provider of the website In simpler words, the user is a registered user of the website There is a means to compare properties on the website/option for property comparison visible More than one property present on the investments page since one can compare properties which are >=2 Post-conditions Properties compared, and result evaluated by the registered user Table 41- Typical course of action: Compare property 1 Go to the Home page 2 Click on Investments button to go to the Investments page where the properties table is found. 3 Select the properties to compare. 4 Click on compare properties. 5 Query properties information from database and compare them. 6 Display comparison in a popup page track investment Table 42- Process description: Track Investment Identifier Purpose Requirements Development Risks UC- 20 Track Investment The user can track his investment using the tracking tool in the website WC_4763 Integration with Zillow API has been SSAD_TRR_F18a_T02_V /02/2018

34 problematic. Only the data for listed houses are shown. We ll need to explore API better or look for alternative. Pre-conditions User is an Investor only/ Both an investor and a service provider of the website In simpler words, the user is a registered user of the website Tracking tool working properly Valid number of parameters passed to the tracking tool so that the result evaluate is correct. Post-conditions Investment by an Investor only/ Both an investor and a service provider of the website tracked Table 43- Typical course of action: Track Investment 1 Go to the Home page 2 Click on Investments button to go to the Investments page where the properties table is found. 3 Query properties from database and show the properties in a table. 4 Select a property and click on it to get detailed information Export Tracking data Table 44- Process description: Export tracking data Identifier Purpose Requirements Development Risks UC- 21 Export tracking data The user can export his data into a.csv file WC_4769 Will need to be careful when matching up the key value pairs, since there will be multiple fields I can foresee a human error of missing SSAD_TRR_F18a_T02_V /02/2018

35 fields. Pre-conditions User is an Investor only/ Both an investor and a service provider of the website In simpler words, the user is a registered user of the website Tracking tool working properly Valid number of parameters passed to the tracking tool so that the result evaluate is correct. Investment by an Investor only/ Both an investor and a service provider of the website tracked. Option to export the tracking data produced visible to the Investor only/ Both an investor and a service provider Post-conditions Tracking data exported to a.csv file Table 45- Typical course of action: Export tracking data 1 Go to the Home page 2 Click on Investments button to go to the Investments page where the properties table is found. 3 Click on Export properties information. 4 Query properties information from database (include expenses). 5 Export the queried information into a CSV file. Table 46- Alternative course of action: Export tracking data failed because error on operating system 1-5 Refer to typical course of action. 6 Display error message indicating the CSV file could not be created. SSAD_TRR_F18a_T02_V /02/2018

36 Write review Table 47- Process description: Write review Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 22 Write review Write a review on a real-estate Agent s profile WC_4634 Database crashes may cause loss in review data; Used by unverified user may cause damage of service provider s reputation or interest. The user using the website is a registered user and is on the profile page of the Service Provider. An option to write a review is present/ visible to the registered user Review about the service provider written and is visible on the profile page of the Service Provider. Table 48- Typical course of action: Write review 1 Follow the typical course of action: View all service providers to go to the list of service providers. 2 Click on Add Review button of the desired service provider. 3 Provide all the information required to create a review (including comments and stars evaluation) 4 Insert review in database. Table 49- Alternative course of action: Write Review failed because database is not available 1-4 Refer to typical course of action. 5 Display error message indicating the SSAD_TRR_F18a_T02_V /02/2018

37 insertion on database failed Read Review Table 50- Process description: Read Review Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 23 Read Review Read a review of a real-estate Agent s profile WC_4758 When a review is too long, some of its data may be lost when storing and transferring; Inefficient or wrong query used on back end may cause wrong data output or too long waiting. The user using the website is a registered user and is on the profile page of the Service Provider. At least one review is written by a registered user of the website on the Service Provider s profile page. Any user, registered/ unregistered/ admin is able to see the review about a service provider Table 51- Typical course of action: Read Review 1 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 2 Query reviews from database. 3 Show reviews in the service provider s profile page. NOTE- UC-24 is not among one of the core capabilities to be implemented this semester, this is beyond the scope of this semester and thus its process and workflow has not been designed yet. SSAD_TRR_F18a_T02_V /02/2018

38 0- Start Discussion (to be developed- beyond scope of semester) tionary requirement Table 52- Process description: Start discussion Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 25 Start discussion Start a discussion using discussion board WC_4681 Yet to be developed The user using the website is a registered user and is on the discussions page. Discussion post seen on the discussion board of the website Table 53- Typical course of action: Start discussion 1 Go to the Home page. 2 Click on Discussion Board button. 3 Click on Add Discussion 4 Provide all the information required to create a discussion. 5 Insert the root discussion entry into the database. Table 54- Alternative course of action: Start discussion failed because database is not available 1-5 Refer to typical course of action. 6 Display error message indicating the insertion in database failed. 1- Read Discussion (to be developed- beyond scope of semester) - evolutionary requirement SSAD_TRR_F18a_T02_V /02/2018

39 Table 55- Process description: Read discussion Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 26 Read discussion Read an existing discussion WC_4766 Yet to be developed The user using the website is a registered user and is on the discussions page. There is at least one entry on the discussion board of the website Discussions on the discussion board seen on the website. Table 56- Typical course of action: Read discussion 1 Go to the Home page. 2 Click on Discussion Board button. 3 Query all the root discussion entries from database. 4 Shows all the root discussions in a table 5 Select a discussion and click on it 6 Show the list of entries related to the root discussion. 2- Like or Dislike reviews(to be developed- beyond scope of semester) Table 57- Process description: Like or dislike reviews Identifier UC- 27 Like or dislike reviews Purpose Requirements Development Risks He can like a review or dislike a review on the review board of a Service Provider WC_4643 Network problem may cause data loss when SSAD_TRR_F18a_T02_V /02/2018

40 transferring, so the result of like/dislike may not be updated in database; Abuse of this function may cause user loss. Pre-conditions Post-conditions The user using the website is a registered user and is on the profile page of the Service Provider. At least one review is written by a registered user of the website on the Service Provider s profile page. There is an option to like/dislike any review on the profile page of the service provider The reviews are liked/ disliked by a registered user of the website Table 58- Typical course of action: Like or dislike reviews 1 Follow the typical course of action: Read Review to go to the profile page of an specific service provider. 2 Select the review and read it. 3 Click on Like or Dislike button 4 Increment amount of Likes or Dislikes in database. Table 59- Alternative course of action: Like or dislike failed because database is not available 1-4 Refer to typical course of action. 5 Display error message indicating the update on database failed. 3- Comment on Blog (to be developed- beyond scope of semester) Table 60- Process description: Comment on blog Identifier Purpose UC- 28 Comment on blog He can comment on a blogpost SSAD_TRR_F18a_T02_V /02/2018

41 Requirements Development Risks Pre-conditions Post-conditions WC_4651 For real-world useability, we may need to implement some kind of spam detection, or rate limiting for comments. This increases complexity of the feature. The user using the website is a registered user and is on the blog page of the Website. At least one blog post is written by the admin of the website on the blog page. There is an option to comment on the blog posted by admin on the blog page The registered user is able to see his comment on the blog of the website Table 61- Typical course of action: Comment on blog 1 Go to Home page. 2 Click on Blogs button. 4 Query blogs from database. 5 Display list of blogs in a table. 6 Select an specific blog from the list. 7 Query all the comments of the selected blog from database. 8 Display all the comments in a table. 9 Click on Add Comment 10 Provide the comment and click on Add. 11 Create the new comment into database. Table 62- Alternative course of action: Comment on blog failed due to error in database 1-10 Refer to typical course of action. SSAD_TRR_F18a_T02_V /02/2018

42 5 Display error message indicating the insert in database failed Two- factor Authentication Table 63- Process description: Two-factor Authentication Identifier UC- 29 Two-factor Authentication Purpose Requirements Development Risks Pre-conditions Post-conditions Two-factor Authentication to prevent unauthorized user access to his profile WC_4767 Any item that deals with security and logging in users need to be tested thoroughly. We don t want a non-authorized user gaining access to registered users account. The user must be a registered user of the website The user wants to login to the website. The user has a mobile connection to the website The user must accept the login request The registered user gets logged in to the website and can access all the privileges the website gives to him Table 64- Typical course of action: Two-factor Authentication 1 Go to Home page. 2 Click on Login button. 3 Provide username and password. 4 Query username and password from database and validate username and password provided 5 If user get access into website, go to settings page and activate two factor SSAD_TRR_F18a_T02_V /02/2018

43 authentication. 6 Logouts user and ask for login again. 7 Go to Login page and write username, password and, if two factor authentication is active then check the two factor authentication box. 8 Provide security code and click on login. 9 Validates answer and login user if correct. Table 65- Alternative course of action: Two-factor authentication failed due to bad username and password 1-9 Refer to typical course of action. 10 Display error message indicating that user name or password is incorrect. Table 66- Alternative course of action: Two-factor authentication failed due to bad answer to question 1-11 Refer to typical course of action. 12 Display error message indicating the code is incorrect and user should try again Reset password Table 67- Process description: Recover password/ reset password Identifier UC- 30 Reset password Purpose Requirements Development Risks Password reset in case he forgets his password WC_4764 When a user requests a password reset URL, the token contains the permission to reset the password. We ll need to handle this token with care, and make sure it expires within a time period so that even if the token gets SSAD_TRR_F18a_T02_V /02/2018

44 stolen, the user s account is still safe. Pre-conditions Post-conditions The user must be a registered user of the website The user wants to login to the website. The user forgets his password and wants to reset it. The user can find the password reset option on the page he is looking at The password is reset, and the user can successfully login to the website using his new credentials Table 68- Typical course of action: Recover password/ reset password 1 Go to Home page. 2 Click on Login button. 3 Click on Forgot Password link. 4 Sends an with a link to reset the password. 5 Click on the link to Reset Password 6 Ask for new password. 7 Provide new password and click on Save button. 8 Redirect user to login page. 9 Provide username and password. 10 Redirect to Home page if password is correct. Table 69- Alternative course of action: Recover password/ reset password failed because link is too old 1-5 Refer to typical course of action. 6 Display error message indicating that link is too old, and user needs to go to the SSAD_TRR_F18a_T02_V /02/2018

45 website and click on Forgot Password again. Table 70- Alternative course of action: Recover password/reset password failed because incorrect password 1-9 Refer to typical course of action. 10 Display error message indicating that username or password is incorrect. 6- Adjust notification(to be developed- beyond scope of semester) Table 71- Process description: Adjust notification Identifier UC- 31 Adjust notification Purpose Requirements Development Risks Pre-conditions Post-conditions He can adjust notification he gets about any update/change in his profile or a review posted WC_4689 None The user must be a registered user of the website The registered user has his own profile page The registered user has an ID linked to his account Any registered user has changed/ added (review, for ex.) something on the Service Provider profile page of the website notification settings changed Table 72- Typical course of action: Adjust notification 1 Follow the typical course of action: Login to log into the site. 2 Click on User Account button. 3 Query the user information from database. SSAD_TRR_F18a_T02_V /02/2018

46 4 Display user information in User Account page. 5 Click on Edit button. 6 Change the related to the user account and click on Save button. 7 Display message indicating update succeeded. Table 73- Alternative course of action: Adjust notification failed because of error in database 1-6 Refer to typical course of action. 7 Display error message indicating that update on database failed. NOTE- UC-32 is same as UC-11, having the same process description, typical course of action and alternative course of action, the only difference is that the actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided. NOTE- UC-33 is same as UC-1, having the same process description, typical course of action and alternative course of action, the only difference is that the actor using the functionality is different. Yet, even if the actor is different, the functionality is the same. Thus, a redundant table has not been provided. 7- Check for new notifications(to be developed- beyond scope of semester) Table 74- Process description: Check for new notifications Identifier UC- 34 Check for new notifications Purpose Requirements Development Risks The Service Provider can check if he has new comments or not by clicking on notification button to see its contents WC_4689 Real-time synchronization would burden system due to frequent communication SSAD_TRR_F18a_T02_V /02/2018

47 between server and client. Pre-conditions Post-conditions The user must be a registered user of the website The registered user has his own profile page Any registered user has changed/ added (review, for ex.) something on the Service Provider profile page of the website The notification option shows the pop up of having got a new change/notification Registered user is able to view any new notification Table 75- Typical course of action: Check for new notifications 1 Go to Home page. 2 Click on Bell button to see if there are notifications. 3 Query notifications from database and display the notification in a list. 8- Reply comments for reviews(to be developed- beyond scope of semester) Table 76- Process description: Reply comments for reviews Identifier UC- 35 Reply comments for reviews Purpose Requirements Development Risks Pre-conditions Service Provider can leave comments for the reviews he received WC_4635 Rapid growth of user amount may cause a sudden burst of reviews, and database may go down because of it; Inefficient query used in database may cause too much waiting time; The user must be a registered user of the website The registered user has his own profile page SSAD_TRR_F18a_T02_V /02/2018

48 Any registered user has changed/ added (review, for ex.) something on the Service Provider profile page of the website The service provider, whom the profile page belongs to, is able to see an option to reply to comments on the profile page of website Post-conditions The registered user replies to comments on the Profile page of the website Table 77- Typical course of action: Reply comments for reviews 1 Follow the typical course of action: Login to log into the site. 2 Follow the typical course of action: Read Review to go to the profile page of an specific service provider. 3 Select and specific review and click on Reply button. 4 Provide the reply and click on Save Comment 5 Save comment into database. Table 78- Alternative course of action: Reply comments for reviews failed because of error in database 1-4 Refer to typical course of action. 5 Display error message indicating that update on database failed Revise personal information Table 79- Process description: Revise personal information Identifier UC- 36 Revise personal information Purpose Requirements Can make changes to their profile Yet to be developed SSAD_TRR_F18a_T02_V /02/2018

49 Development Risks Pre-conditions Post-conditions Yet to be developed The user must be a registered user of the website The registered user has his own profile page Option to revise personal information is present on the Service Provider s profile page Personal information of the Service provider changed/ revised by him Table 80- Typical course of action: Revise personal information 1 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 2 Review personal information Add a profile Table 81- Process description: Add a profile Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 37 Add a profile Register for someone else- create account for a Service Provider to portray his profile in the website WC_4637 None The database is initialized The user accessing the website is a registered user The profile is added to the system Table 82- Typical course of action: Add a profile 1 Follow the typical course of action: View all service providers to go to the SSAD_TRR_F18a_T02_V /02/2018

50 list of service providers. 2 Click on the button Add Provider 3 Provide the information required to create a service provider. 4 Click on the button Create 5 Insert the profile in database. Table 83- Alternative course of action: Add profile failed because of error in database 1-4 Refer to typical course of action. 5 Display error message indicating that insert in database failed. 1- Claim an existing service provider s profile (to be developed- beyond scope of semester) Table 84- Process description: Claim an existing service provider s profile Identifier UC- 38 Claim an existing service provider s profile Purpose Requirements Development Risks Pre-conditions Post-conditions Claim already existing service provider s page as his or hers. Yet to be developed Yet to be developed An existing registered user has created a profile/ filled a referral form for another person who could be using the website The user claiming his profile becomes registered user of the website Another profile is added to the website Table 85- Typical course of action: Claim an existing service provider s profile 1 Follow the typical course of action: Login to log into the site. SSAD_TRR_F18a_T02_V /02/2018

51 2 Follow the typical course of action: View all service providers to go to the list of service providers. 3 Click on Claim button. 4 The service provider profile is added to the account of the logged user. NOTE- UC-39 implementation is beyond the scope of this semester and is not considered to be one of the core capabilities of the system for this semester. Thus, no design decision has been made for it so far. 2- Write a blog(to be developed- beyond scope of semester) Table 86- Process description: Write a blog Identifier Purpose Requirements Development Risks Pre-conditions UC- 40 Write a blog Write a blog on website WC_4680 Yet to be done The user accessing the website is the website administrator or any person acting under guidance of the administrator user is on the blog page of the website Post-conditions Content is added to the blog Table 87- Typical course of action: Write a blog 1 Follow the typical course of action: Login to log into the site. 2 Go to Home page 3 Click on Blogs button. 4 Click on Create Blog button. 5 Add content information. SSAD_TRR_F18a_T02_V /02/2018

52 6 Click on Create button. 7 Insert blog information into database. Table 88- Alternative course of action: Write blog failed because of error in database 1-6 Refer to typical course of action. 7 Display error message indicating that insert in database failed Verify User Table 89- Process description: Verify user Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 41 Verify user Authenticate a user on website WC_4650 none The user accessing the website is the website administrator or any person acting under guidance of the administrator The user is a verified person and there is a tick mark on his profile. Table 90- Typical course of action: Verify user 1 Follow the typical course of action: Login to log into the site as administrator. 2 Follow the typical course of action: View a service provider s profile to go to the profile page of an specific service provider. 3 Authenticate the profile. 4 Save authentication in database. SSAD_TRR_F18a_T02_V /02/2018

53 Table 91- Alternative course of action: Verify user failed because of error in database 1-3 Refer to typical course of action. 4 Display error message indicating that update of database failed. 4- View statistics(to be developed- beyond scope of semester) Table 92- Process description: View statistics Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 42 View statistics Collect website utilization statistics or view them WC_4652 The site needs to be careful what data it collects and at what frequency. If there s too much data, loading the statistics may take a while for it to show up. The user accessing the website is the website administrator or any person acting under guidance of the administrator User is able to see the statistics Table 93- Typical course of action: View statistics 1 Follow the typical course of action: Login to log into the site as administrator. 2 Go to Administration page. 3 Click on Statistics. 4 Process data, load statistics and display information in Statistics page. 5- Remove flagged/fake website users (to be developed- beyond scope of semester) SSAD_TRR_F18a_T02_V /02/2018

54 Table 94- Process description: Remove flagged/fake website users Identifier UC- 43 Remove flagged/fake website users Purpose Requirements Development Risks Pre-conditions Post-conditions The admin can remove flagged/fake website users Yet to be developed User data would have a lot of relation between other information, such as reviews, or discussions. If we remove a user data, we need to handle every other information related to the user data. The user accessing the website is the website administrator or any person acting under guidance of the administrator User can view service provider profile activity User can view blog/ discussion board pages Flagged/fake website users removed from the system Table 95- Typical course of action: Remove flagged/fake website users 1 Follow the typical course of action: Login to log into the site as administrator. 2 Follow the typical course of action: View a service provider s profile to go to the profile page of a specific service provider. 3 Flag the profile as fake. 4 Save fake flag in database. Table 96- Alternative course of action: Remove flagged/fake users failed because of error in database 1-3 Refer to typical course of action. SSAD_TRR_F18a_T02_V /02/2018

55 4 Display error message indicating that update of database failed. 6- Delete inappropriate user content(to be developed- beyond scope of semester) Table 97- Process description: Delete inappropriate user content Identifier UC- 44 Delete inappropriate user content Purpose Requirements Development Risks Pre-conditions Post-conditions The admin can delete inappropriate user content WC_4646 Yet to be developed The user accessing the website is the website administrator or any person acting under guidance of the administrator User can view service provider profile activity User can view blog/ discussion board pages Inappropriate user content removed from the website Table 98- Typical course of action: Delete inappropriate user content 1 Follow the typical course of action: Login to log into the site as administrator. 2 Remove inappropriate contents in profiles. Remove inappropriate contents in reviews. Remove inappropriate contents in discussions. 3 Remove inappropriate content from database. SSAD_TRR_F18a_T02_V /02/2018

56 Table 99- Alternative course of action: Delete inappropriate user content failed because of error in database 1-2 Refer to typical course of action. 3 Display error message indicating that update of database failed. 7- Enable/disable write button on review button Table 100- Process description:enable/disable write button on review button Identifier Purpose Requirements Development Risks Pre-conditions Post-conditions UC- 44 Enable/disable write button on review button Write review option is only available for registered users and unregistered user should not have access to it new_use_case similar to WC_4634 none The user accessing the website is the the registered user of the website and must be logged in to access this feature. disabled for unregistered user and enabled for registered user Table 101- Typical course of action: Enable/disable write button on review button 1 Follow the typical course of action: Login to log into the site as registered user. 2 click on pencil to add a review 3 form appears for registered user Table 102- Alternative course of action: for unregistered user 1-2 Refer to typical course of action. SSAD_TRR_F18a_T02_V /02/2018

57 3 pencil grayed out for unregistered user Modes of Operation The Real-estate investment and Review tool Website will only operate in one mode; therefore, no further information is required. 2.2 System Analysis Rationale The Real-estate investment and Review tool Website is an efficient way to search for and connect to any service provider, or for the investor to track investments using the investment tool. There are three levels of access given to the website. They are- 1. Unregistered Users- The Unregistered users can only browse through the website, search for a service provider they want or see the list of all available service providers. This user can also sign up to be a service provider or an investor, or both. Then he will be able to access all privileges of a registered user. 2. Registered Users- The Registered users enjoy the privileges of Unregistered users along with having their profile on the website, reviews on them, comments and rating, specific only to the registered users. They can also give rating/ leave reviews/ give comments to other service providers. There are many categories under Registered users, like Service Providers, investors, contractors, etc. a. The investors are the only registered users that have an inbuilt tracking tool in the website which lets them track their investments and save their costs for future reference. b. The Service Providers have the privileges of Registered Users, and moreover, a service provider can also be an investor. c. Other registered users also share the same characteristics of a Registered User. d. Administrator- All the above website users can view and search for service providers but what they are able to see depends on their level of access. SSAD_TRR_F18a_T02_V /02/2018

58 3. Technology-Independent Model This section has been intentionally omitted as our client has specified what technologies we should use for the proposed system. SSAD_TRR_F18a_T02_V /02/2018

59 4. Technology-Specific System Design 4.1 Design Overview System Structure Figure 6- Conceptual domain model SSAD_TRR_F18a_T02_V /02/2018

60 Fig- 7- Hardware Component Class diagram Figure 8- Software Component Class diagram SSAD_TRR_F18a_T02_V /02/2018

61 Table 103: Hardware Component Description Figure 9- Deployment Diagram Hardware Component Description Networked Device Any device that can connect to the website Computer Desktop computer or portable laptops Server that hosts the website Database which feeds the website SSAD_TRR_F18a_T02_V /02/2018