Cell Phone Based Remote Home Control System
May-06-13
Project Plan
Client:
ECpE Department
Advisor:
Prof. Ahmed Kamal
Team:
Arturo Palau (EE)
Chau Nguyen (EE)
Issa Drame (EE)
Adam Mohling (CprE)
REPORT DISCLAIMER NOTICE
DISCLAIMER: This document was developed as a part of the requirements of an
electrical and computer engineering course at Iowa State University, Ames, Iowa.
This document does not constitute a professional engineering design or a
professional land surveying document. Although the information is intended to
be accurate, the associated students, faculty, and Iowa State University make no
claims, promises, or guarantees about the accuracy, completeness, quality, or
adequacy of the information. The user of this document shall ensure that any
such use does not violate any laws with regard to professional licensing and
certification requirements. This use includes any work resulting from this studentprepared document that is required to be under the responsible charge of a
licensed engineer or surveyor. This document is copyrighted by the students
who produced this document and the associated faculty advisors. No part may
be reproduced without the written permission of the senior design course
coordinator.
23 – September – 2005
Table of Contents
i.
ii.
iii.
1.
List of Tables ................................................................................................ 3
List of Figures ............................................................................................... 4
List of Definitions .......................................................................................... 5
Introductory Material ..................................................................................... 6
1.1. Abstract ................................................................................................... 6
1.2. Acknowledgements ................................................................................. 6
1.3. Problem Statement .................................................................................. 6
1.4. Operating Environment ............................................................................ 6
1.5. Intended Users and Uses ........................................................................ 7
1.6. Assumptions ............................................................................................ 7
1.7. Limitations ............................................................................................... 8
1.8. Expected End Product ............................................................................. 9
2. Proposed approach .................................................................................... 10
2.1. Functional Requirements ....................................................................... 10
2.2. Constraints Considerations ................................................................... 11
2.3. Technology Considerations ................................................................... 11
2.4. Technical Approach ............................................................................... 12
2.5. Testing Requirements ........................................................................... 12
2.6. Security Considerations ......................................................................... 19
2.7. Safety Considerations ........................................................................... 20
2.8. Intellectual Property ............................................................................... 20
2.9. Commercialization ................................................................................. 20
2.10. Risks and Management ......................................................................... 21
2.11. Milestones and Evaluation ..................................................................... 22
2.12. Project Tracking Procedures ................................................................. 23
3. Statement of work ....................................................................................... 24
3.1. Task 1 – Problem Definition .................................................................. 24
3.2. Task 2 – Technology Considerations .................................................... 25
3.3. Task 3 – Cell Phone Receiver Station (End-Product Design)................ 26
3.4. Task 4 – End-Product Prototype Implementation .................................. 27
3.5. Task 5 – End-Product Testing ............................................................... 28
3.6. Task 6 – End-Product Documentation ................................................... 29
3.7. Task 7 – End-Product Demonstration.................................................... 30
3.8. Task 8 – Project Reporting .................................................................... 31
4. RESOURCES ............................................................................................. 33
4.1. Personnel .............................................................................................. 33
4.2. Financial Requirements ......................................................................... 33
5. Schedule ..................................................................................................... 34
5.1. General Summary of Project Schedule ................................................. 34
5.2. Project Reporting Schedule ................................................................... 35
5.3. Project Development Schedule ............................................................. 36
May-06-13
Senior Design
Page 1
3/3/2016
Table of Contents Continued
6.
Closure material.......................................................................................... 37
6.1. Client Information .................................................................................. 37
6.2. Faculty Advisor Information ................................................................... 37
6.3. Student Team Information ..................................................................... 37
7. References ................................................................................................. 38
May-06-13
Senior Design
Page 2
3/3/2016
i.
List of Tables
Table 4.1 Personnel Hours ..…………………………………………………28
Table 4.2 Financial Layout……………………………………………………28
May-06-13
Senior Design
Page 3
3/3/2016
ii.
List of Figures
Figure 2.1 System Operation Flow Diagram………………………………….… 7
Figure 5.1 General Summary of Project Schedule………………………….....29
Figure 5.2 Project Reporting Schedule…………………………………............30
Figure 5.3 Project Development Schedule…………………………………......31
May-06-13
Senior Design
Page 4
3/3/2016
iii.
List of Definitions
GSM (Global System for Mobile communications); is a cellular communication
standard.
DTMF (dual-tone multi-frequency): is used for telephone signaling over the line in
the voice frequency band to the call switching center.
GPRS (General Packet Radio Service): is a mobile data service offered to GSM
mobile users.
SMS (short message service): is a service available on most digital mobile
phones that permit the sending of short messages (also known as text
messaging service).
M2M (machine to machine): concept of communications between a device containing
some amount of data and another device that requires the use of that data.
May-06-13
Senior Design
Page 5
3/3/2016
1. INTRODUCTORY MATERIAL
This section will introduce the project. It also will state the basic problem, and the
basic characteristics of the project, such as operating environment, users, etc.
1.1.
Abstract
The objective of this project is to enable users to remotely control their home
appliances and systems using a cell phone-based interface. To access the
control unit, the user should send an authentication code along with the
required/desired function/action to his/her home control system via GSM. Upon
being properly authenticated, the cell phone-based interface at home (control
unit) would relay the commands to a microcontroller that would perform the
required function/action, and return a function completion code that would be
sent to the source of the original command (user’s cell phone).
1.2.
Acknowledgements
Special thanks are extended to Professor Ahmed Kamal for his support and
mentorship towards the development and success of this project.
1.3.
Problem Statement
The objective of this project is to develop a device that allows for a user to
remotely control and monitor multiple home appliances using a cellular phone.
This system will be a powerful and flexible tool that will offer this service at any
time, and from anywhere with the constraints of the technologies being applied.
Possible target appliances include (but are not limited to) climate control
systems, security systems, and lights; anything with an electrical interface.
The proposed approach for designing this system is to implement a
microcontroller-based control module that receives its instructions and
commands from a cellular phone over the GSM network. The microcontroller
then will carry out the issued commands and then communicate the status of a
given appliance or device back to the cellular phone. For security purposes, a
means of identification and user authentication will be implemented, and will
combine caller identification with a password authorization.
1.4.
Operating Environment
The control system will include two separate units: the cellular phone, and the
control unit. There will therefore be two operating environments. The cellular
phone will operate indoors and outdoors whereas the control unit will operate
indoors within the temperature and humidity limits for proper operation of the
hardware.
May-06-13
Senior Design
Page 6
3/3/2016
1.5.
Intended Users and Uses
This product is aimed toward average consumers who wish to control household
appliances remotely from their cell phones provided that the appliances are
electrically controllable. Example of feasible appliances and applications under
consideration include; enable/disable security systems, fans, lights, kitchen
appliances, and adjusting the temperatures settings of a heating/ventilation/air
conditioning system.
1.6.
Assumptions
The following is a list of assumptions for the project;
1.)
The user and control unit will establish communication via GSM.
2.)
The cell phone and service provider chosen will support text
messaging service.
3.)
The user is familiar with the text messaging program on their cell
phone.
4.)
All service charges from service provider apply.
5.)
The controlled appliances can will have to have an electrical
interface in order to be controlled by microcontroller.
May-06-13
Senior Design
Page 7
3/3/2016
1.7.
Limitations
The following is a list of limitations for the project.
1.)
The receiver must reside in a location where a signal with sufficient
strength can be received from a cellular phone network.
2.)
The only person who can communicate with the control module is
the person who will be successfully authenticated.
3.)
Only devices with electrical controlling input ports will be possible
targets for control.
4.)
The controlled devices will have I/O ports that will make
communication with the receiver possible.
5.)
The receiver must have a power source (120V) attached at all
times.
6.)
Operation of the controlling unit is only possible through a cell
phone with SMS messaging capabilities.
7.)
The controlling unit must be able to receive and decode SMS
messages.
May-06-13
Senior Design
Page 8
3/3/2016
1.8.
Expected End Product
The following is a list of expected end products and other deliverables.
A single M2M controller module that can perform the following:
1.)
a.
Receive instructions and commands from a messaging
device on a communication network
b.
Monitor a device status from an electronic interface
c.
Control target devices through an electrical interface
2.)
A list of approved message input commands that the device is
capable of executing
3.)
Develop a user manual for reference by the end user.
4.)
Project plan is required to defined and outline project approaches
and deliverables.
5.)
Project poster is required to showcase the project to the students
and faculties members.
6.)
Design document is required to outline our technical requirements
and system’s functionalities.
7.)
Final report is required for documentations on the overall project,
including; end results, success, failures, etc
May-06-13
Senior Design
Page 9
3/3/2016
2. PROPOSED APPROACH
This section outlines the criteria that will be considered in the development of the
control system.
2.1.
Functional Requirements
The following is a list of functional requirements of the control unit/module.
1.)
The control unit will have the ability to connect to the cellular
network automatically.
2.)
The control unit will be able to receive text messages and will be
able to parse and interpret (ASCII) text messages for password
identification and instructions to be sent to the microcontroller.
3.)
The microcontroller within the control unit will issue its command to
the electrical appliances through a simple control circuit.
4.)
The control unit will control the electrical appliances and detect the
status of the appliances to be relay back to the microcontroller.
5.)
The microcontroller within the control unit should be able to send
status messages back to the cellular phone through the cellular
network.
6.)
The system should provide user authentication through cell phone
number identification and/or password verification contained within
the (SMS) text message.
May-06-13
Senior Design
Page 10
3/3/2016
2.2.
Constraints Considerations
The following is a list of constraint considerations
1.)
The controlled appliances will need an electrical control interface.
This simple system is only capable of controlling electrical devices.
2.)
The control module will need to be shielded against electrostatic
discharges. This will increase reliability of the system.
3.)
Battery backup for controlling unit will be implemented in case of
power disruption. This is necessary to provide the user with status
messages such as “power failure - system unavailable”. With this
information, the user knows that communication with the system
has been established. If there was not return message sent, the
user has no knowledge of whether the message was received by
the controlling unit.
2.3.
Technology Considerations
The considerations for this system will include a choice of networks,
communication protocols, and interfaces.
1.)
Cellular Networks: The widely available networks are based on
GSM. This network provides a wide area of coverage and can be
utilized more cost-effectively for this project.
2.)
Communication protocols: The available communication
protocols are DTMF, GPRS and SMS. The SMS is the most
efficient because this project requires a cellular communication and
limited data to be sent.
3.)
I/O interfaces between microcontroller and devices: Serial or
parallel I/O will be considered as options for connection between
the GSM receiver and the microcontroller.
Using the
microcontroller, a control circuit will be implemented to control the
electrical appliances.
May-06-13
Senior Design
Page 11
3/3/2016
2.4.
Technical Approach
Assuming that the control unit is powered and operating properly,
the process of controlling a home device will proceed through the
following steps:
1.)

