Choosing an Organizational Strategy
Apart from choosing a deployment strategy, defining your organizational structure is one of the most critical deployment decisions you will make. It is important to choose a structure that is stable and will endure over time. After you establish your registry's structure and put your governance processes in place, it is difficult to make fundamental changes to the way in which the registry is organized. Such a change would not only require you to transfer assets to different organizations, but might also require you to redefine the lifecycle models, policies and permissions that support your governance environment.
When planning your organizational strategy, take the following points into consideration:
In general, create organizations around the concept of asset visibility, ownership or responsibility. In the pre-production stages, use organizations to represent the major stakeholders involved in the pre-production aspects of the asset's development lifecycle. Example, service owners, developers and the
SOA Competency Center. In the production stage, use organizations to represent the groups of users who represent assets owners, consumers of assets, and the operators of the production services.
If a particular group of users requires the use of custom lifecycle models or design-time policies, create a separate organization for those users.
If you have groups of users whose needs are consumer only, create separate consumer organizations for those users.
Keep in mind that a user can belong to only one organization within a
CentraSite registry. If you have a user who will create assets for multiple organizations, add the user to the organization in which he or she will work primarily. Then use roles to give the user the ability to create assets in other organizations.
Keep in mind that an asset also belongs to only one organization. To make an asset accessible to multiple organizations, you must give the users in those organizations permission to access the asset.
Avoid creating an organizational structure that is too fine-grained. Keeping the structure of the registry synchronized with your low-level development teams and work-units will require a significant amount of work. Moreover, a fine-grained structure is generally not needed in order to govern your assets effectively.
