CAST 2016 has ended
Testing: Software Development Catalyst

Testing is not an isolated activity. It interacts with and influences other disciplines in software development such as design, coding, release management, and deployment. As testers, our skills and experiences add value far beyond the immediate context of verifying functionality. Threats to value other than software errors exist.

Yet our discussions are often constrained to the testing space, omitting the connections to, and dependencies on, other roles and activities. Testing is an integral discipline of software development, and often plays an active and important role in bridging gaps between technical and business-focused roles, between leaders and engineers, and between makers and users.

How does the testing piece fit into the software development puzzle? How does – and how should – testing interact with other disciplines in software development? How can we most effectively add value to the software development projects we participate in?

Please join us for our 11th annual conference at the Simon Fraser University Harbour Centre campus in downtown Vancouver, Canada, August 8-10 2016.


IMPORTANT NOTE: Creating a profile on this site does not constitute registering to attend the conference. If you would like to attend and have not yet registered, please Learn More »

Tuesday, August 9 • 14:30 - 15:30
Cooperating to Exercise Judgment and Skill: Requirements

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

Requirement engineering is an important part of the software development lifecycle. Gathering the right information so we can build the right system is critical for a project’s success. Regardless of how this information takes form, whether it comes in formal requirement specifications, user stories, or even just general ideas in a spreadsheet, ­this first step is the key to reducing bugs in our software and building better quality products. It has been estimated that almost 50% of bugs are the result of poorly written requirements.

How can we avoid bad requirements and reduce the number of bugs in our products? We can have testers involved early in the requirements process and ensure that requirements are written to be complete, consistent, and testable. Although there are lots of methods that will help remove bugs from requirements, I believe a human factor (and ideally a tester) is needed to really understand what the stakeholders are trying to communicate. Testers bring a different perspective and dynamic skill set that can be very valuable in requirement gathering. Testers can become active participants in the requirement process, and should advocate for well written and testable requirements. This session will explore why testers should be involved in the requirement process, how they can contribute, and the impact on quality this can have on a project.

avatar for Julie Lebo

Julie Lebo

Julie Lebo is a software engineer with over six years of test engineering experience. Her software testing experience started as a student where she developed her interest andappreciation for finding bugs and solving problems. After graduation, she continued on as a software developer... Read More →

Tuesday August 9, 2016 14:30 - 15:30 PDT
Canfor Policy Room (1600) Simon Fraser University Vancouver 515 West Hastings Street Vancouver, BC V6B 5K3