design
thanks reto for your little example.
all right, today i've extended the dcd and the sequence diagrams.
the dcd isn't perfect now. but i think it's a good fundament to start with the implementation tomorrow. i've updated the sequence diagrams with the new methods and name from the dcd. please take a look at these atifacts below.
design class diagram
sd createsharedcodedocproject
sd edit comment
sd synchronizedocumentationproblem?
----------------------------
for the locking of the different documentation parts when a user starts editing, i haven't a good solution now. i thougt, that i make for each project a file, in which the documentation parts are saved, which are at this time locked. but i don't know, if this is a feasible solution? what are your thinkings about that?
posted by Remy Blaettler @ 6:39 PM
3 comments
3 Comments:
Looks good from my point of view. Maybe I would not put the whole signature of a method into the diagram. As you can see it does not help in the overall readability. If you are using Together, is it not possible to actually create a navigateable html output? So one can just click on a class and dig down to the details?
Have to look at the class diagramm a bit closer again tonight. Off the the elephant caves now :-)
About your problem, instead of locking it, why don't you use the conflict resolution algorithm if two users really end up changing the same thing at the same time? So you don't need to lock anything.
Class & Interaction Diagramms:
------------------------------
Overall looks good. I'm a little confused with Synchronizer and ProjectSychronizer classes. Do we need all this? Can't we simplify this a little bit?
The last interaction diagramm about the Synchronization is not in sync with your latest class diagramm. E.g. CommentSynchronizationEngine is not in the class diagramm.
Rename wherever you use Log with ChangeLog. Otherwise it gets misunderstood with error log.
Regarding your problem:
------------------------
Remy, currently we only support conflict resolution between comment changes in source code and web pages. To simplify things we should leave it that way. Although a future release should also support this type of conflict resolution. Coming back to the locking, can't we use the file locking flag itselft? Whenever a user requests an edit page, we simply set that file to read-only. Would that make sense?
Post a Comment
<< Home