Why Do Business Analysts Miss Software Requirements?

Why Do Business Analysts Miss Software Requirements?

A project that ends with a deluge of change requests once operations have started can only signify one thingmissed requirements or unmet expectations. Requirements may be missed for many reasons on business projects. This article explores the reasons why requirements can end up as missed and some best practices to keep in mind for successful software implementation. 

Read More

How to Discover Missing Requirements

How to Discover Missing Requirements

Non-functional requirements are easy to overlook. This is most likely because stakeholders often assume that these requirements are given and go without saying. Missing requirements are harder to spot during requirements evaluation than poorly specified requirements and are usually detected further down the line when the system is in the testing phase or has already been deployed to thousands of users. They become even more expensive to fix if they are architecturally significant. For example, It is often difficult to include performance, safety and security features to an existing architecture - Donald Firesmith, Software Engineering Institute, U.S.A.

Read More