1 Introduction.....................................................................................................................................

2
1.1 Purpose .................................................................................................................................2
1.2 Project Scope and Product Features......................................................................................2
1.3 References.............................................................................................................................2
2. Functional requirements..................................................................................................................2
2.1 System Requirements...........................................................................................................2
2.2 Scope and Boundary............................................................................................................2
2.2.1 System Diagram........................................................................................................................2
2.2.2 System performance..................................................................................................................3
2.2.3 Interface.....................................................................................................................................4
2.3 System Boundary.........................................................................................................................4
2.4 Context Diagram..........................................................................................................................4
2.5 Business Events............................................................................................................................6
2.5.1 Test Procedure...........................................................................................................................6
2.6 Set Procedure................................................................................................................................7
2.7 Store Procedure............................................................................................................................8
2.8 External Events............................................................................................................................8
2.9 Temporal Events...........................................................................................................................9
2.10 Inputs and Outputs.....................................................................................................................9
2.10.1 Test Mode..............................................................................................................................10
2.10.2 Set Mode................................................................................................................................11
2.10.3 Store Mode............................................................................................................................11
2.11 Screens......................................................................................................................................11
3. Operating Environment Requirements.........................................................................................13
3.1 Hardware.............................................................................................................................13
3.2 Software..............................................................................................................................13
3.3 Communication ..................................................................................................................13
4．External Interface Requirements................................................................................................13
4.1 User Interfaces...................................................................................................................13
4.2 Hardware Interfaces...........................................................................................................14
4.3 Software Interfaces.............................................................................................................14
5 Other Nonfunctional Requirements..............................................................................................14
5.1 Performance Requirements................................................................................................14
5.2 Safety Requirements..........................................................................................................14
1 Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for the Glucose Test
Device (GTD). Contain the main process circuit, program system structure and functional
component division, provide basis for the schema design. This document is intended to be used by
the members of the project team that will implement and verify the correct functioning of the
system.

1.2 Project Scope and Product Features

The Glucose Test Device will permit diabetes patients or normal people test their blood sugar
content using a test strip with blood on it.

1.3 References
1. Lucas 郭明森. PPT of software engineering. School of Software Engineering, Tongji
University.
2. Ian Sommerville. Software Engineering, Eighth Edition. ISBN: 9787111204596
3. 软件工程之需求说明书—需求规格说明书
http://java.ccidnet.com/art/3561/20060314/476253_1.html

2. Functional requirements

2.1 System Requirements

The Glucose Testing Device is medical equipment which can be used to test user’s
blood glucose content. The Glucose Testing System processes for testing and
checking results in the Glucose Test Device. The system is expected to do glucose
testing and device setting, test results checking and moving.

2.2 Scope and Boundary

2.2.1 System Diagram

The GTD’s system diagram in Figure T2-1 illustrates the system’s functional
structure. The Glucose Testing includes three modes: test mode, set mode and store
mode.
 T2-1: System Diagram
Test Mode: In the test mode, user can do their test and check their test results.
Set Mode: In the set mode, user can reset the hour, minute, time format, year, month,
day and test result’s measurement in sequence.
Store Mode: In the store mode, user can use the USB interface to transfer their test
results into computer.

2.2.2 System performance

The GTD’s system performances in Figure T2-2 illustrate the system’s performances.
P_ID Description Response time uses
P_01 Press the M button to start the system <= 3 seconds
P_02 Check screen display(triggered by the events: insert a <= 5 seconds
test strip or system start)
P_03 Waiting for blood sample <= 5 seconds
P_04 Test results display <= 20 seconds
P_05 Test results history check(press the M button, when <=3 seconds
“mem” is displayed, within 3 seconds, the latest test
result will be displayed)
P_06 System reset(shut down GTD and press the M button > 3 seconds
more than 3 seconds, it will change into Set Mode)
P_07 Do a test <= 300 seconds
P_08 Test results upload(upload test history to PC via USB
)
P_07 Device automatic shut down(no button push) <=15 seconds
T2-2: System Performance Figure
2.2.3 Interface
Software interface: There’s no software interface.
Hardware interface: AC Plug-in, USB
User interface: User A/ User B

2.3 System Boundary

The GTD’s system boundary in Figure T2-3 illustrates the system’s boundary.

T2-3: System Boundary

2.4 Context Diagram

The context diagram in Figure T2-4 illustrates the external entities and system
interfaces.
 T2-4 System Context Diagram

