INF20003 project 1 Outline Individual

This report evaluates GRTM stakeholder and the interaction of medical professionals with GRTM, requirements determinant, primary functional requirements, implications of the functional requirement system, GRTM non-functional requirements, and evaluation of next wearable healthcare devices. It also includes a context diagram, event table, DFD fragments, and ERD diagram. Subject: INF20003, Course Name: Information Systems, College/University: University of Melbourne

INF2003 PROJECT 1
OUTLINE INDIVIDUAL

Table of Contents
INTRODUCTION...........................................................................................................................3
PART A...........................................................................................................................................3
1. Stakeholder of GRTM and will there is interaction of medical professional in GRTM.........3
2. The determinant of requirements.............................................................................................3
3. System primary function requirement.....................................................................................4
4. Implications of the functional requirement system.................................................................5
5. GRTM non-functional requirements.......................................................................................5
6. Evaluation of next wearable healthcare devices should focus by the managers of
MedTechCorp..............................................................................................................................6
PART B...........................................................................................................................................7
1. Context diagram.......................................................................................................................7
2. Event table...............................................................................................................................8
3. DFD fragments for use cases.................................................................................................10
4. ERD diagram.........................................................................................................................11
5. Level 1 Data flow diagram (DFD).........................................................................................12
CONCLUSION..............................................................................................................................14
REFERENCES................................................................................................................................1

INTRODUCTION
Glucose real time measuring (GRTM) is the glucose body level measuring device which
measure the presence of glucose in the body of the patients. The first part of the report will study
GRTM stakeholder and the interaction of medical professional with GRTM (Ioushua and Eldar,
2019). Further, the report will study the requirements of determinant to GRTM. The report will
study the requirements of primary functional. The report will study the functional requirement
system implication. Further, the report will identify the non-functional and functional
requirements. The report will provide the recommendation on future product development in the
industry of health care. In the second part report will focus on the product requirements through
data and technical. Further, the report will include the ERD and context diagram and will create
the DFD fragments and event table.
PART A
1. Stakeholder of GRTM and will there is interaction of medical professional in GRTM
To the system of GRTM there will be the direct connection of the stakeholders of GRTM.
The stakeholders live outcomes can define the outcomes of system. To benefit the patients in
their health the system was used by the main stakeholders. Caregivers and the patients are the
main stakeholders (Qian, Li and Chen, 2021). The transformation of the information provided by
doctors to caregivers through the devices. There was a direct association with the system by
updating data by the person. Members of project team, doctors, medical staff, patients, engineers
of medical equipment and technical staff are the stakeholders.
In the system the most important stakeholders are the patients. The requirements of the
system can be defined by patients as the system directly affect the patient. Physician can use the
other medical professional input to become more effective. Medical professional can provide
input as the system data was understood by the professional (Dupuy, Guille and Jacques, 2022).
2. The determinant of requirements
The stakeholders need can be met efficiently by collecting the essential requirements in
the process of gathering requirements. The resource can be effectively analysed through
gathering the requirements. Stakeholders will get higher satisfaction and the delivery of product
will be benefit due to the fewer defects. To manage the service of the product implementation the
stakeholder requirements are gathered. Apple phones were efficiently worked with the system

designed. Android phones fails in operating the system. Questionnaire, interview, brainstorming
and observation are the different techniques for requirements of gathering. To provide the better
service to the customer the GRTM system was designed (Lew and et.al., 2020). To associate the
GRTM components there was developed a set of questionnaire:
Question1. To implement the GRTM into smartphones what features will required?
Question2. Will GRTM device will improve the health?
Question3. To develop the GRTM in device how much time will be required?
Question4. Does android system include the operating system?
Question5. Which features the patients will receive?
3. System primary function requirement
To use the product there will be offering of feature is known as the functional
requirements. The requirements can be identified in a better way by efficiently determining the
functional requirement. Analysing the functional requirement use will expect the behaviour
system to perform easily. The features can be easily understood to the people by determining
every system with the functional requirements (Ioushua and Eldar, 2019). To easily understand
the features of GRTM it should associate with the functional requirements. Requirement
association primary function are:
 In the body the real time level of glucose can be monitored by the login the device by the
user.
 Patients health condition can be easily understood when the personal details were
provided by the user.
 In the body the current level of glucose can be viewed by the patients.
 There will be the association of view of history and trends by the patients with the level