The remote user sends text messages including authentication
information and commands to the receiver.

GSM receiver receives messages sent from user cell phone.

GSM receiver parses the string for the authentication information,
and the commands.

GSM receiver sends the commands to the microcontroller.

Microcontroller issues commands to the appliances.

Microcontroller checks for completion status and sent it back to the
GSM receiver.

GSM receiver informs the remote user of the outcome of their
request by sending a completion status message back to remote
user in the form of another SMS message.
Lamp
Micro
controller
Send
status
Cell Phone
• Send text
message
•Receive status
message
Send
messa
ge
Send
status
GSM chip
Send
completion
status
Issue
command
Send
messag
e
• Decode incoming
• Transfer data to
• Send instruction
microcontroller
Appliances
• Perform
• Communicate
with network
Security
System
required
instructions
Fan
Garage
Door
message
to appliance
•Monitor
completion status
Figure 2.1 System Operation Flow Diagram
May-06-13
Senior Design
Page 12
3/3/2016
2.5.
Testing Requirements
The following testing requirements will be indicators that the system can
successfully be implemented.
1.)
The GSM receiver will be tested for successful communication with
network. This will test include automation and consistency of the
connection and will be conducted by a team member in the
following way:

The cellular phone will dial the GSM receivers’ number

Once the connection is established a stream of data will be
send to the GSM receiver.

