Search results
Results from the WOW.Com Content Network
Knowledge-based configuration, also referred to as product configuration or product customization, is an activity of customising a product to meet the needs of a particular customer. The product in question may consist of mechanical parts, services, and software.
Configuration identification is the process of identifying the attributes that define every aspect of a configuration item. A configuration item is a product (hardware and/or software) that has an end-user purpose. These attributes are recorded in configuration documentation and baselined.
Configuration items are represented by their properties. These properties can be common to all the configuration items (e.g. unique item code that we will generate, description of function, end of the lifecycle or business owner that is approving configuration item changes and technical owner, i.e. administrator, that is supporting it and implementing the changes).
The creation of configuration capabilities in today's market means that configuration data is increasingly likely to be distributed across multiple applications throughout an enterprise system. [14] CLM software supplies the needed functionality for a lifecycle approach to product configuration. [2]
Software configuration management (SCM), a.k.a. software change and configuration management (SCCM), [1] is the software engineering practice of tracking and controlling changes to a software system; part of the larger cross-disciplinary field of configuration management (CM). [2]
In configuration management, a baseline is an agreed description of the attributes of a product, at a point in time, which serves as a basis for defining change. [1] A change is a movement from this baseline state to a next state.
A product structure is a hierarchical decomposition of a product, typically known as the bill of materials (BOM). As business becomes more responsive to unique consumer tastes and derivative products grow to meet the unique configurations, BOM management can become unmanageable.
With the case based approach, one tries to solve the current configuration problem by finding a similar, previously solved problem and adapting it to the new requirements. The basic processing cycle in a case based configurator is: input customer requirements, retrieve a configuration and adapt the case to the new situation.