Month: April 2011
Capturing Business Requirements Using Use Cases
This article presents seven principles tor capture business requirements with use cases, based on experiences with a business requirements engineering project a payment system that operates via mobile phone.
Read More
RSpec Best Practices
This article presents the best practices of using RSpec, a Behavior-Driven Development (BDD) tool for Ruby programmers.
Read More
Software Requirements Impact on Technical Debt
This is a two part post by Brent Hoffman explores the impact of software requirements on technical debt. Part one defines technical debt and part two discusses the impact that software requirements can have on technical debt.
Read More
The Credibility Gap in Software Requirements Traceability
In this serie of blog posts, Jim Reardan explains why and how the business process is the true point of origin and the most practical and robust context for requirements identification. He also discusses the best form to capture requirements.
Read More
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