The GSM receiver will be given data to be transmitted to the
cellular phone.
Success/Failure criteria: The data received will be observed on
both ends to verify its consistency. The test will be considered
successful if the integrity of the sent and received data is
maintained up/downstream. It will be considered a failure
otherwise.
2.)
The GSM to microcontroller driver will be tested by verifying the
integrity of command strings sent from the remote user. The
following procedure will be performed in majority by a CprE team
member:

The remote user will send a command to the control module.

The contents of the data stream will be observed at the GSM
communication port.

These contents will be compared with those received and stored
at the microcontroller’s corresponding communication port.

The procedure will be repeated in reverse with
microcontroller sending a data steam to the GSM receiver.
the
Success/Failure criteria: The test will be considered successful if
the integrity of the data sent up/downstream is maintained. It will be
considered a failure otherwise.
May-06-13
Senior Design
Page 13
3/3/2016
3.)
The GSM receiver will be tested for successful communication with
network. This will test include automation and consistency of the
connection and will be conducted by team members in the following
way:

The cellular phone will dial the GSM receivers’ number.

Once the connection is established a stream of data will be
send to the GSM receiver.

The GSM receiver will be given data to be transmitted to the
cellular phone.
Success/Failure criteria: The data received will be observed on
both ends to verify its consistency. The test will be considered
successful if the integrity of the sent and received data is
maintained up/downstream. It will be considered a failure
otherwise.
4.)
The GSM to microcontroller driver will be tested by verifying the
integrity of command strings sent from the remote user. The
following procedure will be performed by team members for this
phase:

The remote user will send a command to the control module.

The contents of the data stream will be observed at the GSM
communication port.

These contents will be compared with those received and stored
at the microcontroller’s corresponding communication port.

The procedure will be repeated in reverse with
microcontroller sending a data steam to the GSM receiver.
the
Success/Failure criteria: The test will be considered successful if
the integrity of the data sent up/downstream is maintained. It will be
considered a failure otherwise.
May-06-13
Senior Design
Page 14
3/3/2016
5.)
Proper decoding of the remote user’s commands and issuance of
the equivalent commands to the controlled device will be performed
by team members using the following procedure:

A simulated instruction will be fed to the microcontroller
communication port.

The output command at the I/O interface with the corresponding
controlled device will be observed.
Success/Failure criteria: The test will be considered a success if the
resulting command issued from the microcontroller is sent to the
right I/O address for the desired controlled device and if that
command is consistent with the command which is expected. The
test will be considered a failure otherwise.
6.)
The I/O command’s voltage will be tested to meet the levels
required to actuate the individual devices. The following procedure
will be performed by EE team members:

