Articles
User Story Length
Story writing is usually taught now as a singsong “As a I want so that .” The writer should then immediately document acceptance criteria in the form of a constraint list or automated acceptance tests. Many consider it poor form to create a story that someone outside the team can’t understand from its documentation alone. […]
Read More
Capture use case documents with DITA
Explore how to combine requirement gathering with documentation that development managers, developers, testers, and technical writers can re-purpose throughout the development cycle. The flexible extension mechanism in Darwin Information Typing Architecture (DITA) is becoming an industry standard for this kind of undertaking. In this article, you create a specialized schema for use case documentation.
Read More
Problems of UML as a Requirements Specification Language
This paper investigates the suitability of UML as a semiformal requirements specification language. It identifies and demonstrates various problems and deficiencies of UML, particularly concerning use case models and system decomposition.
Read More
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
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