Sre Document

FROM: M ZAIN UL ABIDEEN KHAN (211346)

ALI ANWAR (211969)

SECTION: BSSE-3-A

SUBJECT: SOFTWARE REQUIREMENT ENGG

TO: SIR AZHAR IMRAN

DATE: 16/12/2022

Page | 1
Table of Contents
Executive Summary ................................................................................................. 4
1. Introduction ...................................................................................................... 5
1.2 Relevance to Course Modules .......................................................................... 5
1.3 Project Background....................................................................................... 6
1.4 Literature Review ......................................................................................... 7
1.5 Analysis from Literature Review ...................................................................... 7
1.6 Methodology and Software Lifecycle for This Project Methodology ........................ 7
2. Functional Requirements .................................................................................. 8
3. Non-Functional Requirements ............................................................................ 9
4. Diagrams ..................................................................................................... 10
1. Data Flow Diagram (DFD Level-1) ....................................................................... 10
2. Activity Diagram .............................................................................................. 11
1. Setup Personal information .................................................................................. 11
2. Add Emergency Contact ................................................................................... 12
3. Nearby Services .............................................................................................. 13
4. Maintain Emergency Information ........................................................................ 14
5. Trigger emergency Function ............................................................................... 15
6. Add Emergency Massage .................................................................................. 16
3. Sequence Diagrams ........................................................................................... 17
1. Setup Personal Information .................................................................................. 17
2. Add Emergency Contacts .................................................................................. 18
3. Add Emergency Message .................................................................................... 19
4. Nearby Services ................................................................................................ 20
5. Trigger emergency Function ................................................................................. 21
4. Class Diagram.................................................................................................. 22
5. Detailed Use Case .......................................................................................... 23
6.1.1. Purpose: ................................................................................................. 24
6.1.2. Project overview: ..................................................................................... 25
7. Test Plan Strategy ............................................................................................ 26
7.1. Unit Testing ............................................................................................... 26
7.2. Integration Testing ...................................................................................... 26
7.3. System Testing ........................................................................................... 26
8. Test Environment ............................................................................................. 27
8.1. Hardware .................................................................................................. 27
8.2. Software.................................................................................................... 27
9. Schedule.......................................................................................................... 27
11. Functions to be tested .................................................................................... 28
12. Functions not to be tested ............................................................................. 28

Page | 2
12.1. Test Case for Setup Personal Information................………………………………..28

12.2. Test for Add Emergency……………………………………………………………......29

12.2. Test for Add Emergency……………………………………………………………….30

12.4. Test case for Emergency Condition Trigger Function………………………………31

12.5. Test case for Send Message or Call……………………………………………………32

12.6. Test case for Nearby Hospitals…………………………………………………………33

12.7. Test case for Access Location…………………………………………………………34

12.8. Test case for Emergency Location History…………………………………………….35

12.9. Test case for Message Receive by Emergency Contacts, Helping Organizations…..36

12.10. Test case for User Information………………………………………………………..37

Page | 3
Executive Summary

In present world a lot of emergency cases like rape, accident on road, trapped in fire and many more
situations where a person can require help from other people and some organizations that provide
help in emergency condition (Like Rescue 1122 ambulance). More dangerous situations occur when
person is unconscious or not able to take action against emergency for example in road accident a
person injured and not able to use their phone to call help to escape from emergency. Many different
applications provide the service to help in the emergency conditions but they have some sort of
limitations like working when a user interact with them and request for help. But these limitations
create difficulties for the victims to get help. This system will cover all remaining causes,
requirements, drawbacks, limitations and disadvantages. For example, if a victim required help in
emergency then system detect the emergency condition by fall detection of mobile and automatically
send helping SMS or Call (specified user) and current user location to listed contacts. User will list
their trusted helping contacts and also list if they required help from organizations (e.g. Rescue 1122).
The main feature of this system is detecting emergency condition automatically by fall detection, jerk
detection of mobile. User will select the one of these detection methods to detect the emergency
condition and set an emergency alarm with time interval to call help. User will also see the current
location and nearby hospital, ambulance service Etc. By implementing this system, we will help the
user easily, quickly and possibility of minimizing these situations in Pakistan.

