SYSTEM METHODOLOGY / APPROACH
3.1 Design Specification
3.1.2 Use Case Diagram
Figure 3.2 Use Case Diagram Use Case Description
Register Account
Use Case Name: Register Account
ID: 1 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to register account in the system
Brief Description: This use case describes the process of registering user of the system.
Trigger: User register as a user in the system Relationship:
Association: User
22
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
Include: - Extend: -
Generalization: -
Normal Flow of Events:
1. The system displays register button for user If the user wants to register an account,
the user needs to fill in the username, email address, and password.
2. The user presses Register button.
3. System validates user username, email and password.
4. System registers the user and redirects user to Home Page.
SubFlows: -
Alternate/Exceptional Flows:
3a. The input details invalid, user needs to fill up the form again.
Table 3.1 Use case description for Register Account Login Account
Use Case Name: Login Account
ID: 2 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to login to their account in the system
Brief Description: This use case describes the process of user login to their account in the system.
Trigger: User launches the application Relationship:
Association: User Include: -
Extend: Logout Account Generalization: -
Normal Flow of Events:
1. User inputs valid username and password 2. User presses Login button.
3. System validates user username and password.
23
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
4. The user login to the system and enter Manage Device Page.
SubFlows: -
1. User inputs invalid username and password.
2. User presses Login button.
3. System validates user username and password.
4. System displays error message to the user.
Table 3.2 Use case description for Login Account Logout Account
Use Case Name: Logout Account
ID: 3 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to logout their account in the system
Brief Description: This use case describes the process of user logout from the system.
Trigger: User presses Logout button Relationship:
Association: User Include: -
Extend: -
Generalization: -
Normal Flow of Events:
1. User presses Logout button.
2. The system will logout the user and redirects user to Login Page.
SubFlows: -
Alternate/Exceptional Flows: -
Table 3.3 Use case description for Logout Account
Select Room
Use Case Name: Select Room
ID: 4 Importance Level: High
Actor: User Use Case Type: Detail, Essential
24
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
Stakeholders and Interests:
User wants to select room in the system
Brief Description: This use case describes the process of user select room in the system.
Trigger: User successfully login to the system Relationship:
Association: User Include: -
Extend: -
Generalization: -
Normal Flow of Events:
1. User presses Login button.
2. User successfully connects to the system.
3. User allows to choose different rooms.
4. User can control the room’s fan and light after choosing the room.
5. System updates the database and redirect to Control Device Page.
SubFlows: -
Alternate/Exceptional Flows:
2a. User fail to login to the system.
2b. System redirects to Login Page.
Table 3.4 Use case description for Select Room
Manage Device
Use Case Name: Manage Device
ID: 5 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to manage home appliances in the system
Brief Description: This use case describes the process of user manage home appliances in the system.
Trigger: User successfully login to the system
25
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
Relationship:
Association: User Include: -
Extend: -
Generalization: -
Normal Flow of Events:
1. The system displays all the added devices.
2. Users choose devices to control.
SubFlows: -
Alternate/Exceptional Flows: -
Table 3.5 Use case description for Manage Device
Control Devices
Use Case Name: Control Devices
ID: 6 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to control device in the system
Brief Description: This use case describes the process of user control device in the system.
Trigger: User presses Control Devices button in the system Relationship:
Association: User Include: -
Extend: Voice command control, AR control Generalization: -
Normal Flow of Events:
1. User presses Control Devices button.
2. System prompt user to choose voice command control or AR control.
3. User selects their choices.
4. User controls device.
SubFlows: -
26
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
Alternate/Exceptional Flows:
2a. User denies controlling devices.
Table 3.6 Use case description for Control Device
Voice command control Use Case Name: Voice command control
ID: 7 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to control device using voice command in the system
Brief Description: This use case describes the process of user control device using voice control function in the system.
Trigger: User presses Voice Control button in the system Relationship:
Association: User Include: -
Extend: -
Generalization: -
Normal Flow of Events:
1. User presses Voice Control button.
2. System starts voice command control service.
3. User gives commands.
4. System recognizes the command and perform on/off function.
SubFlows: -
Alternate/Exceptional Flows:
3a. User does not give voice commands.
4a. The system fails to perform on/off function.
Table 3.7 Use case description for Voice Command Control
27
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
AR control
Use Case Name: AR Control Devices
ID: 8 Importance Level: High
Actor: User Use Case Type: Detail, Essential Stakeholders and Interests:
User wants to control device in the system using AR
Brief Description: This use case describes the process of user control device in the system using AR.
Trigger: User presses AR Control Devices button in the system Relationship:
Association: User Include: -
Extend: -
Generalization: -
Normal Flow of Events:
1. User presses AR Control Devices button.
2. System access user’s smartphone camera.
3. User points their smartphone to the home appliances.
4. User controls the device.
SubFlows: -
Alternate/Exceptional Flows:
2a. System unable to access user’s smartphone camera.
Table 3.8 Use case description for AR Control
28
Bachelor of Computer Science (Honours)
Faculty of Information and Communication Technology (Kampar Campus), UTAR
3.1.3 Activity Diagram