Professional Documents
Culture Documents
Final Project Report
Final Project Report
PROJECT REPORT
(PHASE-II)
on
“Mental Health Development Application with Face Recognition
Login”
BY
D. Sahithya 1MV17IS017
Mohit Sinha 1MV17IS030
Mrudula R 1MV17IS031
Ruchika Jain 1MV17IS045
CERTIFICATE
Certified that the project work entitled “Mental Health Development Application with
Face Recognition Login” is a bonafide work carried out by D. Sahithya, Mohit Sinha,
Mrudula R and Ruchika Jain bearing USN 1MV17IS017, 1MV17IS030, 1MV17IS031
and 1MV17IS045 respectively, students of Sir M. Visvesvaraya Institute of Technology,
Bengaluru. It is certified that all corrections/suggestions indicated for Internal Assessment
have been incorporated and the project report has been approved as it satisfies the
academic requirements in respect of Project work .
Signatures:
The World Mental Health Survey conducted in 17 countries found that on an average about 1
in 20 people reported having an episode of depression in the previous year. Depressive
disorders often start at a young age. They reduce people’s functioning and often are
recurring.
For these reasons, depression is the leading cause of disability worldwide in terms of total
years lost due to disability. The demand for curbing depression and other mental health
conditions is on the rise globally.
The aim of this project is to develop an application which will make the users feel that they
always have someone who will listen to their problems and help to talk them out of
depression and strive towards reducing the percentage of suicide in the country.
Socialization is a process that introduces people to social norms and customs. This process
helps individuals function well in society, and, in turn, helps society run smoothly. Family
members, teachers, religious leaders, and peers all play roles in a person's socialization.
Finally, some ways in which health promotion might build on the findings are identified and
discussed.
CONTENTS
1. Introduction
2. Software Requirement Specification
3. High Level Design
4. Detailed Design
5. Implementation
6. Testing
Chapter 1
INTRODUCTION
Introduction
CHAPTER 1
INTRODUCTION
This report documents how mental disorders are detrimental to the development of low- and
middle-income countries and the poor within these countries. It proposes cost-effective
solutions that can be adopted by countries to promote development. Suicide is an extreme but
common outcome for people with untreated mental disorders, particularly depression and
substance abuse, which are associated with up to 90% of all cases of suicide in some
countries . Contrary to the common belief that these are concerns of high-income countries
only, mental disorders and their effects are also important issues for developing countries.
Over 80% of people suffering from mental disorders such as epilepsy, schizophrenia,
depression, intellectual disability, alcohol use disorders and those committing suicide are
living in low- and middle-income countries . Mental health has been hidden behind a curtain
of stigma and discrimination for too long. It is time to bring it out into the open. The
magnitude, suffering and burden in terms of disability and costs for individuals, families and
societies are staggering. In the last few years, the world has become more aware of this
enormous burden and the potential for mental health gains. We can make a difference using
existing knowledge ready to be applied.
We need to enhance our investment in mental health substantially and we need to do it now.
1.1 PURPOSE
Mental health includes our emotional, psychological, and social well-being. It affects how we
think, feel, and act. It also helps determine how we handle stress, relate to others, and make
choices. Mental health is important at every stage of life, from childhood and adolescence
through adulthood.
Department of ISE, Sir MVIT
Introduction
The focus of this project is to create a user friendly interface for people suffering due
to mental health disorders and depression , help them to overcome the phase through
advanced features .
1.2 SCOPE
The project involved seeking information both from young people representative of the
general community and also from a number of groups regarded as being at particular risk -
for example young people who have previously attempted suicide, young people with a
mental illness, young people living in rural and remote areas,what the Brief describes as
'marginalised or seriously disaffected' young people who may engage in self-harming
behaviour . These promising innovations in treatment and care can be customized as per the
context for scale up and integrated into the primary healthcare system through the District
Mental Health Programme. The innovative approach not only makes mental health services
more accessible and affordable but also empowering in nature by encouraging community
members in early detection, prevention of mental illness and appropriate treatment referral to
existing primary health care services.
[1] Paper Name: Machine learning in mental health: a scoping review of methods
and applications
Authors: Andrian B R Shatte
Methods Used: employed a scoping review methodology to rapidly map the field of ML
in mental health. Eight health and information technology research databases were
searched for papers covering this domain. Articles were assessed by two reviewers, and
data were extracted on the article's mental health application, ML technique, data type,
and study results. Articles were then synthesised via narrative review.
Methods Used: Expenditures are modeled using generalized linear models with a log
link for quantity and a probit model for any utilization. We adjust for group differences
in health status by transforming the entire distribution of health status for minority
populations to approximate the white distribution. We compare disparities according to
the IOM definition to other methods commonly used to assess health services disparities.
[3] Paper Name: Natural Language Processing in mental health application using non
clinical texts
Authors: Rafael A Calcvo and David N Milne
Methods Used: In the period between August 2014 and May 2015, the authors
performed multiple searches using Google Scholar. Relevant research published after this
period was added during the reviewing process. Google Scholar was chosen because it
indexes journals, conferences and patent documents. Conference papers and patents are
particularly important sources because a significant amount of the research in NLP and
computer science is not published in journals, which is the standard in the mental health
domain.
Results: Text-driven psychological interventions are possibly the most common form of
Internet intervention.Online counseling and peer support groups provide human-to-
human communication where the computer mediation can add significant value through
automatic triaging, summarization and personalization of the interventions.
[4] Paper Name: Digital Health application in mental Health care for immigrants and
refugees
Authors: Andrien Liem and Jimmy.
Methods Used: This review adopted a rapid review methodology. Available literature
was searched in three online databases January 1, 2005, to February 28, 2019. Studies
were included if they (1) applied digital health technologies, (2) focused on immigrants,
refugees, or asylum seekers without age and country limitation, (3) reported nonclinical
and/or clinical outcomes, and (4) were published in English or Indonesian. Narrative
synthesis was developed based on the data extraction and quality assessment.
Results: The ethical standards of these digital health applications were poorly
implemented and reported. Stigma toward mental disorders and lack of technology
literacy were the main challenges in scaling up digital health applications for immigrants
and refugees.
[5] Paper Name: Mental Health care application for Primary health care workers .
Authors: Ed-Edily Mohd. Azhari, Muhd. Mudzakkir Mohd. Hatta, Zaw Zaw Htike
Department of ISE, Sir MVIT
Introduction
Methods Used: The principal goal of the MEGA project is to provide youth with better
access to mental health services and appropriate care, by developing a mental health
screening mobile application tool to be used in PHC settings in South Africa and Zambia.
In this study, we will use a mixed methods multi-center study design. In phase one, we
will investigate the mental health literacy of PHC practitioners to identify areas in need
of development.
Results: common psychiatric disorders remain largely undetected and untreated in PHC
settings. By identifying limitations in PHC workers knowledge with regard to youth
mental health, we aspire to improve the depression care provided to youth in Southern by
developing and implementing a locally relevant m-health application.
1.7 SUMMARY
Web apps have significant potential to deliver high-efficacy mental health interventions. Given the global sho
the lack of mental health care access in rural regions, apps have emerged as a viable tool to bridge the mental
Technology is well-poised to transform how mental health treatment is delivered and accessed, but this transf
combined mobilization of science, regulation, and design.
Web apps have significant potential to deliver high-efficacy mental health interventions. Given the global sho
the lack of mental health care access in rural regions, apps have emerged as a viable tool to bridge the mental
Technology is well-poised to transform how mental health treatment is delivered and accessed, but this transf
combined mobilization of science, regulation, and Web apps have significant potential to deliver high-efficac
interventions. Given the global shortage of psychiatrists and the lack of mental health care access in rural reg
as a viable tool to bridge the mental health treatment gap. Technology is well-poised to transform how menta
delivered and accessed, but this transformation requires the combined mobilization of science, regulation, and
CHAPTER 2
2.1 INTRODUCTION
Non-Functional requirements are not directly concerned with the specific functions
delivered by the system. These are constraints on the service or functions offered by the
system. They include timing constraints, constraints on the developing process and
standards. They may relate to emergent system properties such as reliability, response
time and store occupancy. Alternatively, they may define constraints on the system such
as the capabilities of I/O devices and the data representations used in system interfaces.
Non-Functional requirements often applied to the system as a whole. They do not
usually just apply to an individual system's features and services.
Performance: CPU time of the proposed software varies from 4seconds to 6seconds
and PSNR value from 25dB to 26dB.
Modifiability: Another key factor that the system should consider is modifiability.
As the system might have to be integrated with other systems and mounted on other
platforms in future, it should be modifiable.
Reliability: The system should be robust in producing results and should be reliable
at all times. The application should not crash under any circumstances such as a user
trying to load unsupported files, etc. It should show appropriate messages for every user
generated message.
Response time: The system should respond in the least amount of time possible.
Usability: The application developed should be easy to use and user friendly. User
must be able to understand and use the components of the application without any
ambiguities.
Robust: The application should be able to produce correct output for all kinds of
inputs given by the user which may have different images of different noises and
intensities.
Department of ISE, Sir MVIT
Software Requirement Specification
2.6 ADVANTAGES
2.7 SUMMARY
This chapter contains the essential functional and non - functional requirements the system
should adhere to the overall general perspective of the system‘s behavior, the hardware,
software and interfaces that are being used. It helps in the generation of the system
architecture and the high level design with more attention to details. It can be implemented
on any system which meets the requirements as mentioned above.
CHAPTER 3
The High-level design is used to explain the design aspect of the functional modules
and the interface between them. It provides an overview of a solution, system, product,
service, or processes. Such an overview is important in a multi-project development to make
sure that each supporting component design will be compatible with its neighboring designs
and with the big picture.
User Constraints
Using this system is fairly simple and intuitive.. A user familiar with basic computer
operability skills should be able to understand all functionality provided by the system.
Hardware Constraints
The system should work on most home desktop and laptop computers and can be extended to
mobile phone apps.
The user must understand the basic English language to understand the terms.
System shall be able to interface with other components according to their specifications.
The system is not limited to any Operating System. It works equally well on Windows, Mac
and LINUX.
Department of ISE, Sir MVIT
High Level Design
System Architecture is the conceptual model that defines the structure, behavior and
more views of a system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the
structure of a system which comprises system components, the externally visible
properties of those components, the relationships (example the behavior) between
them and provides a plan from which products can be procured, and systems
developed, that will work together to implement the overall system. The language for
architecture description is called architecture description language (ADL).
3.6 SUMMARY
CHAPTER 4
DETAILED DESIGN
4.1 PURPOSE
The purpose of the design phase is to bring the conceived project to the real stage using
various technologies by creating a user interface using which the user can interact with the
system and the system produces the required results to the users.
User Interface:
The user interface is the aggregate of means by which people interact with a particular
machine, device and computer program other complex tool. The user interface provides the
means of either
Graphical user interface: Accepts input via devices such as computer, keyboard and mouse
clicks etc. Displays the output on devices like monitors.
Software graphical user interfaces are the one from which the end users that is client or
administrator interact with the system with the help of buttons, checkboxes, radio buttons, text
box etc.
The user interface for this project will be implemented by developing the following
wireframes for the different screens
1. Login Page
2. Home Page
Department of ISE, Sir MVIT
Detailed Design
The login screen of WEvolve is shown in the following figure. The left hand side of the
screen has the logo and name of the application. Users can login using a button by using face
recognition or manually by entering the username and password.
Login Screen
Home Screen
4.3 SUMMARY
This chapter helps us know how the creation of user interfaces happen. It summarizes
the various GUI components used and their use in the project.
CHAPTER 5
IMPLEMENTATION
5.1 IMPLEMENTATION
Our application is built in such a way that it is independent of the platform. It will run
well in Mac OSX, Windows as well as Linux.
Department of ISE, Sir MVIT
Implementation
Throughout our code, we have given meaningful variable names and functions so that it is
intuitive for anyone who is seeing the code.
Our project is developed by keeping in mind the various features and screens and a
hierarchical tree structure is given for the different files in the project.
1. Managing Folders:
The Current Folder Browser provides a few features to make managing separate
folders easier. The tree views multiple projects from a root directory. Having a top-down
hierarchical view makes it easy to move files between project directories. The address bar is
used for quickly switching back and forth between project directories.
2. Write Comments:
Having comment lines in files enables the functions, scripts, and classes to participate
in functions like help and look for. When a directory is supplied to the help function it reads
out a list of functions in that directory. The display may be customized with a Contents.m
file, which can be generated with the Contents Report.
All the properties like database name, API’s and other configuration data is written in a
separate properties file so that it can easily be changed in only one place if at all there is any
change.
Department of ISE, Sir MVIT
Testing
CHAPTER 6
TESTING
Software testing is an investigation conducted to provide stakeholders with information about the qualit
under test. Software testing can also provide an objective, independent view of the software to allow the
understand the risks of software implementation. Test techniques include the process of executing a prog
intent of finding software bugs (errors or other defects).
It involves the execution of a software component or system component to evaluate one or more properties
properties indicate the extent to which the component or system under test:
● Is sufficiently usable.
As the number of possible tests for even simple software components is practically infinite, all software te
select tests that are feasible for the available time and resources. As a result, software testing typically (but
execute a program or application with the intent of finding software bugs (errors or other defects).
Software testing can provide objective, independent information about the quality of software and risk o
sponsors.
Software testing can be conducted as soon as executable software (even if partially complete) exists. The o
development often determines when and how testing is conducted. For example, in a phased process, most
requirements have been defined and then implemented in testable programs. In contrast, under an Ag
programming, and testing are often done concurrently.
Unit Testing: Unit testing, also known as component testing, refers to tests that
verify the functionality of a specific section of code, usually at the function level.
Integration Testing: Integration testing is any type of software testing that seeks to
verify the interfaces between components against a software design.
Unit testing, also known as component testing, refers to tests that verify the functionality of a
specific section of code, usually at the function level. In an object-oriented environment, this
is usually at the class level, and the minimal unit tests include the constructors and
destructors.
These types of tests are usually written by developers as they work on code (white-box
style), to ensure that the specific function is working as expected. One function might have
multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot
verify the functionality of a piece of software, but rather is used to ensure that the building
blocks of the software work independently from each other.
Integration testing 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 ("big bang"). Normally the former is considered a better practice
since it allows interface issues to be located more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction between
integrated components (modules). Progressively larger groups of tested software components
corresponding to elements of the architectural design are integrated and tested until the
software works as a system.
Black-box testing treats the software as a "black box", examining functionality without any
knowledge of internal implementation. The testers are only aware of what the software is
supposed to do, not how it does it. Black-box testing methods include: equivalence
partitioning, boundary value analysis, all-pairs testing, state transition tables, decision table
testing, fuzz testing, model-based testing, use case testing, exploratory testing and
specification-based testing.
system, as well as programming skills, are used to design test cases. The tester chooses
inputs
to exercise paths through the code and determine the appropriate outputs. While white-box
testing can be applied at the unit, integration and system levels of the software testing
process, it is usually done at the unit level. It can test paths within a unit, paths between units
during integration, and between subsystems during a system–level test. Though this method
of test design can uncover many errors or problems, it might not detect unimplemented parts
Chapter 7
CONCLUSIONS
Conclusion
CHAPTER 7
CONCLUSION
The goal of this project is to develop a Mental Health application using Face Recognition for
login with a good performance rate.The aim is to normalise people talking about mental
health and keep their bodies and their minds as a priority in this fast pacing world. All
concepts are implemented on the selected tech stack using our own written codes, with only a
minimalistic use of in-built functions. A GUI is also developed which enables the above
application to have a user friendly interface.
Department of ISE, Sir MVIT
REFERENCES
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3146226/
https://www.medicalnewstoday.com/articles/322395#symptoms
https://www.medicalnewstoday.com/articles/193026#causes
https://www.verywellmind.com/depression-research-paper-topics-1066996
https://www.healthpovertyaction.org/news-events/mental-health-world-health-day-
2017/
https://www.who.int/mental_health/management/depression/