Outline design specification
1 Introduction
1.1 Purpose of writing The purpose of writing
this article is mainly to develop this system and make a general structural design for the system. After review, it will be further refined, and detailed solutions and interfaces for each module will be carried out respectively. and database design, clearly describe all input and output parameters, type logic algorithms and calling relationships. As a basis for developers and testers to further turn and write test cases.
1.2 Background
a. The name of the software system to be developed: computer room charging system
b. List the tasks of this project Presenter: Professor Mi Xinjiang
c. Developer: Cao Xiangming
d. User: Managers of Langfang Normal University engaged in management
1.3 Definition
1.4 References
1. "Software Engineering Affairs" edited by Liu Xuejun, Li Jifang and Liu Hanzhong, Zhejiang University
Press
Database Basic Course "Computer Vocational Education Alliance Editor-in-Chief Tsinghua University Press 4. Overall design
of student management system 2. 2.1 Requirements regulation A. Main input: registration information, recharge information, on and off machine and card return information B. Main output: query information, Excel Forms, daily bills, weekly bills, and printing The functions of this system are divided into the following parts: You can enter your user name and password to log in on the login interface. If you forget your password, you can retrieve and reset your password through the password retrieval function. Users are divided into three levels of authority, general users, operators, administrators, administrators have the highest authority! Add module: add system user, student registration card number, basic data setting, recharge Delete module: delete system user, delete card number Modify module: modify login password, modify student's basic information, modify basic spending unit data Query module: students on Inquiry of computer records, inquiry of student's computer information, inspection of student's computer . General users mainly operate on basic information such as students getting on and off the machine, student attendance, etc. The operator can set and operate the work records of system users, and the system administrator has complete and complete management rights to the system. The system has a function of retrieving passwords for administrative users. Users are required to set their own password security questions after the initial login. When they forget their passwords, they can retrieve their passwords in the login form!
The system has different levels of input restriction functions for input in different places. This function will not affect the normal use of users, but is conducive to the stable operation of the system!
The operation mode should meet the needs of arbitrary switching between mouse and keyboard, and
support system versions above Windows 7.
2.2 Operating environment
A. Processor model and memory capacity: The processor is Pentium 4 2.5, and the memory is 256M
B. Outer village capacity: 20G
C. Windows7 system
D. Device model: 1.0 model credit card machine * 6 data communication devices Model and Quantity
2.3 Basic Design Concept and Processing Flow
2.4 Structure Explain the division of system elements (modules, subprograms, public programs, etc.) of this system in the form of
a list and block diagram, briefly explain the identifiers and functions of each system element, and give the differences between elements in a hierarchical manner. The relationship between control and controlled.
Element identifier function
General user module General user Student information query, password modification, password modification
Operator Operator Student login record, teacher work record query, export Excel, registration, recharge, card return, etc.
Management Member Administrator checkout, weekly checkout, daily checkout, report generation
Block diagram
2.5 The relationship between the function device and the program
This article uses the following matrix diagram to illustrate the distribution relationship between the realization of each functional requirement and each block program:
general user operator administrator
Student information management √ √ √
User information management √ Revenue and
expenditure accounts Management √ √
System information management √
2.6 Manual processing process
Describe the manual processing process (if any) that must be included in the working process of this software system.
2.7 Unresolved Issues
Describes during the outline design process and that the designer believes must be resolved before the system is completed.
3 Interface design
3.1 User interface
Command syntax information reply
Confirm OK, click event, default key enter Realize the input command
Query Click, click to display the queried content
Modify click, click on the data to get the focus, you can make changes
Clear Click, click to clear the interface data
Cancel Cancel, click to cancel the modification of the data
3.2 External interface
Report part: link to printer
, computer, work record: output Excel document Mainly to check the student balance, the student's computer record, the student's recharge record, the student's computer status query, and the password modification modules, which all involve the database call . 2. Operators: registration, recharge, card refund, student access status query, Modules such as balance refund query, teacher work record query, and charge amount query involve database query and update . Modules such as weekly statements involve database query and modification 4.2 Operation control 1. User name, password, and user level verification are required when logging in Set the password. If the password is not set, remind the user to set the password. 3. Registration, recharge, card return and other operations need to be checked by the operator, and then executed by the operator. 4. Checkout needs to be checked by the administrator and then executed. 5. The administrator can set and modify the system after logging in. 4.3 Running time 1. General The user module will run frequently, occupying 1/2 of the database usage time. 2. The operator module is used next, accounting for 1/3 of the database usage time. 3. The administrator module is used the least, accounting for 1/6 of the database usage time. 5 system data structure design
5.1 Key points of logical structure design
Give the name, identifier of each data structure used in this system, and the identification, definition, length and hierarchy of each data item, record, file and department in them. or interrelationships of tables.
1) Duty information (worklog_info)
Name Identifier Data Type Length
Username UserID Char 10
level level char 10
login date Logindate char 10
login time logintime char 10
logout date logoutdate char 10
logout time logouttime char 10
computer name computer char 10
status status char 10
2) daily statement name
Identifier data type length
balance remaincash numeric (18,0)
recharge amount rechargecash numeric (18,0)
consumption amount consumecash numeric (18,0)
refund amount cancelcash numeric (18,0)
all amounts allcash numeric (18,0)
date date char 10
time time char 10
3) card refund information
name identifier data type length
student number Studentno char 10
card number cardno char 10
refund amount cacelcash numeric (18,0)
date date char 10
time time char 10
username userid char 10
status status char 10
4) weekly statement
name identifier data type length
balance remaincash numeric (18,0)
recharge amount rechargecash numeric (18,0)
consumption amount consumecash numeric (18,0)
Card refund amount cancelcash numeric (18,0)
all amounts allcash numeric (18,0)
date date char 10
time time char 10
5) on-board information (online_info)
name identifier data type length
card number Cardno char 10
card type cardtype char
10student number studentno char 10 student
name studentname char 10
department department char 10
gender sex char 10
computer date ondate char 10
computer time ontime char 10
computer computer char 10
6) recharge record (recharge_info)
Name identifier data type length
student number Studentno char 10
card number cardno char 10
recharge amount addmoney numeric 10
date date char (19,4)
time time char 10
user name userid char 10
status status char 10
7) student information (student_info)
name identifier Character data type length
Student number Studentno char 10
Card number cardno char 10
Student name studentname char 10
Department department char 10
Gender sex char 10th
grade grade char 10
Class class char 10
Amount cash numeric (10,3)
Remark explain varchar 50
Username userid char 10
status status char 10
checkout ischeck char 10
date Date char 10
time Time char 10
8) basic data setting (basicdata_info)
Name identifier Data type length
Half- hour charge Halfcharge char 10
Increment time increasetime char 10
Minimum computer time leasttime char 10
Computer preparation time readytime char 10
Minimum balance in the card leastcash char 10
Date char 10
Time time char 10
9) User information (user_info)
name identifier data type length
account Userid char 10
password pwd char 10
level level char 8
username username char 10
5.2 Key points of physical structure design
Give the storage requirements of each data item in each data structure used in this system, the access method, access unit, physical relationship of access (index, device, storage area), design considerations and confidentiality conditions.
5.3 The relationship between the data structure and the program
1. The data structure of the system is generated by the standard database language SQL
2. For example, the specific program that creates the user table user_info
CREATE TABLE [DBO].[USER_INFO]
[USER_ID] CHAR NOT NULL
[PWD] CHAR NOT NULL
......
6 System error handling design
6.1 Error information
Error type error prompt
Input information is wrong Input information is wrong, please log in again If
there is no selection condition, to query or modify, please select the information you want to query or modify
Program running error Program running error, will auto close
6.2 Remedial measures
Describe the possible workarounds after the failure occurs, including:
a. Backup technology Description of the backup technology to be used, the creation and startup technology of the copy to be enabled in case the original system data is lost, such as periodically resetting the disk The recording of information to tape is a back-up technique for disk media;
b. Fallback technique describes the back-up technique to be used, using another slightly less efficient system or method to obtain some part of the desired result, such as a Reduction techniques for automated systems can be manual operations and manual recording of data;
c. Recovery and restart techniques describe the recovery and restart techniques to be used, the methods for enabling the software to resume execution from the point of failure or to restart the software from scratch.
6.3 System Maintenance Design The
system is small and does not involve too many modules, so only the database needs to be maintained during the maintenance process!