Exam System Summary

After three months of hard work, dark sky, and miserable efforts, the examination system was finally restructured. The system is not difficult,What's hard is to draw a clue from the chaosThere is also an attitude towards restructuring. The project was said to be three months old. In fact, it was about 30 days after Jia Lin and dashuai came back to join the internship and completed the system compilation, the following describes how the examination system feels.

Precondition reconstruction attitude

I think it is a little important, that is, the attitude towards restructuring the system,Refactoring is a reference rather than a copyWhy did it take a long time (nearly a month) in the early stage, but there was almost no progress? The important thing is that we want to understand the source code, create a database, draw a UML diagram, and then add it on it. I think this is a wrong approach. At least it is not very correct, because refactoring means restructuring. There must be a change in demand, and the change in demand will certainly lead to changes in databases and UML diagrams.

At the same time, refactoring means that development on the basis is actually more like a supplement and improvement, so it is also necessary to learn from the original system, but it is necessary to clearly identify what can be used for reference and what cannot be used for reference, from this point of view, I think we can learn from the following:Database conceptual models, technical difficulties, and Algorithms.

Reading the source code seems to save a lot of time. In fact, it takes more time to read the source code..

Prerequisites

The preparations mentioned here are common comments, naming rules, and SVN usage rules.

Both the first two annotation specifications and naming rules aim at the beauty and readability of the Code. Good code comments and naming rules make the system easier to maintain, easier to read, and more consistent, therefore, it is important to have a set of uniform standards and naming conventions before development.

Imagine, when you open the solution, full screen error, is there an impulse to throw the keyboard? SVN is used for better cooperative development and version control. Therefore, you must have a set of usage rule documents for SVN. Common rules:

• Update the code to the local device before submission.
• You can generate a solution before submission to ensure that no error code is submitted.
• Do not submit DLL, PDB, Suo, and other files (ignore using SVN)
• Update notes must be written for each submission.
• Develop the habit of submitting frequently

Project Plan

There should be a development plan for the project as a whole, from feasibility analysis to the final test deployment. The completion period, Mark and standard should be set for each stage, which may not be reasonable at the beginning, however, as experience increases, it will gradually move closer to a reasonable one.

Every developer should have expectations and summaries every day, and then hold a group meeting to discuss and develop a plan for the next day.

The goal is,Development cannot be the same as development in the "fangyang" mode. There must be a summary and planning.Gradually learn from accumulated experience and make more reasonable plans.

Development Process

In this UML diagram, document, and code, you must make full use of the auxiliary software and functions, such as prototype tools, entitycodegenerte, forward engineering, and reverse engineering.

During the development process, we often encounter a problem called "degree", that is, to which extent the page is beautified? To which extent is this function easy to use? Which degree is the database design standard? If you are perfect, a project in a month may be delayed for one year. If you are satisfied, a function may produce multiple bugs; these questions must be fully integrated with the project time, user standards, and knowledge storage to obtain a moderate answer ..

For details about the issues encountered during the development process, see other blogs.

Complete

• Corrected Exam System database connection problems
• Change course-centered to test-centered
• Beautify UI display and dynamic effects
  
• New exam control and IP Address Access Control
• Added the simultaneous Examination Function
• New Historical Data Processing
• Improve user and instructor Permissions
• Improved Score export Function
• New Fixed exam Function
• Added the mark and share questions function.
• Added the browsing Question Bank function.
• Modify other buckets

Summarizing a lot of knowledge, such as SVN usage, project planning, and personnel allocation, can be learned not in a day or two, but only in practice, although it took three months from the beginning to the end of the development, it is worth it.