This is going to sound like a terribly simplistic question but I'd like the community's opinion on the use of Together Control Center running in synchronous code and diagram mode and the Step 4 milestones of Design and Design Review.
The problem as I perceive it is that classes are "owned" by their owners but in order to draw a sequence diagram, a single developer has to check-out all of those classes in order to create the methods on the classes and complete the diagram. This breaks the class ownership constraint. In an ideal world, all the developers involved in the classes of a single sequence diagram would all be involved in the same CPWP at the same time and hence all working on the same sequence diagrams for the same batch of Features. However, in reality I find this problematic on a day-to-day basis - for example, a class owner may be involved in bug fixing whilst also participating in a new Feature Team.
This is how I have solved it for the time being... (I am interested to hear how others have done it)
First I ask the Feature Team to draw the sequence diagram for a Feature on a white board. I then ask the diagram creator to make the method signatures in all the classes - breaking the class owner constraint for a few brief minutes. I then have the classes checked-in. The diagram creator then draws the diagram with all the method signatures in place. This allows Together to prompt for the method call between classes on the diagram which makes drawing the diagram easier and faster.
In the event that a class in a sequence is currently checked-out by its owner due to work-in-progress, I ask the diagram creator to comment the method arrow on the sequence diagram rather than designate an "operation". This looks the same on the diagram but makes no changes to the code. This means that the diagram creator did not have to check-out the class but that the code and diagram are not synchronized.
Then the design review occurs. The diagram is checked-in.
In the original FDD project, Together did not keep sequence diagrams and code synchronized so that the act of drawing a sequence diagram did not create a need to lock class files. I would like to hear how others are dealing with this now and what is considered to be best practice.