table of Contents
First. Summary
1.1 Project Background ******************************** 4
1.2 Writing the purpose ****************************** 4
1.3 Software Definition ******************************* 4
1.4 Development Environment ****************************************** 4
Second. Demand analysis part ****************************** 4
1.1 User Function Implementation Figure *************************************** 5
1.2 Main features Overline ****************************************************************
Student file management ***************************** 5
1.2.2
Student's management ***************************************** 5
1.2.3
Student results management ***************************** 5
3. Design part ******************************* 6
1.1 Separation of data and page effects ************************ 6
1.2 Static page and handling page ***************************** 61.3 Optimization and code and module are reused ****** ******************* 7
1.3.1
Module reuse ******************************* 7
1.3.1
Code reuse and optimization *************************** 7
1.4 Data and page processing ***************************** 7
2. Program frame design ****************************** 8
2.1 Basic Design ******************************* 82.2 Package Design *********** ***********************8
3. Database concept design ****************************** 9
3.1 E-R entity relationship map ************************************** 9
3.1.1
Student Basic Information Module ************************************ 9
3.1.1
Student status management module ************************** 11
3.1.1
Student score management module *************************** 123.2 ER model diagram conversion to relational table *********** ************* 14
3.2.1
Student file management (entity transformation into relational mode) ***************** 14
3.2.2
Student file management (contact transformation into relational mode) ***************** 15
3.2.3
Student's management (entity transformation into relational model) ***************** 15
3.2.4
Student's management (Contact Transformation into Relationship Model) ***************** 15
3.2.5
Student performance management (entity transformation into relational mode) ***************** 15
3.2.6
Student performance management (contact transformation into relational mode) ***************** 15
3.3 Basic Table Relationship Information **************************** 153.4 Data Dictionary ************* ******************* 18
4. System design part ****************************** 10
4.1 System specific operation flow chart *********************************** 20
4.2 System Permissions Analysis ***************************************** 20
4.2.1
Student landing ***************************** 20
4.2.2
Teacher landing ****************************** 104.2.3
Administrator landed ***************************** 20
5. Interface design (main interface screenshot) ************************ 20
5.1 Landing Interface ****************************** 10
5.2 Student Operation Interface ***************************** 21
5.2.1
Student modify password interface ************************* 21
5.2.2
Student modification see the basic situation interface ********************** 22
5.2.3
Student Resume and Download Interface ************************* 225.2.4
Students' selection and retraction and selection interface ******************************** 23
6. Design experience ******************************** 23
7. Appendix: User Manual *************************************** 24
First. Summary:
1.1 Project Background:
A few years ago, the student's performance management of each school was basically carried out. With the increase in the size of each school, the amount of data related to students' performance management work is getting bigger, and some schools have to increase human resources. , Material resources for students' performance management. However, manual management has an efficiency, high error rate. So I want to use this course design, develop a general university student score management system that is not only applicable to each other and applies to other schools.
1.2 Writing purposes:
Establish a student score management system, using a computer to manage students' achievements, further improve the efficiency and modernization of running schools. Help the majority of teachers to improve work efficiency and realize systematic, standardization and automation of students' performance information management workflows.
1.3 Software Definition:
Based on the three-class user management system, students and teachers for low-rights users, administrators are the highest administrative authority users, and please refer to the back section.
1.4 Development Environment:
Server: Tomcat 5.59
IDE: NetBeans
Database: SQL Server 2000
Development Language: HTML, JSP, JavaScript, JavaBeans Technology
2. Demand analysis section:
Each user function realization map
