Year: 2011
Automated Acceptance Tests and Requirements Traceability
This article explains an approach to automated acceptance testing that allows requirements traceability with an example using Java and Concordion. Acceptance tests directly tie into software requirements specification and the key for achieving maintainable tests is proper handling of traceability between the requirements and implementation as well as between the requirements and acceptance tests.
Read MoreUsing a Model Office to Gather Requirements
In this blog post, Adrian McGrath discusses how a ‘Model Office’ approach to requirements capture, design, build and test can play a significant role in improving the success of an Electronic Document and Records Management System implementation.
Read MoreNarrative Journey Maps
This blog post introduces the concept of narrative journey maps (NJM), a mashup inspired by other Usage Centered Design (UCD) techniques combined
Read MoreThe Dangers of Design by User
In this article, Demetrius Madrigal and Bryan McClain explains why you should not take user feedback or requests for design changes at face value.
Read MoreNon-Functional Requirements
The blog post “Non-functional requirements… the forgotten, overlooked and underestimated” discusses the role and impact of non-functional requirements in software projects.
Read MoreBDD to the Rescue
In this blog post, Mehdi Khalili explains that Behavior Driven Development can help you in more than one way. First and foremost it removes the ambiguity from the requirements, but taking it a step further could give you a lot of significant benefits.
Read More