Category Archives: Requirements & Testing

As a software tester, I find that using models is very helpful. Models allow us to understand a business process or how a system should behave in a given situation. In my practice of software testing, I keep sketches of … Continue reading →

In my current context I’m required to use a certain tool for managing the test effort; you probably know the tool. I won’t mention it by name unless the vendor pays me to, but it’s the first on the list … Continue reading →

Take everything you know about bug advocacy – the art of maximizing the likelihood that any given bug is fixed as per its impact on those who care about it – and direct it towards feature advocacy – the art … Continue reading →

How do you know what a system is supposed to do and what it is not supposed to do? Formal requirements are intended to create an easily validated, maintainable and comprehensive set of documents communicating the system’s planned functional scope … Continue reading →

I presented “Capturing Wild Requirements – For Testing” to VANQ.org, the Vancouver Software Quality Assurance User Group, and I wanted to share that material with you. Later, I developed this material into a 1-day workshop “Requirements Ghostwriting: Filling in the … Continue reading →

In the fast-paced changing world of software product development there is a continuous challenge to document the expectations for the system and its internally and externally facing behaviours. Requirements often suffer because of the challenges of keeping up with an … Continue reading →

How do you know what a system is supposed to do and what it is not supposed to do? Requirements are intended to create an easily validated, maintainable and verifiable document describing a system’s planned functionality. What is lacking in … Continue reading →

A typical software project lifecycle includes such phases as requirements definition, design, code and fix. But, are you shipping software applications with minimal to no requirements and little time for testing because of time-to-market pressures? Build it, ship it, then … Continue reading →