REP relationship statement?

REP relationship statement?

• A. The granule of reuse is broader than the granule of release
• B. The granule of release dictates reuse
• C. Increase the granularity of release to improve reuse
• D. The granule of reuse equals the granule of release

Answer: (D)

The main idea here is that the unit you release should be the same unit that others reuse. This REP principle means the granule of reuse is the same as the granule of release: you package and publish a component as a whole, and that same package is the unit that other developers will reuse. Keeping them aligned makes versioning, dependency management, and compatibility straightforward—there’s a clear, stable unit to release and a clear, stable unit to reuse. If the reuse granule were broader than the release granule, you’d be expecting to reuse larger pieces than what is actually released, which complicates versioning and distribution. If the release granularity dictates reuse, you’d be forcing reuse decisions based on how you chose to release, which reduces flexibility. And trying to increase the release granularity to improve reuse isn’t guaranteed to help, because it can fragment the release, create more options to manage, and still fail to provide a consistent, reusable unit. The alignment of the two granules—being equal—best supports predictable reuse.

The main idea here is that the unit you release should be the same unit that others reuse. This REP principle means the granule of reuse is the same as the granule of release: you package and publish a component as a whole, and that same package is the unit that other developers will reuse. Keeping them aligned makes versioning, dependency management, and compatibility straightforward—there’s a clear, stable unit to release and a clear, stable unit to reuse.

If the reuse granule were broader than the release granule, you’d be expecting to reuse larger pieces than what is actually released, which complicates versioning and distribution. If the release granularity dictates reuse, you’d be forcing reuse decisions based on how you chose to release, which reduces flexibility. And trying to increase the release granularity to improve reuse isn’t guaranteed to help, because it can fragment the release, create more options to manage, and still fail to provide a consistent, reusable unit. The alignment of the two granules—being equal—best supports predictable reuse.