Completion of the third draft of CMDB

Goal 1. Rebuild the current implementation Code, Clear the model-instance from the architecture. 2. Take the complex configuration model as an example to implement configuration model = instantiation, impact analysis, and other operations. 3. Configuration Management introduction status, Online --> checkout for change --> check in for review --> change online --> online check after going online --> online third, no... lazy. Restructuring this time is a lot easier, basically all in one breath. Data structure, ProgramThe structure is good. The method used this time is not menu/button-driven. I tried the command line driver method, that is, the program provides a command line: note that, before the main function, you need to write a line [stathread]. If it is not in the sta mode, there will be a problem during running. Well, this problem is too easy to solve. After all, I am not a CMDB project team. It is a little bit of trouble to influence this idea to the project team. I have talked about it several times .... I have never studied Maximo, but I don't know how Maximo works with this idea. The ultimate goal of making a CMDB is to apply it, rather than making a CMDB for making a CMDB. people cannot be limited by tools. After all, I have been thinking about CMDB for several years. I learned how to write a program in Excel several years ago to create a simple model. Later, I used Visio to write a program for simple display. Dijistra is also used to determine the connectivity configuration. The same is true for the current verification model. To implement it in the project team, you still need to use your brains.