Download Objectiver User Manual

Control units
If control units limit writing accesses to concepts, they do not introduce any limitation on reading accesses to them.
R2. All concepts, packages, control units and documents in a project are
always visible to any user having opened the project, whatever the location of those items is: in packages or in locked/unlocked control units.
To manage concurrent accesses to the global project as for a single control unit, the
root of the package hierarchy behaves like a control unit.
R3. In any project, the root of the package hierarchy, namely, Concept Index
behaves like a control unit.
Control units can also contain packages but cannot contain other control units. We
need therefore to specify how a lock put on a control unit propagates to the packages defined inside it.
R4. Locking a control unit A locks all the packages included in A. Sub-packages and the concepts they contain are also locked in a recursive way.
For instance, consider the following project structure (Figure 52).
FIGURE 52.
Packages and control units
Entries with a blue box icons (A, A2, B1 and B2) stand for packages. Entries with a
green box icons (Control Index, A1, and B) stand for control units.
Locking the Concept Index also locks package A and package A2. Control units
A1, B and package B1, B2 are not locked. They can be locked by any other user.
The next rules explains how control units impact information display in documents.
R5. In any diagram, all the concept references belonging to a control unit you
haven’t locked are dimmed and read-only. All the concept references
belonging to a control unit you have locked are displayed in plain text.
© Respect-IT sa
Objectiver User Manual
85