Projects that use the same PVOB have access to the same set of components. If developers on
different projects need to work on some of the same components, use one PVOB for those
projects. For example, the following
figure shows concurrent development of
two versions of the Webotrans product. While most members of the team work on the 4.0 release
in one project, a small group works on the 4.0.1 release in a separate project. Both projects use
the same components, so they use one PVOB. Figure 1. Related projects sharing one PVOB
Consider using multiple PVOBs only if your projects are so large
that PVOB capacity becomes an issue.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.
