3 system processes and related technical descriptions
The best demand understands that it is too much to understand the process, you can use this system well if you can understand the process well, and you are also your own system base condition.
We simply look at a bug's lifecycle map (below), the previous steps are common steps, which is generally defined at a very few modifications, starting from a bug's birth to a repeated process.
The system uses Javamail technology to realize real-time transmission of the message; XML technology is used as a configuration underlayer, such as the establishment of projects and modules, allocation tasks, etc.; also uses mysql as a record stored database; you can choose any mail system as a message Server, I am using Linux Sendmail, this is a good match; the Tomcat I use in the server; development tools use Eclipse. Basically, some public source code or free project support. This is a good choice. I hope that China's open source project is strong and developed. The use of foreign open source project information or technology is a good way to achieve such a desire.
All operations are simple. Including the installation Bugwin system (my BUG management system), login bugwin system, system interface introduction, new bug, query bug, to the existing bug operation, test document upload, and use, statistical report (summary report, graphics report), Basically, it can achieve simpleness, suggestibility is the summary of many people's use, if you want to operate simpleness, then the best practice is to see what others want to do, you only need to press him, her idea implements this process. Afterwards, the larger the amount of investigation, the more meticulous statistics, the more it can reflect this feature. You may have to choose one or a few features as the main feature of your system. For example, ease of use, easy mountability, portability. Then we will make a detailed argument around these. Apply your argument results to the design.
