I am a backend dev who mostly works on personal projects and has done a few small collaborations with frontend devs here and there.
Suppose a non-technical client approaches me with an idea for the next revolutionary app (which happens to me on a monthly basis lol) – how can I best gather the specs? Should I involve the client in the UML diagram stage and ask him to write out detailed use cases? Or should the client make a simple wireframe?
Effective communication is key when working with a team.
I've never used UML diagrams but in my understanding they offer the following benefits:
- The development team understands what needs to be built
- Non-technical teammates understand how the app will function and can easily communicate their ideas via the UML diagram
- New teammates who join at a later stage of the development understand the full functionality of the app/website
submitted by /u/lewz3000
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/3y5tOQD