Executable Requirements
English is a poor programming language. That's why we don't use it to write code... but why do we use it to write specifications? Specifications are an attempt to describe the function of code. Anytime we can move that description from English and into something more like code, the more accurate our descriptions are. There are a number of tools, ranging from JUnit to Selenium to Fitnesse, that can be used to specify a program's requirements. Come learn how to make better change requests within your company and extract better requirements from your users as well. Executable requirements has been a theme for several years and is now reaching critical mass in the industry. Be sure to take advantage of this exciting paradigm inside your company.
Session Agenda
Sessions begin at 9AM and end at 5PM. Attendees must bring their own laptop.
Day 1
- English vs Tests: What's the Diff?
- External Customers: Requirements clarified
- Internal Customers: Higher bandwidth communications
- How to Communicate: Learning a new language
- Immersion Therapy: Exchange students
- APIs vs GUIs
Day 2
- Unit testing with jUnit
- API testing with jUnit
- GUI testing with Selenium
- GUI testing with Fit and Fitnesse
Day 3
- Dreaming in Code
- Avoiding Big Up Front Design: How much is too much?
- Commander's Intent
- Complete SDLC: Tip to tip executable requirements
- Maintenance Benefits