tag:blogger.com,1999:blog-13831777.post-85409874307261048092008-02-10T13:32:00.000-05:002008-02-10T13:32:00.000-05:00Hi Damon,<BR/>At college, I’m taking a course about "Requirements Engineering" and I've been assigned a presentation about requirements in eXtreme Programming. <BR/><BR/>I've read some blogs and I think that I got a general idea about how requirements are handled in XP: incremental requirements, onsite customers, the whole team sit together, express business rules through customer tests (fitnesse)... Also I’ve learned that User Stories are not requirements documents but an estimation tool for the weekly iteration.<BR/><BR/>In the course, my professor focuses on RUP and use cases. I want to share that use cases can be a helpful technique but XP focuses on personal interaction over documentation, and that use cases are not required or prohibited by XP. <BR/><BR/>Do you think I’m in the right track? Can you do XP and still apply use cases as technical documentation that is done just-in-time by the developer?Oscar Centenohttp://www.blogger.com/profile/04294807270100386744noreply@blogger.com