Skip to main content
Wednesday, June 5, 2013 - 2:15pm - 3:30pm
Business Analysis & Requirements

Find Requirements Defects to Build Better Software

Requirements defects are often the source of the majority of all software defects. Discovering and correcting a defect during testing is typically twenty-five times more expensive than correcting it during the requirements definition phase. Identifying and removing defects early in the software development lifecycle provides many benefits including reduced rework costs, less wasted effort, and greater team productivity. This translates into software projects that deliver the committed functionality on schedule, within budget, and with higher levels of customer satisfaction. John Terzakis shares powerful tips and techniques for quickly identifying requirements defects and providing feedback on how to improve them. Learn the ten attributes of a well-written requirement and how to detect various categories of requirements issues including ambiguity, passive voice, subjectivity, and missing event triggers. Using the concepts presented, John leads the analysis of a set of requirements. Leave with checklists that will make your requirements reviews more effective.

John Terzakis, Intel

John Terzakis has more than twenty-five years of experience developing, writing, and testing software. With Intel for fourteen years, John is currently a staff engineer working with teams on enhancing product requirements to reduce planning and development times, minimize defects, and improve overall product quality. He is a certified Intel instructor for Requirements Engineering courses. John’s prior experience includes director and manager roles with Shiva, Racal InterLan, and Dataproducts. He was also a member of the technical staff at Bell Labs.

read more