HOME APPLIANCE CONTROL SYSTEM

0240 –Use Case Document

Version 1.0

Author:
Major Revision Date:
Version: 0.1
 Table of Contents

Table of Contents.....................................................................................................................................................2
Document Version Control...................................................................................................................................5
Privacy Information..............................................................................................................................................5
Document Revision History.....................................................................................................................................5
Status........................................................................................................................................................................ 5
Approved By............................................................................................................................................................5
Use Case Brief..........................................................................................................................................................6
1.0 Use Case Model............................................................................................................................................6
1.1 Use Case List..........................................................................................................................................6
1.2 Actor List................................................................................................................................................7
1.3 Use Case Relation Diagram....................................................................................................................8
1.4 Use Case Glossary...................................................................................................................................9
2.0 Use Cases...................................................................................................................................................10
2.1 Place Request........................................................................................................................................10
2.2.3 Alternate Scenarios...........................................................................................................................12
2.2.4 Exception Scenarios..........................................................................................................................12
2.2.5 Business Rules\Constraints....................................................................................................................13
1. Introduction....................................................................................................................................................15
2. Purpose...........................................................................................................................................................16
3. Business Components.....................................................................................................................................16
4. System Component.........................................................................................................................................16
5. Object List......................................................................................................................................................17
6. Description of the Classes:.............................................................................................................................18
7. Class Diagram................................................................................................................................................20
8. Sequence Diagram for Lights.........................................................................................................................21
9. Collaboration Diagram for Lights...................................................................................................................23
10. Sequence Diagram for AC..........................................................................................................................24
11. Collaboration Diagram for AC...................................................................................................................25
12. Sequence Diagram for Microwave.............................................................................................................26
13. Collaboration Diagram for Microwave.......................................................................................................27
14. Sequence Diagram for Security System......................................................................................................28
15. Collaboration Diagram for Security System...............................................................................................29
16. State Chart Diagram...................................................................................................................................30
17. State Chart Diagram for Light System........................................................................................................31
18. State chart Diagram for AC........................................................................................................................32
19. State chart Diagram for Microwave............................................................................................................33
20. State Chart Diagram for Security System...................................................................................................34
21. Package Diagram........................................................................................................................................35
22. Component Diagram...................................................................................................................................36
23. Deployment Diagram.................................................................................................................................37
Document Version Control
It is the reader's responsibility to ensure they have the latest version of this document. Questions should be directed to the
preparer of this document above, or the project manager.

Privacy Information
This document may contain information of a sensitive nature. This information should not be given to persons other than
those who are involved in the project or who will become involved during the lifecycle.

Document Revision History

Revised By Revised Version CR # Comments
Date

Status
Status  Open  In Process  Ready for  Pending  Approved
Review Approval

Approved By
Department Name Date Comments
Product Management
Release
Development
 Use Case Brief
Home appliance control system (HACS) is a system which allows us to control, monitor and coordinate
home appliances such as air conditioner, microwave oven, lights and security system through a remote
device (such as Cell Phone, Laptop or Palmtop). Hence, with a HACS, we can operate our home
appliances according to our convenience from our school, work, and car or from any place where our
remote input device is functional.

In order to control a device the user needs to connect its input device to the Service Provider who is
responsible for implementing the requested operation by sending a required command to the HACS
Interaction Device. For this, the User enters the User id and PIN for authentication and then device id
and operation to be performed given. The HACS Interaction Device interacts directly with the device
controller and controls the device. Every device is assigned an id along with the operations that can be
implemented on them.

1.0 Use Case Model

1.1 Use Case List
Name Description
2.1 Place Request The use case describes the ability of the user to place request for a specific
operation to be implemented on a particular appliance. The user sends its ID
followed by its Personal Identification Number (PIN) along with the device
ID & the operation to be implemented.
2.2 Send request to HACS Interaction The use case describes the ability of the user to the interaction between the
Device Service Provider & the HACS Interaction Device, where the service
provider sends the command required to implement the requested operation.

