Features vs. Use Cases vs. Requirements

Here’s my answer. Disclaimer: This is not a universally accepted answer, and you may find other answers on the internet that directly contradict mine. But that’s totally fine, as you and I know they’re all wrong and I’m correct – Yes?!

Onto the answer…

Feature vs. Use Case vs. Requirement

You see, it all starts with user needs. After all, the goal of building (or enhancing) a product is to meet the needs of our users.

The other goal is to impress our boss’ Portugese water dog – but that is the subject of another post, on my secret blog! 😉

Features:
Once we understand user needs, we translate them into features – one or more features meet one or more user needs.

Features are descriptions of high-level product functionality. Usually a feature is something you’ll print on a detailed datasheet of your product – i.e. to share with your customers and prospective customers.

Use Cases:We then derive one or more use cases from each feature. A use case defines how a user achieves a goal using our product.

Requirements:
After defining use cases, we define other types of requirements – such as non-functional requirements, UI requirements, etc.

Typical Workflow

In a typical project – we start by understanding user needs. Then we translate needs into features. We then create functional requirements – i.e. use cases – to describe how users will achieve a need using our product. Then we define other types of requirements: non-functional requirements, UI requirements, etc.

For those of you who like pictures, here you go!

Finally, we send all of these to the engineering team – who use them to build an awesome product!

I'm your author, Michael Shrivathsan, an expert in requirements management with successful experience at several innovative companies in Silicon Valley, USA over the past two decades. I'm also a USPTO patent recipient. For my day job, I'm the VP of Product Management at Accompa, we make the popular requirements management software.

Search

Legal Disclaimers

1) Nothing in this blog shall be construed as legal, accounting or other professional advice. In fact, the authors are quite UNprofessional. We're not responsible for bad things that happen if you're dumb enough to follow anything this blog says.
2) Do not read this blog while jumping out of an airplane at 20,000 ft without a parachute. If you do, you will very likely die. We're not responsible for that.
3) Do not read this blog one sentence per day during your lunch break, while eating a quadruple bypass burger. If you do - by the time you finish this blog, you will be a total fatty and may even die. Again, we're not responsible for it.
4) In summary - we're not responsible for anything. We're Americans, baby!

Secondary Sidebar Widget Area

This is the Secondary Sidebar Widget Area. You can add content to this area by visiting your Widgets Panel and adding new widgets to this area.