Documente Academic
Documente Profesional
Documente Cultură
M.Tosiq Ahmed(BB-5575)
Teacher:Miss Nasreen
Testing without requirements can be difficult. Not knowing what is required of the software poses
risks in knowing what and how to test the software. After all, how can you test something if you
don’t know how it’s required to work? The importance of requirements often goes overlooked.
Software requirements specifications (SRS) are the foundation of the pillars of software. They drive
design, development, user experience, support documentation, and more. Yet, so often, they do
not exist. Or do they?
The truth is, there are always requirements, but they often go undocumented. Every software has a
purpose, therefor every software has requirements. But when they are not documented, testers are
left to find the them their-selves.
This requires the tester putting on their detector hat and sifting through any existing clues and
information to determine how exactly the software application should work. Some of these clues
might be previous versions of the software or help documents. Other clues might be discussions
with stakeholders and product owners. Either way, it’s going to take time.
Lets take a closer look at some of the things that can happen when requirements are not
documented.
Conclusion
Taking the time up front to document requirements will save you and your team time further
down the line. Requirements don’t always need to be extremely detailed documents but
they should exist in some form. They are the document of record to make sure every one is
on the same page.