Family Medical History Management System

Associate Degree
in
Computer Science

Submitted By:

Rimsha Naz

Muskan Rasool

2018-GCUF-000001

2018-GCUF-000000

Submitted To:
Mr. Faheem Altaf

DEPARTMENT OF COMPUTER SCIENCE

Government College University Faisalabad

2021
Table of Contents
Table Of Content........................................................................................................................................ii
Revision History.........................................................................................................................................iii
1. Introduction..............................................................................................................................................1
1.1 General Information........................................................................................................................................1
1.2 Purpose...........................................................................................................................................................1
1.3 Document Conventions...................................................................................................................................1
1.4 Project Objective............................................................................................................................................1
1.5 Intended Audience and Reading Suggestions.................................................................................................2
1.6 Project Scope..................................................................................................................................................2
2. Overall Description..................................................................................................................................2
2.1 Product Perspective........................................................................................................................................2
2.2 Product Features.............................................................................................................................................3
2.3 User Classes and Characteristics.....................................................................................................................3
2.4 Operating Environment...................................................................................................................................3
2.5 Design and Implementation Constraints.........................................................................................................3
2.6 User Documentation.......................................................................................................................................3
2.7 Assumptions and Dependencies......................................................................................................................3
3. System Features.......................................................................................................................................4
3.1 System Feature 1............................................................................................................................................4
3.2 System Feature 2 (and so on)..........................................................................................................................5
4. External Interface Requirements...........................................................................................................5
4.1 User Interfaces................................................................................................................................................5
4.2 Hardware Interfaces........................................................................................................................................5
4.3 Software Interfaces.........................................................................................................................................5
4.4 Communications Interfaces............................................................................................................................5
5. Other Nonfunctional Requirements.......................................................................................................6
5.1 Performance Requirements.............................................................................................................................6
5.2 Safety Requirements.......................................................................................................................................6
5.3 Security Requirements....................................................................................................................................6
5.4 Software Quality Attributes............................................................................................................................6
6. WBS Project Management......................................................................................................................7
7. Analysis model.........................................................................................................................................7
7.1 Use Case Diagram...........................................................................................................................................7
7.2 Class Diagram.................................................................................................................................................7
7.3 Object Diagram...............................................................................................................................................7
7.4 Sequence Diagram..........................................................................................................................................7
7.5 Activity Diagram.............................................................................................................................................7
7.6 Collaboration Diagram....................................................................................................................................7
7.7 State Transition Diagram.................................................................................................................................7
7.8 ERD................................................................................................................................................................. 7
8. Tools & Technologies..............................................................................................................................7
8.1 Programming Languages................................................................................................................................7
8.2 Databases/Data storages.................................................................................................................................7
8.3 Operating System...........................................................................................................................................7
Appendix A: Glossary.................................................................................................................................8
Appendix B: Check List..............................................................................................................................9
Appendix C: Supervisory Committee......................................................................................................10
Revision History
Name Date Reason For Changes Version
 Government College University Faisalabad Page 4

1. Introduction

1.1 General Information

Project Name: Family Medical History Management

System Starting Date:
_

Controlling Agency: Final Date:

_ _
_
Prepared By: Authorized by:
_

1.2 Purpose

A family health history is a record of health information about a person and his or her close relatives. A
complete record includes information from three generations of relatives, including children, brothers and
sisters, parents, aunts and uncles, nieces and nephews, grandparents, and cousins.

1.3 Document Conventions

A family health history is a record of health information about a person and his or her close relatives. A
complete record includes information from three generations of relatives, including children, brothers and
sisters, parents, aunts and uncles, nieces and nephews, grandparents, and cousins.
1.4 Project Objective

A family health history can identify people with a higher-than-usual chance of having common disorders,
such as heart disease, high blood pressure, stroke, certain cancers, and type 2 diabetes. These complex
disorders are influenced by a combination of genetic factors, environmental conditions, and lifestyle choices.
A family history also can provide information about the risk of rarer conditions caused by variants
(mutations) in a single gene, such as cystic fibrosis and sickle cell disease.

1.5 Intended Audience and Reading Suggestions

While a family health history provides information about the risk of specific health concerns, having
relatives with a condition does not mean that an individual will definitely develop that condition. On the
other hand, a person with no family history of a disorder may still be at risk of developing the disorder.
 Government College University Faisalabad Page 5

1.6 Project Scope

The easiest way to get information about family health history is to talk to relatives about their health. Have
they had any health problems, and when did they occur? A family gathering could be a good time to discuss
these issues. Additionally, obtaining medical records and other documents (such as obituaries and death
certificates) can help complete a family health history. It is important to keep this information up-to-date and
to share it with a healthcare professional regularly.

2. Overall Description

2.1 Product Perspective

A family health history can identify people with a higher-than-usual chance of having common disorders,
such as heart disease, high blood pressure, stroke, certain cancers, and type 2 diabetes. These complex
disorders are influenced by a combination of genetic factors, environmental conditions, and lifestyle choices.

