Year: 2013
Prototypes, Prototypes and Prototypes
Scope creeping? Vision dissipating? Stakeholders disengaging? Team splintering? Specification ballooning? User experience rehashing? Application prototyping can help with these ailments and more by creating a common vision for team members, stakeholders and customers.
Read More
Linking Requirement and Acceptance Tests
Acceptance tests and requirements are linked. You can’t have one without the other. The tests clarify and amplify the requirements. A test that fails shows that the system does not properly implement a requirement. A test that passes is a specification of how the system works.
Read More
Formal Requirements Modeling Languages: RML Revisited
Requirements Modeling Language (RML) offers a notation for requirements modeling which combines object-orientation and organization, with an assertional sublanguage used to specify constraints and deductive rules. RML provides both an object-centered modeling framework and an ontology for requirements modeling.
Read More
Using Approval Branching for Business Requirements
When the business changes rapidly, this is a problem for a development team that has in its current release trunk both approved and unapproved features. In this blog post, Jack Low presents a solution to minimise the issues created by unapproved features in the codebase at the time of a release and contrasts this approach […]
Read More