COMSATS University Islamabad,

COMSATS Road, off GT Road, Sahiwal, Pakistan

SOFTWARE DESIGN
DESCRIPTION
(SDD DOCUMENT)

for

<PROJECT NAME>
Version 1.0

By
Student Name 1 CIIT/SP09-BCS-xxx/SWL

Student Name 2 CIIT/SP09-BCS-xxx/SWL

Supervisor
Supervisor Name

Bachelor of Science in Computer Science (20xx-20xx)

 Table of Contents
Revision History ........................................................................................................................... 38
1. Introduction ............................................................................................................................ 40
2. Design Methodology and software process model .............................................................. 40
3. System Overview .................................................................................................................... 40
3.1 Architectural Design .................................................................................................................. 40
3.2 Process Flow/Representation ..................................................................................................... 40
4. Design Models [along with descriptions] ............................................................................. 40
5. Data Design ............................................................................................................................. 41
5.1 Data Dictionary ......................................................................................................................... 41
6. Algorithm & Implementation ............................................................................................... 41
7. Software Requirements Traceability Matrix ...................................................................... 41
8. Human Interface Design........................................................................................................ 42
8.1 Screen Images ............................................................................................................................ 42
8.2 Screen Objects and Actions ............................................................................................................. 42
9. Appendix I .............................................................................................................................. 42

----------------
 Revision History
Name Date Reason for changes Version
 Application Evaluation History

Comments (by committee) Action Taken

*include the ones given at scope time both in doc and
presentation

Supervised by
<Supervisor’s Name>

Signature______________
Introduction
Emergency help mobile application will work like an emergency pocket assistant to help people
during the urgent situation. The idea for this application is easy and effective. The basic concept
of this mobile application is, when the user get into the emergency situation this application
automatically fall detection of their phone in order to activate all the emergency function inside
the app, and then the function will help the user to look for help or tell someone about the current
user situation in a short period of time. The emergency function will be sent emergency message,
personal information and GPS location through SMS to particular contact, and also time interval
function, phone call function besides, the user also can trigger the emergency function by
automatically fall detection of mobile phone.

Modules

1. Fall detection
2. Jerk Detection
3. GPS Location
4. Nearby Hospital and Ambulance
5. SMS

Design methodology and software process model

Methodology

The software methodology that are used for this project is Iterative and incremental
development. Iterative and incremental development is the method that use to produce a good
quality and reliable system. This model allow the developer to increase the functionality of the
system in the increment way. Basically, this method has divided into two approach which is
iterative and incremental approach.
In iterative approach the author can choose to review or redesign part of the system and
improve some of the feature in order to make the system become better. For instance every
times the developer review or revisit the system, some modification or improvement will be
made in that iteration. By the way, the developer can get user feedback in order to make quality
improvement for the system.
In incremental approach the developer are develop and analyses the system many times at
different portion, each times the new feature of the system will be add incrementally until the
whole system is finish developed. Besides, the system design, testing and implement also will
perform incrementally until the system is done. In the end of the development the author will
check the system completion and make sure it is fulfil the user requirement.
The reason that choosing this methodology
Because the method allow the emergency mobile apps add new feature in anytime.

3: System overview
The basic concept of this mobile application is, when the user get into the emergency situation
this application automatically fall detection of their phone in order to activate all the emergency
function inside the app, and then the function will help the user to look for help or tell someone
about the current user situation in a short period of time. This system is beneficial for all the
people that want to ensure their safety and the people who want to inform their current
condition in emergency cases by sending helping massage with location.

3.1: Architectural design

3.2: Process flow/Representation

3.2.1: Setup Personal information

 Activity Diagram for setup personal information

When the user open application than check if personal information is already setup after than the system
will end the task, if personal information is not already setup then will proceed to setup personal
information, after finish setup personal information will proceed to add emergency contact and
emergency message, after done all the setup the system will save the all information to particular
database.

3.2.2: Add Emergency Contacts

 Activity Diagram for Add contacts

First user open the application and check the limit of contacts if there are maximum number of
contacts are added then system will end the task otherwise system allow the user to add contacts
that will use at emergency condition. After done enter the contact number, the system will save the
contact to the database.

3.2.3: Nearby Services

 Activity Diagram for Nearby Services

First user open the application and click nearby service button get user location if location not found
than system will end the task otherwise user get location of all nearby hospitals. After that user
select the hospital and show the location on map.

3.2.4: Maintain Emergency Information

 Activity Diagram for Emergency Information

User can edit all the information that he or she save at the previous time.
User can choose the edit option, after the editing the information the system will
update the information to particular database.

