IoT based mobile Application

This document provides an overview of a project design for an IoT-based healthcare application. It includes information about the organization, project description, company size, and the impact of the problem on the organization. The document also discusses the intended research process and feasibility analysis of the project. The project plan and risk analysis are also included.

Running Head: Project Design 1
IoT based mobile Application
Student Name
Professor’s Name
Institution
Location of Institution
Date

Project Design 2
Contents
Project Outline.................................................................................................................................2
Organization Description.............................................................................................................2
Project Description......................................................................................................................3
Company Size & Information......................................................................................................3
Impact of the Problem on the Organization.................................................................................4
Intended Research Process..........................................................................................................5
1 System Analysis..........................................................................................................................17
1.1 Strategies..................................................................................................................................17
1.1.1 Top Down Strategy...........................................................................................................17
1.1.2 Bottom Up Strategy..........................................................................................................17
1.1.3 Structured Design.............................................................................................................18
1.2 Advantages and Disadvantages...............................................................................................18
1.3 Justification..............................................................................................................................19
1.4 Requirement Elicitation...........................................................................................................19
1.4.1 Steps taken for analysis of database requirements...............................................................20
1.4.2 Database requirements developed........................................................................................21
1.4.3 Approach discussion.............................................................................................................22
1.4.4 Justification...........................................................................................................................23
2 Conclusion..................................................................................................................................23

Project Design 3
Project Outline
Organization Description
The organization is a large-scale software development firm that develops web and mobile
applications for its clients. The major clients of the organization are the small and medium scale
business enterprises in the business domains as healthcare, finance, and commercial. The
organization was established in the year 2009 and is engaged in the software development
projects since its inception. The headquarters of the organization are in Sydney, Australia.
The organization has always believed that innovation is the key to business and commercial
success. Technology is enhancing itself and the organization makes sure that it reflects latest
technology in all the software development and other business operations that it performs. There
are latest development and management techniques that are adopted by the company to provide
its customers with the expected set of services and products.
Project Description
The project that is being carried out by the company is the development of an IoT-based
healthcare application for one of its medium-scale healthcare organization. The project will be
developed using Internet of Things (IoT) as the primary technology. IoT is one of the emerging
technologies that refer to the inter-connection of a varied set of components to achieve a
common goal (Lingam, 2017). The components that will be involved and integrated in the
application will be healthcare equipment, such as heart rate monitor, glucometer, etc., computer
systems, database, database server, web server, Smartphones, network peripherals, sensors, data
analytics tools, and Big Data tools (Harsh, 2017).
The software development project will include the development of the IoT-based healthcare
application along with a front-end for the application which will act as the interface for the users.
The web interface will be accessible from the mobile as well as desktop platforms. The primary
users for the application will be the patients, medical professionals, nursing staff, and healthcare
organization’s management. The other users may include the administrative staff, healthcare
authorities, and the family members of the patient. The project will be developed as per the
business requirements & specifications handed over by the client. Some of the high-priority
requirements include the management of the healthcare data sets by including the security and

Project Design 4
privacy of the information along with the automated analytics of the patient data to speed up and
enhance the accuracy of medical diagnosis (Dziak, Jachimczyk & Kulesza, 2017).
Company Size & Information
The company has its headquarters in Sydney, Australia and it is set-up in three further locations
in Australia as Melbourne, Brisbane, and Canberra. There are currently 325 employees engaged
with the organization. About 40% of these resources are associated with the Sydney office and
the rest 60% are spread across the other three offices.
There are over 180 dedicated software development professionals deployed with the organization
and these resources have varied development skills. For instance, there is a wide range of
programming languages and the software developers associated with the organization have
expertise on the languages as PHP, Python, C#, C++, Java, Ruby, etc. The other employees
deployed in the organization include managers, data scientists, web designers, UI Experts,
business analysts, human resource management staff, and support staff.
The company has completed over 1,676 projects since its inception and has succeeded in
developing a distinguished name in the market. This is because the organization always makes
sure that it provides its clients with the latest software packages that are in accordance with
trends and patterns in the market.
The management unit that is associated with the organization also adopts varied managerial and
leadership styles to successfully carry out the project. The project management methodologies
that are applied by the organization include Project Management Body of Knowledge (PMBoK),
agile methodology for Project Management, Projects In Controlled Environment (PRINCE2),
and Lean Project Management (Serrador & Pinto, 2015).
The company has always achieved a rating of 4+ on a scale of 5 from its customers.
Impact of the Problem on the Organization
The client of the project of IoT-based healthcare application development project is a medium-
scale healthcare firm. The healthcare firm is facing a lot many issues with its data management
and handling processes.

