<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Requirements on Rusty Eddy</title><link>https://rustyeddy.com/tags/requirements/</link><description>Recent content in Requirements on Rusty Eddy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Jun 2026 20:01:44 -0700</lastBuildDate><atom:link href="https://rustyeddy.com/tags/requirements/index.xml" rel="self" type="application/rss+xml"/><item><title>Use Cases</title><link>https://rustyeddy.com/software/use-cases/</link><pubDate>Fri, 27 Sep 2024 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/use-cases/</guid><description>&lt;h2 id="why-this-matters"&gt;Why This Matters&lt;/h2&gt;
&lt;p&gt;Use cases are the first concrete step after recognizing that
&lt;a href="https://rustyeddy.com/software/software-is-hard/"&gt;software is hard&lt;/a&gt;. Before writing a single line
of code, we need to understand what we are building — and more importantly,
&lt;em&gt;why&lt;/em&gt; someone would use it. Use cases give us that foundation.&lt;/p&gt;
&lt;p&gt;A use case is a single, focused story that describes one way a user achieves
a specific goal with the system. Keep them in plain language, from the user&amp;rsquo;s
point of view, with no technical jargon. A good use case has a clear success
condition: you can observe or measure when it worked.&lt;/p&gt;</description></item></channel></rss>