3.2.5: Trigger emergency Function

 Activity Diagram for Trigger emergency function

User open the application and system check any detection occur or not. If detection not detected than
system will end the task otherwise system check which detection take place (fall detection, jerk detection,
panic button).Then system will display alarm massage.

3.2.6: Add Emergency Massage

 Activity Diagram for save massage
First user open application and check that emergency massage already added or not if added then system
will exit the task otherwise user add emergency massage then user will enter the message such as “Please
help me!!!” that will send to emergency contact during the apps trigger moment. After done enter the
message, the system will save the message to the database table.

Design models [along with descriptions]

Sequence Diagrams
Sequence Diagram is the advance version of the Activity diagram. It will show each
of the process run in detail. The reason to choose Sequence Diagram is because it
will show user how the object deliver or send sequence message between each other.
1:Setup personal Information

This diagram is show detail process on how the user setup the personal information.
They can proceed to key in personal information, after done the system will call
addUserInformation () function to save the information. Then, the system will
proceed to key in emergency contact, after done key in everything the system will call
addEmergencyContact () function to add the contact number. Now, proceed to last
setup which is add emergency message, the system will call addEmergencyMessage
() function to add the message, after the user done key in the help message.
2: Add Emergency Contacts

This diagram show the detail view of add emergency contact process. The user can
enter the contact number, the system will call addEmergencyContact () function to
add the contact number to the system.
3: Add Emergency Massage

This diagram show the detail view of add emergency message process. The user can
key in the important message, the system will call addEmergencyMessage () function
to add the message to the system.
4: Nearby Services

This diagram show the detail view to check nearby services like hospital and ambulance. The user can the
system will choosenearbyservices () function to get help from nearby services.
5: Trigger emergency Function

This diagram show detail on the process of setup emergency trigger function. The
user can choose which option they want to perform, the option will be active Jerk
detection, active Fall Detection and active panic button. The system will call the
updateFunctionStatus () function to update the function status when the user to the
particular option.
6: Maintain Emergency Information

This diagram show the process of maintain emergency information in detail. The
user can edit all the information if they want to. The user can edit the personal
information, emergency contact and emergency message. After done editing the
information the system will call the edit () function to update the database table.
Different information have their own edit () function.
Class Diagram
Data design
This application(E-Help) use personal data and emergency message to alarmed other listed helping contacts by the
user.so when user use this application then the user data like personal information, Emergency message, Emergency
Contacts are stored on device locally. Application store data locally because this application work offline so the user
data store on that device. Then this application accesses the user data quickly.
List of databases
Relational Database (Sqlite)

Data dictionary
We use the Object Oriented description so we listed object with its attributes ,method and
parameters of methods.

Algorithm & Implementation

The fall detection algorithm with utilize the accelerometer sensor that embedded in smartphone. The
accelerometer will generate three acceleration values ax, ay, az according to the axes as shown in
Fig. 4.

a√𝑎𝑥 2 + 𝑎𝑦 2 + 𝑎z 2 = √𝑎𝑥 2 + 𝑎𝑦 2 + 𝑎z 2

Software requirements traceability matrix

This section should contain a table that summarizes how each software requirement has been
met in this document. The tabular format permits one-to-one and one-to-many relationships to
be shown.

Table 7 Requirements Traceability Matrix

Req. Number Ref. Item Design Component Component Items
FR01 Class Diagram ClassName FunctionName(s)
 OR
FR01 DFD DiagramNumber/Level FunctionName(s)

Human interface design

Describe the functionality of the system from the Explain how the user‟s perspective. all the
user will be able to use your system to complete and the feedback expected features
information that will be displayed for the user.
Screen images
Display screenshots showing the interface from the user‟s perspective. These can be hand-
drawn, or you can use an automated drawing tool. Just make them as accurate as possible.
(Graph paper works well.)

8.2 Screen objects and actions

A discussion of screen objects and actions associated with those objects

Appendix I (For Help and General Knowledge)

 How to design using UML (OOP): For guidance please follow the instructions
mentioned in the link: http://agilemodeling.com/artifacts/

How and when to design ER diagrams: For guidance please follow the instructions
mentioned in the link:
http://people.inf.elte.hu/nikovits/DB2/Ullman_The_Complete_Book.pdf
 Data flow diagrams: For guidance please follow the instructions mentioned in the
link and book:
o http://www.agilemodeling.com/artifacts/dataFlowDiagram.htm
o Software Engineering –A Practitioner‟s approach by Roger Pressman
 Architecture diagram: For guidance please follow the instructions mentioned in the
link and book:
o Ian Sommerville – Software Engineering 9th Edition– Chapter 6