of glucose (Zang, Zhang and Chen, 2021).
 In the body the high and the low level of glucose will be alerted to the patients.
 Threshold alert will be set by the medical personnel.
 Using of the application will allow the patient to communicate with the management
personnel.
 To provide the better treatment to the patient the medical personnel will able to view the
history of the patient.

 Determining of the floor on the beta glucose there will be able to set the alerts by the
patients.
 On the sudden fall of glucose the patients were capable of requesting the emergency help
(Ioushua and Eldar, 2019).
 The alerts were set by the patients regard with the doctor's appointment.
 Using of the system will help the patients in getting the monthly glucose level record.
 To take the medicine at time the patients were able to set the alarms accordingly.
4. Implications of the functional requirement system
To each patient there will be different measurement of parameters. Doctors should
manually schedule the alerts. According to the patients requirements the alerts where should be
scheduled. The measure was depended on the patient for someone it would be low and for some
other person it would be high. To all the devices the criteria for measurement and readings are
same. Over the time period of changing the condition of health of a person the reading alert and
measurement may change (Gonzalez and et.al.). Thus, according there will also change in the
patient medical history. The alerts should be regulated by the doctors according to the
requirements. The identification of the alert system through doctor functional requirement.
Therefore, the functional requirement's system does not have implication due to the change in the
patient health condition. To the mind changing possibilities there will be the development of
system.
5. GRTM non-functional requirements
The system which were associated with the quality are refereed as non functional
requirements. To easily identify overall system performance the determinant of non functional
requirements is important. Non functional requirements should be determined by the system
analyst which will benefit the user to easy understand the application features (Lew and et.al.,
2020). The glucose real time monitoring system non functional requirements are:
 Accuracy- Patients get better facility as glucose real time measuring system collect
accurate data of patient. System performance can be evaluated easily after the process of
collecting accurate data. Users will get proper service only when the device collects
accurate data.

 Secured- Patients using the glucose real time monitoring system is secured as the system
offered encrypted communication. Users will get proper control over the application and
will get the higher security (Zang, Zhang and Chen, 2021).
 Flexibility- Both the android and the iPhone users can use the interface as the system was
developed flexible. All the set of data can be accessed by the users as the proper
flexibility of the system.
 Accessibility- There will be no issue to any patients as the interface of the system was
designed for easy access. Users will get better service with the help of greater
accessibility (Ioushua and Eldar, 2019).
 Efficient- Evaluating the past record of the patient will help in producing the efficient
data by the system. Patients overall level of glucose can be determined easily through the
glucose real time monitoring system.
 Transparency- The system will provide the better support as the system was well
designed (Gonzalez and et.al.). To easily manage the system of overall performance the
system provide the huge transparency for the patient. Patients will get better offering in
the service because there will be the maintaining of the transparency.
 Integrity- Users will easily get the best offering by using the application of glucose
monitoring. System will maintain the essential data was users privately.
6. Evaluation of next wearable healthcare devices should focus by the managers of
MedTechCorp
The system of android is currently not capable to work with GRTM which should be
focused by the managers of MedTechCorp. The person who do not use the iPhone will not able
to use the device which will difficult for the organization. According to the organizational
planning the system should be compatible with the android device, it is a major drawback for the
company (Zang, Zhang and Chen, 2021). Organization all data cloud storing system should be
integrated with the platform database. The set of data can be properly accessed by the user
through this. Developers of android and the person having expertise in the skill of database
handling should be hired by the managers.

PART B
1. Context diagram
This diagram usually defines how external records (Entities) interrelate with internal
software network. It is widely used in business where it assists them to wrap their business
objectives around system's scope (Shao and et.al 2020). As a result they aim to design a new
system which consists of all needful things to improvise the existing system. DFD 0 level
sometimes also called as context diagram, it's a basic structure of overall system, it is important
because it helps in analysing the interfaces which needed to be considered. Above context
diagram is made for the medTechCorp medical devices, as their GRTM device is compatible
with apple iPhones while it is still not integrated with android devices.

Context diagram
2. Event table
Event table in system discuss how changes are made in application table and it also concerns
with identification of changed row. To design an event table it is important to create more than
one triggers, where triggers can be understood as database that is created which can easily runs
the SQL script when pre identified action occurs. For this project event table is made by using
level 0 data flow diagram where it discusses what are the certain events triggered in the system.

