Charles Williams Systems Analysis, Design and Integration(IT425-1704B-02) IP2 Brian Rodgers 11/26/2017 Contents Introduction 2 Current business activities 2 Business rules 3 Entities & their relevant attributes 5 Entity list 5 Entity structures with relevant attributes: 5 Primary Keys & Foreign Keys 9 Data Definition Language implementations: 10 Relationship between all entities 15 Cardinality 16 Final ER Diagram 18 References 19 Introduction FHTS is a new and specialized travel agency who cater for Australian companies with high travel needs. Their market niche is in low cost business travel packages by airlines. They keep their prices low by dealing directly with the airlines, who provide combined cheap flights and accommodation. FHTS has several branches in different countries. Most branches are in Nepal on many states. Its dedicated employees are keen to prove the quality service often recommended by its customers. FHTS is well known for low airfare for both way routes services across domestic customers. Highly dedicated in customer services, FHTS offers several discount schemes for children and people with disabilities. FHTS has won multiple awards for its safety & reliability records of flying from national and international organizations. Due to its high reliability, safety records and highly gained trusts from customers, FHTS is having more transactions, causing day to day expanding business activities hard to manage its operations. To ensure more flexible service for customers, it’s highly recommended to implement and Airlines Reservation System, a computerized system that will help manage all information related to flight, passengers, their contact details, reservation, transactions, schedule publishing, air fare payments etc. Current business activities FHTS is operating on spot airline reservation, flight booking services with help of several travel agencies. It’s not only causing inconvenience for customers but also raises the actual tariff that customer has to pay. Though having branches in multiple cities targeting high range of customers, employee something fails to satisfy customers in remote areas when they have to travel for reservation also when they need to travel for cancellation or flight day extension. Followings are the key operations of Buddha Air’s day to day business: 1. Sales Transactions All sales transactions are related to flight ticket sales; advance reservations, reservation cancellations etc. a. Reservation FHTS provides flight pre-reservation to its customers. All customers are open to reserve flights to travel in future. Reservations are taken before 11 hour of flight. Pre-reservation insuring future sales forecast. b. Cancellation No hard rules, as far as company does not have to lose anything. A customer is always can cancel their flights. Cancelled seats are released for re-sell instantly. Company denies canceling a sold ticket, if cancellation request is made wit ...

1. Charles Williams
Systems Analysis, Design and Integration(IT425-1704B-02) IP2
Brian Rodgers
11/26/2017

2. Contents
Introduction 2
Current business activities 2
Business rules 3
Entities & their relevant attributes 5
Entity list 5
Entity structures with relevant attributes:5
Primary Keys & Foreign Keys 9
Data Definition Language implementations: 10
Relationship between all entities 15
Cardinality 16
Final ER Diagram 18
References 19
Introduction
FHTS is a new and specialized travel agency who cater for
Australian companies with high travel needs. Their market
niche is in low cost business travel packages by airlines. They
keep their prices low by dealing directly with the airlines, who
provide combined cheap flights and accommodation.
FHTS has several branches in different countries. Most
branches are in Nepal on many states. Its dedicated employees
are keen to prove the quality service often recommended by its
customers. FHTS is well known for low airfare for both way
routes services across domestic customers.
Highly dedicated in customer services, FHTS offers several
discount schemes for children and people with disabilities.
FHTS has won multiple awards for its safety & reliability
records of flying from national and international organizations.
Due to its high reliability, safety records and highly gained
trusts from customers, FHTS is having more transactions,
causing day to day expanding business activities hard to manage

