3. INTRODUCTION
Based on a new report in Britain, shown that a third of people who consciously put off
seeing their doctor do so for fear of finding bad news with middle-aged men the worse
culprits[1]. So, Early Diseases Diagnosis System is a reliable system that can help the users to get
early diagnosis about their diseases based on the selection of the symptoms and issues. It is a
system that can let the users know about their health better before make an appointment for
further knowledge with medical practitioners. The users only need to answer a certain number of
questions regarding the symptoms that they have then the system will respond by displaying the
diseases that the users encountered with based on the selected symptoms. In order to display the
result, there are two things the system need to decide; (1) what is the disease that related with the
symptoms, (2) how severe the disease is. For the first question, the decision tree will be used.
While the second question will be answered by using weighted sum model. The higher the
weight, the more severe the disease.
4. OBJECTIVES
• To develop a system that meet all the requirements in minimizing time and
money consuming to go to the clinic or any health institutes for the medical
check-up.
• To design a system that ease the user in checking of their health.
• To test the system that has been implemented with Weighted Sum Model in
calculating the severity of the diseases.
5. SCOPE
• Target user
• The people who are scared of bad news especially regarding their health conditions and those who are trying
to help their love ones in facing the diseases are the main target as the user of the system.
• The user does needs to has an account to know about their symptoms. He /she just need to answer the
questions in order to know about their conditions. They can do so by answering the questions provided by
the system about their symptoms.
• Admin
• Admin is a person in charge and can be a doctor to manage this system. He/she can add, edit, view and delete
any questions whenever he/she needed. Admin also can add new set of questions about different diseases.
The main role of the admin is to ensure that the system is functioning well and does not give unrelated results
about the diseases. Besides, they also need to display the questionnaire that are suitable according to time and
relevant to be used.
• Target system
• This system is to be as a web-based system that can help users in knowing about their health conditions. The
results of the answered questionnaire will be regarding on what kind of diseases that the user suffered, and
what to do next about their diseases
7. CONTEXT DIAGRAM
• Mental Health Diagnosis System process at the centre.
• There are two actors that mainly involved in this system, they
are USER and ADMIN.
• There are 5 flows incoming and outgoing of the ADMIN and 4
flows that incoming and outgoing of the USER. So in total
there are 9 flows incoming and outgoing the system.
• As for the USER, there are 3 outgoing flows; USERS’
INFORMATION, USERS’ ANSWER and FEEDBACK
INFORMATION, and 1 incoming flow; RESULTS’ DETAILS.
• As for the ADMIN, there are 4 outgoing flows; ADMIN’S
INFORMATIONS, QUESTIONS INFORMATION,
SUGGESTION INFORMATION and REPORT DETAILS, and 1
incoming flow; FEEDBACK DETAILS.
8. DFD LEVEL 0
• Consists of 8 processes, 2 entities and 6
data dictionaries.
9. DFD LEVEL 1
• PROCESS 2.0 : MANAGE USER
• A USER inputs USERS INFORMATION into LOGIN
process, D1-USER will retrieve USERS DETAILS that
been stored from REGISTRATION process.
• The USER will get the USER AUTHENTICATION and
capable to access VIEW DETAILS and UPDATE
DETAILS processes. The updated details will be
stored as USERS DETAILS in D1-USER thru process
UPDATE DETAILS.
• The USER also get the USER AUTHENTICATION to
go to MANAGE QUESTION process after the LOGIN.
10. DFD LEVEL 1
• PROCESS 3.0: MANAGE ADMIN
• An ADMIN inputs ADMINS INFORMATION into LOGIN
process, D2-ADMIN will retrieve ADMIN DETAILS that
been stored before.
• The ADMIN will get the ADMIN AUTHENTICATION and
capable to access VIEW DETAILS, UPDATE DETAILS and
ADD NEW ADMIN processes. The updated details will be
stored as ADMIN DETAILS in D2-ADMIN thru process
UPDATE DETAILS. The ADMIN DETAILS from process
ADD NEW ADMIN will be stored in D2-ADMIN.
• The ADMIN also get the ADMIN AUTHENTICATION to
go to MANAGE QUESTION process after the LOGIN.
11. DFD LEVEL 1
• PROCESS 4.0: MANAGE QUESTION
• The ADMIN will get the ADMIN AUTHENTICATION from
Process 3.0. He will get access to ADD NEW QUESTION, VIEW
QUESTION, UPDATE QUESTION and DELETE QUESTION.
• The ADMIN will input QUESTIONS’ INFORMARTION to ADD
NEW QUESTION, will be output as QUESTIONS’ DETAILS soon
will be stored into D3-QUESTION.
• The ADMIN can VIEW QUESTION soon can either UPDATE
QUESTION or DELETE QUESTION. The UPDATE QUESTION
output will be stored into D3-QUESTION while the DELETE
QUESTION will be retrieved from D3-QUESTION and will be
deleted.
• The USER will get the USER AUTHENTICATION from Process
2.0. The USER can VIEW QUESTION and answer the question at
the same time. The output of VIEW QUESTION will be directed
to MANAGE RESULT as USERS’ANSWER.
12. DFD LEVEL 1
• PROCESS 5.0: MANAGE RESULT
• The ADMIN can ADD RESULT, UPDATE RESULT
and DELETE RESULT. The RESULT INFORMATION
input by ADMIN thru ADD RESULT and UPDATE
RESULT will be stored in D4-RESULT as RESULT
DETAILS.
• The USERS ANSWER from previous process will be
calculated in this process. The USERS ANSWER will
going thru CALCULATE WSM and CALCULATE
SYMPROMS processes.
• In order to CALCULATE SYMPTOMS, the
QUESTION DETAILS from D3-QUESTION will be
retrieved.
• The USER will capable to get FULL RESULT thru
process VIEW RESULT where the data come from D4-
RESULT, CALCULATE SYMPTOMS, CALCULATE
WSM and MANAGE SUGGESTION.
13. DFD LEVEL 1
• PROCESS 6.0: MANAGE SUGGESTION
• The ADMIN can ADD SUGGESTION, VIEW
SUGGESTION, UPDATE SUGGESTION and DELETE
SUGGESTION. The SUGGESTION INFORMATION input
by ADMIN thru ADD SUGGESTION and UPDATE
SUGGESTION will be stored in D5-SUGGESTION as
SUGGESTION DETAILS.
• The SUGGESTION will be directed to Process MANAGE
RESULT as one of the input in displaying the FULL
RESULT to the USER.
14. DFD LEVEL 1
• PROCESS 7.0: MANAGE FEEDBACK
• The USER can ADD FEEDBACK and
VIEW FEEDBACK. The FEEDBACK
INFORMATION input by USER thru
ADD FEEDBACK will be stored in D6-
FEEDBACK as FEEDBACK DETAILS.
• The ADMIN can VIEW FEEDBACK and
DELETE FEEDBACK
19. SOLUTION COMPLEXITY
n = number of alternative
j = initial number of alternative
wj = weight of jth criterion
aij = value of the jth of i criterion
20. SOLUTION COMPLEXITY
• For example:
• Question 1 of Anxiety Test - How often have you been bothered by feeling
nervous, anxious or on edge over the last two weeks?
• Not at all [0]
• Several days [1]
• More than half the days [2]
• Nearly every days [3]
• Let’s say the user choose “Not at all” which is the weight is [0]
21. SOLUTION COMPLEXITY: Example of code:-
If (question1 == 0){
a++; // increment number of question with the answer weighted 0
Else if (question1 == 1){
b++; //increment number of question with the answer weighted 1
Else if (question1 == 2) {
c++; //increment number of question with the answer weighted 2
Else
d++; //increment number of question with the answer weighted 3
}}}
22. SOLUTION COMPLEXITY: Calculation:-
• So, the calculation will be
• wsmanxiety = ∑ weight * numberofquestion
= (0*a) + (1*b) + (2*c) + (3*d)
• By doing so, it can be concluded that the higher the value of WSM the higher the
risk.