Microsoft Word - Thesis Hardcover - Kenrick Tjandrean

Comments

Transcription

Microsoft Word - Thesis Hardcover - Kenrick Tjandrean
CHAPTER 4
DESIGN OF THE PROPOSED SYSTEM
4.1
The Proposed Policy and Procedure
A policy is a designed rule and regulation used as guidance to reach a desired goal. A
procedure is a way to accomplish the policy [21]. The proposed policies for this system
are:
1. Only registered number can give command to household appliances via SMS.
2. User must login to the system by providing username and password before
controlling household appliances via iDevices, editing user profile and editing
system profile.
3. While changing the password, user need to enter new password twice and
providing old password for security purposed.
4. Before editing user profile, users have to provide password.
To achieve the proposed policy, certain procedure must be follow. Some procedures in
this system are:
1. Control appliances via SMS
• Send command (in a form of SMS messages) to the system.
• System verifies sender number.
• System validates the command.
• System makes changes on household appliance.
• Report the completion of the process.
30
31
2. Set profile via SMS
• Send command to set profile in a form of SMS messages to the system.
• System verifies sender number.
• System validates the profile.
• System set a profile.
• System makes changes on household appliance.
• Report the completion of the process.
3. Control appliances via iDevice
• User login to the system.
• In appliances tab, choose appliance to control.
• Choose action to be done to the selected appliance.
• System makes changes on household appliance.
• Report the completion of the process.
4. Set profile via iDevice
• User login to the system.
• In profile tab, choose profile to be activated.
• System set a profile.
• System makes changes on household appliances.
• Report completion of the process.
5. Edit profile via iDevice
• User login to the system.
• In profile tab, choose profile to be edited.
• Change preference setting of household appliances.
32
• Save preference setting
6. Delete profile via iDevice
• User login to the system.
• In profile tab, delete the profile.
• System will delete profile from database.
• Succeed report will be shown.
7. Add profile via iDevice
• User login to the system.
• In profile tab, choose add new profile.
• Fill the profile detail then submit.
• System will save new profile.
• Succeed report will be shown.
8. Delete reminder of appliances via iDevice
• User login to the system.
• In reminder tab, choose delete.
• System will delete reminder from database.
• Succeed report will be shown.
9. Add reminder of appliances via iDevice
• User login to the system.
• In reminder tab, choose add new reminder.
• Fill the reminder detail then submit.
• System will save new reminder.
• Succeed report will be shown.
33
10. Change password via iDevice
• User login to the system.
• In more tab, choose change password.
• Enter new password twice.
• Provide old password.
• Submit changes.
11. View edit profile via iDevice
• User login to the system.
• In more tab, choose edit profile.
• Edit profile.
• Provide password, then submit.
34
4.2
Data Flow Diagram
This section will discuss the flow of data from input given by user to the output
produced by the system. Here context diagram, detail DFD, and system flowchart is use
to explain how data processed in the system.
4.2.1
Context Diagram
Figure 13 - Context Diagram of the system
Figure 13 shows there are two actors outside a system that could interact with the
system. These two actors are iDevice application and mobile phone. Figure 13 also
shows all data inputted to the system and data outputted from the system. The list of
the data inputted to the system and data outputted from the system will shows at
table 1.
35
iDevice Application
Input
• Delete profile
Mobile Phone
•
• Edit profile
• New profile
Command to
control appliances
•
Set profile.
•
System alert
• Set profile
• Edit user profile
• View user profile
• Login detail
•
Command to
control appliances.
Output
• Appliances detail
• Completion report
notification
•
User profile
•
Completion report
•
System profile
•
Error report.
• Authentication
report
• System alert
notification.
Table 1 – List of Input and Output Data
36
4.2.2
Detail Data Flow Diagram
4.2.2.1
SMS Data Flow Diagram
Figure 14 - SMS DFD
Figure 14 show SMS detail data flow diagram. This diagram shows the breakdown of all process between mobile phone and
home automation server via SMS as well as the flow of data within the system. The communication used between mobile
37
phone and home automation server is using SMS technology. All SMS messages used to control the system will be parsed
before it will be processed further. The system will then verify the mobile phone number with phone number that has been
registered in the user database. After the verification process completed, the command (which is a body of the messages) will
be processed in the home automation server. After this command completely processed, home automation server will return
the completion report to mobile phone via SMS.
38
4.2.2.2
iDevice Data Flow Diagram
Figure 15 - iDevice DFD
Figure 15 iDevice data flow diagram. This diagram shows the breakdown of all
process between iDevice and home automation server as well as the flow of
data within the system. Here input command from iDevice will be send to
home automation server to be processed further there. Home automation server
39
will return the completion of the requested process and all information needed
by user to iDevice.
4.2.3
Flowchart
4.2.3.1
Control Appliances via SMS
Figure 16 - Control Appliances via SMS Flowchart
Figure 16 shows the flowchart for controlling appliances via SMS messages.
Firstly, SMS messages will be parsed then the sender phone number will be
verified. If the verification process is success, the command inside the bodies
of SMS will be processes in home automation server to control appliances. The
40
log of changes on appliances will be saved and the system will return success
report to user via SMS.
41
4.2.3.2
Control Appliances via iDevice
Figure 17 - Control Appliances via iDevice Flowchart
Figure 17 shows the flowchart for controlling appliances via iDevice. To control appliances via iDevice, user has to pass
validation check. The command given by user will be processed to make changes on appliances then the log of changes will
be saved. The system will then return completion report to user after all process successfully processed.
42
4.2.3.3
Set Profile via SMS
Figure 18 - Set Profile via SMS Flowchart
Figure 18 shows the flowchart for setting profile via SMS messages. Firstly, SMS messages will be parsed then the sender
phone number will be verified. If the verification process is success, the command inside the bodies of SMS will be processes
43
in home automation server to change system profile and setting the appliances as stated in profile. The log of changes on
appliances will be saved and the system will return success report to user via SMS.
44
4.2.3.4
Set Profile via iDevice
Figure 19 - Set Profile via iDevice Flowchart
45
Figure 19 show the flowchart for setting flowchart via iDevice. To set profile via iDevice, user has to pass validation check.
User request to activate profile that has been registered then the system will automatically make changes on appliances as
stated in profile then the log of changes will be saved. The system will then return completion report to user after all process
successfully processed.
46
4.2.3.5
View Profile via iDevice
Figure 20 - View Profile via iDevice Flowchart
Figure 20 shows the flowchart for viewing profile from iDevice. To view
profile via iDevice, user has to pass validation check. After passing validation
check, user can request to view profile by going to profile tab in iDevice. The
system will automatically request profile detail from profile database then
show the list of profile and its detail to user.
47
4.2.3.6
Delete Profile via iDevice
Figure 21- Delete Profile via iDevice
Figure 21 shows the flowchart for deleting profile from iDevice. To delete
profile via iDevice, user has to pass validation check. After passing validation
check, user can delete the profile that will not be use anymore by specifying
profile to be deleted. The system will automatically delete specified profile
from profile database then showing completion report.
48
4.2.3.7
Add New Profile via iDevice
Figure 22 – Add New Profile via iDevice
Figure 22 show the flowchart for adding new profile via iDevice. To add new
profile via iDevice, user has to pass validation check. After passing validation
check, user is able to add new profile by going to profile tab then choose add
new profile. The system will reply with new profile form in which user has to
fill the form. After submitting the form, the system will add new profile to
49
profile database as attribute filled before. After successfully adding new
profile, the system will return the completion report to user.
4.2.3.8
Update Profile via iDevice
Figure 23 – Update Profile via iDevice
Figure 23 shows the flowchart for updating profile via iDevice. To update
profile via iDevice, user has to pass validation check. After passing validation
50
check, user is able to update profile by going to profile tab then choose profile
to update. The system will reply with profile update form in which user have to
fill it. After submitting the form, the system will update the profile in profile
database as attribute filled before. After successfully updating the profile, the
system will return the completion report to user.
51
4.2.3.9
View User Profile via iDevice
Figure 24 – View User Profile via iDevice
Figure 24 shows the flowchart for viewing user profile via iDevice. To view
user profile via iDevice, users have to pass validation check. After passing
validation check, user is able to request to view user profile by going to more
tabs then choosing user profile. The system will automatically request user
detail from user database then show the user profile to the user.
52
4.2.3.10
Update User Profile via iDevice
Figure 25 - Update User Profile via iDevice
Figure 25 shows the flowchart for updating user profile via iDevice. To update
user profile via iDevice, user has to pass validation check. After passing
validation check, user is able to update user profile by going to view user
profile then choose update. The system will reply with user profile update form
in which user have to fill it. After submitting the form, the system will update
53
the user profile in user database as attribute filled before. After successfully
updating the profile, the system will return the completion report to user.
4.2.3.11
SMS Alert
Figure 26 - SMS Alert
Figure 26 shows the flowchart of SMS alert. The trigger of this process to be
activated is when the system needs to alert the user about their appliances.
Here, the alert will be sent via SMS to the user phone number as in user
database.
54
4.2.3.12
Delete Reminder via iDevice
Figure 27 - Delete Reminder via iDevice
Figure 27 shows the flowchart for deleting reminder from iDevice. To delete
reminder via iDevice, user has to pass validation check. After passing
validation check, user can delete the reminder that will not be use anymore by
specifying reminder to be deleted. The system will automatically delete
specified reminder from reminder database then showing completion report.
55
4.2.3.13
Add New Reminder via iDevice
Figure 28 – Add New Reminder via iDevice
Figure 28 show the flowchart for adding new reminder via iDevice. To add
new reminder via iDevice, user has to pass validation check. After passing
validation check, user is able to add new reminder by going to reminder tab
then choose add new reminder. The system will reply with new reminder form
56
in which user has to fill the form. After submitting the form, the system will
add new reminder to reminder database and report the result to the user.
57
4.3
Sequence Diagram
4.3.1
Control Appliances via SMS
Figure 29 - Control Appliances via SMS
Figure 29 shows the sequences of steps for controlling household appliances via
SMS. Mobile phone is use for sending SMS to SMS Gateway in order to enable user
controlling their household appliances. SMS that reach SMS Gateway will be parsed
so it can be processed farther. After successfully parse the messages the sender
number will be verified. If the messages pass verification check the system will
redirect the command to the home automation server via web server to be processed
there. In home automation server, the system will make changes on appliance as the
58
command given by user then the log will be saved. The system will return
completion report to user after all process done.
4.3.2
Control Appliances via iDevice
Figure 30 - Control Appliances via iDevice
Figure 30 shows the sequences of steps for controlling household appliances via
iDevice. Firstly, user request changes on appliances from iDevice by selecting the
appliances to controlled and select command to be done by the appliance. iDevice
will pass the request to web server. Then web server will ask home automation
server to make changes on appliance as requested earlier. In home automation server,
59
system will make a change on appliance as requested and save a log of this action.
The system will return completion report to the user when all process is done.
4.3.3
Set Profile via SMS
Figure 31 - Set Profile via SMS
Figure 31 shows the sequences of steps for setting profile via SMS. Mobile phone is
use for sending SMS to SMS Gateway in order to enable user for setting profile from
their mobile phone. SMS that reach SMS Gateway will be parsed so it can be
processed farther. After successfully parse the messages the sender number will be
verified. If the messages pass verification check the system will redirect the
command to the home automation server via web server to be processed there. In
home automation server, the system will change the profile as requested earlier and
60
make changes on appliances as stated in profile and save the log. The system will
return a completion report to user after all process done.
4.3.4
Set Profile via iDevice
Figure 32 - Set Profile via iDevice
Figure 32 shows the sequences of steps for setting profile via iDevice. Firstly, user
request to change profile from iDevice going to profile menu and activate one profile
from the list provided there. iDevice will pass the request to web server. Then web
server will ask home automation server to change the profile as requested earlier. In
home automation server, system will change the profile and make changes on
appliances stated in the profile and save the log. The system will return completion
report to the user when all process is done.
61
4.3.5
Login on iDevice
Figure 33 - Login on iDevice
Figure 33 shows the sequences of action while login from iDevice. After running
iDevice application, login form will automatically display. User need to enter
username and password to be able to continue to next phase of the application. The
username and password provided by user will send to web server for further process.
Web server will request home automation server to validate the username and
password provided earlier. The server return validation result to web server. If the
user passes the validation check, iDevice will grant access for user to access some
features that can only be accessed by registered user.
62
4.3.6
Add New Profile via iDevice
Figure 34 - Add New Profile via iDevice
Figure 34 shows the sequences of steps for adding new profile via iDevice. When the
user request to add new profile, the system will return add profile form. New profile
detail will be sent to web server to be processed further. Web server will request
home automation server to add new profile to the profile database. If new profile
successfully added to the database, the system will display success messages to user.
63
4.3.7
View Profile via iDevice
Figure 35 - View Profile via iDevice
Figure 35 shows the sequences of steps for viewing profile via iDevice. User can see
a list of profile by going to profile tab in iDevice application. This request will be
redirected to home automation server via web server. Home automation server will
return a list of profile to iDevice. iDevice will processed this information and show it
to user.
64
4.3.8
Update Profile via iDevice
Figure 36 - Update Profile via iDevice
Figure 36 shows the sequences of steps for updating profile via iDevice. When the
user request to update profile, the system will return update profile form. Updated
profile detail will be sent to web server to be processed further. Web server will
request home automation server to update the profile. If profile is successfully
updated to the database, the system will display success messages to user.
65
4.3.9
Delete Profile via iDevice
Figure 37 - Delete Profile via iDevice
Figure 37 shows the sequences of steps for deleting profile via iDevice. User
specifies profile to be deleted. The detail of profile user willing to delete will be sent
to web server to be processed further. Web server will request home automation
server to delete the specified profile earlier. If profile is successfully deleted, the
system will display success messages to user.
66
4.3.10 View User Profile via iDevice
Figure 38 - View User Profile via iDevice
Figure 38 shows the sequences of steps for viewing user profile via iDevice. User
can see their user profile by going to more tab and see user profile. Automatically
iDevice will ask web server to get detail user profile by providing the username.
Web request the detail user profile by passing the username to home automation
server. Home automation server will return user profile to iDevice. iDevice will
processed this information and show it to user.
67
4.3.11 Update User Profile via iDevice
Figure 39 - Update User Profile via iDevice
Figure 39 shows the sequences of steps for updating user profile via iDevice. When
the user request to update user profile, the system will return update user profile
form. Updated user profile detail will be sent to web server to be processed. Web
server will request home automation server to update the user profile in user
database. If user profile is successfully updated to the database, the system will
display success messages to user.
68
4.4
Entity Relational Diagram (ERD)
Figure 40 – ERD
Figure 40 shows the database relation in this system. The diagram show how each table
interact with each other and its cardinality relations. The cardinality relations of the table
said that:
• One user can have zero to many profile.
• One appliance can have zero to many reminder.
• One appliance have exactly two command
• One user can have zero to many appliances.
• One profile has many appliances.
• One appliance can have zero to many log.

Similar documents