User The test user can press M button to start the device within 3
seconds, when the system is started, it will check the screen,
and then you can insert a test paper and supply you blood
sample to do the test, the result will display within 30 seconds,
and you can check your test result, the system will be shut
down if no button push within 15 seconds. There are two
bottoms for all operation. User should do their test within 5
minutes
Screen The screen is a place where the test results will be displayed.
It can be display Battery Flag, AC Flag, Error Flag, User Flag,
Test result, Unit Flag, Date, Date Time and Progressive bar.
Test paper The user insert a test strip, wait 5 seconds, tester will be
allowed to supply his/her blood sample.
AC The user can use AC plug-in to connect AC
Computer The user can use GTD’s USB interface to connect his/her
computer and upload test history. In the store mode, if no
operation occur within 2 minutes, the system will be shut
down automatically
2.5 Business Events

2.5.1 Test Procedure

The test procedure in Figure T2-5 illustrates the test procedure.

T2-5 System Test Procedure

Test Procedure Description

Press the Button M(<= 3 seconds)
The system is started and initialized
Check Screen display(if there is no display error, do the test, else shut down the
device and press the M button more than 3 seconds, reset the device)
Select user A or B
Insert a test strip(wait 5 seconds)
Feed the strip tip with blood sample
After 30 seconds, the test result is displayed
(if there is no button push within 15 seconds, the system will be shut off)
Press the M button, then the “mem” flag will be displayed, within 5 seconds, the latest
test result will be displayed
2.6 Set Procedure
The set procedure in Figure T2-6 illustrates the set procedure.

T2-6 System Set Procedure

Set Procedure Description

Shut down the system(if the system is power on)
Press the Button M(> 3 seconds, the system will be restarted and initialized in set
mode)
Set hour (the hour flag is blinking, press the C button to increase one hour, when the
correct hour is displayed, press the M button to acknowledgement.)
Set minute (the same steps like hour setting)
Set date time format(the system’s default date time format is 12 hour, press the C
button to change it into 24 hour button, press the M button to acknowledgement.)
Set year (the same steps like hour setting)
Set month (the same steps like hour setting)
Set day (the same steps like hour setting)
Set unit (the system’s default unit is mol/L, press the C button to change it into mg/dL
format, press the M button to acknowledgement and exit Set mode.)
2.7 Store Procedure
The store procedure in Figure T2-7 illustrates the store procedure.

T2-7 System Test Procedure

Store Procedure Description
Shut down the system(if the system is power on)
Use the USB interface to connect to the user’s computer, the GTD’s screen will
display a “PC” flag. It means the GTD is in the Store mode.
Upload the test history to the user’s computer. (If no instructions accepted, the GTD
will shut down automatically. Or you can press the M button to shut down the GTD)

2.8 External Events

The GTD’s system external events in Figure T2-8 illustrate the system’s external
events.
E_ID Description
E_01 Test strip is damaged
E_02 The USB line disconnect accidentally
E_03 AC plug-in disconnect accidentally
E_04 Blood sample is not enough
E_05 The device work temperature is out of the range [-10 C ~~ 45 C]
E-06 Select user incorrect.
E-07 Battery is running out.
E-08 The beeper can be used to remind/warn the user when needed.
T2-8: System External Events Figure

2.9 Temporal Events

The GTD’s system temporal events in Figure T2-9 illustrate the system’s temporal
events.
T_ID Description
T_01 Press the M button within 3 seconds to start the system(if the GTD
system is not power on)
T_02 Press the M button to shut down the system(if the system is power on)
T_03 When the system is started, it will check the screen with 5 seconds
T_04 Insert a test strip, there will be a flag blink 5 second, and then user can
supply blood sample
T_04 If the test strip is act and blood sample is enough, within 30 seconds the
test results will be displayed
T_05 When a test is finished, if no button push within 15 seconds, the system
will be shut down automatically
T_06 If the system is power on, shut down (press the M button), and then press
the M button more than 3 seconds to restart the device into the set mode.
T_07 When the system is in the set mode, set the hour, minute, date time
format, year, month, day and the test unit in sequence (use the C button to
increase data by one or to change the date time format and the test unit to
another one, user the M button to acknowledgements or shut down the
device.)
T_08 When the device is connecting to the user’s computer via USB interface,
a “PC” flag will be displayed. And then the user can upload test history to
their computer. If there’s no instructions accept within 2 minutes, the
system will be shut down automatically.
T2-9: System Temporal Events Figure

2.10 Inputs and Outputs

The GTD’s system structure in Figure T2-10 illustrates the GTD’s top business events
and their relationship.
 T2-10: System Top Business Events Figure

2.10.1 Test Mode

The test mode inputs and outputs:
TS_id inputs outputs
TS_01 Press M button(<= 3 seconds) System start
TS-02 Check Screen(<= 5 seconds) None
TS_03 Insert a test strip(wait 5 seconds) A flag(blink 5 seconds)
TS_04 Blood sample A signal(send to the sensor)
TS_05 Test result(within 30 seconds) Test result(displayed on the screen)
TS_06 Press M button(system is power System shut down
on)
TS_07 Press C button System start( a “mem” flag blink 3
seconds, and the latest test results is
displayed)
TS_08 Press C button The next test results
2.10.2 Set Mode
The set mode inputs and outputs:
SS_id inputs outputs
SS_01 Press M button(>3 seconds) System start(in set mode)
SS_02 Check Screen(<= 5 seconds) None
SS_03 Hour value Minute value
SS_04 Minute value Date time unit
SS_05 Date time unit Year value
SS_06 Year value Month value
SS_07 Month value Day value
SS_08 Day value Test unit
SS_09 Test unit None
SS_10 Press M button System shut down

