- October 26, 2009
Start-up VisibleThread's new document structure and quality analysis tool has uses ranging from requirements management to documentation quality enforcer. VisibleThread's software structure and quality detection capabilities can improve development ...
- June 14, 2009
Blueprint Requirements Center 2010 from Toronto-based Blueprint launched this week with new features targeting the needs of distributed teams and offering enhanced stakeholder collaboration. According to Tony Higgins, VP of products at Blueprint, ...
- October 22, 2008
Agile software development bridges the software requirements communications gap by embracing flexibility and face-to-face communication rather than depending on documents to communicate, agile practitioners say.
- April 11, 2008
Not properly signing off on a software project's requirements limits the quality assurance (QA) team's ability to ensure that the software does as it's intended.
- February 21, 2008
A recent IAG Consulting study finds that companies that have poor business requirements processes can expect to spend 49% more money and 39% more time on a project.
- November 01, 2007
It's tempting to consider use case diagrams as context diagrams because they do show context. But having one diagram for both will result in an unreadable cloud of bubbles.
- October 25, 2007
Eliminating documentation may speed software development, but it will create problems at the end as supporting groups try to figure out what the product actually does.
- September 24, 2007
Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. Kevlin Henney recommends a more balanced and restrained approach in order to not lose readers in a myriad of bubbles and ...
- July 18, 2007
Ideally use cases capture the functional requirements of a system in terms of identifiable and testable goals. The trick is writing and documenting them so that they offer value not just for requirements gathering but also for software design and ...