Page | 4
1. Introduction
1.1 Brief

Emergency cases are spread over the whole country. Many applications are developed that are providing
help to persons that are in emergency conditions but there are some limitations like they give response
when user interact with these applications and ask for help. These limitations create difficulties for peoples
when they need help. Some time they are not able to interact with these applications for getting help in
some critical conditions like road accident, trapped in fire and many other such critical conditions. So
problem is that what people should done for getting help in such critical conditions. The system which
we are going to develop will cover all these limitations like causes, drawbacks. For example, if a person
required help in emergency condition then system detect the emergency condition by fall detection of
your device and automatically send helping massage with current location to listed contacts that are stored
in application by user. User will be entered phone numbers of their trusted people like family members,
relatives, and people that come in friend zone.

Moreover, the idea of the emergency mobile application that we develop in this project is quick, easy and
effective. For example, the user wants to operate the apps, they use fall detection in order to activate all
the function in the apps. This will make the user feel easy, effective and less burden when they need to
operate the apps, because fast and quick is the most important things during emergency situation. The
basic concept of the mobile application that we develop in this project will be like when the user clicks
and enter in first time the apps will pop-up a screen and ask user to register some personal information.
The personal information will include the name of the user, date of birth, identity number, personal contact
number, address and some personal message. Besides, the apps will need some emergency contact number
from user. The contact number can be the relative of the user or even the friend of the user. The apps use
sends all the information or even call the emergency contact during the emergency situation. To trigger
the emergency function of application user use, fall detection, jerk detection of phone.

1.2 Relevance to Course Modules

Some of our Degree courses are Related to our project that are following:

Table 1: Courses Relevance to Project

Course Name Project Relevance Description
Software Requirement Engineering We use different technique to get the user
requirements for our project requirement
that we study in our SRE course.

Database We use SQLite database for our project to store

project data that uses the knowledge of database
course.

Page | 5
Object-Oriented Programming We use Class and Other OOP concepts that uses the
Knowledge of OOP course.
Data Structure We use List, Array in our project that we study in
our Data structure.
Algorithms and Data Structure We use Algorithm technique for our project module
“fall detection” that we study in our Algorithms and
Data Structures course.

Human Computer Interaction We use Best techniques to make our project user
interface more user friendly.

1.3 Project Background

In present world a lot of emergency cases like rape, accident on road, trapped in fire and many more
situations where a person can require help from other people and some organizations that provide help in
emergency condition (Like Rescue 1122). More dangerous situations occur when person is unconscious
or not able to take action against emergency for example in road accident a person injured and not able to
use their phone to call help to escape from emergency. People face trouble due to of these cases. These
cases in present word are major issues that should need to be minimized. Problem is that how people get
out from these situations, and get a quick help from their trusted contacts and helping companies. In
Pakistan the occurrence of these cases is very high and there is no such a method or systems that provide
help in these kinds of situations to help the victims.

Many different applications provide the service to help in the emergency conditions but they have some
sort of limitations like working when a user interact with them and request for help. But these limitations
create difficulties for the victims to get help. This system will cover all remaining causes, requirements,
drawbacks, limitations and disadvantages. For example, if a victim required help in emergency then
system detect the emergency condition by fall detection of mobile and automatically send helping SMS
or Call (specified user) and current user location to listed contacts. User will list their trusted helping
contacts and also list if they required help from organizations (e.g. Rescue 1122). The main feature of this
system is detecting emergency condition automatically by fall detection, jerk detection of mobile. User
will select the one of these detection methods to detect the emergency condition and set an emergency
alarm with time interval to call help. User will also see the current location and nearby hospital, ambulance
service Etc. By implementing this system, we will help the user easily, quickly and possibility of
minimizing these situations in Pakistan.