3. its operations. To ensure more flexible service for customers,
it’s highly recommended to implement and Airlines Reservation
System, a computerized system that will help manage all
information related to flight, passengers, their contact details,
reservation, transactions, schedule publishing, air fare payments
etc.
Current business activities
FHTS is operating on spot airline reservation, flight booking
services with help of several travel agencies. It’s not only
causing inconvenience for customers but also raises the actual
tariff that customer has to pay. Though having branches in
multiple cities targeting high range of customers, employee
something fails to satisfy customers in remote areas when they
have to travel for reservation also when they need to travel for
cancellation or flight day extension. Followings are the key
operations of Buddha Air’s day to day business:
1. Sales Transactions
All sales transactions are related to flight ticket sales; advance
reservations, reservation cancellations etc.
a. Reservation
FHTS provides flight pre-reservation to its customers. All
customers are open to reserve flights to travel in future.
Reservations are taken before 11 hour of flight. Pre-reservation
insuring future sales forecast.
b. Cancellation
No hard rules, as far as company does not have to lose anything.
A customer is always can cancel their flights. Cancelled seats
are released for re-sell instantly.
Company denies canceling a sold ticket, if cancellation request
is made within 6 hour of flight.
2. Flight scheduling
Day to day flight scheduling, new flight arrangements according

4. to sales potentiality, flight departure delay decisions all takes
rooms in its daily flight scheduling activities etc.
3. Ticketing
On spot ticket sales, online reservation sales, urgent sales,
VVIP ticketing is done in its several branches, authorized
agents from different travel agencies.
Business rules
Quality services to customers aren’t possible with defined
business principles. FHTS has several business rules that apply
from its own staffs to third party sales agents and potential
customers. For each, business rules are as per listed below:
1. Customers
· They are welcome to those from different flight schedules
those are available throughout a day depending upon their
comfort, willingness and flexibility and of course upon flight
availability.
· All customers are required to submit valid contact details.
· All customers must reserve a flight to travel. No on the gate
sales are available. Also customers can’t buy tickets at airports,
instead they need to visit online store or a sales counter to get a
ticket or reserve for future plans.
· Full payments are necessary in-order to confirm a booking.
Yes, there can be several discounts schemes which can be
claimed by customers & is given upon proper alignment with
discount descriptions.
· Customers must be penalized for cancellation. How much
charges they have to pay, depends when they are canceling the
flights. If it’s before 11 hour of flight they need to pay 10% of
sales and if it’s within 11 hour of flight – 33.33% will be
deducted from actual sales amount.
· Customers can demand the cancellation & 100% refund of
flight is cancelled due to technical reason, bad weather.
· All customers are allowed up to 5 KG cargo free with each
ticket. Exceeding 5 KG causes the additional fees.
· Each customer is eligible for $20,000 life insurance.

5. · Wheel chairs & oxygen is available for special passengers.
2. Employees (including sales agents)
· All employees must be dressed according to company dress
code with an ID card, easily visible to guests.
· Employees are expected to be presence on their seat within
duty hours.
· All employees are assigned to serve client based on first come
first services. Yes- there is a provision for special cure for
urgent & national security matters.
· Employees are hereby responsible for serving customers first,
second their own jobs.
· Employees are not allowed to take flight reservations within
11 hour of flight.
Database Design for Airline ReservationEntities & their
relevant attributesEntity list
1. Aircrafts
2. Route
3. Airfare
4. Flight Schedule
5. Discounts
6. Charges
7. Countries
8. State
9. Contact Details
10. Passengers
11. Branches
12. Employee
13. TransactionsEntity structures with relevant attributes:
Aircrafts
Field
DataType
Description
Constraints
AcID

6. INT
Field will store unique row number.
Primary Key
AcNumber
Varchar(32)
Aircraft number that identifies the plane.
NOT ULL
Capacity
INT
No. of seats available.
NOT NULL
MfdBy
Varchar(128)
Manufacturing company.
NOT NULL
MfdOn
DATETIME
Manufactured date of aircraft.
NOT NULL
Route
Field
Data Type
Description
Constraints
RtID
INT
Stores unique row id.
Primary Key
Airport
Varchar(32)
From where the flight will take off.
NOT NULL
Destination
Varchar (32)
Flight destinations.

7. NOT NULL
Route Code
Varchar(16)
A unique Route code generated using Source & Destination of
flight.
NOT NULL
UNIQUE
AirFare
Field
Data Type
Description
Constraints
AfID
INT
Stores unique row id.
Primary Key
Route
INT
Route id from Route table.
Foreign Key
Fare
Currency
Stores service charge amount.
NOT NULL
FSC
Currency
Stores fuel surcharge amount.
NOT NULL
Flight Schedule
Field
Data Type
Description
Constraints
FlID

