Requirements and Functional Decomposition

What is the difference between these two specifications?

1. Security: a team of 10 hackers [profiled elsewhere] per hour attempting to access account holders' credit card information shall be successful no more than an average of once every five years.
2. The system shall require users log in with a user name and password. On the third consecutive unsuccessful log-in attempt using a particular user name, the system will lock the corresponding account.

The first specification is a nonfunctional requirement. The second specification is a functional decomposition of that nonfunctional requirement.

All nonfunctional requirements can be decomposed into functional specifications.

In fact, when an interaction designer fleshes out (defines the particular steps in) a use case, she is functionally decomposing both functional and nonfunctional requirements. She is specifying functional steps that will satisfy the requirements.

Comments

Murray said…

I agree that the 1st specification is a nonfunctional requirement. However, I disagree with you about the 2nd specification.

The 2nd specification looks to me to be a specific design (not requirement) that is trying to satisfy the nonfunctional requirement in the 1st specification.

Wed Apr 29, 10:59:00 AM 2009

Roger L. Cauvin said…

Murray, I completely agree that the 2nd specification is design and not a requirement. In fact, the point of the 2nd specification was to show that, as a functional decomposition of a nonfunctional requirement, it is design.

Wed May 06, 08:50:00 AM 2009

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

Cauvin

Search This Blog