Articles
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 More
The 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 More
Decision Table Based Methodology
This article describes a decision table based methodology for the analysis of complex conditional actions.
Read More
Agile Product Management using Effect Maps
Effect maps are charts of project scope which help teams ensure that software delivery is focused on business goals, stakeholders and their needs. Effect Mapping facilitates the implementation of several techniques of agile planning, product design, prioritisation and scoping.
Read More
Capturing Value in Requirements Specification
The requirements specification practices fail to capture value-related information. In addition, managers do not communicate about value and demand to deliver it. This article by Tom Gilb outlines suggestions to tackle these problems and improve the quality of requirements specification.
Read More
Non-Functional Requirements: Do User Stories Really Help?
This interesting article by Rachel Davies discusses if user stories can be used to express non functional requirements in agile software development projects.
Read More