Our configuration management is borne out of our requirements. In our earlier blog post, we discussed how the project scope must be traceable to the requirements. In the case we present below, the project scope is a particular function or need to be met, for example a new feature or function for an automobile. We […]
This may sound difficult, but there are some rules for good requirements. According to the International Council on Systems Engineering (INCOSE http://www.incose.org/chicagoland/docs/Writing%20Effective%20Requirements.pdf), requirements should have the attributes below (similarly can be found at IEEE): Necessary – driven by the objective of the project and business Verifiable – ability to objectively confirmed that the requirement is […]
Consider a rather large project that like so many projects had some difficulties. The project team had a major component (subsystem) delivered from a supplier. The supplier has one set of processes and the customer organization another. This supplier delivers multiple versions of this major subsystem. The customer integrates this subsystem into the larger system […]
Creating a separate software test group has pluses and minuses. At a minimum, we may have more to manage. Some of the minuses are a product of human nature. When we know our work will be inspected, we will often assume the inspector will catch issues and we pay less attention to the issue ourselves. […]
Another piece of the configuration management pie is the ability to move backward and forward from revision to revision. To demonstrate the importance of this concept I will relate a story. There once was a developer who was writing in assembly language for a new product. He was incrementally developing the features for the product […]
Configuration auditing occurs so we can verify that what we said we were going to do actually happened. MIL-STD-973 specifies two flavors of auditing: functional and physical. Functional configuration auditing occurs when we verify that the change functions as the engineering change proposal specified it would. A change can be to hardware, software, or both […]
Configuration control is generally, what first comes to mind when somebody brings up the topic of configuration management (CM). While it lies at the heart of the system, all the components of a CM system are critical. The purpose of this component is to: Maintain and control configuration baselines (known and defined states) Document and […]
MIL-STD-973 lists configuration identification as the first step in the configuration management (CM) process. We do not think this is some bureaucratic whim, but rather, one of the most important components of CM. Are speaking about systems, subsystems, components, parts, software revisions, and more? The simple answer is, yes! To avoid confusion when using bills […]
Once we are using a configuration management (CM) system, how do we ascertain the status of our engineering change? Configuration status accounting (CSA) is the method by which we accomplish this record tracking. We can get software support by using a dedicated tool or implementing a dedicated database that tracks what we want tracked: Approved/rejected […]
One of the principal roles of configuration management (CM) is to protect us from ourselves. In so doing, we also protect our suppliers and our customers. When high school or college students first encounter bills of materials, they experience shock and awe. An automotive wire harness with 368 leads must have a bill of materials […]