8. INT
Unique number to identify the flight.
Primary Key
Flight Date
DATETIME
Date of flight.
NOT NULL
Departure
DATETIME
Stores the departure time of flight.
Arrival
DATETIME
Stores the arrival time of flight on destination.
Aircraft
INT
Aircraft number that will fly, a number from Aircraft table.
Foreign Key
NetFare
INT
To determine total fare of flight, an ID from Airfare table.
Foreign Key
Discounts
Field
Data Type
Description
Constraints
DiID
INT
Unique row id.
Primary Key
Title
Varchar(32)
Label to know discount.

9. NOT NULL
Amount
INT
Discount amount in %
NOT NULL
Description
Varchar(255)
Discount remarks & details.
Charges
Field
Data Type
Description
Constraints
ChID
INT
Unique row id.
Primary Key
Title
Varchar(32)
Label for charge.
NOT NULL
Amount
INT
Amount of charge in %.
NOT NULL
Description
Varchar(255)
Describe cause of charge.
Countries
Field
Data Type
Description

10. Constraints
CtID
INT
Unique row id.
Primary Key
Country Name
Varchar(32)
Room to store country name
NOT NULL
State
Field
Data Type
Description
Constraints
StID
INT
Unique row id.
Primary Key
StateName
Varchar(32)
State name will take place here.
Country
INT
PK from Country table.
Foreign Key
Contact_Details
Field
Data Type
Description
Constraints

11. CnID
INT
Unique row id.
Primary Key
Email
Varchar(16)
Passenger’s contact email for transaction about flights.
NOT NULL
Cell
Varchar(16)
Passenger’s contact cell no for transaction about flights.
NOT NULL
Tel
Varchar(16)
Passenger’s contact telephone no. for transaction about flights.
Street
Varchar(64)
Street address of the passengers.
NOT NULL
State
INT
PK from State table.
Foreign Key
Passengers
Field
Data Type
Description
Constraints
PsID
INT
Unique row id.
Primary Key
Name
Varchar(32)

12. Passenger’s name
NOT NULL
Address
Varchar (64)
Passenger’s address
NOT NULL
Age
INT
Passenger’s age
NOT NULL
Nationalities
Varchar (16)
Nationality of the passenger.
NOT NULL
Contacts
INT
ContactID from Contact_Details table.
Foreign Key
Branches
Field
Data Type
Description
Constraints
BrID
INT
Unique id for each branches
Primary Key
Center
Varchar(16)
Branch Title
NOT NULL
Address
Varchar(32)
Address of the branch
NOT NULL

13. State
INT
State ID from state table
Foreign Key
Employees
Field
Data Type
Description
Constraints
EmpID
INT
Unique number to identity employee, unique on entire system.
Primary Key
Name
Varchar(32)
Employee name
NOT NULL
Address
Varchar(32)
Employee address
NOT NULL
Branch
INT
Associated branch id from Branch Table
Foreign Key
Designation
Varchar(32)
Working duty position.
NOT NULL
Email
Varchar(32)
Contact email of the employee
NOT NULL
Tel
Varchar(16)

14. Contact telephone number.
Ext
INT
Ext number of employee cabinet, if applicable.
Transactions
Field
Data Type
Description
Constraints
TsID
INT
Unique row id
Primary Key
BookingDate
Date/Time
Keeps the booking date.
NOT NULL
DepartureDate
Date/Time
Keeps the departure date.
NOT NULL
Passenger
INT
Transaction creator passengers row id to associate
booking/cancellation, payments etc.
Foreign Key
Flight
INT
Flight no, a PK of Flight_Schedule to determine flying details &
costs.
Foreign Key
Type
BIT

15. Reservation/Cancellation
NOT NULL
Employee
INT
Reservation agent, a row id of employee who helps the
passenger to make transaction.
Foreign Key
Charges
INT
If transaction is cancellation, charges may apply as per business
rules.
Foreign Key
Discount
INT
Discount offers may apply based on scheme criteria.
Foreign Key
Total
INT
Calculated value of actual payable cost by customer to make a
transaction.
NOT NULL
Primary Keys & Foreign Keys
SN
Table
Primary Key
Foreign Keys
Column
References
1
AirCraft
AcID
-

