The Product Directory Structure is logically organized to ensure that there is a placeholder for all
project related work products.
The product directory structure serves a logically nested placeholder for all product-related work products. The shape
of the directory (which serves as the project repository) depends on the number of subsystems in the overall system,
and the number of elements in each subsystem.
The logical structure of the product does not emerge until these tasks are underway: Analysis
& Design. An initial project repository needs to be created for the management and planning work products.
Guidance for the initial structure is provided under Concept: Product Directory Structure.
The rest of the structure can be elaborated once design decisions have been made, and the nature of the Implementation
View becomes clearer on how various design elements are to be packaged for implementation.
Create a placeholder for each subsystem that needs to be implemented in the directory structure. Estimate the storage
requirements for the work products that will be developed, and ensure that there will be sufficient physical storage.
For CM purposes, there must be a high degree of cohesion between internal elements in the product directory structure.
The subsystems should have clearly defined interfaces with the other parts of the system, and be independently
buildable and testable. The key reason here is to allow for independent and parallel development of the systems by
separate teams. The idea is to significantly speed up development and promote reuse and ease of system