A Successful Journey Down Use Case Paths 

Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.

Unlock the secrets to mastering software requirements with use cases, from a major telecom project. Learn how these techniques drive success in both waterfall and agile methodologies.  

A challenge in software development is to gather and document requirements so that a software solution can be developed and delivered for business users. This article will describe the experience and insights gained from utilizing use cases¹ as the primary technique for eliciting, specifying, and refining solution requirements for a sales follow-up software development effort at a major telecommunications company. 

The software development effort that developed and delivered a software solution for retail stores of the telecommunications company, consisted of a waterfall life cycle methodology (i.e., requirements definition, design, development, testing, deployment). However, the requirements approach described in this article can be used to elicit and define features and functions that will form a requirements decomposition of user stories for an agile life cycle methodology—which will be illustrated as an extension of the requirements approach.