2.3 Operate A.C
2.4 Operate Lights
2.5 Operate Microwave
2.6 Operate Security System
The use case describes the ability of the user to perform the requested
operation on the A.C. This operation could be Switching ON/OFF or
changing the temperature settings.
The use case describes the ability of the user to set the state of the specified
lights as requested. For example if the state of light-1 is OFF & its requested
state is ON, it will be switched ON. If the requested state is OFF the state
will remain unchanged.
The use case describes the ability of the user to enable the HACS interaction
device to set the mode, time & duration of microwave according to the
request placed. It might result in an error message if there is nothing placed
inside the microwave.
The use case describes the ability of the user to send the command to the
security system, which sets its state & level. The state can be ON or OFF.
The level can be 1,2,3,4 depending on the stringency of the security
required.
1.2 Actor List
Use Case List

Actor Description or Role

User A ‘User’ is a person to place request for a specific operation to be implemented on a
particular appliance.
Service Provider A type of ‘User’ interacts with the HACS Interaction Device to control the device.
Maintenance Agency A type of ‘User’ interacts with the HACS user for trouble shooting.
Interaction Device The HACS Interaction device received the instruction from service provider and sends the
command required implementing the requested operation.
A.C Implement the requested operation on the A.C.
Lights Set the state of the specified lights as requested.
Microwave Set the mode, time & duration of microwave according to the request.
Security System Send the command to the security system, which sets its state & level. The state can be ON or
OFF.
1.3 Use Case Relation Diagram

User places request for device

operation to service provider.

User-x

Places Request

Service Provider

Security System

Maintanence
Agency

Operate Security System

Trouble Shoot

Lights
Operate Lights

Service Provider Send request to HACS Interaction Interaction

Device Device

The service Provider interacts Operate Microwave

with the HACS Interaction
Device to control the device. Microwave

Operate AC
STORE REQUEST
Various devices are connected to HACS
Interaction Device and receives the
instructions to be implemented.

AC

DATA BASE
1.4 Use Case Glossary
Term Definition
Home appliances Home application are such as air conditioner, microwave
oven, lights and security system
Service Provider Service Provider who is responsible for implementing
the requested operation by sending a required command
to the HACS Interaction Device. For this, the User
enters the User id and PIN for authentication and then
device
SUD System under design. It is the computer program under
design.
Use case Records behavioral requirements for the SUD. It is a
contract for the behavior of the SUD.

Captures a contract between the stakeholders of a system

about its behavior.

Describes the system’s behavior under various

conditions as the system responds to a request from one
of the stakeholders, called the primary actor.

Primary actor initiates an interaction with the system to

accomplish some goal.

System responds, protecting the interests of all the

stakeholders. Gathers different sequences of behavior,
or scenarios, together
Stakeholders Someone or something with a vested interest in the
behavior of the SUD. For example, people who use the
program, the company that owns the program,
government regulatory agencies, and other computer
programs or devices
Primary actor The stakeholder who or which initiates an interaction
with the SUD to achieve a goal.
Scope What is really the system under design? Identifies the
system that is being discussed. For example, the Pfx.Net
suite is the system being discussed.
Preconditions and guarantees What must be true before and after the use case runs.

Main success scenario A case in which nothing goes wrong

Alternate courses An alternate course to any main success scenario step.

Failure conditions Failure of any step of the main success scenario.

Extensions What can happen differently during the main scenario?
Documents special case processing for the main
scenario. They represent unusual business processing.

Summary-level goal Involves multiple user goals. They show the context in
which the user goals operate. They show life-cycle
sequencing of related goals. They provide a table of
contents for the lower-level use cases.
User-level goal Goal that is of the greatest interest. It is the goal the
primary actor has in trying to get work done or the one
the user has in using the system.
Sub function-level goal Goals that is required to carry out user goals. Include
them only as you have to – they are needed on occasion
for readability or because many other goals use them.
For example, Find and Save, As are sub function-level
goals.
2.0 Use Cases
2.1 Place Request
Description The use case describes the ability of the user to place request for a specific operation to be
implemented on a particular appliance i.e. (A.C, Lights, Microwave, Security System).
Level User goal
Primary Actor(s) 1. User
2. Service Provider
Secondary Actor(s)
Precondition(s) 1. User devices (such as Cell Phone, Laptop or Palmtop) is access to service provider
trough any methods
i. Pont to point,
ii. Dial-up
iii. Internet cloud
iv. Wireless
v. Fixed IP etc.