Project Design 5
The number of patients is increasing on a per day basis and there is a lot of information that is
associated with every patient. Some of these information sets include demographic details of the
patient, medical details of the patients, medical history, medical professional details, payment
details, etc. Also, there is a record of every medical professional that is required to be stored and
managed in the database. This leads to the presence of a huge cluster of information that includes
a wide range of data. These data sets have varied data structures and the volume of these sets
also varies.
It is, therefore, becoming difficult for the organization to manage all of these data sets. Also, the
patient engagement and satisfaction levels are deteriorating as a result. There is a lot of time that
is spent in data searching and retrieving. There have also been occurrences wherein the medical
reports of the patients have been duplicated or deleted from the records. The traditional tools and
methods for data management are no longer sufficient to manage the data requirements of the
organization.
Another problem that the organization faces is data security and privacy. There are several data
security and privacy risks that are now associated with the organizational data. The occurrence of
these risks, such as data loss, data leakage, malware attacks, denial of service attacks, etc. have
legal and organizational issues for the company (Deursen, Buchanan & Duff, 2013). Also, the
repeated occurrence of the security and privacy issues has resulted in the reduction of the market
shares and customer base. The overall revenues and sales of the organization have also come
down.
It has become essential for the organization to automate the business processes and manage its
data adequately.
Intended Research Process
It is intended to conduct the research using a mix of qualitative and quantitative research
methods. The exploration of the issues will be done under the qualitative methods and the
analysis will be made as per the data sets gathered. The data techniques that are intended to be
used and applied under this method would be interviews, observations, surveys, domain analysis,
and group discussions. There will be interview sessions planned with the target audience of the
mobile application and the response will then be analyzed to understand the nature of issues and
the associated impacts. Similarly, group discussions will be done. The observation of the existing

Project Design 6
system will be done to understand the process flow and to get an idea of the issues and problems
associated with the same. The surveys and questionnaires will be prepared as per the user type
and the response will be collected to determine the functional and non-functional requirements
(Jervise & Drake, 2014).
The quantitative research methods will make use of the mathematical and statistical approaches
to determine the issues and the associated impacts. Co-relational and experimental research
processes are intended to be applied under the quantitative set of methods. The sample size in all
of these processes will be kept small to moderate.
The data sets that will be gathered as per both the research methods and categories will then be
analyzed using the automated data analytics tools. The associated patterns and trends will be
identified to get the details of issues that will be involved. The impact assessment will then be
carried out for all the issues that will be listed. This will provide a detailed identification of the
issues, type of the issue, nature of the impact, degree of the impact, and associated details.
Feasibility Analysis
The system designer and developers associated to the project needs to access the feasibility of
the general requirements those are formulated by the project stakeholder and approved by the
project managers. In addition to this, they should also consider the existing possible solutions.
The large scale software development company deals with design and development of website
and mobile applications for different organizations such as healthcare, finance commercial etc.
This specific project deals with design and development of an IOT based healthcare application
for a SME healthcare center. The feasibility of the project is measured in the below section:

Project Design 7
Information
of the project
IOT project related Purchase
Information