A simulated command from the microcontroller will be written to
its I/O port.

The output voltage at the desired device’s control interface will
be measured to verify its strength.
Success/Failure criteria: The test will be considered successful if
the simulated command from the microcontroller causes the proper
voltage to be observed at the desired device’s control interface.
May-06-13
Senior Design
Page 15
3/3/2016
7.)
The scaling circuit from the controlled devices to the I/O will be
tested for proper operation. This will be tested by EE team
members:

The controlled devices will be manually triggered to force the
desired voltage.

The output of the scaling circuit will be measured.
Success/Failure criteria: The testing will be considered successful
if the measured output voltage is properly scaled to the
microcontroller’s required input value. The test will be considered a
failure otherwise.
8.)
The ability of I/O to detect an input voltage and store a value in the
microcontroller’s memory will be tested by team members:

Test voltages to the input of the I/O will be applied.

The contents of the memory shall be checked for validity.
Success/Failure criteria: The testing will be considered successful
if the values of the memory are as expected. The test will be
considered a failure otherwise.
9.)
The circuit’s power surge protection will be tested for acceptable
performance by EE team members using the following procedure:

The circuit’s power supply will be removed from the circuit and
connected to a dummy load.

A simulated voltage spike will be inputted by using a step signal
from a signal generator.

The output voltage and current will be measured at the load.
Success/Failure criteria: The success of the test will be determined
by verifying that the output signal to the dummy load falls with the
tolerance indicated by the microcontroller and the GSM chip’s
manufacturers. The test will be considered a failure if the measured
characteristics of the power supply’s output do not meet the
manufacturers’ requirements.
May-06-13
Senior Design
Page 16
3/3/2016
10.)
The password authentication will be tested for proper operation.
The following procedure will be performed by team members:

The password protection of the code will be run in debug mode.

A simulated mix of correct and incorrect passwords will be sent
to the microcontroller

The response of the microcontroller will be observed for each of
the inputted passwords.
Success/Failure criteria: The testing will be considered successful
if the microcontroller grants access to all the right passwords and
none of the wrong passwords. The test will be considered a failure
otherwise.
11.)
The ability of an I/O status to trigger the execution of status
messaging subroutine will be tested as well as the ability to send
the resulting status to the remote user. The following procedure will
be performed by team members:

A simulated device status will be written to the I/O in debug
mode.

The simulated status will trigger the execution of the
microcontroller’s device status notification subroutine

The subroutine output will be checked prior to being sent to the
GSM chip.

Verification that the status message was received by the user
cell phone will be performed.
Success/Failure criteria: The testing will be considered successful
if the simulated I/O triggers execution of the subroutine and if the
correct status message is sent to the GSM chip and that status
message is received by the cell phone. The test will be considered
a failure otherwise.
12.)
The end-product functionalities will be tested by team members and
non-team members in the following way:

May-06-13
Senior Design
Team members will ensure that all subsystems function properly
together from remote user command to execution and back to
completion status notification.
Page 17
3/3/2016

Non-team members from the general public will be allowed to
access and use the control unit for a frame of time.

