New answers tagged

0

It does make sense in some scenarios but I think this is not a question which one is better. The real question is which one you are better at? On the other hand, you can learn and be master of Agile methodologies but your software architecture, team structure, size, geographical distribution, quality processes, ... may not suit agile.


8

Waterfall works great if you know exactly what the code needs to do and can articulate it in such a fashion that your developers clearly and unambiguously understand what is required of them. Most clients are not able to describe what they want/need that well. There are some situations where Waterfall is and should be the methodology of choice, but ...


6

Sounds like your current software development process is not iterative, and it needs to be. The customer doesn't know what they want, and they're not qualified to determine whether or not a routine wireframe diagram will fully meet their needs. Having an iterative process will allow you and the customer to make adjustments along the way as the ...


2

This sounds reasonable, save for two considerations. Multiple client access: what if your service is handling two simultaneous requests to modify the same remote entity? At the very least, you have to make sure they do not update the remote side in an interleaved manner, resulting in a remote state none of them expects. You should (optimistically) lock ...


1

I'd rather that the server providing the data actually performed work on it for you, rather than farm it out and let you manipulate it. How are you going to handle multiple clients manipulating the same data at the same time ? I'm thinking particularly when you write it back - how will your service resolve who is correct ? Furthermore, how will the ...



Top 50 recent answers are included