Non-functional requirements template

From Use Cases to User Stories, I’ve always struggled with how to treat the non-functional requirements. I haven’t tried it yet, but this article by Ryan Shriver on Qualities and User Stories contains something that looks like it just might work:

Name: A unique name for the quality

Scale: “What” you’ll measure (aka the units of measure, such as seconds)

Meter: “How” you’ll measure (aka the device you’ll use to obtain measurements)

Target: The level of performance you’re aiming to achieve (how good it can be)

Constraint: The level of performance you’re trying to avoid (how bad it can be)

Benchmark: Your current level of performance. Read more of this article »

Working with Robert

It never hurts to talk. The first conversation is free. There’s no sales pitch. I’ll listen a lot (I’ve actually been trained in how to do that), and after the meeting I’ll send you some notes and initial observations. If you think I can help, we’ll go from there.

Browse specific services I offer, or check out my blog.

See examples of what I've done for other clients, and read what people have to say about working with me.

Call 608-692-2638 or email letstalk@uFunctional.com.