Page | 6
1.4 Literature Review
Table 2: Related System Analysis for Proposed Project

Rescue 1122 Weaknesses may include This system works

activation of app when automatically by fall
emergency occurred, not detection, jerk detection
work automatically by fall
detection
Mohafiz App (2019) Not work on fall detection This system works

automatically by fall
detection, jerk detection
Seizario App Work only for UK, USA Work for Pakistan

1.5 Analysis from Literature Review

❖ ADVANTAGES/BENEFITS OF PROPOSED SYSTEM

1. Users don’t need to active or open this app when an emergency condition to get the help.
2. User will get the help at current location quickly

3. If user phone lost or fall, then user receive the location where their phone lost and find easily
4. Automatically Call and SMS

5. Easy to use

1.6 Methodology and Software Lifecycle for This Project Methodology

Figure 1: Incremental model

Page | 7
The software methodology that is used for this project is Iterative and Incremental development.
Iterative and incremental development is the method that uses to produce a good quality and reliable
system. This model allows the developer to increase the functionality of the system in the increment way.
Basically, this method has divided into two approaches 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 time 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 is 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 fulfilling the user requirement.

1.6.1 Rationale behind Selected Methodology

Because the method allows the emergency mobile apps add new feature in anytime. the method allows
the developer to design and testing the emergency call mobile application in an incrementally way. For
example, during each iterative process some of the feature and the function of the system will be added
or modify

2. Functional Requirements

UR1: User will enter his/her personnel information at first login.

UR2: User will enter person’s contacts for getting help from these persons at emergency condition.

UR3: User will be entering their own emergency massage also if he/she will not agree to send app default
Message

UR4: Emergency function is trigger by fall, jerk detection and panic button.

UR5: User will send message to their emergency contacts and as well as helping organizations.

UR6: User will able to search the nearby hospitals and dispensaries, first aid center etc.

Page | 8
UR7: Accessing their current location and share with their emergency contacts and helping
organization in emergency condition.
UR8: User will able to see their emergency condition location history

3. Non-Functional Requirements

3.1.Reliability
Application will be installed on mobile devices; it does not need to Internet connection to run. It shall
be available in 24 hours a day, 7 days of a week on mobile device. Our application will deliver
messages to the intended recipient(s), and then it will check if it is not sent then it will resend the
message.

3.2.Supportability
Programming language used in this project is object-oriented so that the tasks are independent of each
other and therefore easy to maintain.
• The codes must be easy to understand and readable.
• All design architecture should be well documented.

3.3. Maintainability
If system detect wrong pattern of fall then it must return to main or abort the emergency condition.

3.4.Portability
This application is Android Based so it easily run on all type of android systems.

3.5. Extensibility
Easy to adapt the new kind of detection method if added to the system.

3.6.Response Time
Because this application is helping in emergency condition so it’s faster work and response to active
emergency condition function is also fast.

Page | 9
3.7. Availability
This system is life helping system so its available 24x7.

3.8. Resource Utilization

This system uses the less resources to performed their work efficiently, like I use less memory to
compute the fall detection formulas

3.9.Reusability
We will use object-oriented language to code this project so its code component is reusable

4. Diagrams
1. Data Flow Diagram (DFD Level-1)

Data Flow Diagram (Level-1)

Page | 10
2. Activity Diagram

1. Setup Personal information

Activity Diagram for setup personal information

Page | 11
2. Add Emergency Contact

Activity Diagram for Add contacts

Page | 12
3. Nearby Services

Activity Diagram for Nearby Services

Page | 13
4. Maintain Emergency Information

Activity Diagram for Emergency Information

Page | 14
5. Trigger emergency Function

Activity Diagram for Trigger emergency function

Page | 15
6. Add Emergency Massage

Activity Diagram for save massage

Page | 16
3. Sequence Diagrams

1. Setup Personal Information

Sequence diagram of Setup Personal Information

Page | 17
2. Add Emergency Contacts

Sequence diagram of Add Emergency Contacts

Page | 18
3. Add Emergency Message