Afterward, the non-team member testing subjects will fill out a
survey on the end-product’s functionalities, ease of use,
difficulties, etc.
Success/Failure criteria: The testing will be considered a success if
the testing subjects find the end-product user friendly, and easy to
figure out.
May-06-13
Senior Design
Page 18
3/3/2016
2.6.
Security Considerations
A combination of cellular phone number identification by the receiver chip and
password authentication will be used to validate user requests. This security
measures can be implemented in both the GSM receiver and the
microcontroller.
1.)
The system will only be able to be controlled by SMS messages
sent over a cellular network. The only interface to the controlling
system will be the GSM microcontroller.
Possible testing procedures:
1.a) Team members will try communicating with the
microcontroller through a device that does not support SMS
messages.
Successful test: The system discards the incoming connection and
does not try to execute any operation.
Failed test: The systems attempts control of an appliance
2.)
The password will be sent along with the SMS message. The SMS
message will be parsed and look for the password. If the password
is not sent with the SMS message, the command will be discarded.
Possible testing procedures:
2.a) Team members will try to send a command to the
microcontroller with incorrect or no password.
Successful test: The command is discarded because of failed user
authentication.
Failed test: The system attempts control of an appliance.
May-06-13
Senior Design
Page 19
3/3/2016
2.7.
Safety Considerations
The following is a list of safety considerations:
1.)
The end-product will be enclosed in grounded metal case. This
measure is necessary for protecting the delicate circuit components
of the end-product and allows the end-product to be relocated
easily.
2.)
Proper ventilation to keep system cool will be implemented. This
can be done attached a small cooling fan into the metal case.
3.)
Proper wiring and insulation will be implemented to avoid damages
and harm to user.
4.)
Incoming power will be regulated by connecting the system to a
standard 120V outlet through a surge protector.
2.8.
Intellectual Property
The following is a list of intellectual property considerations:
1.)
This project shall not infringe upon any patents of existing similar
products
2.)
This project shall be the intellectual ownership of its creation team.
2.9.
Commercialization
Possible customers for this product would be home improvement contractors,
and supply stores. The benefit of this is the end-product can be sold in large
quantities and it can be incorporated into the construction of modernize
homes. The end-product will be not be sold in retails stores because
reconfiguring of the end-product to control different electrical appliances will
be complicated and it should only be attempted by trained technicians. Retail
stores would also not be a good target for commercialization due to the
system requiring a cellular phone plan in order to operate. Advertising through
cellular phone providers would be a more feasible option.
May-06-13
Senior Design
Page 20
3/3/2016
2.10. Risks and Management
The following is a list of possible risks and risk management:
1.)
Loss of team member(s)
There will be always at least two team members that are involved with
designing of every subsystem. This will ensure that at least two team
members who are familiar with every subsystem. So in the event of losing a
team member, there will be a secondary team member who can take over the
responsibilities.
2.)
Lack of expertise in team members
Adequate time to research the technology will be required after selecting the
technology to be used in the project. Team member are also responsible to
seek out help where ever it applies. Frequent meeting and project update
with faculty advisor will ensure correct approaches are utilized in the
completion of the project.
3.)
Legal risk of product failure/defect
Appropriate warnings will accompany the product.
4.)
Electric Shock
Proper electric device practices will be included in the product manual and
warnings will be posted in a highly visible spot on the product.
May-06-13
Senior Design
Page 21
3/3/2016
2.11. Milestones and Evaluation
The following are the proposed milestones and evaluation criteria:
1.)
Project outline is defined with the completion of the project plan.
2.)
Project outline is defined with the completion of the project plan.
3.)
All the background information about the technology in use and the
appliance controls has been acquired and understood.
Team members will research various cellular networks and GSM
microcontrollers and discuss the pros and cons. When team
members feel comfortable with the assigned project, this milestone
will be considered to be achieved.
4.)
Finalized design – Overall design of the final product is completed.
When the team has completed the design document, this milestone
will be considered to be achieved. Failure would be not completing
the design document.
5.)
Required parts have been received.
The parts that make up this system will be ordered in the F’05
semester by filling out the order form located in the Senior Design
packet. When all parts have been delivered in the S’06 semester
this milestone will be considered to be completed. If any part has
not been delivered, this task will have failed and shall be reexecuted.
6.)
Hardware aspect of module is interconnected
This milestone will be used to identify that all the parts ordered from
milestone #4 were correct and connect together correctly to form
the controlling unit. If all the parts connect together correctly and
function properly, this system will be considered to pass, else fail.
May-06-13
Senior Design
Page 22
3/3/2016
Coding is complete and tested
7.)
This milestone will be used to track that the coding process has
been completed. This milestone will pass if a message can be sent
to the controlling unit, be parsed, decoded and send the proper
controlling information to the I/O. If a message can not be detected
by the microcontroller or the message can not be parsed properly
this milestone will fail.
Final testing phase is completed
8.)
This milestone will be used to identify when the product is ready for
commercialization. When all identified test cases have been
executed with the expected result this milestone will pass.
2.12. Project Tracking Procedures
Microsoft Project will be used to track the status of the project. It will
include task time estimates, individual assignments, and hours spent
on each task to determine how well the project is proceeding along
schedule.
May-06-13
Senior Design
Page 23
3/3/2016
3. STATEMENT OF WORK
3.1.
Task 1 – Problem Definition
1.)
Subtask 1a – Problem Definition Completion
Task Objective: The team will define the problem at hand and how the
project will address the problem.
Task Approach: The team will research the different issues associated
with the problem by reading online articles and looking at similar
projects. From the information gathered, the team will decide on the
most important issues that the project will entail and ensure that these
issues are addressed.
Task Expected Results: The team will have a problem that will be solved
by completing our project.
2.)
Subtask 1b – End User(s) and End Use(s)
Task Objective: The team will determine the users of the final project.
Task Approach: The team will research the applications and the users of
the project. The applications will have to be any device that has an
electrical interface. All controlled appliances will have to be addressed
individually because all appliances are not created with the same
interfaces.
Task Expected Results: The team will decide on a suitable market for
the project.
3.)
Subtask 1c – Constraint Identification
Task Objective: The team will research the limitations of the project.
Task Approach: The team will get together and discus what tasks the
end product will not be able to accomplish before development.
Task Expected Results: The team will save time and money by not trying
to develop functionality that has been declared unobtainable during the
previous discussion.
May-06-13
Senior Design
Page 24
3/3/2016
3.2.
Task 2 – Technology Considerations
1.)
Subtask 2a – Identification of Possible Technologies
Task Objective: The team will research the possible products that will be
used for the development of the product.
Task Approach: The team will research similar projects that are related
to this project and check what technologies were used and discus
whether they could be applied to this project.
Task Expected Results: The team will compile a list of possible
technologies that can be used for the project.
2.)
Subtask 2b – Identification of Selection Criteria
Task Objective: The team will identify the technologies that we will be
using for the project.
Task Approach: The team will get together and selectively eliminate
technologies that would not allow the system to perform the minimum
operations. If a technology is found to be able to perform the minimum
operations, it will be added to a list of technologies to be considered.
Task Expected Results: The team will have a better idea of the
technology it will be using.
3.)
Subtask 2c – Technology Research
Task Objective: The team will research the technologies chosen for the
project.
Task Approach: The team will look up in the internet or other sources
about the technologies and how to use it, its functions, etc.
Task Expected Results: The team will have a better understanding of all
the technologies that are available work and will be able to weigh the
pros and cons of all the options.
4.)
Subtask 2d – Technology Selection
Task Objective: The team will select the exact components that will be
used for the development of the project.
Task Approach: The team will study the results of step 2c and will decide
which technology and equipment will be used for the project.
Task Expected Results: The team will have made a selection of a
technology to be used in the project and will have the exact components
of the project c.
May-06-13
Senior Design
Page 25
3/3/2016
3.3.
Task 3 – Cell Phone Receiver Station (End-Product Design)
1.)
Subtask 3a – Cell Phone to Device Control
Task Objective: To receive a message from a cell phone and execute
the requested command
Task Approach: Investigate various cell phone communication
technologies and select a microcontroller capable of communicating with
the selected network. Then be able to take the information received by
the communication network and decode the information into an
executable command. The command will be executed and an electrical
device can be manipulated and monitored.
Task Expected Results: Communication to a central unit that can decode
a message into useable data stream. This data stream will be checked
for validity and be able to control and monitor an assortment of electrical
devices.
2.)
Subtask 3b – Design Process
Task Objective: The team will identify various ways of cell phone
communication.
Task Approach: The team will search through various cell phone
provider websites and articles online to identify the pros and cons of the
different networks.
Task Expected Results: The team will have a good understanding of all
the networks available. From this list, the team will be able to select a
communication network that will satisfy the project’s needs.
3.)
Subtask 3c – Documentation of Design
Task Objective: To create detailed documentation on every subsystem
of the entire product.
Task Approach: All members of the team will keep an updated log book
to help in the writing of formal documentation. This document will be
created before any development is actually begun and will be referenced
during the development stage. If any unexpected issues arise, changes
will be made to the documentation.
Task Expected Results: A detailed design document breaking the project
down into subsystems and explicitly stating the details of each
subsystem.
May-06-13
Senior Design
Page 26
3/3/2016
3.4.
Task 4 – End-Product Prototype Implementation
1.)
Subtask 4a – Identification of Prototype Limitations
Task Objective: To discover the extent of the capabilities of the available
resources and their limitations.
Task Approach: The team will attempt to implement as much
functionality as possible with the limited budget, knowledge, timeline and
tools. The system will have to be tested for a limit to the number of
devices that can be controlled by the controlling unit. Voltage levels that
can be applied to the controlled device will probably have to be amplified
in order to successfully operate the controlled device.
Task Expected Results: Identification of a prototype that will be fully
functional.
2.)
Subtask 4b – Implementation of Prototype End Product
Task Objective: To complete the hardware/software integration of the
project
Task Approach: The team will discuss various hardware solutions that
can be used to accomplish the project’s end-product. After the team
receives the microcontroller device and have become familiar with the
software users guide, the team will select from the available coding
languages and begin the coding development stage.
Task Expected Results: A working baseline of the project that will allow
for the team to begin testing.
May-06-13
Senior Design
Page 27
3/3/2016
3.5.
Task 5 – End-Product Testing
1.)
Subtask 5a – Test Planning
Task Objective: To clearly outline testing criteria and procedures of the
end-product.
Task Approach: The team will work with the faculty advisor to plan the
testing phase in detail. This will include outlining testing criteria,
procedures, time-frame, arrange any necessary equipment, and
assigning the proper team member(s) who will perform the test. The
tests and expected end result will be written up prior to the actual testing.
Each test will have an expected end result documented. If the test fails
to perform the expected end result then the test will be considered to
have failed.
Task Expected Results: The team will have a clear understanding of
when, where, and how the end-product will be tested. The team will also
know what the expected results of individual tests will be ahead of time
for evaluation purposes.
2.)
Subtask 5b – Actual Testing
Task Objective: The team will perform the required test and evaluate if
the end-product meets the pass/fail criteria outlined in Subtask 5a.
Task Approach: Each test will be performed by a main team member
and a back-up team member. Team members are expected set up,
perform, and evaluate end-results. Team members are expected to keep
sufficient documentation throughout the test phase.
Task Expected Results: The team will follow proper testing procedures,
complete the test efficiently, and keep adequate documentation.
3.)
Subtask 5c – Test Results Evaluation
Task Objective: To outline pass/fail criteria of individual end-product test.
Task Approach: The team will work with the faculty advisors to develop a
list of criteria that will evaluate the end-product’s functionality. This will
include minimum standards for the end-product’s functionality and define
what measurement errors are acceptable.
Task Expected Results: Based on test results, the team will use the
outlined criteria to determine if the end-product meets the minimum
requirement for each of its function.
May-06-13
Senior Design
Page 28
3/3/2016
3.6.
Task 6 – End-Product Documentation
1.)
Subtask 6a – Development of End-User Documentation
Task Objective: Team members will compile a user manual for the end
product.
Task Approach: The user manual will include information such as: setup, operation and troubleshooting for the end-product. Team members
will have to ensure that the owner manual is understandable to the end
user and detailed enough to troubleshoot any potential issues.
Task Expected Results: The team will create a user manual that is
comprehensive, and easy to read and follow.
2.)
Subtask 6b – Development of Maintenance Support
Documentation
Task Objective: Team will compile a troubleshooter guide to assist in any
potential problem that the end user might encounter.
Task Approach: Any unique errors or complications the team encounters
while developing the system shall be documented and the resolution
shall be recorded for this troubleshooter guide.
Task Expected Results: The troubleshooter guide will be incorporated
into the user manual.
May-06-13
Senior Design
Page 29
3/3/2016
3.7.
Task 7 – End-Product Demonstration
1.)
Subtask 7a – Demonstration Planning
Task Objective: The objective of demonstration planning is to prepare the
team for the demonstration of the end product the faculty advisors and the
industrial review panel.
Task Approach: The team will prepare for the presentation by:
 Reviewing relevant documentation.
 Preparing visual aids.
 Rehearsing a thorough and complete demonstration of the
