Documente Academic
Documente Profesional
Documente Cultură
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.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
The GTD’s system boundary in Figure T2-3 illustrates the system’s boundary.
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.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
3.2 Software
3.3 Communication