2. The user has the valid ID, PIN along with the device ID & the operation code to be
implemented.
Minimal Guarantee System sends an error message when the requested task cannot be performed.
Success Guarantee Display message to the user that the requested task successfully performed.
Trigger User places a request for a specific operation.
Frequency On demand
Reference
2.1.1 Activity Diagram
2.1.2 Main Success Scenario

Action
1. The user accesses the service provider
through a remote device (such as Cell Phone,
Laptop or Palmtop).
2. The user specifies the Login ID, PIN and
then user submits the details. <A1>
<A2><A3>
3. The user specifies the device id and operation
to be performed (On / Off / Other control
parameter).
4. The user submits request to service provider
Response
The service provider system displays login screen to the user.
The system validates the information entered by the user if user
is valid user of HAC System then system gives access to the
user and displays the list of user home appliance control
devices.
1. The service provider forward the request to the HACS
Interaction Device

2. The service provider received feedback from the HACS

interaction device.
5. The user received message command has
been successfully executed.

2.2.3 Alternate Scenarios

A1. The user doesn’t enter the Login ID or PIN and submit the details
Action Response Next
Action
The user does not enter any value in the Login ID The system informs the user that Login ID and 2
or PIN field and submit the details. PIN is mandatory and must be entered.

A2. The user enters the wrong Login ID or PIN and submits the details
Action Response Next
Action
The user provides wrong Login ID or PIN and The system informs the user that Login ID and 2
submits PIN is not valid ID or PIN

A3. The user enters Special Characters in Login ID

Action Response Next
Action
The user enters Special Characters in the Login ID The system informs the user that Special 2
field and submits the details. Characters cannot be entered.

2.2.4 Exception Scenarios

E1. The user selects the option to cancel the place request option
Action Response Next
Action
The user selects the option to cancel the place The system exits from the place request option The user
request option exits the
use case
E2. The user submitted request does not execute.
Action Response Next
Action
The user submits the request to service provider. The system generates error report and notifies to The user
the user. exits the
use case
2.2.5 Business Rules\Constraints
B1 The Subcategory Login ID is a mandatory field
Rule\Constraint Description
The Login ID is a mandatory field that must be E.g. Login ID like Jhon-Pam-Kelly-12345.
entered by the user to place request.

B2. The user can enter a maximum of 25 Characters in the Login (ID), PIN
Rule\Constraint Description
The number of Characters in the login ID would E.g. Jhon-Pam-Kelly-12345.
be limited to twenty-five Characters only.

B3. The PIN can have Alphanumeric and Special Characters

Rule\Constraint Description
Alphanumeric and Special Characters can be E.g. #, $, %, &,
entered in PIN
Non-alphabetic or non-numeric character, such as
@, #, $, %, &, * and + and also all the Characters
that are either alphabetic or numeric, that is, all
letters from A to Z and all numbers from 0 to 9
can be entered in the PIN.
HOME APPLIANCE CONTROL SYSTEM

0250 – System Design Document

Version 1.0
1. Introduction
System Design Document must contain both – the Functional Specification and Class Description. This document describes
the behavior of HAC System as seen by an external observer, and contains the technical information and data needed for the
design. This document defines what the functionality will be, and how that functionality will be implemented.

SyDD depicts the Components – Business and System – for describing the system design. The Components described here
would be further sub divided into the Classes and for each of the Classes identified; all Methods and Attributes associated
with the Classes would be listed. The Methods relate to the “functions” and Attributes relate to the “database” part of design
considerations of the Classes respectively.