EVENT TRIGGERS SOURCES SPECIFIC
ACTION
RESPONSE DESTINATION
View
alert
Alert System Specify alert Prepare
response for
alert
Doctor
Physician
respond
to alert
Alert System Alert data Forwarding it
to doctor
Doctor
condition
s
Set
conditions
for alert
System Checking alert Respond to
alert
doctor
Patient High rate in
blood
glucose,
sends
message to
doctor
doctor Send message to
patient
Wait for
patient
patient
Annotate
history
Checking
online
patient Annotate history Keep data System
View
history
Check online system View history Check history patient
Respond
to alert
alert Patient Response Alert doctor doctor

3. DFD fragments for use cases
DFD fragments usually presented by the row within table records, every fragment refers
as single process over Data flow diagram, then moving on all fragments associates and form a 0
level DFD diagram. It helps in mapping out data flow of system where it suitably discusses how
records in the system interacts with each other as how data flow from one fragments to other
fragments. Below are the diagram that discuss the data flow fragments based on the use cases
where it shows how patient can view their history in the system, further it shows how messaging
in the system can be done.
a) View history
b)Send message to physician

c)Send message to patient
4. ERD diagram
Entity relationship diagram a flowchart that shows how entities which carries details of
the system interlinked with each other (Heayyoung and et.al, 2018). It is a graphical
representation that shows how relationship can be shown between data present or stored within a
system. It is essential for modelling the system as how information is arranged within the
database system so that it can easily retrieved anytime. ER diagram also specify which
information need to be keep in system where, attributes of entity involves the properties that
defines the type of entity.

ER diagram
5. Level 1 Data flow diagram (DFD)
In level 1 data flow diagram, where single process node shown in context diagram further
divides into subprocesses so that better understanding about system can be achieved. Such
processes are included, so diagram requires an additional flow of data which is stored and linked
with each other. Thus DFD provides the information related to input and output of every
processes, where DFD generally don't have control flow where no decisions rules are applied.
Below discussed an level 1DFD.

Level 1 DFD

CONCLUSION
It has been concluded from the above report that the level of glucose in the body can be
measured through setting the alerts. The first part of the report evaluated the function
requirement system implications to the patients. Further, the report identified the functional
requirements of GRTM. Further, the report evaluated the involvement of medical professional in
GRTM and identified the major stakeholder of GRTM. Thus, the report evaluated the
determinant of functional requirement and prepared questions to associate the components of
GRTM. The primary function requirement system was evaluated. Lastly, the report provided the
evaluation to MedTechCorp managers about the next wearable devices of healthcare.

REFERENCES
Books and Journals
Dupuy, J., Guille, A. and Jacques, J., 2022. Anchor Prediction: A Topic Modeling
Approach. arXiv preprint arXiv:2205.14631.
Gonzalez, A.G., and et.al. A Supervisory Control-Based Navigation Architecture for Multiple
Autonomous Robots in Industry 4.0 Environments.
Heayyoung, J.O. and et.al, 2018. Ripple effect analysis of data flow diagram in modification of
data flow requirements. IEICE Technical Report; IEICE Tech. Rep.. 117(465). pp.61-66.
Ioushua, S.S. and Eldar, Y.C., 2019. A family of hybrid analog–digital beamforming methods
for massive MIMO systems. IEEE Transactions on Signal Processing. 67(12). pp.3243-
3257.
Lew, R., and et.al., 2020. The rate of dasotraline brain entry is slow following intravenous
administration. Psychopharmacology. 237(11). pp.3435-3446.
Qian, Y., Li, Z. and Chen, X., 2021. An Improved Method for Computing Broadband Green’s
Functions of Surface Sources and Its Application to Inverting the Processes of the 2017
Xinmo Landslide. Seismological Research Letters. 92(5). pp.3113-3125.
Shao, W. and et.al 2020, November. Extraction and Recognition of Device Graphics in Process
Flow Diagram. In 2020 IEEE 9th Data Driven Control and Learning Systems Conference
(DDCLS) (pp. 778-782). IEEE.
Zang, N., Zhang, W. and Chen, X., 2021. An overset-grid finite-difference algorithm for
simulating elastic wave propagation in media with complex free-surface
topography. Geophysics. 86(4). pp.T277-T292.