Wiki has a tendency to bury the content if it isn't properly organised from the beginning. If the idea is about shared modifiable resource (instead of versioned document), I would buy it if someone offer me a solution on how avoid version conflicts between updates and 'shareability'.
- Michael ----- Original Message ---- From: htshozawa <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, June 20, 2008 2:50:40 PM Subject: [service-orientated-architecture] Re: Joe & Linthicum on Modelling et al. --- In service-orientated- architecture@ yahoogroups. com, "Steve Jones" <jones.steveg@ ...> wrote: > This is why I tend to recommend that > things like the BA be developed in a Wiki (easy to update etc) as > there aren't any simple tools I've found in that space, then you use > that to give the context and framework for the other elements (rather > than translating it). > ... >Taking something simple and then embedding it in the rest of the >approaches is (IME) a much more effective way of working than document >passing Just wondering what other tools people are using in this area. One problem I've seen with Wiki is that people tend to get more interested in what they themselves are writing and less interested in what others and writing. H.Ozawa