Sequence diagram of Add Emergency Message

Page | 19
4. Nearby Services

Sequence diagram of Nearby Services

Page | 20
5. Trigger emergency Function

Sequence diagram of Trigger Emergency Function

Page | 1
4. Class Diagram

Class Diagram

Page | 2
5. Detailed Use Case

Page | 3
Table 3: Setup Personal Information
Use Case ID: UC-1
Use Case Setup Personal Information
Name:
Actors: Primary actor: User
Description: User accesses the system from the mobile, setup their personal
information that use in emergency condition.
Trigger: User wants to enter Personal information one time to access the
application.
Preconditions:
Post POST-1. User access to the application.
conditions: POST-2. User Personal information saved permanently in application.
Normal Flow: 1. User open the application interface.
2. Application displays the form of setup Personal information.
3. User enter Personal information
4. Application display the message “successfully Setup”.
5. The Main screen of application is displayed
Alternative No alternate flow.
Flow:
E1. if user already setup personal information then:
1. System will skip step 2,3,4 and reached at step 5
Exceptions: E2. If user enter wrong name, phone number or blood group then:
1. System will automatically display a error massage to show the
missing required valid information.
Business Rules User have to enter valid Name, phone number, blood group.

Assumptions: Assume that user not know their blood group correctly

Table 4: Add Emergency Contacts

Use Case ID: UC-2
Use Case Add Emergency Contacts
Name:
Actors: Primary actor: User
Description: User accesses the system from the mobile, and select the add emergency
contact, add the new contacts.
Trigger: User indicates that he/she wants to add the Emergency Contacts.
Preconditions: PRE-1. User must have setup Personal information first.
Post conditions: POST-1. User can add the Emergency Contacts.
Normal Flow: 1. User open the application
2. User open setting.
3. select personal information
4. chose add emergency contacts button
5. add the emergency contacts in list
7. Application display the list of added emergency contacts.
Alternative No alternate flow.
Flow:

Page | 4
E1. User will enter wrong number or number from outside the country
then:

1. System will not add the number and notify the user by message to
enter correct number.
2. If attempt to save number forcefully then system terminate this use
case.
E2. User will exceed the fixed number of adding contacts then:
Exceptions: 1. System will notify the user by message that contact list is full.
Business Number is must be valid and must from Pakistani Networks
Rules
Assumptions: Assume that user will enter PTCL number that is not allowed.

Table 5: Add emergency Massage

Use Case ID: UC-3
Use Case Add emergency Massage
Name:
Actors: Primary actor: User
Description: User accesses the system from the mobile, select the setting, enter the
Emergency message.
Trigger: User indicates that he/she wants to enter emergency message.
Preconditions: PRE-1. User must have setup Personal information first.
Post conditions: POST-1. User can add the Emergency message.
Normal Flow: 1. User open the application
2. User open setting.
3. select personal information
4. chose add emergency contacts button
5. add the emergency contacts in list 6. Application show message
“successfully added”.
7. Application display the list of added emergency contacts.
Alternative No alternative flow.
Flow:
E1. If user enter more words then fixed number of words then:
Exceptions: 1. System will show an error message to notify that you exceeded the
words limit.
2. System stop taking words input from user.
Business Rules Message will be not more than 60 words.
Assumptions: Assume that user message is more than 60 words and its compulsory by
user to add the same length of message

Table 6: Emergency Condition Trigger Function

Use Case ID: UC-4
Use Case Emergency Condition trigger function
Name:
Actors: Primary actor: User Secondary actor: Emergency help application
(E- Help)
Description: User trigger the emergency function through fall detection, jerk
detection and panic button. Application detect these one of the methods
to activate the application emergency function.
Trigger: User indicates that he/she wants to activate the emergency function.
Page | 5
Preconditions: PRE-1. User must have knowledge of how these detection methods work
to activate the application method.
Post conditions: POST-1. Emergency function is triggered.
Normal Flow: 1. User do one these detection methods (Fall detection, jerk detection,
panic button) to activate the application.
2. Application detect these methods and activate the emergency
condition function.

