SRS VERSION:1

1. Software requirement specificaions
Page |1
Software RequirementsSpecification
For
GSM Based Home Automation
VERSION:1.00
GROUP NO:14
PROJECT LEADER: JINU JAMES
GROUP MEMBERS
NAME
ID
E-MAIL
ABRAHAM K JOSEPH
3737
kjabraham007@gmail.com
JACKSON THOMAS
3762
jacksonthomas22@gmail.com
JINU JAMES
3767
jinuvettikkattu@gmail.com
SHIBIN MATHEW
3786
Shibinthehurricane@gmail.com
DATE:10-01-2014

2. Software requirement specificaions
CONTENTS
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction .............................................................................................................................. 1
1.1
1.2
1.3
1.4
1.5
Purpose ............................................................................................................................................ 1
Document Conventions .................................................................................................................... 1
Intended Audience and Reading Suggestions .................................................................................. 1
Project Scope ................................................................................................................................... 1
References ........................................................................................................................................ 1
2. Overall Description .................................................................................................................. 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Product Perspective ......................................................................................................................... 2
Product Features .............................................................................................................................. 2
User Classes and Characteristics ..................................................................................................... 2
Operating Environment .................................................................................................................... 2
Design and Implementation Constraints .......................................................................................... 2
User Documentation ........................................................................................................................ 2
Assumptions and Dependencies ...................................................................................................... 3
3. System Features ........................................................................................................................ 3
3.1 System Feature 1 .............................................................................................................................. 3
3.2 System Feature 2 (and so on) ........................................................................................................... 4
4. External Interface Requirements ........................................................................................... 4
4.1
4.2
4.3
4.4
User Interfaces ................................................................................................................................. 4
Hardware Interfaces ......................................................................................................................... 4
Software Interfaces .......................................................................................................................... 4
Communications Interfaces ............................................................................................................. 4
5. Other NonfunctionalRequirements ....................................................................................... 5
5.1
5.2
5.3
5.4
Performance Requirements .............................................................................................................. 5
Safety Requirements ........................................................................................................................ 5
Security Requirements ..................................................................................................................... 5
Software Quality Attributes ............................................................................................................. 5
6. Other Requirements ................................................................................................................ 5
Appendix A: Glossary.................................................................................................................... 5
Appendix B: Analysis Models ....................................................................................................... 6
Appendix C: Issues List ................................................................................................................. 6
Page |2

3. Software requirement specificaions
Page |3
Revisions
Version
Primary Author(s)
Description of Version
1.00
Jinu James
Abraham K Joseph
Jackson Thomas
Shibin Mathew
Initail Release
Date Completed
10/01/2014

4. Software requirement specificaions
Page |4
INTRODUCTION
1.1 Purpose
The purpose of the project is mainly concerned with design a system that allows
users,uponauthentication,to remotely control and moniter multiple home applicances using a cell
phone based interface
1.2 Document Conventions
The format of this document is referred from the standard IEEE guidelines:
· Font face : Arial
· Font size
· Heading : 16
· Sub-heading : 14
· Description : 12
· Bold face and indentation is used on general topics and or specific points of
interest including the heading and sub-heading.
1.3 Intended Audience and Reading Suggestions
This document is mainly intended for project guides, developers and module coordinator(OOSP).
The sequence for reading the document begins with the overview sections and proceeding through
the sections that are most pertaining to each reader type.
1.4 Project Scope
The scope of our project “GSM Based control system” is immense.The future implications of the
project are very great considering the amount of time andresources it saves. The project we have
undertaken can be used as a reference or as a basefor realizing a scheme to be implemented in
other projects of greater level such asweather forecasting, temperature updates, device
synchronization, etc. The project itselfcan be modified to achieve a complete Home Automation
system which will then create aplatform for the user to interface between himself and the
household.
1.5 References
1. Mazidi, Muhammad ali, The 8051 Microcontroller and Embedded Systems,Second Edition,
Prentice Hall, 2007
2. www.embedtronics.com,October 2008
3. www.forum.nokia.com, October 2008

5. Software requirement specificaions
Page |5
OVERALL DESCRIPTION
2.1 Product Perspective
Device2
Device1
Issue
Send
Send
Message
Cell
Phone
GSM
Chip
Message
Command Appliances
Microcontroller
Instructions
Communicate with
Network
Transfer data to
• Send Text
Message
microcontroller
Perform
Required
Device3
Decode incoming
message
Send instruction to
appliance
Monitor completion
2.2PRODUCT FEATURES
Assuming that the control unit is powered and operating properly, the process of controlling a
device connected to the interface will proceed through the following steps;
1.The remote user sends text messages including commands to the receiver.
2.GSM receiver receives messages sent from the user cell phone.
3.GSM receiver decodes the sent message and sends the commands to the microcontroller.
4.Microcontroller issues commands to the appliances and the devices connected will ON/OFF

6. Software requirement specificaions
Page |6
2.3 USER CLASSES AND CHARACTERISTICS
Theproposed
systemcharacteristicsinvolveremotecontrolling
ofappliances,intrustiondetection,systemsecurity and auto-configurationsuch thatsystemautomatically
adjuststhesystemsettingsonrunninghardwaresupport
check.Thesystemhasusefulfeaturessuch
asdisplaying ofbatterylevel,charging statusand signalstrength ofthemobilethusmakingsystemreliable.
2.4 OPERATING ENVIRONMENT
Software requirements:
Number
Description
1
Windows 2000/ XP/ or
Higher with C language
Hardware requirements:
Number
Description
1
GSM module
2.
phone
3.
Microcontroller kit
4
Network availability
2.5 Design and Implementation Constraints
The following is a list of constraint Considerations
a. The controlled appliances will need an electrical control interface. This system is only
capable of controlling electrical devices.
b. The control module will need to be shielded against electrostatic discharges. This will
increase the reliability of the system.
c. Battery backup for controlling unit can be implemented in case of power disruption.