User Requirements
|
Use case document
|
High Level System Design: Functional Specification & Class Description
|
Detailed Design
|
Coding

 Specifically, the functional specification translates the User and System Requirements into a technical description that:
 Ensures that the system feature requirements are correctly understood before moving into the next step, the software
design or the detailed design process.
 Clearly and unambiguously provides all the information necessary to design the software at the higher level.
 Classes identified; all Methods and Attributes associated with the Classes would be listed.
2. Purpose
The purpose of this document divided design into two parts Functional Specification and Class Description. Here SyDD
describes the Functional Specifications of HAC System, and the Classes of HAC System.

3. Business Components
The following summarizes the module specific business components.
Sr. No. Name Description

1 CompUsrPlaceReq Provide the functionality to place request for a specific

operation to be implemented on a particular appliance.
2 CompSerProvider Provide the functionality to keep the information of
service provider.
3 CompSendReqDevice Provide the functionality to the interaction between the
Service Provider & the HACS Interaction Device
4 CompOpeAC Provide the functionality to perform the requested
operation on the A.C
5 CompOpeLights Provide the functionality to set the state of the specified
lights as requested
6 CompOpeSecSys Provide the functionality to send the command to the
security system.
7 CompMicroCont This component interacts with HACS interaction device.

4. System Component
Sr No. Name Description

1 CompUserManagement This component manages details of users groups, users and

privileges. It would facilitate to associate users with user
group and allow to assign access privileges to users / user
groups.
2 CompSecurity This component manages security credential of the system.
It would ensure that only eligible user can access the system.
3 CompArchive This component allows archiving historical data,
periodically.
4 CompBackup This component allows user to take backup on
daily/periodically/user-defined time basis.
5 CompRestore This component would allow to restore the backed up /
archived data.
Sr No. Name
6 CompAuditTrail
7 CompErrorHandling
8 CompQueryBuilder
9 CompOnlineHelp
10 CompLookupMaintenance
Description
This component would track all the sensitive activities
performed by the user.
This component would handle errors and keep log of the
errors.
This component would facilitate to prepare user-defined
query to fetch required data from the database and display
the resultant data.
This component would facilitate to provide on line help to
the user.
This component would maintain details of lookup for state,
country, city and such other entities
5. Object List

Sr. Object Y/N Remark

1. Users Y Object
2. User ID
3. PIN
4. Service Provider Y Object
5 Service ID
6 PIN
7 Services
8. HACS Interaction device Y Object
9. Device ID
10. Command
11. Microwave controller Y Object
12. Microwave Controller ID
13. Mode
14. Time
15. Device
16. Ac Controller Y Object
17. AC Controller ID
18. Temp
19. Status
20. Light Controller Y Object
21. AC Controller ID
22. Name
23. Status
24. Security System Controller Y Object
25. AC Controller ID
26. Status
27. Mode
28. Place Request (Database) Y Object
29. Device ID
30. User ID
31. Last Access
32. Date
33. Time
34. Action
6. Description of the Classes:

ClsUser -The class holds the information of various users. This information refers to their UserID, name & address
associated to each other.
Sr. No. Class Name Class Attributes Methods Functional details
1 User UserId requestaccess Places a request with the service provider for the
Name access to HACS
Address
sendcommand Pass on the requested command along with the
user & PIN to the service provider

ClsUser-X - This is a sub class of USERS & inherits the properties of the class USERS. This class holds the
information of a particular user, named ‘X’.
Sr. No. Class Name Class Attributes Methods Functional details
2 User-X UserId opname() It is used to send the details of operation to be
performed.

ClsServiceProvider – The class holds the details of users associated with their unique PIN along with the services they
can access.
Sr. No. Class Name Class Attributes Methods Functional details
3 ClsServiceProvider ProviderID acceptreq() These function used to process the request it
Pin receives for the access of a particular HACS
Services

reqPIN
acceptcmnd
reporterror().
acceptreq() This function used to process the request it
receives for the access of a particular HACS
reqPIN() This function sends a request to the user for the
PIN
acceptcmnd This function processes the request for an
operation sent by the user & forwards it to the
HACS Interaction Device.