3. Application display the emergency condition alarm for some

interval of time.
4. if user cancel this alarm this application close.
5. is user not cancel then application send message to contacts.

Alternative No alternate flow.

Flow:
E1. User wrongly trigger function by panic button.
1. System will display an emergency condition alarm for some time that
Exceptions: help to user to cancel this use case.
Business Rules Must be one method is required to trigger this use case or function.
Assumptions: Assume that an emergency condition occurs but not trigger this function.

Table 7: Send Massage or Call

Use Case ID: UC-5
Use Case Send Message or Call
Name:
Actors: Primary actor: Emergency help application Secondary actor: User
Description: System will send message or call automatically when emergency
condition function is triggered to the added contacts and helping
organizations.
Trigger: User indicates that he/she wants to send message or call to contacts and
helping organizations in emergency condition.
Preconditions: PRE-1. Personal information is given.
PRE-2. Emergency contacts is added.
PRE-3. Emergency function is triggered.
PRE-4. Balanced is required for call.
Post conditions: POST-1. User will send message or call to the listed emergency contacts
and helping organizations.
POST-2. emergency contacts and helping organizations received user help
message

Page | 6
Normal Flow: 1. Emergency function is triggered by (Fall detection, jerk detection,
panic button).
2. System will detect the trigged function.
3. system will collect user added number for message or call form
system
Database and current location of user.
4. show an emergency alarming message for some time, and then
send
the message to the
contacts.
5. After call the helping organization if user select the call option.
But
first check Balance in
phone.
6. Call is placed.

If user cancel the alarming message then

Alternative 1. System will terminate this message and close this use case by skip
Flow: step 4,5,6

Exceptions: E1. If user not add his own emergency message then: 1.
System will use default message write by system.

Business Rules 1. Balance is required for call.

2. Emergency contacts is must added first.
Assumptions: Assume that SIM balanced is zero that used for call

Page | 7
Table 8: Nearby Hospitals
Use Case ID: UC-6
Use Case Nearby Hospitals
Name:
Actors: Primary actor: User
Description: User accesses the system from the mobile, user will search the nearby
hospitals and dispensaries, first aid center etc., in case of minor
emergency.

Trigger: User indicates that he/she wants to search nearby hospitals and
dispensaries, first aid center etc.
Preconditions: PRE-1. Internet connection is required.
PRE-2. User current location is required.
Postconditions: POST-1. User can see the list of nearby hospitals.
POST-2. User will see this list on Map and see their current position.
Normal Flow: 1. User open the application
2. Application display the main screen of application.
3. User select the icon of search nearby.
4. Application access the user current location.
5. Application search the nearby hospitals according to the user
current location.
6. Application display the list of nearby hospitals.
7. Application map this nearby location on MAP and also show user
current location.
Alternative No alternate flow.
Flow:
E1. If user internet is not available then:
1. System will display message of unavailable of internet. E2.
Exceptions: If user location system is off then:
1. system will show message to on the location of the phone.
Business Rules 1. User must need internet connection to search nearby hospital.
2. User must have access to their current location.
Assumptions: Assume that user have not a internet connection.

Table 9: Access Location

Use Case ID: UC-7
Use Case Access Location
Name:
Actors: Primary actor: User, Helping Organization, Emergency contacts
Description: Accessing user current location where the emergency condition is
occurred.
Trigger: User indicate that he/she want to share his current location in emergency
condition.
Preconditions: PRE-1. Emergency function is triggered.
PRE-2. Location services is on in phone.
Postconditions: POST-1. System will access the user location and share with user.
Normal Flow: 1. Emergency function is triggered by (Fall detection, jerk
detection, panic button).

2. System will detect the trigged function.

