Software Configuration Management Seven heavy situation

Software development Hot words continue to evolve, CMMI. Agile lean, continuous delivery, continuous integration, grayscale ... But one word has actually been there, supporting a variety of new hotspots. It is # Software configuration Management #. It is also a major factor affecting the efficiency of team software development.

English abbreviation SCM

SCM from the birth of software project, even before the birth is there. Because the program code documents are always stored.
SCM Development after a lot of stages, try to do seven situation grading

the first priority of the seven-heavy situation

Shared folders, copied to handle multi-person collaboration, daily or weekly backups under.

There is only one person in charge of each part. It is manually processed on the shared folder at compile time.
Key version number additional folders are stored. or the engraving version number

the second of the seven-heavy situation

Using the Configuration management tool, there is no branch, and each part only agrees with the specified individual changes. Document files are stored in the tool after finalization.
Publication version number can be traced

the third of the seven-heavy situation

The documentation starts with the Configuration management tool. File name with version number, multiple people are developing at the same time in Project project.
Intermediate milestone baselines are identified
Use configuration Management three libraries: development library. Static library (Stable library), publication library (product library)

the four of the seven heavy situations

Documents and code can be managed under a unified baseline, with all file names without a version number, and using the tool's Tag/label function to manage baselines, the code can be compiled with one click.

seven of the weight of the situation

Have a clear trunk branching strategy. The purpose of the publication is to establish a branch, rather than building a branch per person, with its own proactive daily build, or/and continuous integration. Each component version number is actively associated with the baseline itself, so. An explicit version number can be traced to a code baseline

the weight of the seven is six .

Get 2 or more version numbers on your own initiative every day. Proactively deploy test reports. The code submitted by different project architects can confirm the coexistence of harmony in the same baseline in 1 hours, make full use of trunk, characteristic switch, virtual trunk and so on.

the seventh priority of the seven-heavy situation

Beyond the 6th-heaviest configuration management?
Candidate
Documents and code are developed under a unified file tool. Tools are document management tools and configuration management tools, and all changes are directly related, just like Requiz Pro or Dors
UML MDA from document directly to code, executable

Software Configuration Management Seven heavy situation