physical end-product.
 Assigning roles for presentation.
 Ensuring that end-product is not damaged and that it will
perform as tested during development.
Task Expected Results: As a result of this preparation, the team should
have a well rehearsed and flawless demonstration. This entails concise
and effective speak, as well as successful operation of the end-product
according to the functional requirements set forth.
2.)
Subtask 7b – Faculty Advisors Demonstration
Task Objective: The objective of the demonstration will be to prove the
successful completion of the project to the faculty advisors and to inform
them of the design and process that were applied. A secondary purpose
will be to invite feedback that would be applied to the industrial review
panel demonstration.
Task Approach: The demonstration will be a combination of oral
presentation and physical demonstration of the end-product, after which
there will be a question and answer session.
Task Expected Results: The expected result is a successful
demonstration, in which the faculty advisors are satisfied and impressed
by the success of the project.
3.)
Subtask 7c – Industrial Review Panel Demonstration
Task Objective: The objective of the demonstration will be to prove the
successful completion of the project to industrial review panel and to
inform them on the design and process that were applied.
Task Approach: The demonstration will be a combination of oral
presentation and physical demonstration of the end-product, after which
there will be a question and answer session.
Task Expected Results: The expected result is a successful
demonstration, in which the industrial review panel is satisfied and
impressed by the success of the project and approves of its sound design.
May-06-13
Senior Design
Page 30
3/3/2016
3.8.
Task 8 – Project Reporting
1.)
Subtask 8a – Project Plan
Task Objective: The objective of the project plan is to involve the team in
thinking ahead, by laying out an outline of the tasks that will make up the
project.
Task Approach: The approach to the project plan is the following:
 Refer to course notes for details of the plan that need to be
