Bouml reference manual - Fedora Project Packages GIT repositories

More documents

Recommendations

Info

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html366 of 378 07/10/2007 15:55When you confirm the execution of Project Synchro is done. Supposing the synchronization done for the first and third image, restartingProject Synchro this the same images, one obtains :Obviously the first and third images have the same aspect and don't contain old packages.As I said it is possible to start the tool giving the project images in parameter, for instance under Linux :projectControl ~bruno/uml/pr/pr.prj /tmp/pr/pr.prj ~bruno/pr/pr.prjPrevious : Project controlNext : Multi user considerations
file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html367 of 378 07/10/2007 15:55Multi users considerationsBOUML attributes an identifier to the main objects to resolve the references to the not already read objects when you load a projecidentifier is establish during the object creation and will not change later, to allow several users to work simultaneously on the sameproject, this object identifier contains the identifier of the user creating the object. This explains why BOUML ask you to have an ownidentifier between 2 and 127 defined through the environment variable BOUML_ID (see Define an environment variable).These identifiers are also used to name the files memorizing a project, refer to Project files. The plug-out API define theUmlBaseItem::supportFile to know whose file(s) support a given item.Notes : When it loads a project, BOUML checks the write permission of the file done through the OS or the applicative permissionindicated inside the file. In the browser the writable objects are written in bold. When you load a project, this one must be consistent, elsethe references to the unknown items are removed and these unknown items are considered deleted.When you are several working on the same project you have to choose between two ways :To share the same project filesIn this case all the users work on the same project files, this means that no one has a copy of the project files. This is possible becausewhen you do a save only the modified files are written. However this suppose at most one user may modify a given project filemodifications made by several will quickly be done.There are two way to allow at most one user to modify a file : to use the write permission set using your OS (difficult under Windows)with the help of File Control, or to use Project Control.File ControlFile control is a plug-out mainly dedicated to be an interface between BOUML and a file control like Clearcase, CVS or Subversion etc..., however to use a file control may affect the write permission of the files.Project controlProject control is a tool managing an applicative write permission optionally memorized in the project files associated to the packages.This allows to set the write permission independently of the OS you use.To use project imagesIn this case each user has an own copy of the project, and sometimes all the modifications done in parallel are grouped. You may adopttwo strategies : to allows any user to modify any part of the project, in this case you will have to merge the modifications by yourself, orto allow only one user to modify a given project file.Even the Project filesare Ascii files, I may be difficult to merge several version of the same file, I know several companies use this way, but it is possible to nothave to merge the modifications using the write protection through File control or Project control and to resynchronize the model usingProject Synchro.To work without mergeLet's suppose Bruno, Olivier and Annie work on the same project and decide to use Project Control and Project Synchro.At the beginning an unique image of the project exist. If the project already exists, using Project Control you give the write access of thepackage to at most one person. If you start from scratch with an empty project, immediately create at least a sub-package for each, thismay be changed later. Because the project itself is used to memorize generation settings and other global information, I propose you todecide immediately what are the settings and to protect the package supporting the project, this means it is not owned by Bruno, Olivieror Annie.When the write accesses are set, duplicate the project files (in fact the directory of the project) to have three images, and perhaps a foimage placed under a file controller. Bruno, Olivier and Annie work each on its private image and don't change the write accesses, exceptto loose the write access, or to get the write access to a protected package(s) not own by the others since the last synchronization.Sometimes, for instance because Annie define a class used by Olivier, you have to synchronize the parallel developments. In this caseusing File Synchro, Annie Olivier and may be Bruno get the modifications done by the others. When the project is synchronized it i
Page 1 and 2:
file:///C:/uml/BOUML/bouml_3.0/doc/
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316: file:///C:/uml/BOUML/bouml_3.0/doc/
Page 365: file:///C:/uml/BOUML/bouml_3.0/doc/
show all

Bouml reference manual - Fedora Project Packages GIT repositories

Create successful ePaper yourself

Delete template?

Save as template?