2.2 Product Features

A family history is a record of a family and of the lives of family members. A record of your family with you
as a child, containing recollections of your parents and other living ancestors. A record of your family with
you as a parent, containing recollections of your children and your other descendants.
2.3 User Classes and Characteristics
Knowing one’s family health history allows a person to take steps to reduce his or her risk. For
people at an increased risk of certain cancers, healthcare professionals may recommend more frequent
screening (such as mammography or colonoscopy) starting at an earlier age. Healthcare providers may also
encourage regular checkups or testing for people with a condition that runs in their family. Additionally,
lifestyle changes such as adopting a healthier diet, getting regular exercise, and quitting smoking help many
people lower their chances of developing heart disease and other common illnesses.
2.4 Operating Environment
This app is Offline WBS so it will run in any operating system with Entranet access through a web browser

2.5 Design and Implementation Constraints

A family health history can identify people with a higher-than-usual chance of having common disorders,
such as heart disease, high blood pressure, stroke, certain cancers, and type 2 diabetes. These complex
disorders are influenced by a combination of genetic factors, environmental conditions, and lifestyle choices.
A family history also can provide information about the risk of rarer conditions caused by variants
(mutations) in a single gene, such as cystic fibrosis and sickle cell disease.
 Government College University Faisalabad Page 6

2.6 User Documentation

The product will include a user manual. The user manual will include product overview, complete
configuration of the required software and hardware, technical details and contact information which will
include email address.
2.7 Assumptions and Dependencies
Family health history is a record of the diseases and health conditions in your family. You and your family
members share genes. You may also have behaviors in common, such as exercise habits and what you like to
eat. You may live in the same area and come into contact with similar things in the environment. Family
history includes all of these factors, any of which can affect your health.

3. System Features
Some Performance requirements identified is listed below:

 The database shall be able to accommodate a minimum record of Users.

 The software shall support use of multiple users at a time.
 There are no other specific performance requirements that will affect development.

3.1 System Feature 1

You can’t change your genes, but you can change unhealthy behaviors, such as smoking, not exercising
or being active, and poor eating habits. If you have a family health history of disease, you may have the most
to gain from lifestyle changes and screening tests. In many cases, healthy living habits can reduce your risk
for diseases that run in your family. Screening tests, such as blood sugar testing, mammograms,
and colorectal cancer screening, help find early signs of disease. Finding disease early can often mean better
health in the long run.

4. External Interface Requirements

4.1 User Interfaces

Registration Screen:
Various fields available on this screen will be:
-Login Name
-Email Id
-Password
Login Screen:
Fields available on this screen are:
-Login Name
-Password
4.2 Hardware Interfaces
Screen resolution of at least 800X600 is required for proper and complete viewing of screens. Higher
resolution will be accepted, and at least system must be core2-duo, minimum RAM at least 2Gb.
4.3 Software Interfaces
Any windows-based operating system.
 Windows 7
 Windows 8
 Windows 10
Or any upgraded operating system.

4.4 Communications Interfaces

None

5. Other Nonfunctional Requirements

5.1 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is
required to take the database backup

5.2 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access, use,
modification below.
Keep specific log or history data sets.

 Assign certain functions to different modules.

5.3 Software Quality Attributes
The Quality of the System is maintained in such a way so that it can be very user friendly
to all the users.
The software quality attributes are assumed as under:
 Accurate and hence reliable.
 Secured.
 Fast speed.
 Compatibility.

6. WBS Project Management

7. Analysis model
7.1 Use Case Diagram
7.2 Class Diagram
7.3 Object Diagram
7.4 Sequence Diagram
7.5 Activity Diagram
7.6 Collaboration Diagram
7.7 State Transition Diagram
7.8 ERD
8. Tools & Technologies
8.1.1 Programming Languages
HTML, CSS, Bootstrap, JavaScript, JQuery, PHP

8.1.2 Databases/Data storages

MySQL (Xammp, Womp)

8.2 Operating System

Any windows based operating system.

 Windows 7
 Windows 8
 Windows 10
Or any upgraded operating system.
Appendix A: Glossary

B: Analysis Models Appendix C: To Be Determined List

Appendix B: Check List
Check List Yes No
I. Starting/Ending Dates

II. Project Scope

III. Product modules (covering all aspects of scope)

IV. System Features (covering scope)

V. Interface Requirements

VI. Non-Functional Requirements

VII. WBS

VIII. Tools and Technologies Detail (for implementation)

IX. Plagiarism Report

Appendix C: Supervisory Committee

For Approval of any two Consultant Teachers

Teacher Consulted Teacher Consulted

Name: _ _. Name: _ _.

Designation: _ . Designation: _ .

Comments:_ Comments:_

_ _

_ _

_ __ _

_ _

Signature: _ Signature: _

---------------------------------------------------------------------

(For office use only)

Date:

 Approved Group ID:

 Meeting Required: Date: Time: Place:

 Rejected

Remarks:
Project Title (if Revised):

Project Coordinator