Transfer from http://www.cnblogs.com/beijiguangyong/archive/2010/09/26/2302822.html
Overview Design Manual
1 Introduction ... 2
1.1 Writing purposes ... 2
1.2 Background ... 2
1.3 Definition ... 2
1.4 References ... 2
2 overall design ... 2
2.1 Requirements ... 2
2.2 Operating Environment ... 2
2.3 Basic design concepts and process flow ... 3
2.4 Structure ... 3
2.5 The relationship between the function and the program ... 3
2.6 Manual process ... 3
2.7 Questions yet to be asked ... 3
3 Interface Design ... 3
3.1 User Interface ... 3
3.2 External interface ... 3
3.3 Internal interface ... 4
4 Running the design ... 4
4.1 Running the module combination ... 4
4.2 Operation Control ... 4
4.3 Run time ... 4
5 system data Structure design ... 4
5.1 Logical Structure Design essentials ... 4
5.2 Physical Structure Design essentials ... 4
5.3 The relationship between data structure and program ... 4
6 system error Handling design ... 5
6.1 Error message ... 5
6.2 Remedial measures ... 5
6.3 System Maintenance Design ... 5
Overview Design Manual
Introduction to the purpose of writing
Through the preparation of this summary design manual, from the overall design of the computer room charge system, I hope Mi Nue-jiang Professor pointed out the shortcomings.
Background
Description
1. Name of the software system to be developed: Computer room charge system
2. Mandate-holders: Professor Mi Nue-jiang
Developer: Shaoyangyong
User: All teachers and students of Langfang Normal University
The center of running the system: Langfang Teachers College Information Center
Defined
Not currently
Resources
"Langfang Normal University computer room charge system opinion"
General Design Requirements Regulations
Input: Save student information to database when registering
Output: Daily, weekly Report can be viewed, printable
Operating Environment
Normal desktop, windowsxp operating system
Basic design concepts and process flow
Structure
The system elements (each layer module, subroutine, utility program, etc.) are explained in the form of the list and block diagram, and the identifiers and functions of each system element are explained, and the control and control relationship between the elements are given in a hierarchical way.
The relationship between functional requirements and procedures
This article uses a matrix diagram as follows to illustrate the functional requirements of the implementation of the same block program distribution relationship:
|
General user Module |
Operator module |
Administrator module |
Student Information Management |
√ |
√ |
√ |
User Information Management |
|
√ |
√ |
Account Management |
|
√ |
√ |
Basic information Management |
|
|
√ |
Manual processing Process
Not currently
Questions that have not yet been asked
Not currently
Interface Design User Interface
Not currently
External interface
Requires a card reader to connect to the computer (USB)
Internal interface
The software needs to connect to the server by configuring the data source
Run the design run module combination
Student Management module for students on-machine, down-machine and query-running
Student recharge, return card; management audit account Operation account Management module
System setup, user management and Operation System Management module
Operation Control
Students on the machine, down the machine, the query needs to be zoned card, and then the operator check after the relevant operation.
Student recharge, return card need to draw card after operator check to carry out related operations
Check the accounts when the administrator is logged in for account management
After the administrator log on the system or operators to set
Run time.
Student Management module occupies a small amount of time in the Student information query, the student's computer management will occupy a lot of time.
The Account Management module takes part of the time to reconcile the accounts and print the reports.
System Management module in modifying system parameters, add, delete users do not need a lot of time
Key points of logical structure design of system data structure design
Student Information
Field name |
Data type |
Length (bytes) |
Card_no |
Char |
10 |
Student_no |
Char |
12 |
Name |
Char |
10 |
Sex |
Char |
2 |
Major |
Char |
20 |
Grade |
Char |
10 |
Class |
Char |
10 |
Cash |
Char |
19 |
State |
Char |
10 |
Remarks |
Char |
100 |
Style |
Char |
10 |
Register_user |
Char |
10 |
Re_date |
Char |
10 |
Re_time |
Char |
10 |
Check_money |
Char |
10 |
User Information
user_id |
Char |
10 |
User_pwd |
Char |
10 |
User_des |
Char |
10 |
User_other |
Char |
10 |
User_name |
Char |
10 |
Operational personnel work record
user_id |
Varchar |
50 |
Enter_date |
Datetime |
8 |
Enter_time |
Datetime |
8 |
Leave_date |
Datetime |
8 |
Leave_time |
Datetime |
8 |
Counter_no |
Varchar |
50 |
Remarks |
Varchar |
50 |
User_des |
Char |
10 |
Recharge Record
user_id |
Char |
10 |
Money |
Money |
8 |
Card_no |
Char |
10 |
Charge_date |
Datetime |
8 |
Charge_time |
Datetime |
8 |
Remarks |
Char |
50 |
Style |
Char |
10 |
Return card record
user_id |
Char |
Ten |
Money |
Money |
8 |
Card_no |
Char |
Ten |
tr>
return_date |
Datetime |
8 |
Reture_time |
Datetime |
8 |
Remarks |
Char |
|
Basic information
Cost |
Char |
19 |
Tempcost |
Char |
19 |
Unit_time |
Char |
10 |
Least_time |
Int |
4 |
Prepar_time |
Int |
4 |
Least_money |
Int |
4 |
Report
Remain_money |
Money |
8 |
Charge_money |
Money |
8 |
Use_money |
Money |
8 |
Return_money |
Money |
8 |
Now_money |
Money |
8 |
Date_check |
Datetime |
8 |
Remarks |
Char |
50 |
On-Machine information
Card_no |
Char |
10 |
On_date |
Datetime |
8 |
On_time |
Datetime |
8 |
Off_date |
Datetime |
8 |
Off_time |
Datetime |
8 |
Use_time |
Char |
10 |
Use_cash |
Money |
8 |
Computer_no |
Char |
10 |
Remarks |
Char |
50 |
Name |
Char |
10 |
Remain_cash |
Money |
8 |
Essentials of Physical Structure design
By the client to get data to the server, different permissions of operators have different access methods.
The relationship between data structure and program
(The form of each data structure and access to these data structures:)
???
System error Handling design error message
The form, implication and processing method of the system output information are stated in a list of the possible error or fault situations in Lang.
Error |
form of output information |
Implications |
Processing methods |
Failed to connect to database |
The database could not be found |
Server Not connected |
Check the firewall |
Remedial measures
Describes possible workarounds that may be taken after a failure, including:
1. Daily data Backup to ensure immediate update of backups
2. System crashes, restart the system, can continue to work
3. Data loss, reply back to the latest
System Maintenance Design
Describes the arrangements for the internal design of the program for the convenience of system maintenance, including the detection points and special modules specially arranged for the inspection and maintenance of the system in the program. The correspondence between the various programs can be used in the form of matrix diagram as follows;
Overview Design Manual