Student Information Management System

The student information management system, as its name implies, is a software designed to manage student-related information. Although the source code is available for our reference this time, I learned how to build a software program from the beginning to the completion. Below I will summarize my student information management system from the order of a software project.

 

I. Requirement Analysis: The first thing we need to do is to look at a finished product, what its functions are, and what tasks each function completes. This is the so-called requirement. For the student information management system, we can imagine that he needs 1. the user name logs in to the system and has the corresponding management user name; 2. the management and storage of Student Information (that is, basic personal information; 3. manage and store the basic information of students in the school (such as the Class, Class teacher, and grade); 4. store and manage the course-related information for each grade; 5, storage and management of Exam Score information for each student. To meet these features, you can manage the basic information of a student.

 

2. Build appropriate databases based on the basic requirements and the general framework of future projects:

With the demand, the establishment of databases is a very important process of engineering. The ability to build a suitable database will make our programming work very easy in the future, and vice versa. Based on the above requirement analysis, our student management system has created six tables:

1, user_info table 2, student_info table

 

3. class_info table 4 and course_info table

 

5. gradecourse_info table 6 and result_info table

 

This is the created tables. Note that the red and green labels are the key to connecting the tables. Let's take a look at my export chart below and give a rough introduction to it:

 

 

After creating tables and establishing relationships with each other, we can take the whole body into consideration. In the design program, we can input the relevant information of a table, the related information of other tables is also called through its contact. in fact, it is also very correct. This database is built around the student entity, and all the relevant information is also related. A database is a relational database that connects entities through links.

 

3. Create a proper program framework (that is, establish the distribution of forms and the relationship between forms) for tables in the basic database ):

 

4. After completing the preparations, we began to design the interface and compile the program code.

Here I want to emphasize three points. First, the interface must be properly designed and beautiful. For Beginners, we can refer to the interface of common software to design and take its essence. (For example, the use of color, whether the controls are neat or not, the order of the tab key, and the addition of common shortcut keys all allow new users to do what they can, so be sure to do well, is embodied in the idea of serving people by heart ). Second, for code writing, I would like to say that as long as there is little link between forms, we can implement the functions of one form and one form, unless there is a lot of connection between those forms, we need to work together (for example, the module in the student management system and the login form, because the login form uses functions defined in the form, there is a very tight connection ). When you complete the function of a form, you need to debug the form. Do not wait until the final debugging is complete. You need to debug a form and a form. This makes the final debugging much easier. Third, it is the preparation of the document (at this stage we are more reflected in adding annotations). For how to design the software, how to Implement functions and so on must be written in the form of a document (not doing well). Of course, you must add comments, these are of great significance for future debugging and maintenance.

 

5. After completing the programming and design of the program, you need to perform packaging and acceptance.

The packaging process can be completed by using the corresponding packaging software tools (such as setup factory 7.0), which is relatively simple. For later acceptance, we need relevant experienced personnel to test our software, find bugs, and provide comments.

 

6. Finally, the test result is the foundation, the program is improved, and the final summary of the completed program is made.

Such a project is basically completed. If we are in the company, we can put it into use after repeated experiments and debugging!

 

Finally, I want to talk about the process I learned in this project. This is a flowchart and I hope to help you: