Documenting 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.
In the IT world, we often hear about product lifecycles and what it takes to envision, develop, and maintain a product over its lifecycle. More specifically, we hear about its subsets, such as the software testing lifecycle. But one thing that we don’t often hear about is the technology lifecycle.
The world we live in is highly competitive, which isn't always a bad thing. Competitors want Apple to succeed with its watch to show the world the potential of the wearables market. They are not concerned that Apple through its success would hold a large part of the market share for itself.
Testers 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.
People 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.
Tim 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.
There are many misconceptions about accessibility that prevent people from making a conscious effort to incorporate it into their websites. But really, developing and testing accessible websites doesn't require more work, and it has many benefits. Let’s disprove the top four web accessibility myths.
Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements.
Online social identity is almost a necessity these days, and companies are reaping the benefits of using social media to connect with customers. Rajini Padmanaban highlights John Legere, TMobile CEO, and his success with using social media to connect first-hand with users.
Discovering performance issues in early builds allows more time to correct the design. By including critical performance-related features and elements earlier, we can take advantage of the incremental nature of the development process to avoid creating engineering in potential performance issues.