Project Design 8
Company
background &
Information
Sydney, Australia and it is set-up in
three further locations in Australia as
Melbourne, Brisbane, and Canberra
Project price 240,000
Town Sydney, Australia Software
cost
$30,000
Numbers of
professionals
180 Hardware
cost
$28,000
Other
information
4. Design and development
information
Modules used for
designing the IOT
based healthcare system
Project
accomplished
till date
1676 WIFI module
Temperature sensor
Pulse Oximeter
Project
development
cost
$850,000 Amazon EC2
Technical
training cost
$6,000
Project
information
Estimated cost
for the project
$850,000
Monthly profit
expected
$80,000

Project Design 9
Cost for
vendors and
suppliers
$50,000
Cost assigned
for different
project
modules
$60,000
Project
Results
Value of
project equity
=100,000
Estimated cost for the project
$850000
less
Total R&D
cost = 75,000
Monthly profit expected $80000 less Net design and
development cost
of $116000
Equals $-
36000
The components and modules used to design the system include hardware, software, cloud
vendor (Amazon EC2), WIFI module, Temperature sensor, Pulse Oximeter etc. The costs for
each of these components are individually updated to define whether the project will be feasible
or not. Apart from this, the training and development cost for the project are also determined and
from the integrated resultant it is defined that the project is feasible for the owners.
Project plan and risk analysis
1. Project plan

Project Design 10
This particular section of the report focuses on details of project planning. The software design
document includes different components and activities and based on the skills, approach and
knowledge of the project team members the activities are individually assigned to separate
resources. As soon as the tasks or activities are assigned it become their responsibilities to
accomplish assigned roles within estimated time maintaining all project requirements. After
estimating and analyzing the IOT based healthcare application project details it is determined
that the total time and cost needed or the projects are respectively 14 months and $900,000. The
methods and estimation techniques that are employed to conduct the project are also elaborated
in the below section.
1.1 Methods applied to conduct the project
There are different methods used by the project managers and project team members to deploy a
cloud based project for the client companies. Agile, scrum, waterfall, Adaptive project
framework and PERT are the most widely used methodologies that helps to estimate the project
including identification of tasks, duration, resource identification etc. However, Agile project
management method is the most suitable one for this specific project. The details of such method
are elaborated below:
Waterfall method: This is the most generic and simple project development method used to
conduct any project successfully. This method is comprising of five phases in terms of
requirement gathering and analysis, design, implementation, verification and maintenance. At the
initiation phase of this method the consumer specified requirements are listed to successfully
develop the content, design and plan for the project. After creating the physical product, the
integrated system is validated and verified respectively to ensure whether it is ready to be
launched in the market or not.

Project Design 11
Agile method: This method is most suitable for developing software products based on the
consumer’s expectations. The agile project managers are focused on creating ways for delivering
value after interacting with the consumers. The project managers have also expanded the concept
in many implementation frameworks which include extreme programming, scrum project
management etc.
PERT: Program Evaluation Review technique (PERT) is used to measure the time, duration and
cost of any project. This approach acts as tool used to plan activities within a project to make the
project easier. It helps to structure project schedule and make proper coordination among the
project team members. The PERT chart also helps to manage and accomplish the work within
estimated timeframe.
Prince2 method: The Prince2 method is also known as a process based method that is used to
achieve the project objectives and goals much effectively and efficiently. This method is strictly
business focused and helps to define organizational structure for the project manager. This
product based planning approach gives flexibility to the project team members and also gives
them controllable stages.
1.2 Usage of estimation technique
There are different techniques used to create project plan including identification of tasks its
respective duration, resources and key milestones as well. The techniques are illustrated in the
below section:
PERT management method: For both the large scale small scale projects this estimation method
is very much applicable. However, for one-time manufacturing and development processes this

Project Design 12
technique is profitable. Through using this technique project manager can make differentiation
between the activities and events.
Critical path method: The Critical Path Method is focused on speeding up any task by
measuring its priority. Any project shows various directions following those it can be
accomplished. CPM governs the project through the simplest and easy direction. A project
manager can provide a clear and visible picture to the project team members by using the
concept of CPM.
Work Breakdown Structure: WBS is the other useful tool or technique used for developing and
sub-diving project activities. In order to complete the project within estimated time frame and
budget this is mandatory to segment the task into small parts. Individuals will be assigned to
those activities according to their responsibilities.
Gantt chart: Gantt chart is used to track any project and it makes the status and structure of the
project visible to the project team members. After completion of each phase the Gantt chart must
be monitored and checked by the project team members to understand what possible changes are
required to be incorporated by the project team members.
1.3 Graphic images

Project Design 13
Figure 1: Gantt chart of the project
(Source: created by author)

Project Design 14
IOT project development
schedule
Project initiation
Defining scope of
the project
Feasibility study to
determine project
cost
Contract to
suppliers
Selection of
vendors
Identify IOT modules
Project planning
Purchasing software
Purchasing
hardware
Risk management
plan
Stakeholder
management plan
Security
implementation
Procurement
management plan
Project execution
Project subdivision
Design prototype
Developing
prototype
Simulation
Final simulation
Project monitoring and
control
Unit testing
Integrated testing
Acceptance testing
IOT based
healthcare Project
launching
Project closure
Stakeholder sig
Final document
submission
Post project
maintenance
planning
Figure 2: Work Breakdown Structure of the project
(Source: created by author)

Project Design 15
2. Risk analysis
2.1 Discussion on the methods that are to be employed
The purpose of applying this IOT application in the healthcare center is to keep the health
records of the patients updated. This cloud based IOT system would be able to store huge
amount of information with high security functionalities. During the diagnosis of the patients the
doctors will be able to access needful information from the server. Not only this but also, with
advancement in technologies the doctors will also be able to update the patient’s current health
status. The patients can take the doctor’s appointment with this updates system much efficiently
and effectively. Though, certain risks are associated to this those have been identified. The
details of the risk management approach are elaborated in the below section. The methods that
are deployed to conduct risk management include the following:
Risk acceptance: There are certain risks which cannot be easily mitigated such as operational
risks theses risk are needed to be accepted first by the project team members and then
accordingly mitigation strategies must be developed.
Risk mitigation: The risks such as improper resource, time and cost management risks are
needed to be mitigated to obtain structured revenue and competitive advantages all over.
Risk transfer: The risk of investment and insurance should be transferred instead of mitigating
this.
Risk mitigation: The risks of lack of communication and lack of technical knowledge are
needed to be mitigated by the project manager.

Project Design 16
2.2 Using risk identification methods
There are different methods thorough which risks of any project can be easily identified. The
process of risk management uses various formula and templates accordingly and that are mostly
based on industrial practices. The methods of risk identification are as follows:
Brainstorming: The session of brainstorming become much clear and visible to the participants
when the objectives of the project are stated directly and understood by the project team
members at the initial phase. Brainstorming helps to identify the risks associated to any project.
For this specific project through brainstorming the risk that is identified is wrong resource
allocation.
Flowchart method: This is the other method utilized for graphical, sequential management of
needful activities. Through flowchart method the risk that has been identified for this project is
improper cost and time estimation for the project.
SWOT analysis: The SWOT analysis is referred to as the tool that is used to identify the
strength, weaknesses, opportunities and weakness of any project easily. The project strength
gives it effective opportunities on the other hand the weakness of the project gives it further
threats. The threats that are identified through this method is lack of training and skills among
the working project team members.

Project Design 17
2.3 Development of risk mitigation strategies
Ris
k Id
Identified risks
for the project
Likelihood Impact Probability Mitigation strategies
for the identified risks
R12 Inaccurate
allocation of
resources
Unlikely m Extreme Based on the
requirement of the
project the project
manager and the project
team members are
required to assign
accurate resources for
the project. It is the
responsibility of the
project manager to
accomplish the project
within the assigned
resources only to avoid
over resource allocation
issues.
R23 Improper
allocation of cost
Likely Severe High Based on project
complexities the project
managers are required to
allocate cost for the
tasks. Additionally,
feasibility study is also
needed.
R5 Improper
estimation of
project time frame
Possible Significant Low Depending upon the
project complexities,
skills and knowledge of
the project managers and
team members at the
initial phase time period
should be designed.
R8 Lack of leadership
and
communication
strategies
Very
unlikely
Minor Medium The project associates
must use open
communication while
interacting with each

Project Design 18
other.
R2 Lack of technical
knowledge among
the users and
project team
members
Very likely Medium Medium While developing the
IOT based healthcare
system on job technical
training program needs
to be arranged by the HR
manager.

Project Design 19
1 System Analysis
1.1 Strategies
IoT based system comes with its complexities. The development of this system will requires
an approach in which in ensures all the functional and the non-function requirements are well
sorted out before the deployment of the final system. In order to fully develop the system, we are
going to consider a number of the analysis strategies for us to meet the desired goal and offer the
best product in the market. The strategies reviewed herein we:
a) Top Down Strategy
b) Bottom Up Strategy
c) Structured Design
1.1.1 Top Down Strategy
The healthcare IoT based system development will be easily implemented and deployed
by the use of the Top Down strategy whereby the system is broken down into units and the
highest module is given the priority (Glover, Sarma, & Overbye, 2012). All the requirements are
gathered here and designed in a way that the overall module is divided into small modules which
are further subdivided into more-smaller sub modules. In this context, this strategy will be of
importance since the overall functionality of the system is already defined before embarking on
the development of the system.
1.1.2 Bottom Up Strategy
On the other hand, the IoT based healthcare system can also employ the Bottom up
software development strategy where by the system developers will look at the smallest possible
sub system from the whole system, work on them and combine them all until they come up with

Project Design 20
the main unit of the system hence developing the system (Tanaka& Sugeno, 2009). This strategy
is best applied when all the system requirements have been defined because they will help to
generate the smallest modules.
1.1.3 Structured Design
Every system employs the use of structures focusing on the flow of the data. Through this
flow, the system developers easily identify the input and the output of the system under
development hence increasing the modularity while reducing all the complexities of the overall
system (Phillips & Nagle, 2011). The IoT healthcare system is simplified by the use of this
strategy where all the requirements are represented graphically using the Data Flow Diagrams
which are later modified and analyzed to further provide basis for the development of the
structure charts.
1.2 Advantages and Disadvantages
a) Top Down Strategy
Advantages Disadvantages
Operational and the managerial resources are
well secure
Limited coverage by the solution
Provides an identity by showcasing the first
implemented sections
Higher cost of implementing the program
b) Bottom Up Strategy
Advantages Disadvantages
Early automation since manual operations
are replaced earlier
Prone to changes due to changing demands
hence double tasks.

Project Design 21
Early awareness both to the user and the
business
There must be an existing structure to compare
hence not that much business oriented.
c) Structured Design
Advantages Disadvantages
Complete and accurate modelling The approach is time consuming
All processes well documented hence proper
understanding
Expensive especially during training staff
1.3 Justification
Having discussed the health diagnostic processes and the strategies to be used. Patients
and the doctors need to be harmonized together in order to make health sector and v more
smooth operational unit of the economy (Skogestad & Postlethwaite, 2011). With this in mind
we can evade the health crisis with the proposed IoT based healthcare system. It will not only
simplify the diagnostic process but also provide an avenue in which accountability, data security,
efficiency within the health care and its operations, reliability and service availability will be
achieved in the health sector.
1.4 Requirement Elicitation
Having a fully functional system results from a well gathered and analysed requirements.
For the IoT based healthcare system, the main elicitation techniques employed were:
prototyping, interviews and the user observations. Prototyping in our case helps in simulation of

Project Design 22
the related systems with a display of a sample aspect other the final product under review. This
creates room for comparison in order to check is the plan matches to the overall final product
being developed. Another common requirements gathering is the interviews from where the
software developer can collect samples form a desired audience before embarking on the
analysis of the overall system.
Along with this the users can be observed hence being another technique we’ll refer to
user observation (Agnelli, Albasini, Bietti, Gnudi, Lacaita, Manstretta & Temporiti, 2016. With
these requirements combined together, we can document the overall development of the system
to ensure that the mention requirements are within the minimum needs of the project and the
acceptable to all the stakeholders in both the planning, development and the deployment of the
system.
1.4.1 Steps taken for analysis of database requirements
Every database has its own constraints and boundaries in which it should operate, in this case
each and every requirement needs to be analyzes well before the deployment of the android
application. Analysis process follows a series of events that need to be considered first so as to
enable consistent flow of data (Wernet et al 2016). In these regard, we are tasked with the
analysis process and herein are the steps that need to be followed.
a) Question definition- Analysis of data should begin by the definition of the questions.
Through this the database manager is able to understand the need for the development of
the database in question. Measurable, concise and clear questions should be set in place
to mark the beginning of the heavy process to be followed ahead.

Project Design 23
b) Setting measurements- Having set all the questions, of importance is to set the
measurements on how to achieve the stated questions. For instance, factors that need to
be measured should be decided and the mode of measurement should be explained. In
this case, objections can be easily drawn on what should be included and those to be left
aside.
c) Data collection- Once the relevant questions are well defined, and all the priorities for
measurements being set aside, collection of the data is a next step to be considered.
Collection begins with what is already contained within or the resources that are at hand.
Naming system is hereby defined so as to avoid recollection of the same data. All this can
be easily retrieved through logging using a unique format. For example, the use of date.
d) Data analysis- With reference to the step one where the questions are stated, this step
deeply brings forth an analysis of this information and all the possible manipulations so
as to find the exact data needed for the overall performance of the system. In case of any
disparity the research questions need to be adjusted so as to meet all the requirements.
e) Results interpretation- Once all the questions are well analyzed and all harmonizes
successfully, with the further research, all the results can now be interpreted so as to
come up with the overall solution for the whole database design to be completed with
ease. Through interpretation, the designer is able to obtain a clear meaning of each and
every step hence coming up with the overall conclusion which is more productive.
1.4.2 Database requirements developed
Having analyzed all the information, we can obtain some of the requirements for our specific
database to be used for the IoT project. This is in line with the presentation according to Yang et
al (2018). These can be summarized as shown below:

Project Design 24
Storage allocation- the design of the database should be clearly developed from the basis of the
size of the information being intended to store.
Security- access of information should be well secure, for instance there should be rules as to
whom should add, modify or delete the information stored in the database. Different access
levels should be set so as to ensure data intergrity.
Integration- every database needs to be integrated to user interface, users should easily fetch the
information while adding more without much struggle since the interface being used is in favor
with the database used. The overall database should be easily integrated to any of the developer’s
programming language.
Complexity of the data- information stored is yet a factor to be considered if for instance, the
database will be storing image files, text files, videos or sound formats, there should be a way of
retrieving each without affecting the overall performance of the database.
1.4.3 Approach discussion
The database is made using any of the two approaches; top-down approach and the bottom-
up approach. The IoT base healthcare system will be using the top-down approach in which all
the requirements are first gathered well in favor of the overall application. The process begins
from the complex requirement downwards to the smallest unit of the whole process (Inzalkar and
Sharma 2015). Having the general idea in mind, successive subdivision is done to each and every
entity stating all its attributes until the final level where all the relationships could be clearly
explained.

Project Design 25
1.4.4 Justification
The problem of prescription and medication is not only affecting the patients, doctors on
the other hand have fallen victims of the same. To curb this problem, this paper explains the
design of the database for storing all the medical records based on the requirements. In this case,
all the information is guaranteed safety from the entry to the final stage where modification is
made based on the user requirements. This process will not only guarantee the data availability
but also ensure all the required safety is provided for all the information
2 Conclusion
As a summary, this paper brings into our attention the application of the IoT systems in diagnosis
of the various diseases and tends to make a vivid conclusion of the design that none of the human
diagnostics modes sufficiently satisfied the whole process unlike the IoT based system. Having
discussed the widespread requirements of the Health care IoT system, the generic
implementation and the overall output becomes a challenging factor in curbing the general
diagnosis of the diseases. In conclusion, the development of the proposed IoT based healthcare
system will not only be of benefit in terms of the data security but will also ensure patient
satisfaction in terms of the prescription design to the final medication and check-ups.

Project Design 26
Process Analysis:
Information Gathering Techniques:
Interviews and Questionnaire: The interview is done by the interviewer through personally
meeting interviewee. The interview allows the interviewer to capture the raw data. If the integrity
of the gathered is concern, then interview is far better than the questionnaire. The interview is
also extremely flexible as the conversation is not fixed. The interview is a very complex
technique that require experience, tremendous communication skills and high managing skills.
Each of the questions asked to the interviewee should be clear and meaningful.
The questionnaire is on the other hand is very powerful technique that can collect a lot of data in
a very less time. The questionnaire is a self-administrative tool. This method is economical in the
comparison of interview. The skills needed to apply questionnaire technique is less than that of
interview.
Description of Processes and Required Data:
Registration of Patient: The first thing that a patient has to do is registering into the system of
the organization. Required data are patient personal and communication details.
Login to System: Using the provided login credentials, any user of the system can access the
functions and data authorized to them. Required data are login id and password.
Monitor Health Data: The IoT device installed on the body of patient will continuously monitor
health related data such as heart beat, blood pressure and more. Required data are patient id and
health data.

Project Design 27
Store Health Data: The IoT device will send these health related data to connected mobile
device. This device will transfer these data into server using internet connection. The server then
validates and store data into server. Required data are patient id and health data.
Use Case:
Figure 1: Use Case Diagram of IoT Healthcare
(Source: Created by Author)

Project Design 28
Data Model:
Figure 2: ER Diagram of IoT Healthcare
(Source: Created by Author)
Figure 3: Class Diagram of IoT Healthcare
(Source: Created by Author)

Project Design 29
References
Agnelli, F., Albasini, G., Bietti, I., Gnudi, A., Lacaita, A., Manstretta, D., ... & Temporiti, E.
(2016). Wireless multi-standard terminals: system analysis and design of a reconfigurable
Albliwi, S., Antony, J., Abdul Halim Lim, S., & van der Wiele, T. (2014). Critical failure factors
of Lean Six Sigma: a systematic literature review. International Journal of Quality &
Reliability Management, 31(9), 1012-1030.
Al-Masree, H. K. (2015). Extracting Entity Relationship Diagram (ERD) from relational
database schema. International Journal of Database Theory and Application, 8(3), 15-26.
Bodily, R., Nyland, R., & Wiley, D. (2017). The RISE Framework: Using Learning Analytics to
Automatically Identify Open Educational Resources for Continuous Improvement. The
International Review of Research in Open and Distributed Learning, 18(2).
Cengage Learning.
Cohen-Vogel, L., Tichnor-Wagner, A., Allen, D., Harrison, C., Kainz, K., Socol, A. R., & Wang,
Q. (2015). Implementing educational innovations at scale: Transforming researchers into
continuous improvement scientists. Educational Policy, 29(1), 257-277.
Conger, S. (2015). Six sigma and business process management. In Handbook on Business
Process Management 1 (pp. 127-146). Springer, Berlin, Heidelberg.
design (Vol. 2, pp. 359-368). New York: Wiley.
Deursen, N., Buchanan, W., & Duff, A. (2013). Monitoring information security risks within
health care. Computers & Security, 37, 31-45. doi: 10.1016/j.cose.2013.04.005

Project Design 30
Dziak, D., Jachimczyk, B., & Kulesza, W. (2017). IoT-Based Information System for Healthcare
Application: Design Methodology Approach. Applied Sciences, 7(6), 596. doi:
10.3390/app7060596
EJAZ, A., KHALID, A., Ahmed, S., & Cheema, M. (2016). Effectiveness of Requirements
Elicitation Techniques in Software Engineering Process: A Comparative Study Based on
Time, Cost, Performance, Usability and Scalability of Various Techniques. International
Journal of Management, Information Technology and Engineering, 4(5), 23-28.
Faitelson, D., & Tyszberowicz, S. (2017, May). UML Diagram Refinement (focusing on class-
and use case diagrams). In Proceedings of the 39th International Conference on Software
Engineering (pp. 735-745). IEEE Press.
First, M. B. (2016). Adopting a continuous improvement model for future DSM revisions. World
Psychiatry, 15(3), 223-224.
Glover, J. D., Sarma, M. S., & Overbye, T. (2012). Power System Analysis & Design, SI Version.
Hambach, J., Tenberg, R., & Metternich, J. (2015). Guideline-based video analysis of
competencies for a target-oriented continuous improvement process. Procedia CIRP, 32,
25-30.
Harsh, K. (2017). IOT Based Calorie Calculator For Healthcare System. International Journal
Of Engineering And Computer Science. doi: 10.18535/ijecs/v6i5.10
Heinemann, B., Ceauau, I., Buchmüller, M., & Kopia, J. (2017). Quality Management System
Certification and the Continuous Improvement Process by the Example of a Training
Company in Germany. Calitatea, 18(156), 97.

Project Design 31
Inzalkar, S., & Sharma, J. (2015). A survey on text mining-techniques and
application. International Journal of Research In Science & Engineering, 24, 1-14.
Ivey, M., Dew, S., Mandal, M., Mohamed, Y., Nychka, J. A., Raboud, D., & Carey, J. P. (2017).
USING POST COURSE ASSESSMENTS TO INVOLVE INSTRUCTORS IN THE
CONTINUOUS IMPROVEMENT PROCESS. Proceedings of the Canadian
Engineering Education Association (CEEA).
Jervis, M., & Drake, M. (2014). The Use of Qualitative Research Methods in Quantitative
Science: A Review. Journal Of Sensory Studies, 29(4), 234-247. doi: 10.1111/joss.12101
Lingam, S. (2017). Transforming Smart Healthcare through the Internet of Things (IoT).
International Journal Of Emerging Trends In Science And Technology, 4(9). doi:
10.18535/ijetst/v4i9.08
Phillips, C. L., & Nagle, H. T. (2011). Digital control system analysis and design. Prentice Hall
Press. RF front-end. IEEE Circuits and Systems Magazine, 6(1), 38-59.
Serrador, P., & Pinto, J. (2015). Does Agile work? — A quantitative analysis of agile project
success. International Journal Of Project Management, 33(5), 1040-1051. doi:
10.1016/j.ijproman.2015.01.006
sets and systems, 45(2), 135-156.
Skogestad, S., & Postlethwaite, I. (2011). Multivariable feedback control: analysis and
Tanaka, K., & Sugeno, M. (2009). Stability analysis and design of fuzzy control systems. Fuzzy
Wernet, G., Bauer, C., Steubing, B., Reinhard, J., Moreno-Ruiz, E., & Weidema, B.
(2016). The ecoinvent database version 3 (part I): overview and

Project Design 32
methodology. The International Journal of Life Cycle Assessment, 21(9), 1218-
1230.
Yang, L., & Cao, L. (2016). The Effect of MySQL Workbench in Teaching Entity-Relationship
Diagram (ERD) to Relational Schema Mapping. International Journal of Modern
Education and Computer Science, 8(7), 1.
Yang, L., Jin, S., Danielson, P., Homer, C., Gass, L., Bender, S. M., ... & Funk, M. (2018). A
new generation of the United States National Land Cover Database: Requirements,
research priorities, design, and implementation strategies. ISPRS Journal of
Photogrammetry and Remote Sensing, 146, 108-123.
Yousuf, M., & Asger, M. (2015). Comparison of various requirements elicitation
techniques. International Journal of Computer Applications, 116(4).
Zampognaro, P., Buys, R., Walsh, D., Woods, C., & Melillo, F. (2017, July). A Use Case based
requirements specification approach to support the development of a rehabilitation
system for CVD patients: The PATHWAY Project. In Computers and Communications
(ISCC), 2017 IEEE Symposium on (pp. 254-259). IEEE.