Bouml reference manual - Fedora Project Packages GIT repositories

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html360 of 378 07/10/2007 15:55Project controlThis tool manages an applicative write access to the project files without using the may be existing operating system capabilities. Thegoal is to give the write access of a the project files to at most one user per file, to avoid to merge modifications made by several users.The tool Project synchro associated to project controlallows you to synchronize a repository project with the modifications made by several users (supposing each package modified by atmost one user).Because of the way the project data are saved by BOUML (see project files), the write access are managed at package level, and eachinformation attached to a package (except its sub packages) have the write access of this package. Recall the generation settings, defaultstereotypes etc are associated to the project package, a good way is to not define views directly in the project package but to immediatelycreate sub packages, each one owned by a different user or protected.Project Control is not a plug-out, it is launch like BOUML or any tool, when you start it the following window appears :To avoid inconsistencies, you can't apply Project Controlseveral times on a given project, and you can't use it on a project while it is edited by BOUML or by Project Synchro, if this is the case amessage warns you :The write access are written inside the project files associated to the packages, if all the users access to the same shared image of theproject, the protection will be taken into account by BOUML. If there are several images of the project, after the use of File Control eachimage must be updated, or you must set the same write access using the tool by yourself.All the operations are presented to be done for a given user, this user is indicated at the bottom of the window. Obviously the user is firsthe one starting the tool, the id is the value of BOUML_ID for this user.Project menu