reporterror() This function sends a message to the user that the

requested task cannot be performed

ClsHacsIntrDevice The class holds the IDs for various appliances & the command that can be processed for a particular
device.
Sr. No. Class Name Class Attributes Methods Functional details
4 ClsHacsIntrDevice Device ID checkstatus() Send a request for the status of a device
Command

acceptstatus() Accept the status sent by an appliance

sendcmd() Forward a request for a command to be
implemented.
informerr() Send a message to the service provider reporting
an error if the status checks tells it so.
ClsMicrowaveController The class holds the information about the microwave such as the device ID, the time at
which to start, the duration & the mode in which to operate.
Sr. No. Class Name Class Attributes Methods Functional details
5 ClsMicrowa Micro ID setmode(), These functions used the mode, time & duration
veController Mode for the microwave to operate. Another function
Time
Device

settime(),
setduration()
returnstatus() This function sends a message to the HACS
interaction device about its status

ClsAcController The class holds the ID of a particular AC along with the mode & temperature
Sr. No. Class Name Class Attributes Methods Functional details
6 ClsAcController ID swON(), These function used to switch it ON, switch it
Temperature OFF & to change the temperature settings
Status respectively

swOFF(),
settepm()
returnstatus() This function sends a message to the HACS
interaction device about its status.

ClsLightController The class holds the information of various lights at the house
Sr. No. Class Name Class Attributes Methods Functional details
7 ClsLights ID switchON The functions it performs are switchON,
Controller Name switchOFF & returnstatus().
Status

switchOFF
returnstatus().

ClsSecSysController The class holds the device ID of the security system along with its status & mode.
Sr. No. Class Name Class Attributes Methods Functional details
8 ClsSecSysController ID setlevel() The functions are used to set the level of
Status stringency, switching ON & switching OFF the
Mode security system.

swON
swOFF
7. Class Diagram
8. Sequence Diagram for Lights
Sequence diagrams are closely related to Communication diagrams and show the sequence of messages passed between
objects using a vertical timeline

USER Service HACS Interaction Database Lights Lights Maintenence

Provider Device Controller Agency

Request access to the HACS

Requests for PIN & the device ID with the required operation

Enter the PIN with the ID of Lights & their required state.

Wrong PIN: User not identified

PIN Verified: Sends the instruction for the required operation.

Add Request

The user request access to HACS.

The service provider asks for PIN and
Device ID. The user enters the Check the status of Lights
Information. Then service Provider
interacts with the Interaction device,
which checks the status of lights
Return Status
and switches it according to the
request.

Switches the lights according to the request

Switches the required lights according to the request.

Send Message: (FAILURE/SUCCESS)

Update Request

Send Message:(SUCCESS/FAILURE)

[FAILURE] Send request to repair device.

9. Collaboration Diagram for Lights
A communication diagram, formerly called a collaboration diagram, is an interaction diagram that shows similar information to
sequence diagrams but its primary focus in on object relationships.

1: Request access to the HACS

3: Enter the PIN with the ID of Lights & their required state. Service14: [FAILURE] Send request to repair device.
Provider
USER
Maintenence
2: Requests for PIN & the device ID with the required operation Agency
4: Wrong PIN: User not identified

13: Send Message:(SUCCESS/FAILURE)

5: PIN Verified: Sends the instruction for the required operation.

HACS Interaction Device

Lights
8: Return Status
11: Send Message: (FAILURE/SUCCESS)

6: Add Request
10: Switches the required lights according to the request. 12: Update Request

7: Check the status of Lights

Lights 9: Switches the lights according to the request
Controller

Database

The user request access to HACS.

The service provider asks for PIN and
Device ID. The user enters the
Information. Then service Provider
interacts with the Interaction device,
which checks the status of lights
and switches it according to the
request.
10. Sequence Diagram for AC

USER Service HACS Interaction Data Base A.C. Controller A.C. Maintenence
Provider Device Agency

Request access to the HACS

Requests for PIN & the device ID with the required operation

