does a developer has to write a usecases.
2 posts in topic
Flat View  Flat View
Older Post First |   Reply to Topic
TOPIC ACTIONS:
 

Posted By:   Anonymous
Posted On:   Saturday, January 4, 2003 03:51 AM

usually when it comes to developer he gets the details from SRS(software requirment specification).and actually whose role is to write use cases exatly ?,if developer has to do so please give me a senario?

Report | Quote This | Send private message | Reply | Print

Re: does a developer has to write a usecases.

Posted By:   Anonymous  
Posted On:   Sunday, January 5, 2003 02:50 AM

I think before being able to answer this question, you have to think about what the *purpose* of the Use Cases is. What do you want to communicate and to whom?
Report | Quote This | Send private message | Reply | Print

Re: does a developer has to write a usecases.

Posted By:   Brian_Glodde  
Posted On:   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.

Report | Quote This | Send private message | Reply | Print
About | Sitemap | Contact