Software engineering -- dental clinic -- demand analysis

dental clinic ---- Demand analysis

1、 System flow chart

2、 Demand priority list

Serial number	Use cases / Name of quality requirement item	priority	explain
1	Login system	high	Must be fully realized
2	Query patient data	high	ditto
3	Modify patient data	high	ditto
4	Record patient information	high	ditto
5	Print work schedule	in	Most of these functions should be implemented
6	Cancel the patient's appointment	high	Must be fully realized
7	Security	high	ditto
8	reliability	high	ditto
9	performance	high	ditto
10	Extensibility	in	It has a certain impact on the acceptability of products
11	Compatibility	low	It can not be fully realized

3、 Requirements specification （ Requirements specification ）

1. System Overview

• Document overview ： This document contains 3 part / modular , They are appointment modules , Query module and transaction processing module . This document is for developers to read
• Overview of the target software system ： This system aims to serve patients' appointments , For all people . Software is relatively independent of other software systems . The software needs to be used in the environment with network and database connection
• User characteristics ： All staff in the clinic

2. Quality requirements

• Usability ： Ensure that the user can simply and easily achieve the action he wants to complete
• performance ： Users can get a timely response when using the system
• Security ： Prevent illegal intrusion , Prevent data leakage

3. Constraint requirements

• Conditionality ： Only used inside the clinic
• Business environment constraints ： Only for appointment of clinic patients

4. Requirements priority

Serial number	Use cases / Name of quality requirement item	priority	explain
1	Login system	high	Must be fully realized
2	Query patient data	high	ditto
3	Modify patient data	high	ditto
4	Record patient information	high	ditto
5	Print work schedule	in	Most of these functions should be implemented
6	Cancel the patient's appointment	high	Must be fully realized
7	Security	high	ditto
8	reliability	high	ditto
9	performance	high	ditto
10	Extensibility	in	It has a certain impact on the acceptability of products
11	Compatibility	low	It can not be fully realized

5. Interface definition

• adopt jdbc Technical connection database
• Connect the peripheral printer through the computer

6. Requirements acceptance criteria

• Most functions of the system need to be realized . Such as logging into the system , Input information , Query information and other functions .
• Plan the later maintenance work in detail

7. Demand source table

• Quality requirements

  1. Usability

  ​ source ： It can make beginners get started quickly

  2. performance

  ​ source ： The system guarantees its performance , In order to serve users in time , Improve users' evaluation of the system

  3. Security

  ​ source ： Prevent illegal intrusion from causing data leakage

• Binding requirements

  1. Conditionality

  ​ source ： Make the system development more targeted

  2. Business environment constraints

  ​ source ： Determine the topic based on the requirement acquisition
  The content of this blog is for reference only , Not the standard answer , It's what I think ！