2.10.3 Store Mode

The store mode inputs and outputs:

SR_id inputs Outputs

SR_01 USB connection instruction A “PC” flag blink
SR_02 test history(upload) Test history(in computer memory)
SR_03 Disconnect instruction System disconnection

2.11 Screens
The Glucose Testing Device’s functional opponent structure view is in figure T2-11
 Test Strip

Beeper
AC
Error

Battery User
E
~ A
Test Unit
Result L
Progressive
07/11/01 15:30 Bar
Date Date
Time

Two USB
Buttons
Glucometer AC plug-in

T2-11: GTD’s functional opponent structure view

Function opponent name Description

Test Strip When insert a test strip, wait 5 seconds, and then supply
user’s blood sample, a react will be occurred, and a signal
will send to the sensor, within 30 seconds, the test results
will be calculated and displayed.
AC A flag, if the user connects the GTD to AC, the flag will
blink.
Battery 3.0 Li Battery which can be used at least one year, the
battery flag will blink if the battery has power and the
system is started
Test Result The user’s test result, the value is based on the unit
Date Display the current date(year/month/day) when the system
is started
The M button(left) User can press this button to start, shut down the device,
and acknowledgements an instruction.
The C button(right) User can press the C button to increase the data value by
one (hour/minute/year/month/day), and change the date
time format, test unit and see the next test result.
Error There are several kinds of errors, if the error triggered by
external events, the error flag will be displayed
Beeper The beeper can be used to remind/warn the user when
needed.
User There two users,(User A / User B), before the test, user can
select the user type
Unit There are two kinds of test unit. (mmol/L and mg/dL).
User can set it in the set mode.
Progressive Bar When the user do a test, it display the test progressive
Date Time Display the current date time (year/month/day) when the
system is started. There are two kinds of time format (12
hour format / 24 hour format); the default time format is
24 hour format.
USB User can use the USB interface to connect to their
computer and upload the test history
AC plug-in A hardware interface, user can use it to connect the device
to AC

3. Operating Environment Requirements

3.1 Hardware

3.2 Software

3.3 Communication

4．External Interface Requirements

The system being developed might interface with many other existing automated
and non-automated systems. The description of the Subsystems, the relationships
with the subsystems, and communication protocol and data are specified here. If a
large number of subsystems is Involved, separate documents shall be generated.

4.1 User Interfaces

UI-1: User A, used by one people with his setting and test data stored for him.
UI-2: User B, used by another people with his setting and test data stored for
him.
UI-2: Button M, used to start device, shutdown device and confirm option.
UI-3: Button C, used to turn to next display and increase one.
4.2 Hardware Interfaces
HI-1: USB interface, this is used to upload GTD test data to the pc.
HI-2: AC plug-in, when it is plugged in, the device will use only AC power.
HI-3: Button Reset, used to reset the system to the initial condition.
HI-4: Strip plug-in, used to plug in a test strip when user wants to make a test.

4.3 Software Interfaces

There is no software interface in this system.

5 Other Nonfunctional Requirements

5.1 Performance Requirements
PE-1: The device shall operated between -10 C to 45 C.
PE-2: The device can be used by user A and user B at the same time.
PE-3: The beeper shall remind the user when some errors happen and no
display can hlep.
PE-4: The system shall display the results of testing to users within 30
seconds after the user insert the test stripe into the slot and push the
functional button.
PE-5: The time of initialization should be less than 3 seconds.
PE-6: The system can display date, time, battery/AC, error status, test unit,
progress bar, user A/B.
PE-7: The system can automatically shut down when only battery is used and
there is no operation within 5 minutes or after one time of testing and
there is no operation within 15 seconds.

5.2 Safety Requirements

No safety requirements have been identified.
Security Requirements
No security requirements have been identified.
Software Quality Attributes
Robustness-1: If the some unknown errors happened, the system can be initialized
through click the button of reset behind the device.

Appendix A: Data Dictionary and Data Model

record of results = User name
+ Value of results
+ Unit
+ Date of testing
+ Time of testing
User name = “A” or “B”
Value of results = *The length of value should less or equal than 3.*
Unit = “L” or “DL”
Date of testing = * the date of testing ; format MM/DD/YY; may not be prior to the current date *

Time of testing = *the time of testing; format HH/MM,HH (0-24) *