350 |
After Step 1 from user's perspective, the computer has *all* the information |
After Step 1 from user's perspective, the computer has *all* the information |
351 |
needed for steps 2 and 3, so *no further changes should be required*. |
needed for steps 2 and 3, so *no further changes should be required*. |
352 |
|
|
353 |
|
- only explicit link from diagram object to the class it represents is |
354 |
|
obligatory, all other are implicit |
355 |
|
|
356 |
For Step 1, it is best to demand explicit links in the UML diagrams. |
For Step 1, it is best to demand explicit links in the UML diagrams. |
357 |
|
|
358 |
Steps 2,3: |
Steps 2,3: |
364 |
|
|
365 |
Goals: |
Goals: |
366 |
|
|
367 |
- "feeling" that the arch. doc will be read(!) |
- "feeling" that the arch. doc will be read because |
368 |
|
of the backlinks(!) |
369 |
|
|
370 |
- if diagrams try to link objects, which don't exist (e.g. removed |
- if diagrams try to link objects, which don't exist (e.g. removed |
371 |
Java class), the linking objects will be specially marked |
Java class), the linking objects will be specially marked |
386 |
documents they relate to. They function like navigation bars on the |
documents they relate to. They function like navigation bars on the |
387 |
WWW, except that the same page may have several of them. |
WWW, except that the same page may have several of them. |
388 |
|
|
389 |
- make diagrams work as context+focusing menus to the code documentation |
- make diagrams work as context+focusing menus to the code documentation |
390 |
|
|
391 |
- Borges's "taxonomy" for animals; |
- Borges's "taxonomy" for animals; |
392 |
http://www.multicians.org/thvv/borges-animals.html |
http://www.multicians.org/thvv/borges-animals.html |
464 |
|
|
465 |
Why UML-language |
Why UML-language |
466 |
|
|
467 |
- minimum barrier to make a diagram (well, at first have to learn our UML-script) |
- not strictly necessary; could have used another editor |
468 |
|
|
469 |
- separate UML structure from presentation, show structure in easily |
- minimum barrier to make a diagram (well, at first have to learn our UML-script) |
|
editable text |
|
470 |
|
|
471 |
- direct manipulation when building diagrams clumsy |
- direct manipulation when building / editing structure of diagrams clumsy |
472 |
|
|
473 |
|
- users are programmers --> a simple programming language is better than d.m. |
474 |
|
|
475 |
- diagrams in the same reST source than the architecture document |
+ elements are easy to create by script language |
476 |
|
|
477 |
- only explicit link from diagram object to the class it represents is |
+ graphical placing could need an GUI |
|
obligatory, all other are implicit |
|
478 |
|
|
479 |
UML diagram component |
- diagrams in the same reST source as the architecture document |
|
|
|
|
- not strictly necessary; could have used another editor |
|
480 |
|
|
481 |
- problem: direct manipulation of UML diagrams very clunky |
- separate UML structure from presentation, show structure in easily |
482 |
|
editable text |
483 |
|
|
484 |
- users are programmers --> allow a simple programming language |
- placement: currently metapost; looking at ways to make |
485 |
|
interactively editable. |
486 |
|
|
|
- placement: currently metapost; looking at ways to make |
|
|
interactively editable. |
|
487 |
|
|
|
+ elements are easy to create by script language |
|
488 |
|
|
|
+ graphical placing could need an GUI |
|
489 |
|
|
490 |
|
|
491 |
Practical use |
Practical use |