1. THE NEW FRONTIER RESEARCH ENGAGEMENT SYSTEM
Man Hung, Tao He
The purpose of the project
The goal of this project is to develop a research engagement system (a web-based application
product) that connects potential patients, caregivers and other stakeholders into patient-centered
outcomes research. This project will effectively bring the voice of patients and interested
stakeholders to the research process and maximize patient-centeredness across diverse
populations. It will also give patients, caregivers and others the opportunities to easily
collaborate with researchers.
The stakeholders
There are many stakeholders who may participate in a research study. Figure 1 depicts a map
showing the potential stakeholders or users of this research engagement system.
Figure 1: Stakeholders map.

2. Constraints
The product shall initially be developed on Macintosh and Windows-based machines. Future
development will include expansion to other operating systems and mobile application.
The scope of the work
The scope of the project includes developing a web-based application that can serve to connect
interested collaborators, including patients and various stakeholders, to formulate research
questions, develop research materials, determine research protocols and help to review and
disseminate research results.
The business data model
The product will consist of at least the following web pages.
(1) Main page:
a. Center page; top row is web title;
b. Two columns; left is pictures; right is <I am researcher> and <I am participant> and login
area (user name/password/forget password)
c. Bottom row is company and language chooses
(2) Register page:
a. Center page; top row is web title;
b. Register area
(a) Researcher: name/email/password/organization/title(/state/city/phone/biosketch/)interests
(b)
interests or project titles
c. Bottom row is company and language chooses
(3) Forgot password page:
a. Center page; top row is web title;
b. Password area

3. (a) Please input your registered email account. Password change link will be set by this link.
(b) Set new password and confirm your password again. Go to login page
c. Bottom row is company and language chooses
(4) Login page:
a. Center page; top row is web title;
b. Login area
(a) Choose login type: researcher / participant
(b) User name/password
(c)
c. Bottom row is company and language chooses
(5) User page:
a. Center page; top row has web title, login user’s menu buttons (small icon, Name,
message center) log off button
b. User menu column; (User Icon; profile)
(a) Researcher: left menu (message center; projects; collaborators; participants)
(b) Researcher: right menu (followers; followings)
(c) Participant: left menu (message center; projects; researchers;)
(d) Participant: right menu (followers; followings)
(e)
(6) Project page:
a. Center page; top row has web title, login user’s menu buttons (small icon, Name,
message center) log off button
b. Survey List; (survey title; status; authors; setting; responses; statistics; document;
preview) click on title will go to Survey edit page.
(7)

4. Figure 2 depicts the database enterprise relational model for the product.
Figure 2: Database EER model

5. Usability and humanity requirements
The following list the ease of use and learning requirements for all users of the product.
1. The product shall be easy for 10-year-old to 100-year-old to use.
2. The product shall help user to avoid making mistakes.
3. The product shall make the users want to use it.
4. The product shall be used by people with no training, and possibly no understanding of
English.
5. The product shall be accessible by elderly and people with disabilities and physical
challenges.
6. The product shall conform to the Americans with Disabilities Act.
7. The product shall retain the user’s research and other preferences.
8. The product shall allow the user to select a chosen language.
9. The product shall be easy for researchers, patients and all stakeholders to learn.
10. The product shall be able to be used by members of the public who will receive no
training before using it.
11. The product shall hide the details of the construct from the user.
12. The product shall use symbols and words that are naturally understandable by the general
public.
Security and privacy requirements
The following list the security requirements for the product.
1. The product shall prevent incorrect data from being introduced.
2. The product shall make its users aware of its information practices before collecting data
from them.

6. 3. The product shall notify users of changes to its information policy.
4. The product shall protect private information in accordance with the relevant privacy
laws.
5. The product shall not be offensive to religious or ethnic groups.
6. Personal information shall be implemented so as to comply with the Data Protection Act.