Analyst’s corner
Published in

Analyst’s corner

We Don’t Need No Stinkin’ Code: Testing Software Requirements

Testing requirements can reveal errors long before the code is implemented. It’s cheaper, faster, and even kind of fun.

Photo from ThisisEngineering RAEng at Unsplash

Someone once asked me when you can begin testing software. “As soon as you’ve written your first requirement, you can begin testing,” I replied. It’s hard to…

--

--

--

All aspects of organisational analysis: business analysis | enterprise architecture | quality

Recommended from Medium

Let’s Do DevOps: Resource-Level Automated Terraform CI/CD Approvals

On DevOps — 2. Why Do We Need DevOps

Istio Service Mesh Observability with Kiali

iOS Developer Roadmap

Running in 30 mins — 1: PhoneGap Build with iOS

Today in Serverless and Open Source

Easy Guide to Create a Custom Read Data Source in Apache Spark 3

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Karl Wiegers

Karl Wiegers

PhD in organic chemistry. Author of 13 books, mostly on software. Guitars, wine, and military history fill the voids. karlwiegers.com and processimpact.com

More from Medium

6/28 #ProductDiaries: Project Brainstorm

Keeping the Project Scope in Focus

A drawing That shows business requirements feeding into user requirements and then into functional requirements. Change requests come in at the user requirements or functional requirements level, leading to negotiating a scope increase at the business requirements level.

Don’t be scared! 7 irrational fears that lead to bad software with wrong architectures

Elephant scared of a mouse

Should I be using story points at all?