explored
 Brainstorm as a team and come to a consensus about the
respective parts of the project indicated in the plan.
 Divide writing tasks among team members, and synthesize
project plan from all contributions.
Task Expected Results: The end-result of the project plan is a detailed
layout of the projected flow of the project. From the project plan, the team
should have a schedule to follow, in order to complete project on time.
2.)
Subtask 8b – Project Poster
Task Objective: The objective of the project poster is to come up a visual
aid summarizing the purpose, approach, effort, and capabilities of the end
product.
Task Approach: The approach to developing a project poster will be as
follows
 Team will collect the relevant information to be displayed on
the poster
 Team will discuss the desired appearance of the poster
 Either the members will contribute graphics to the poster, or
a talented and artistic member will be responsible for the
visual design or the poster
 Budget constraint will be applied to the printing and
lamination of the poster
 Based on the constraints, a printing company will be
selected to print poster
 The final design will then be submitted to the selected
company for printing
Task Expected Results: The project will be attractive in design and
concisely informative to the reader.
May-06-13
Senior Design
Page 31
3/3/2016
3.)
Subtask 8c – Design Report
Task Objective: The objective of the design report is to document in detail
the design of the end product.
Task Approach: The design report will require the following to fulfill its
objective
 Detailed drawings, schematics, calculations, simulation
results and steps and drawings
 A detailed description of the parts in the design and of the
