4 possible starting way
You can choose to start, for example, you want to start a record effect on bugs at the beginning, late to expand other features, this is my choice, I first focus on the management of BUG's life cycle, mainly bugs The management of each state, I started to build on my main goal, then I will slowly expand other features, such as user management, authority management, log management, configuration management, document management, communication management, recently I design The change management of the process also added to the system so that my BUG management system slowly separated from the original BUG management, but this is not my choice, it is the choice of project management needs, everything is guided by the market may It is the best look.
If you have enough time, it is recommended that you use the "quasi" standard software engineering ideology to develop your BUG system, such as systematically analyzing, and then designed, then designed, coded, test, deploy test, trial Wait, according to the quality requirements of software engineering, this is a small scale, mature business process, and small technical difficulties. Therefore, risk is also low, for such systems, 2 people can complete the main task in a short time. In the later stage expansion, one person is maintained.
5 functionality that can be included with
I repeat the possible features of the BUG management system, which is for a project, than all project managers are willing to do these jobs in this environment, with features that come with graphical reports, documentation customization Category management, diverse support for peer reports, the granularity of the report is accurate, communication management, query automation, process steps are more flexible, etc., these tries me in constant improvement, but it is not necessary, but I think I think This is a good choice in my world, it may not be appropriate to you. You may just pay attention to the control of the life cycle of bugs.
6 summary
For any software that wants to work to a group, the most important thing is to make this software generic, ease of use, stability, and high processes. It is indeed, you need to add it. Your meaning and management thinking, because of your management thoughts, your software can highlight its characteristics, but what you want to explain is that your management is advanced.
7 self-introduction
Li Kexi: Long-term J2EE development and research, the J2EE system design and the Rational tool set have in-depth research and application, especially Rose and RequestPro; familiar with the IBM WebSphere platform and Oracle database;
The email is: jem @ buildersoft.cn, kxli @ headsun.net, Kexi2002 @ Hotmail.com
