requirements
|
Testing Nonfunctional Requirements in an Agile LifecycleAs organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle. | 
|
|
Five Techniques for Creating Testable RequirementsDocumenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements. | 
|
|
Performing Accessibility Testing on a Live Site: A Case Study Because accessibility is just starting to really gain awareness in the product development world, organizations are often not fully informed on what it takes to build accessible software—they just want to get there. Here’s a case study from a project that involved making a live product accessible. |
|
|
Why Testers Should Get Involved in Requirements EngineeringTesters use requirements as the basis of test cases, review them for testability, and often participate in general requirements reviews or inspections. However, many testers have little knowledge of requirements engineering. Erik van Veenendaal provides five critical success factors to get started. | |
|
Three Ways to Increase Test CoverageMost defects are due to poorly defined requirements and incomplete test coverage, and fixing an error is cheaper at the coding phase than during testing. In order to ensure more thorough testing, try functional workflow documentation, four-dimensional test coverage, and risk-based prioritization. |
|
|
Let’s Stop the Password MadnessPeople and organizations definitely should take security seriously. That said, some of the “experts” advising about password security are going too far. Frequent password changes give the appearance of more robust security without actually affecting anything. Payson Hall unpacks this requirement. | 
|
|
Web Accessibility and a Call for ActionTim Berners-Lee, inventor of the World Wide Web, said, "Access by everyone regardless of disability is an essential aspect." But websites using sophisticated visual effects make it difficult for the blind and disabled to have equal access. It's important to design and configure sites for everyone. | 
|
|
Analyzing the Value of a Test Tool ApproachMany test managers want to assess the value of their test tool approach. There is a way to do it that does not require writing code—only the ability to read it a little. Matt Heusser helps you figure out if what your team is doing is working, what you could drop, and what might be worth picking up. | 
|