3. system will collect user added number for message or call form
system
Database and current location of user.
4. show an emergency alarming message for some time, and then
send the message with user current location to the Emergency contacts
and helping organizations.
5. Emergency Contacts and helping organizations use this message
location to locate the user for help them.
If user cancel the alarming message then
1. System will terminate the message and close this use case by skip step
Alternative 4,5
Flow:
E1. If user location system is off then:
Exceptions: 1. system will show message to on the location of the phone
Business Rules User phone GPS system is on.
Assumptions: Assume that user phone not support GPS system.

Table 10: Emergency Location History

Use Case ID: UC-8
Use Case Emergency location history
Name:
Actors: Primary actor: User
Description: User will able to see their emergency condition history where the
emergencies occurred.
Trigger: User indicate that he/she want to see the emergency history.
Preconditions: PRE-1. History list is not empty.
Postconditions: POST-1. User will see the history of emergency conditions.
Normal Flow: 1. User open the application
2. Application display the main screen of application.
3. User select the icon of emergency Location history.
4. see the all emergencies that is occurred in past.
Alternative No alternate flow.
Flow:
E1. If no emergency is occurred then:
Exceptions: 1. system will show empty list and message that no emergency was
occurred.
Business Rules
Assumptions: Assume that system accidently not save the history.

Table 11: Massage Receive by Emergency Contacts and Helping Organizations

Use Case ID: UC-9
Use Case Message receive by Emergency contacts and helping organizations.
Name:
Actors: Primary actor: Helping Organization, Emergency contacts
Description: Helping Organization, Emergency contacts received a message of help
from the user
Trigger: Helping Organization, Emergency contacts indicates that they want to
check user current location to rescue them.
Preconditions: PRE-1. Helping Organization, Emergency contacts Must be added
in user emergency contact list.

Postconditions: POST-1. Helping Organization, Emergency contacts help the user.

Normal Flow: 1. Helping Organization, Emergency contacts open the message location
2. open the location on the map
3. and reached to the user to rescue them
Alternative No alternate flow.
Flow:
Business Rules Helping Organization, Emergency contacts must be added in user
emergency contact list.
Assumptions: Assume that Helping Organization, Emergency contacts is not in user
emergency list and not receive message.

Table 12: User Information

Use Case ID: UC-10
Use Case User Information
Name:
Actors: Primary actor: Helping Organization, Emergency contacts.
Description: Helping Organization, Emergency contacts received user information by
message of help from the user
Trigger: Helping Organization, Emergency contacts indicates that they want to
check user information.
Preconditions: PRE-1. Helping Organization, Emergency contacts Must be added
in user emergency contact list.

Postconditions: POST-1. Emergency contacts and helping organizations get the user
information.
Normal Flow: 1. Helping Organization, Emergency contacts open the message
send by the user.
2. get the user information.
Alternative No alternate flow.
Flow:
Exceptions: E1. If user not share their information then:
1. message will contain only user location
Business Rules Helping Organization, Emergency contacts must be added in user
emergency contact list.
Assumptions: Assume that user not share information.

6. Test Case Document

6.1. Introduction

llllllllllllll

6.1.1. Purpose:

This system will cover all remaining causes, requirements, drawbacks, limitations and disadvantages. For
example, if a victim required help in emergency then system detect the emergency condition by fall detection
of mobile and automatically send helping SMS or Call (specified user) and current user location to listed
contacts. User will list their trusted helping contacts and also list if they required help from organizations (e.g.
Rescue 1122). The main feature of this system is detecting emergency condition automatically by fall detection,
jerk detection of mobile. User will select the one of these detection methods to detect the emergency condition
and set an emergency alarm with time interval to call help. User will also see the current location and nearby
hospital, ambulance service Etc. By implementing this system, we will help the user easily, quickly and
possibility of minimizing these situations in Pakistan.
6.1.2. Project overview:

Many different applications provide the service to help in the emergency conditions but they have some sort
of limitations like working when a user interact with them and request for help. But these limitations create
difficulties for the victims to get help. This system will cover all remaining causes, requirements, drawbacks,
limitations and disadvantages.

