Requirements are complex and detailed, sometimes it can feel like they will never be complete. But do they really need to be? On a recent software development project, many requirements models and diagrams were drafted and discussed, helping the stakeholders and solution designers to communicate about needs and ideas—but very few of them were actually “done.” This presentation will discuss which requirements models made my project a success, even though few of them were actually finished. I’ll explain the rationale for creation along with the extent of completion of each model. Come hear a project success story where few of the requirements were “finished!”

Learning Objectives:

• Understand the rationale for use and value of various requirements and analysis techniques
• See examples of how requirements evolve on a real project
• Learn to recognize when a requirements technique has stopped being useful