Skip to main content

John Terzakis


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, reduce 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.

Speaker Presentations
Tuesday, November 11, 2014 - 1:00pm
Half-day Tutorials
Specifying Non-Functional Requirements

Non-functional requirements present unique challenges for authors, reviewers, and testers. Non-functional requirements often begin as vague concepts such as “the software must be easy to install” or “the software must be intuitive and respond quickly.” As written, these requirements are not testable. Definitions of easy, intuitive, and quickly are open to interpretation and dependent on the reader’s experiences. In order to be testable, non-functional requirements must be quantifiable and measurable. John Terzakis discusses the problems with non-functional requirements—weak words, ambiguity, and unbounded lists. To facilitate the development of quantifiable and testable non-functional requirements, John introduces a solution—Planguage—and its associated keywords. By documenting requirement-specific parameters—scale (unit of measure), meter (method to determine the position on a scale), and range of success—you can remove subjectivity and ambiguity so that non-functional requirements are expressed in quantifiable and testable terms. Explore exercises to apply these ideas and develop the skills you need to improve your non-functional requirements.