For example, if a victim required help in emergency then system detect the emergency condition by fall
detection of mobile and automatically send helping SMS or Call (specified user) and current user location to
listed contacts. User will list their trusted helping contacts and also list if they required help from organizations
(e.g. Rescue 1122). The main feature of this system is detecting emergency condition automatically by fall
detection, jerk detection of mobile.

User will select the one of these detection methods to detect the emergency condition and set an emergency
alarm with time interval to call help. User will also see the current location and nearby hospital, ambulance
service Etc. By implementing this system, we will help the user easily, quickly and possibility of minimizing
these situations in Pakistan.
7. Test Plan Strategy

7.1. Unit Testing

Definition:

Unit Test consists of testing individual programs or subroutines as they are written instead of
testing the entire system after it has been written. The testing of the smaller building blocks is done
first and then these blocks are combined and tested. Unit testing means testing each function
independently to verify correct processing in a stand-alone environment. Testing each module
individually. Follows a white box testing. It is a testing method using which every independent
module is tested to determine if there are any issue.
Participants:
Zain ul Abideen Khan 211346
Ali Anwar 211969

Methodology:
1. Initial Unit Test will be conducted by the developers.
2. As the completed modules are received from the development department, the test team
will start the Unit Test on these modules.

7.2. Integration Testing

Definition:
It is any type of software testing that seeks to verify the interfaces between components against a
software design. Software components may be integrated in an iterative way or all together.
Normally the former is considered a better practice since it allows interface issues to be localized
more quickly and fixed.

Participants:
Zain ul Abideen Khan 211346
Ali Anwar 211969

Methodology:
1. Initial integration testing will be conduct by the developers
2. As the developer did the initial testing, the testing team test the all module that
integrated by the developers

7.3. System Testing

Definition:
System testing is defined as testing of a complete and fully integrated software product. This
testing falls in black-box testing wherein knowledge of the inner design of the code is not a pre-
requisite and is done by the testing team. System Testing verifies that a system is integrated to any
external or third-party systems defined in the system requirements
Participants:
Zain ul Abideen Khan 211346
Ali Anwar 211969

Methodology:
1. After the all testing unit and integration testing we will give our project to third part
2. The third party test the whole project
3. After the checking from the third party the testing all most complete.

8. Test Environment
8.1. Hardware
 Ram 512MB
 Hard Disk Space 10 GB (min.)

8.2. Software
 Resolution (for graphics)1366*768 (32bit)
 Operating system: Windows XP/Windows 7/ Windows 8 Processor:
Pentium- II or higher
 Browser Firefox/Google chrome/internet Explore 8/Safari
 Apache server 1.8.2
 SQLite database Server 5.5
 IDE: Adobe Dreamweaver

9. Schedule

Testing Activities Begin End

Designing Test Cases 02-12-2022 08-12-2022

Executing Test Cases 09-12-2022 10-12-2022
Unit Testing 11-12-2022 12-12-2022
Integration Testing 13-12-2022 14-12-2022
System Testing 15-12-2022 16-12-2022
10.Control Activities
Three meetings for the reviews
1st Meeting
The designing of the test cases will be discussed and reviewed. Furthermore, Execution of test
cases will be discussed.

2nd. Meeting
When unit and integration testing will be completed. In this meeting all the
developers and testing team member will have gathered. In this meeting all the errors and
mistake will be discussed. If there are many mistakes, then we will design new test cases.

3rd. Meeting
After the all testing like system, unit etc. All the member of project team will be gathered and
discuss all the issue about the testing. In this session we shall check all the errors and their
reason. If something will be going wrong, then one time again we shall check the code of error.

11. Functions to be tested

11.1. Setup Personal Information.

11.2. Display personal information.
11.3. Edit personal information.
11.4. Edit personal information.
11.5. See Nearby Hospital Services.
11.6. Check History of emergency conditions.
11.7. Add/update/delete emergency message.

12. Functions not to be tested

There are no any functions that are not tested.

Following scheme is recommended for listing and description of requirements to be tested: