interdisciplinary team of specialists to clearly identify
the problem and its possible causes, as well as align
this understanding among the team. Based on this, a
hypothesis is established that emerging technologies
such as artificial intelligence and the Internet of
Things (IoT) have shown great potential in driving
innovation in interdisciplinary methods, enabling
scalable and adaptive solutions to complex problems
(Sarker et al., 2022).
Based on preliminary discussions, the hypothesis
is used as a guiding question for a systematic review
(Staples; Niazi, 2007) or integrative review (Torraco,
2005) of the literature, using scientific databases and
portals to deepen the theoretical understanding of the
topic and identify existing similar solutions. As a
result, the scientific validation of the problem and
potential solution alternatives are expected.
Consider the following example of a problem:
injuries caused by falls in elderly individuals in home
care settings, observed by a master's student in
nursing working for a health cooperative. In the first
phase, the student conducted a root cause analysis to
identify the motivations behind the falls. With data
from the cooperative and interdisciplinary team
support, it was identified that the falls occurred due to
multiple causes, including the lack of a dedicated
caregiver, who had to step away for other domestic
duties such as meal preparation. Consequently,
specialists proposed a monitoring system using IoT
(Internet of Things) for fall detection and prevention.
Using this hypothesis, the student searched scientific
databases such as Google Scholar, Elsevier, and
others specific to health to identify similar research
and solutions that could support her work. She found
technologies aiding fall detection but none for
prevention. With this result, she moved on to the
second phase.
The Second Phase involves identifying user needs
(target audience) and establishing requirements to
solve the identified problem. Methods to identify
these needs include: 1) interviews and focus groups
with potential users (aligned with designed profiles),
2) creation of personas and usage scenarios (Barbosa
and Silva, 2011) by the interdisciplinary team (Carrol,
2006), and 3) market data research. Based on these
needs, specialists analyze and define the
technological requirements (functional and non-
functional) of the solution. These requirements are
used to structure a matrix, comparing solutions found
in the market and academia, indicating full, partial, or
unmet requirements.
Continuing the example, the nursing student
conducted a needs assessment through interviews
with cooperative clients. These interviews revealed
that families did not adopt existing preventive
techniques like physical bed restraints, as they were
deemed invasive and uncomfortable, compromising
the elderly's quality of life. Additionally, the routine
of the elderly included natural activities like hygiene
and meals. Based on these reports and other needs,
the team mapped functional and non-functional
requirements for the system. For instance, a non-
functional requirement was non-invasive monitoring
that preserves the patient's privacy and quality of life,
while a functional requirement was the ability to
temporarily pause and resume monitoring to
accommodate caregiving routines. With these
requirements, the student revisited her research and
confirmed that existing technologies did not meet all
mapped requirements, justifying the development of
new technology, and proceeding to the next phase.
The Third Phase encompasses the ideation
process to design the initial solution. Based on the
requirements and alternative technologies identified
in earlier phases, the interdisciplinary team meets to
conduct brainstorming sessions (Godoy, 2001) to
devise a solution. Initial drafts are created according
to the technology (e.g., low-fidelity app screen
prototypes (Barbosa and Silva, 2011), schematic
drawings of small hardware devices, etc.). The group
validates these drafts with potential users and refines
them as needed to ensure the solution makes sense.
When a viable theoretical solution is achieved, a
more refined version is produced. The team specifies
components such as electronic hardware, visual
identity (if applicable), color palette, and other details
to enhance fidelity to the final product.
In the fall prevention system case, the last phase
concluded with mapped requirements. In the third
phase, the team produced a general architecture of the
solution, listing necessary components to satisfy the
requirements. Low-fidelity drafts were conceptually
validated, followed by high-fidelity versions closer to
the final output. Using the same approach, low- and
high-fidelity versions were created for each
component of the architecture, such as information
panel screens. With the designs completed, the team
proceeded to the next phase.
The Fourth Phase proposes the development of an
interactive or functional prototype, which may also
take the form of a Minimum Viable Product (MVP)
(Ries, 2011), based on a selected design proposal. At
this stage, the technological architecture of the
solution is defined, including the development
environment and platform, tools, programming
languages, software components (libraries, database
management systems, frameworks), hardware design
and components, or other technical artifacts