7. Software requirement specificaions
Page |7
2.6 User Documentation
DOCUMENTS
DESCRIPTIONS
User Manual
This document describes the how
to use system
features.
Online help will contain the
information about system
controls.
A document with snap-shots that
describes each
function of the system in detail and
how to perform
them.
On-Line Help
Tutorials
FORMAT
PDF
Web pages
PDF
2.7 Assumptions and Dependencies
It is assumed that :
1. User has the basic knowledge of mobile.
2. signal connectivity is intermittent in the system(mobile).

8. Software requirement specificaions
Page |8
SYSTEM FEATURES
3.1 System Features
PC:Thisunit containsthesoftwarecomponentssuch
astheHACSSystemthroughwhichtheappliancesarecontrolled and homesecurityismonitored.
GSMModem:Itisahardwarecomponentthatallowsthecapability
tosend
receiveSMStoandfromthesystem.Thecommunication
withthesystemtakesplaceviaRS232serialport.Cellphonecan
beattachedattheplaceofGSMhardwarebutitlimitsthehardwarefunctionalitysuchassending
orreceivingofSMS.
and
MobileDevice:Cellularphonecontaining SIMcard hasaspecificnumberthroughwhichcommunication
takesplace.ThedevicecommunicateswiththeGSMModemviaradiofrequency.MobileusertransmitsS
MSusingGSMtechnology.
3.2Functional Requirements
The following is a list of functional requirements of the control unit/module.
a. The control unit will have the ability to connect to the cellular network automatically.
b. The control unit will be able to receive text messages and will be able to parse and interpret
text messages and instructions to be sent to the microcontroller.
c. The microcontroller within the control unit will issue its command to the electrical
appliances through a simple control circuit.
d. The control unit will control the electrical appliances.

9. Software requirement specificaions
Page |9
EXTERNAL INTERFACE REQUIREMENTS
4.1 User Interfaces
Message send by the user will received by the gsm module and the acknowledgment send back to
the user mobile.
4.2 Hardware Interfaces
PC:Thisunit containsthesoftwarecomponentssuch
astheHACSSystemthroughwhichtheappliancesarecontrolled and homesecurityismonitored.
GSMModem:Itisahardwarecomponentthatallowsthecapability
tosend
receiveSMStoandfromthesystem.Thecommunication
withthesystemtakesplaceviaRS232serialport.Cellphonecan
beattachedattheplaceofGSMhardwarebutitlimitsthehardwarefunctionalitysuchassending
orreceivingofSMS.
and
MobileDevice:Cellularphonecontaining SIMcard hasaspecificnumberthroughwhichcommunication
takesplace.ThedevicecommunicateswiththeGSMModemviaradiofrequency.MobileusertransmitsS
MSusingGSMtechnology.
4.3 Software Interfaces
The software for our project was developed using a simple high level language tool in C. The
software extracts the sent message from the SIM location at a regular interval and processes it to
control the different appliances connected within the interface. We have made use of the Nokia FBus protocol to communicate with the mobile phone set. Most Nokia phones have F-Bus and M-Bus
connections that can be used to connect a phone to a PC or in our case a microcontroller. The
connection can be used for controlling just about all functions of the phone, as well as uploading
new firmware etc. This bus will allow us to send and receive SMS messages
4.4 Communications Interfaces
Communication Protocols: The available communication protocol that we have used is SMS. The
SMS is the most efficient because this project requires a cellular communication and limited data
to be sent.

10. Software requirement specificaions
P a g e | 10
OTHER NON FUNCTIONAL REQUIREMENTS
5.1 Performance Requirements
Performance is measured in terms of the output provided by the application. Requirement
specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into required
environment. It rests largely in the part of the users of the existing system to give the requirement
specifications because they are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system once it has been
designed and on the other hand designing a system, which does not cater to the requirements of
the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system
The system should be accurate
The system should be better than the existing system
5.2 Safety Requirements
This application require the Internet availability, and is also requires that the user should keep his
phone safe and secure and the same should not beshared with any one.
5.3 Security Requirements
User should keep his phone safe. The system or the place where the key is
stored should not be public. In the case if the user loses his phone then he/she should immediately
cancel the sim connection.
5.4 Software Quality Attributes
The user interface of SYSTEM is to be designed with usability as the first priority. The SYSTEM will
be presented and organized in a manner that is both visually appealing and easy for the user to

11. Software requirement specificaions
P a g e | 11
navigate.
OTHER REQUIREMENTS
1.Hardware Tester:
Device which is used to check wheather the hardware is in running
mode.
2.Signal Booster:
Device which helps to increase signal strength of the network.

12. Software requirement specificaions
APPENDIX A:GLOSSARY
Short Message Service Center (SMSC)
Global System For Mobile Communication(GSM)
P a g e | 12

13. Software requirement specificaions
P a g e | 13
Appendix B:Analysis Model
Security
system
Lamp
Issue
Send
Send
Message
Cell
Phone
GSM
Chip
Message
Command Appliances
Microcontroller
Instructions
Communicate with
network
Transfer data to
• Send Text
Message
microcontroller
Perform
Required
Fan
Decode incoming
message
Send instruction to
appliance
Monitor completion

14. Software requirement specificaions
P a g e | 14
Appendix C:Issues List
By using any other device instead of GSM then their will be a distance limit between the
remote device and kit.With the help of GSM module we can control device from anywhere.

15. Software requirement specificaions
P a g e | 15