Thinking of the development of BUG life cycle management
1 preface ... 1
2 Summary of questions: 1
3 system flow and related technical description ... 3
4 possible starting way ... 6
5 The function of the system may come with ... 6
6 summary ... 6
7 self-introduction ... 7
1 Introduction
User familiar with the Bugzilla system should have a relatively thorough understanding, but for many users, Bugzilla is a hurdle, first it is developed for applications under Linux, although it is also available under WINDOW. Configuration is used, but the configuration process is a very difficult process. The configured users should have deep understanding; English is also a problem that makes a headache, not everyone can understand English instructions in Bugzilla, once understood If you don't have a certain amount of operational deviation, the application will produce a certain misunderstanding. All these don't say that bugzilla is not good or not suitable, but hopes to have a similar BUG management system, support Chinese, simple configuration, It can be easily applied to any platform, which can be well understood for any level of users, which is a system that progress. Commercial software is much larger, you can search for Baidu or Google search, and there are a lot of content. If you want you to develop such a system to meet your needs, do you consider development costs, develop difficulty, development time ...... Nothing is that you have to put. But you can't find some shortcuts to help you implement you Wish. This article is my own feelings after I have developed such a system. I hope to help you. If you are happy to use my system, please give me email (jem @ buildersoft.cn / kexi2002 @ hotmail.com) I can authorize you. Let you use the Chinese people's own "bugzilla".
2 Summary issues
The main purpose of the BUG system is to implement the development team's effective management of the BUG of the application, helping the project manager and the security department better define the quality of the project final result (product or project implementation), for very development People are undoubtedly a good BUG record method, using this way to change a developer's move is a good way to optimize the project management.
So what kind of design idea should such a management system? We temporarily take a look at some questions:
A, allocated personnel design idea
The distribution person is "coarse granularity" or "fine grain size"
One: Coarse granularity: assign project managers to the project, distribute developers and testers to the module after the module
Two: fine grainity: assign the project manager to the project, to the functionality of the module to allocate developers and testers, even to smaller units (such as code segments)
Design Ideas: You can choose the rule when you create a project. If you choose, you will find fine particle size by default. If fine grain is unable to satisfy, look for coarse particle size.
B, email send design ideas
In terms of communication, the email played a lot, how to ensure that the relevant personnel promptly, the habitual pass mail conveys a variety of information (bug modification process) is the system
An important part of the design.
Design Ideas: You can allocate multiple people to develop and test in the coarse / fine-grained distribution personnel. In order to solve the problem of sending mail, the system system is sent or
It is the test person to choose to send two different ways.
C, what you see after logging in
It is also one of the important characteristics of the system to achieve more humanized, for example, each developer is hoped.
Seeing the bugs he needed to modify, there are several, where you can communicate this information in a timely, the development of the developers will be active, or then to form a conscious thinking. This is a kind of ideology.
Design ideas:
One: You can see all the unresolved BUGS belonging to her or his unresolved BUGS after the developer landed.
Second: The general staff can see him or the project, module, and function of the project, modules, and all content in the tree catalog.
Third: The project manager and the manager have seen the content and modified content of the bug after entering.
Its four: After the test personnel have entered the function, it is basically consistent with the content that appears when the developer landed.
5: BUG to be modified, developers can click to modify bugs to enter her bug page
Six: All people can query all bugs
Its seven: After the function test is completed (the project decision is decided to report a paragraph), the system provides statistical mechanisms
D, BUG status management, if it defines the lifecycle of the bug, then naturally involves the state of bugs, the BUG has different representations in the life cycle.
Different stages, how to control the state of BUG? Effective monitoring of these states can effectively track the development of each bug.
Design Ideas: The state of the bug has new discovery, to be determined, modified, acceptable, review, close, recurrence
E, the system may need to provide attachments carrying features, such as test analysis reports, test case lists, unit test schemes, system test schemes, test file templates,
Project BUG analysis, module BUG analysis, developer BUG analysis, test staff BUG analysis.
Design Idea: This is an optional component that selects more or less modules as auxiliary according to project management needs.
F, the system provides comprehensive query, such as the project bug query, module BUG quantity query, test staff BUG quantitative query, developer BUG quantity query, comprehensive query
Design Ideas: The query is an important part of a system or a Website. How to achieve intelligent queries is also an important design problem, according to user level
Don't provide different characteristic queries is a very heavy design idea.
G, whether the system provides communication management and information release, which is a module design that the system should consider, for most development team, communication management and letter.
Intersection is an important management object, and the communication is determined by a project, remote communication or face-to-face communication. Real-time communication is still different.
Step communication, etc. There are too many ways, do you have to take into account these?
Design Ideas: The way communication can be real-time or asynchronous, such as BBS, or forums, etc.
H, the last question, that is, the management, the management, allocation management of the basic data of the system, the management of the system.
. These are the basis of the system operation. We will explain the following process.
