| < Day Day Up > |
|
The beginning of wisdom is to call things by their right names. —Chinese proverb
Chapters 2 and 3 gave general and coherent descriptions of the PDM and SCM domains, respectively. In this chapter, we will continue discussing these domains but focus on a technical comparison. We will compare the typical functionality of tools within the two domains, both on a fundamental principle level and with respect to specific functions.
Many companies use various PDM and SCM methods and tools for similar purposes. It might seem easy to compare a PDM and an SCM tool, but this is not necessarily the case. The same or similar terminology is used in both domains but often with different meanings, and a thorough analysis of their use shows that there are significant differences. Different ranges of functionality and different user cultures are two more factors that make a comparison difficult. For example, Estublier [1] considers that although the PDM and SCM domains appear to be very similar, this is only on a principle level, as their implementations are very different.
We begin this chapter with a comparison of some fundamental principles of PDM and SCM:
System architecture;
Product model;
Evolution model;
Process model.
We then compare specific functionality important in one or both of the domains. These are:
Version management;
Product structure management;
Build management;
Change management;
Release management;
Workflow and process management;
Document management;
Concurrent development;
Configuration/selection management;
Workspace management.
The comparisons of principles and functionalities overlap. In the comparison of principles, we discuss differences and similarities in a more conceptual way, whereas when comparing specific functionality, we compare tool functionality.
| < Day Day Up > |
|