What are software configuration items?
It is generally considered that the product of activities in various stages of the software life cycle can be called software configuration items after approval. Software configuration items include:
① Documents and materials relating to contracts, processes, plans and products;
② Source code, target code, and executable code;
③ Related products, including software tools, reusable software in the database, purchased software, and software provided by customers.
Software Configuration-related
When the software is built, it is inevitable, and the change is even worse than the chaos between software engineers in the project. Chaos occurs because no careful analysis or change control is performed before a change is made. Babich once said: "Coordinating software development makes configuration management the least confusing technology. Configuration Management is a technology that identifies, organizes, and controls modifications. It aims to minimize errors and improve growth rates most effectively.
Software Configuration Management, called SCM, is applied to the entire software engineering process. Because changes may occur at any time, the goal of SCM activities is
(1) logo change;
(2) control changes;
(3) ensure that changes are implemented correctly;
(4) report changes to other relevant personnel.
Software Configuration Management is a technology that runs through the entire software lifecycle. Its main function is to control software changes in the software life cycle, reduce the impact of various changes, and ensure the quality of software products. Correct Application Software Configuration Management is indispensable for developing high-quality software. The Software Configuration Management process is the essence of quality management in the software development process.
========================================================== ========================
This is a good suggestion:
The software configuration item list is the output of the configuration item recognition activity. In cmme, a documented configuration item recognition criterion is required. The configuration item list is listed based on the criterion, the unique ID and name of a configuration item, and some important properties of the configuration item, such as its storage location, its owner, corresponding source code language, and controlled level.
For most traditional software development companies, configuration items should include requirement documents, outline design documents, test outlines, Code of each module, installation and deployment manuals, user manuals, etc.
For software products, we recommend that you use Visio to draw an asset structure diagram (which is actually a configuration map of the Code module) for each product and mark the aforementioned attributes. For important interfaces, we recommend that you use different line arrows to indicate the components, sources, similarities, associations, and other relationships among the configuration items. Such a configuration item list makes sense.