When working for a few years, the projects that take over, more and more, and the version management and BUG management have failed. I am not a professional configuration administrator, just a kind of management tool for VSS, and the VSS version management is only the relatively weak version of the code management, software products and modules, of course, maybe I don't will use. So, you have to solve the clearness of the same modules in n projects, but it is more troublesome.
Until one time I rushed to upgrade the system patch at the MS website, I saw the downloaded patch file as KB135732, which means that Microsoft's patch is numbered. So corresponding, the patch should correspond to the BUG number, and the bug number corresponds to the test plan number, and the test plan should correspond to the product module or function number. Of course, how Microsoft is doing, I don't know, but such a structure is in my mind.
Manage management, want to manage, first. My idea is to build modules and bugs, test plans, patches, etc., and manage them, should be clarified now.
I first made a simple design and established the module unified number database. All the original developed modules and new modules to be developed must first register in the module table and start doing the unified number. The number of numbers is relatively simple: product name project name digital version number. For example, ERP CP 001 01. The function numbers under the module are longer: module number digital version number.
Similarly, bugs and module functions, test schedules, patches, etc. also correspond. The structure is as follows:
After the above design is established, it has a clear idea at least in terms of testing, bug, patches, etc., although it is not very good. I hope that more people can talk about their management ideas in this area, let everyone learn! :)