16. -
2
Flight_Schedule
FlID
AirCraft
AirCraft.AcID
Route
Route.RtID
AirFare
AirFare.AfID
3
Route
RtID
-
-
4
AirFare
AfID
Route
Route.RtID
5
Discounts
DiID
-
-
6
Charges
ChID
-
-

17. 7
Passengers
PsID
Contacts
Contact_Details.CnID
8
Contact_Details
CnID
State
State.StID
9
State
StID
Country
Country.CtID
10
Country
CtID
-
-
11
Transaction
TsID
Passenger
Passengers.PsID
Flight
Flight_Schedule.FlID
Employee
Employee.EmpID

18. Charge
Charges.ChID
Discount
Discounts.DiID
12
Employee
EmpID
Branch
Branch.BrID
13
Branch
BrID
Data Definition Language implementations:
/* 0. Create Database & use it */
CREATE DATABASE BuddhAirBase;
USE BuddhaAirBase;
/* 1. Create AirCrafts table*/
CREATE TABLE AirCrafts(
AcID INT Primary Key,
AcNumber Varchar(32) NOT NULL,
Capacity INT NOT NULL,
MfdBy Varchar(128) NOT NULL,
MfdOn Datetime NOT NULL
);
/* 1.1 Insert data into AirCrafts table*/
INSERT INTO AirCrafts
(AcID, AcNumber, Capacity, MfdBy, MfdOn)

19. VALUES
(1, "ATR 72-500", 75, "Alenia Aeronotica", "23 April 1998");
/* 2. Create Route table*/
CREATE TABLE Route(
RtID INT,
Airport Varchar(32) NOT NULL,
Destination Varchar(32) NOT NULL,
RouteCode Varchar(16) NOT NULL UNIQUE,
PRIMARY KEY (RtID)
);
/* 2.1 Insert data into Route table*/
INSERT INTO Route
Values (1, "Kathmandu", "Pokhara", "KTM-PKR");
/* 3. Create AirFare table*/
CREATE TABLE AirFare(
AfID INT,
Route INT,
Fare Currency,
FSC Currency,
PRIMARY KEY (AfID),
CONSTRAINT fk_Route FOREIGN KEY (Route)
REFERENCES Route(RtID)
);
/* 3.1. Insert DATA into AirFare table*/
INSERT INTO AirFare
VALUES
(1, 1, 86, 12);
/* 4. Create Flight_Schedule table */
CREATE TABLE Flight_Schedule(
FlID INT,
FlightDate DATETIME,

20. Departure DATETIME,
Arrival DATETIME,
AirCraft INT,
NetFare INT,
PRIMARY KEY (FlID),
CONSTRAINT fk_AirCraft FOREIGN KEY (AirCraft)
REFERENCES AirCrafts(AcID),
CONSTRAINT fk_NetFare FOREIGN KEY (NetFare)
REFERENCES AirFare(AfID)
);
/* 4.1 Insert DATA into Flight_Schedule */
INSERT INTO Flight_Schedule
VALUES
(1, 'January 23, 2012', '23:20', '1:20', 1, 1);
/* 5. Create Discounts table */
CREATE TABLE Discounts(
DiID INT PRIMARY KEY,
Title Varchar(32),
Amount INT,
Description Varchar (255)
)
/* 5.1 Insert data into Discounts table */
INSERT INTO Discounts
VALUES
(1,'Childrens', 10, 'Discount is provide all childrens under age
of 10.');
/* 6. Create Charges table */
CREATE TABLE Charges(
ChID INT PRIMARY KEY,
Title Varchar(32),
Amount INT,

21. Description Varchar (255)
)
/* 6.1 Insert data into Charges table */
INSERT INTO Charges
VALUES
(2,'Urgent Cancellation', 33.33, '33.3% will be charged for
cancellation for booking within 11 hrs from flight time');
/* 7. Crate Country table*/
CREATE TABLE Countries (
CtID INT PRIMARY KEY,
CountryName Varchar (32) NOT NULL
);
/* 7.1 Insert data into Country table */
INSERT INTO Countries
VALUES
(1, 'Nepal');
/* 8. Create State table*/
CREATE TABLE State(
StID INT,
StateName Varchar (32),
Country INT,
PRIMARY KEY (StID),
CONSTRAINT fk_Country FOREIGN KEY (Country)
REFERENCES Countries(CtID)
);
/* 8.1. Insert data into State table*/
INSERT INTO State
VALUES
(1, 'Bagmati', 1);
/* 9. Create Contact_Details table*/
CREATE TABLE Contact_Details(

22. CnID INT PRIMARY KEY,
Email Varchar (16) NOT NULL,
Cell Varchar (16) NOT NULL,
Tel Varchar (16),
Street Varchar (64),
State INT NOT NULL,
CONSTRAINT fk_State FOREIGN KEY (State)
REFERENCES State(StID)
);
/* 9.1 Insert data into Contact_Details */
INSERT INTO Contact_Details
VALUES
(1,'[email protected]', '9851121824', '01-4215384', 'Gandaki
Marga', 1);
/* 10. Create Passengers table */
CREATE TABLE Passengers(
PsID INT PRIMARY KEY,
Name Varchar (32) NOT NULL,
Address Varchar (64) NOT NULL,
Age INT NOT NULL,
Nationality Varchar(16) NOT NULL,
Contacts INT NOT NULL,
CONSTRAINT fk_Contacts FOREIGN KEY (Contacts)
REFERENCES Contact_Details(CnID)
);
/* 10.1 Insert data into Passengers table */
INSERT INTO Passengers
VALUES
(1,'Shekhar Kumar Sharma', 'Sinamanga-39, KTM', 23,
'Nepalese', 1);
/* 11. Create Branch table */

23. CREATE TABLE Branches(
BrID INT PRIMARY KEY,
Center Varchar(16) NOT NULL,
Address Varchar(32) NOT NULL,
State INT,
CONSTRAINT fk_StateOfEmployee FOREIGN KEY
(State) REFERENCES State(StID)
);
/* 11.1 Insert data into branches table */
INSERT INTO Branches
VALUES
(1, 'Kathmandu', 'New Road, Kathmandu', 1);
/* 12. Create Employee table */
CREATE TABLE Employee
(
EmpID INT PRIMARY KEY,
Name Varchar (32) NOT NULL,
Address Varchar (32) NOT NULL,
Branch INT NOT NULL,
Designation Varchar(32) NOT NULL,
Email Varchar (16) NOT NULL,
Tel Varchar (16) NOT NULL,
Ext INT,
CONSTRAINT fk_Branch FOREIGN KEY (Branch)
REFERENCES Branches(BrID)
);
/* 12.1 Insert data into Employee table */
INSERT INTO Employee
VALUES
(1, 'Diwan Adhikari', 'Bagbazaar - 11, KTM', 1, 'Sales
Executive', '[email protected]', '01-4215254', 12);
/* 13. Create table Transactions */

24. CREATE TABLE Transactions(
TsID INT PRIMARY KEY,
BookingDate DATETIME,
DepartureDate DATETIME,
Passenger INT,
Flight INT,
Type BIT,
Employee INT,
Charges INT,
Discount INT,
CONSTRAINT fk_Passenger FOREIGN KEY (Passenger)
REFERENCES Passengers(PsID),
CONSTRAINT fk_Flight FOREIGN KEY (Flight)
REFERENCES Flight_Schedule(FlID),
CONSTRAINT fk_Employee FOREIGN KEY (Employee)
REFERENCES Employee(EmpID),
CONSTRAINT fk_Charges FOREIGN KEY (Charges)
REFERENCES Charges(ChID),
CONSTRAINT fk_Discount FOREIGN KEY (Discount)
REFERENCES Discounts(DiID)
);
/* 13.1 Insert data into Transactions */
INSERT INTO Transactions
VALUES
(1,'12 November 2011', '21 December 2011', 1, 1, 0, 1, NULL,
NULL);
Running head: DATA ANALYSIS
DATA ANALYSIS
2
Relationship between all entities
Cardinality
Cardinality notations, using Chen style.

25. M = many, N = 0, 1, 2 …
SN
Entities
Cardinality
1.
AirCrafts & Flight_Schedule
1 : M
2.
Route & AirFare
1 : 1
3.
AirFare & Flight_Schedule
1 ; M
4.
Discounts & Transactions
N : 1
5.
Charges & Transactions
N : 1
6.
Countries & State
1 : M
7.
State & Branches
1 : M
8.
Contact_Details & State
M : 1
9.
Passengers & Contact_Details
1 : 1
10
Passengers & Transactions
1 : 1
11.

26. Branches & Employee
1 : M
12.
Employees & Transactions
1 : M
13.
Transactions & Flight_Schedule
M : 1
Cardinality diagram (Information engineering style notations)
Final ER Diagram
References
Ramez Elmasri and Shamkant B. Navathe , ‘Fundamentals of
Database Systems’ Addison Wesley Publishing Company
Allan Leake, (2000), Definition of Database
http://searchsqlserver.techtarget.com/definition/database
SmartDraw (2011), Resources –
Tutorialshttp://www.smartdraw.com/resources/tutorials
BuddhaAir, Nepal (2011) – Company
Historyhttp://www.buddhaair.com/company/history.php
Live longer mobile application
Charles Williams
Systems Analysis, Design and Integration(IT425-1704B-02)
Unit 1 IP
Brian Rodgers
11/22/2017

27. TABLE OF CONTENTS
Table of Contents
1 Application overview 3
1.1 Objectives of the Study 4
1.1.1General Objective 4
1.1.2 Specific Objectives 4
1.2 Assumptions for the project scope 4
1.3 Constraints for the project scope 4
1.4 Scope of the project 5
1.5 Target users 5
1.6 Research questions for the project 5
1.7 Information gathering 5
1.8 Functional requirements 6
1.9 Nonfunctional requirements 6
CHAPTER ONEApplication overview

28. The app is a health management app that guides the user on
healthy eating tips, work outs and gives statistics of the user
lifestyle based on information the user feeds into the system. On
installing the app, the user is required to provide their age,
height, weight, gender and race. Based on this information the
system does analytics and provides daily, weekly and monthly
report of the user’s lifestyle in terms of exercising, how healthy
their diet is and gives recommendation tips to improve on. The
application will also be a source of user medical health
information, where the user will be able to record any health
incident indicating the how they feel, the meal they had taken or
drink before the incident, the activity they were doing, date and
time. Upon visiting a medical doctor the patient can easily refer
to the application and give a medical history to the doctor
without skipping necessary details. The system will also give
alerts on upcoming health seminars near the user. The system
will also provide daily health news on upcoming health diet,
new work out exercises, medical research, medical
breakthrough, health risks, and health warnings issued in case
of disease out breaks. The system will also have the capability
to remind the user to go for medical checkups through
reminders. With lifestyle diseases such as cancer, it is
recommended for men to go for check-up once in a year while
for women twice in a year. The application will be able to give
the user such reminders. The system will be able to learn user
pattern over a period of time and can suggest to the user a
certain food they take at a specific time or exercise.Objectives
of the Study
General Objective
The main objective of the project will be to create an
application that can help users manage their health and keep a
check on their lifestyle choices in terms of diet choices and
exercising. 1.1.2 Specific Objectives
i. Collection of a user’s daily health lifestyle trend
ii. Provide analysis of individual’s health lifestyle

29. iii. Offer tips on improving individual’s health based on their
health lifestyle.
iv. Act as an information tool to keep individual updated on
upcoming health events.
v. Keep the user informed of developments in the health sector.
vi. Remind users to go for medical check-ups.
vii. Act as an information tool for a user’s medical
history.Assumptions for the project scope
i. The user is willing to have their information stored by the
application
ii. The user is ready to accept assistance in managing their
health. Constraints for the project scope
i. The application has focus on an individual’s health.
ii. The information collected by the application shall only be
accessible to the user and only he can share the information at
will.Scope of the project
The project will focus on how to better manage an
individual’s health through mobile application.Target users
The target users of the app are all smart phone users in
the world. The health risks facing the world population
increase on a daily basis due to poor lifestyle choices. The
application is aimed to help individuals watch their health
before a visit to the doctor forces them to do so. Research
questions for the project
i. How often do you exercise?
ii. What is your daily diet composition?
iii. How often do you go for medical check-ups?
iv. How regularly do you go for medical check-ups?
Information gathering
The researcher will use questionnaires as the main tool for
collection of data. A questionnaire is a research instrument
consisting of a series of questions and other prompts for the
purpose of gathering information from respondents. A
questionnaire is commonly used to obtain important information
about the population. Each item in the questionnaire will be
developed to address a specific objective, such that a research

30. question or hypothesis providing the information required for
the project. The questionnaire will be composed of structured
(closed- ended) and unstructured (open – ended questions).
Structured or close-ended questions will be the questions with a
list of all possible alternatives from which respondents will
select the answer that best describes the situation. Unstructured
or open –ended questions are questions which give the
respondent complete freedom of response. These free responses
permit the respondent to answer in his/her own way. They allow
great depth of response.Functional requirements
This are the requirement describing what the system should do.
To elaborate upon registering on the app, where the user feeds
in his/her personal information including age, weight, height,
the system should give a breakdown of the user data such as
users B.M.I. Throughout the day the user feeds the meals they
have consumed and any exercises done during the day. The
system should respond with an analysis of the user’s lifestyle
for the day, providing suggestions on what to stop and what to
increase. The system will provide health news to the user on a
daily basis. The news will be alerts on upcoming health events
around the user such as health seminars. Based on this
information the system does analytics and provides daily,
weekly and monthly report of the user’s lifestyle in terms of
exercising, how healthy their diet is and gives recommendation
tips to improve on. The application will also be a source of user
medical health information, where the user will be able to
record any health incident indicating the how they feel, the meal
they had taken or drink before the incident, the activity they
were doing, date and time. Upon visiting a medical doctor the
patient can easily refer to the application and give a medical
history to the doctor without skipping necessary details. The
requirement shall be verified during functional and acceptance
testing.Nonfunctional requirements
This are the requirements place constraint on how the system
should be. They fall under usability, security, privacy,
portability and stability. Under usability the app shall be easy to

31. use with simple, easy to use and user friendly interface. The
layout shall be self-explanatory in such a way that looking at a
certain interface already tells you what it does. This shall be
tested during usability and functional testing.
The application shall be secure using encryption to store user
data on the device database. The information being entered by
the user is very sensitive to the user and hence the information
must be protected from unauthorized access. Even the user can
not be able to access the database files on their own device.
This shall be tested during functional testing.
The application shall ensure privacy of user data by requiring
login password in order to access the application. This ensure
that even when a user’s phone is accessed by another person
without the password the live longer application cannot be
accessed. This shall be tested during functional testing.
The application shall be stable with crush and lag being handled
appropriately. In the event the application crushes may be due
to slow network the application should redirect the user
appropriately with appropriate error message. This shall be
tested during performance and functional testing.
The application shall run on all android devices irrespective of
size and operating system. This shall be tested during
functional, system, performance and usability testing.
References
Fuggetta, A., & Di Nitto, E. (2014, May). Software process.
In Proceedings of the on Future of Software Engineering (pp. 1-
12). ACM.
Van Lamsweerde, A. (2009). Requirements engineering: From
system goals to UML models to software (Vol. 10). Chichester,
UK: John Wiley & Sons.
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-
functional requirements in software engineering (Vol. 5).
Springer Science & Business Media.
Matthews, B., & Ross, L. (2014). Research methods. Pearson
Higher Ed.

32. Loucopoulos, P., & Karakostas, V. (1995). System requirements
engineering. McGraw-Hill, Inc..
Beizer, B. (1984). Software system testing and quality
assurance. Van Nostrand Reinhold Co..