Saturday, January 4, 2003 12:01 PM
I believe that is the responsibility of the Architect, not the Developer. If you go by "the book", the roles are fairly clean cut...the Architect develops the plan, the use cases and all associated diagrams. He communicates the implementation plan to the team and they are responsible for bringing the plan to life.
Generally, the Architect has little or no hands-on coding and the Developer has little or no high level diagramming.
I wouldn't say these are rules to live by...with a small team, you may end up sharing responsibilities across the board, which ends up being to your benefit.