Enter the PIN with the ID of A.C.& the temprature

Wrong PIN: User not identified

PIN Verified: Sends the instruction for the required operation.

Add Request

The user request access to HACS.

The service provider asks for PIN and
Device ID. The user enters the Checks the status of A.C.
Information. Then service Provider
interacts with the Interaction device,
which checks the status of AC and
set the Temperature and starts AC. Return Status

Sets the Status and thermostat according to the request

Starts the A.C. accordingly.

Sends Message: (SUCCESS/FAILURE)

Update Request

Send Message: (SUCCESS/FAILURE)

[FAILURE] Send Request to Repair device

11. Collaboration Diagram for AC

1: Request access to the HACS

3: Enter the PIN with the ID of A.C.& the temprature Service
Provider
14: [FAILURE] Send Request to Repair device
USER
2: Requests for PIN & the device ID with the required operation
4: Wrong PIN: User not identified

Maintenence
Agency
13: Send Message: (SUCCESS/FAILURE)
5: PIN Verified: Sends the instruction for the required operation.

A.C.

HACS Interaction Device

8: Return Status
11: Sends Message: (SUCCESS/FAILURE)
10: Starts the A.C. accordingly. 6: Add Request
12: Update Request

7: Checks the status of A.C.

9: Sets the Status and thermostat according to the req...
The user request access to HACS. A.C.
The service provider asks for PIN and Controller
Device ID. The user enters the Data Base
Information. Then service Provider
interacts with the Interaction device,
which checks the status of AC and
set the Temperature and starts AC.
12. Sequence Diagram for Microwave

USER Service HACS Interaction Data_Base Microwave Microwave Maintenence

Provider Device Controller Agency

Request access to the HACS

Requests for PIN & the device ID with the required operation

Enter the PIN with the ID of Microwave with the required mode, duration & time.

Wrong PIN: User not identified

PIN Verfied: Sends the instruction for the required operation.

Add Request

Checks if the Microwave is empty.

[YES], sends the ERROR message.

Informs the user about the ERROR.

[NO], sets the timer & mode according to the request.

Starts the Microwave at the desired time with the given duration & mode.
The user request access to HACS. The service
provider asks for PIN and Device ID. The user
enters the Information. Then service Provider Send Message (SUCCESS/FAILURE)
interacts with the Interaction device, which
checks if or not microwave is empty. If not it
sets the timer and mode and starts it. If empty
it returns a error. Update Request

Send Message (SUCCESS/FAILURE)

Request for repir of the device

13. Collaboration Diagram for Microwave

1: Request access to the HACS

3: Enter the PIN with the ID of Microwave with the required mode, duration & time.
15: Request for repir of the device
USER Service
Provider Maintenence
Agency
2: Requests for PIN & the device ID with the required operation
4: Wrong PIN: User not identified
9: Informs the user about the ERROR.

8: [YES], sends the ERROR message.

14: Send Message (SUCCESS/FAILURE)
5: PIN Verfied: Sends the instruction for the required operation.
Microwave

HACS Interaction Device

6: Add Request
13: Update Request

11: Starts the Microwave at the desired time with the given duration & mode.
Data_Bas
12: Send Message (SUCCESS/FAILURE) e

7: Checks if the Microwave is empty.

The user request access to HACS. The service 10: [NO], sets the timer & mode according to the requ...
provider asks for PIN and Device ID. The user
enters the Information. Then service Provider
interacts with the Interaction device, which
checks if or not microwave is empty. If not it
Microwave
sets the timer and mode and starts it. If empty
Controller
it returns a error.
14. Sequence Diagram for Security System

USER Service HACS Interaction Data_Base Security System Security Police Dept
Provider Device Controller System.

Request access to the HACS

Requests for PIN & the device ID with the required operation

Enter the PIN with the ID of Security System & the state required.

Wrong PIN: User not identified

PIN Verified: Sends the instruction for the required operation.

Add Request

