Most Business Analysts are familiar Use Cases. There are plenty of books about them. Use Cases came into the mainstream for software development in the late 90s and have evolved over time. Some people prefer User Stories, as they are called in agile methodologies. This book will argue that they are essentially the same, it's just what you put into them that might be different. More importantly, I wrote this book to share my insights of the when to write use cases, how to write them lean, and why bother with them at all. ...
Read More
Most Business Analysts are familiar Use Cases. There are plenty of books about them. Use Cases came into the mainstream for software development in the late 90s and have evolved over time. Some people prefer User Stories, as they are called in agile methodologies. This book will argue that they are essentially the same, it's just what you put into them that might be different. More importantly, I wrote this book to share my insights of the when to write use cases, how to write them lean, and why bother with them at all. This book is focused on use cases and touches on the peripheral competencies that are needed elicit and develop good requirements. A use case writer should also have strong skills in requirements analysis, requirements traceability, and visual modeling. Also, this book follows a philosophy of being a minimalist and keeping to only what adds value to the process. A general knowledge of lean principles is recommended to aide in understanding why some things are important and some are not. There are several good books on the subject.
Read Less
