Question 1

What are acceptance criteria in software development?

Accepted Answer

Testable conditions, typically in given-when-then format, that define when a piece of functionality is complete. Without pre-agreed criteria, the definition of done comes from the builder, which is a weak contractual and commercial position for the buyer.

Question 2

Why specify what custom software should NOT do?

Accepted Answer

A specification that defines out-of-scope is usually sharper than one that only defines in-scope. The boundary protects budget and planning from feature creep, and every unanswered question becomes a feature request later.

Question 3

Who should own the source code of custom software?

Accepted Answer

The buyer, contractually, with an escrow and knowledge transfer arrangement. Custom software where the buyer does not own the source code is not an asset but a vendor dependency, which becomes material at sale or transfer.

Question 4

Why do custom software projects go over budget?

Accepted Answer

Three causes dominate: vague specs that developers fill in by assumption, integrations discovered too late, and a change request process that was never agreed upfront. The first prevents the second and third.

Question 5

What is the difference between functional and non-functional requirements?

Accepted Answer

Functional requirements describe what the software does. Non-functional requirements describe how well: performance thresholds, security level, scalability ceiling, availability percentage. Builders deliver what is specified; missing non-functionals get no attention.

Is your company ready for the next software project?