The user request access to HACS. Checks the status of the system.
The service provider asks for PIN
and Device ID. The user enters the
Information. Then service Provider
interacts with the Interaction device,
which checks the status of Security Return status
System and sets its state according
to the request.

Sets the state according to the request

Sets the required state of the system.

[BREAK ENTRY] Inform Police

15. Collaboration Diagram for Security System

1: Request access to the HACS

3: Enter the PIN with the ID of Security System & the state required.
Service
USER Provider
2: Requests for PIN & the device ID with the required operation
4: Wrong PIN: User not identified

5: PIN Verified: Sends the instruction for the required operation.

11: [BREAK ENTRY] Inform Police

Security
System. Police
Dept

8: Return status HACS Interaction Device

10: Sets the required state of the system.

Security System 7: Checks the status of the system.

Controller 9: Sets the state according to the request
6: Add Request

The user request access to HACS.

The service provider asks for PIN
and Device ID. The user enters the
Information. Then service Provider Data_Bas
interacts with the Interaction device, e
which checks the status of Security
System and sets its state according
to the request.
16. State Chart Diagram
A State Machine Diagram models the behavior of a single object, specifying the sequence of events that an object goes through
during its lifetime in response to events.

Unsuccessful Ready State

CELL PHONE(INPUT Dial Service Provider Connecting

DEVICE) Idle State

Successful

UserID and Password not authenticated

Connected to
Service Provider

UserID and Password authenticated

logged in

Send request
Wait for
feedback

Successful
Error

Feedback= Troubleshoot
ERROR
17. State Chart Diagram for Light System

Service Provider
Active

Sends Command

HACS Interaction Device Active

Ready Error

The request placed at the service

recieve the command from the service Provider
provider is sent to the HACS
Interaction device which forwards
the same to the respective device
Scanning the controller which is responsible for
Request implementing the request.

Update the Database

Database
Updated

Send command to respective Device controller

Error

Device Controller Active

Ready

Receive command from HACS Interaction Device

Scanning
Request

Scanning Successful

Implementing
Command

Send Command To Device

Database update Database

Updated Command
Executed
18. State chart Diagram for AC

Idle State

Receive command from the AC Device Controller, i.e. set status & temprature

Status= ON/OFF.
Temprature=As specified in the reqest, T.

Temprature != T

A.C. Temprature = T
Running.
Switch OFF requested

Error
19. State chart Diagram for Microwave

Idle State

Receive command from the Microwave Controller, i.e. set mode & time.

MODE=Normal/Slow/Fast/Reheat
Time= As specified in the request

Execute Command

No Responce for 10 minutes

Idle State 2:Food Ready

Error Swithched Off by the Microwave Controller Device or by the user

20. State Chart Diagram for Security System

Idle

Set mode & status as specified

Receive Command from the security system controlling device

Status= ON/OFF.
Mode= HI / NORMAL

Breakthrough Detected

ALARM
TRIGGERED
21. Package Diagram
To simplify complex class diagrams, you can group classes into packages. A package is a collection of logically related UML
elements.

ServiceProvi
CellPhone der

HACS Interaction
device

HACS Device
Controller Devices
Database
22. Component Diagram
The component diagram shows the organization and dependencies among the set of components of the system. The Home
Appliance Control System contains the following components:

login.dll

Service
Provider.exe
TroubleS
hoot.dll

HACSInteracti
onDevice.exe

deviceContr
ollerGUI.exe
Databas
e.dll

appliance.
dll
update.dl
l

microwa ac lights securityS

ve ystem
23. Deployment Diagram

The deployment diagram shows the configuration of run-time processing elements and the software processes living on them.
The nodes we have in our deployment diagram are:
-Trouble Shoot
-Database
-Cell phone Client
-Service Provider Server
-HACS Interaction Device
-Microwave Controller
-System Security Controller
-AC Controller
-Lights
-Microwave
-System Security
-AC
-Lights

Trouble Shoot Database

Cellphone-client

ServiceProvider
Server HACS interaction
Device

Security System
Microwave Controller Light
Controller AC
Controller Controller

Micro Security AC
wave System Lights