Warren discusses some of the considerations that you need to take into account when you’re considering using Cucumber with other requirements methodologies, using UML as an example.
Ninety Nine Point What?
Andrew follows up his earlier post on Availability Requirements Elicitation, describing the stakeholders that are commonly present in non-functional requirements workshops and some of the key technical concepts that you’ll need to be familiar with.
So what do cucumbers have to do with requirements anyway
Paul introduces Cucumber (and Gherkins), and discusses techniques for developing executable acceptance criteria using a domain specific language. Cucumber is a tool that is frequently used in agile environments and Gherkins are feature files.
Performance Problems?
Andrew discusses the basics of modelling performance requirements and describes the key factors which effect the performance of web based solutions.
Stop Specifying the Obvious
Paul discusses the problems with over-specification with regards to common problems and proposes some solutions.
Ninety-nine point what?
Andrew discusses some of the challenges with eliciting Availability requirements, and begins to propose a framework.
Global Developments
Andrew discusses how global changes in the IT Consulting landscape are affecting the way that software is delivered.
Analogies – Handle with Care!
Paul discusses some of the risks with using analogies as an analysis technique.