mechanics of their interaction supported by the documents
mentioned in the first bullet.
To be able to provide the outlined documentation, the team will save all
documents in hardcopy forms.
Task Expected Results: The result of a design report should be a detailed
document that can be used as a reference to implement the design.
4.)
Subtask 8d – Final Report
Task Objective: The objective of the final report is to provide a complete
history of the project from start to end.
Task Approach: The final report will synthesize the design of the endproduct with the history of the project. The approach that will be used in
developing the final report will be the following:
 Gather all relevant documents (design, calculations, test
runs etc…)
 Divide writing duties
 List all important events (including all details that should be
noted)
 List problems encountered
 Merge documents
Task Expected Results: The final design will be the most complete
document of the project and will give the user a good understanding of the
overall process that was required to complete the project.
5.)
Subtask 8e – Weekly Email Reporting
Task Objective: The objective of the weekly email report is to inform the
team, faculty advisor, and the client of the progress of the project.
Task Approach: A person will be designated the communicator, and will
keep track of the minutes of all meeting and of the documentation. That
person will send out an email to the project mail list every week by set
deadline.
Task Expected Results: The weekly email report will give everyone on the
mailing list an update on the progress of the project.
May-06-13
Senior Design
Page 32
3/3/2016
4. RESOURCES
The information in this section outlines the people and projected hours to be
spent on the various sections outlined in this document.
4.1.
Personnel
These are the team members that will be developing this project.
Table 4.1 Personnel Hours
Personnel
Task Task
Name
1
2
Drame, Issa
5
12
V
Mohling,
5
12
Adam David
Nguyen,
5
10
Chau Vinh
Palau,
5
10
Arturo
Other
0
0
Resources
Totals
20
44
Task
3
Task
4
Task Task Task Task
5
6
7
8
Total
20
35
30
15
10
45
172
15
50
25
25
5
42
179
20
35
35
20
10
35
170
25
0
0
0
0
30
70
0
0
8
0
0
0
8
80
120
98
60
25
152
599
Other Resources
The team will request volunteers to try out the system and see if they can
utilize the system’s service. If individuals with no prior knowledge of how the
system works are handed a user manual and given the system, the test would be
to see if they could in fact operate the system.
4.2.
Financial Requirements
4.2.1 Project must be completed within senior design project budget ($150).
Table 4.2 Financial Layout
Item
Labor at $10.30 per hour:
a. Palau, Arturo
b. Mohling, Adam David
c. Nguyen, Chau Vinh
d. Drame, Issa V
Totals
May-06-13
Senior Design
Page 33
W/O Labor
With Labor
$-$-$-$-$150
$721.00
$1843.70
$1751.00
$1771.60
$6237.30
3/3/2016
5. SCHEDULE
5.1.
General Summary of Project Schedule
Figure 5.1 General Summary of Project Schedule
May-06-13
Senior Design
Page 34
3/3/2016
5.2.
Project Reporting Schedule
Figure 5.2 Project Reporting Schedule
May-06-13
Senior Design
Page 35
3/3/2016
5.3.
Project Development Schedule
Figure 5.3 Project Development Schedule
May-06-13
Senior Design
Page 36
3/3/2016
6. CLOSURE MATERIAL
This closure material consists of client, faculty advisor, and team information, as
well as a project summary and references.
6.1.
Client Information
Senior Design, Iowa State University
Dr. John W. Lamont
324 Town Engineering
Ames, IA 50012
(515) 294-3600
jwlamont@ee.iastate.edu
6.2.
Prof. Ralph Patterson III
326 Town Engineering
Ames, IA 50012
(515) 294-2428
repiii@iastate.edu
Faculty Advisor Information
Prof. Ahmed E. Kamal, Professor
Iowa State University
Ames, IA 50011-3060
(515) 294-3580
kamal@iastate.edu
6.3.
Student Team Information
Arturo Palau – EE
80 Linden Devitt
Ames, IA 50011
(515)708-3812(Cell)
apalau@iastate.edu
Chau Nguyen – EE
137 S. Franklin Ave.
Ames, IA 50014
(319)321-8619
chayman@iastate.edu
Issa Drame – EE
4335 Frederickson Court
Ames, IA 50010
(515)572-7820
issad@iastate.edu
Adam Mohling – CprE
2635 Knapp St.
Ames, IA 50014
(515)292-2161(Cell)
mohbandy@iastate.edu
May-06-13
Senior Design
Page 37
3/3/2016
6.4.
Closing Summary
The extensive capabilities of this system are what make it so interesting.
From the convenience of a simple cell phone, a user is able to control and
monitor virtually any electrical device in a household. This makes it possible for
users to rest assured that their belongings are secure, that the garage door is
shut, and that the television was not left running when they left the house to just
list a few of the many uses of this system.
The end product will have a simplistic design making it easy for users to
interact with. This will be essential because of the wide range of technical
knowledge that homeowners have.
7. REFERENCES

Senior Design Course Notes – Iowa State University
Available at http://seniord.ee.iastate.edu/notes/
May-06-13
Senior Design
Page 38
3/3/2016