Student Information Management System (III)-Interface Analysis

In the previous two blogs, we analyzed the functions and databases of the system. Today, we started to practice and further analyze the system. Our program design consists of two steps: interface design and code design. Today, let's take a look at its interface design. In the previous blog, I analyzed the functions of the system. A figure in it shows the interface layout of the program. Next, we will further analyze the system. The system consists of 16 forms and one module. I have classified these forms, and the code will be sorted in this order. See:

In this figure, the original interface layout is completely disrupted. According to the function, 16 forms are divided into seven categories. First, log on to the form, followed by the main form, and then add, query, modify, and set the form. Finally, it is about the form. Is it much simpler?When designing the interface, pay attention to the following points:1. unified format (Forms and controls ). 2. the shortcut keys are in line with everyone's habits. 3. Adhering to the idea of serving the people wholeheartedly, set the enabled attribute of unused buttons to False. This is just a few points I have come up with. You can add anything you need to pay attention. Some systems, databases, and interface analysis have already been done almost the same. The following code is used in practice. Please wait for the next blog "student information management system (IV)-module analysis"