brady gaster

yadnb

How do you define the structure of a requirement?

That's about all i can say, and this is, mind you, a call for comments. What are the parts of a requirement? How do you define what a “requirement” is? What is it made up of? Don't flame one another. Use the comments. Tell me/one another what you think it means to be a requirement. Let's define the ontology of a requirement. Help. Comment. Speak.

Posted: Sep 25 2003, 06:49 PM by tatochip | with 7 comment(s)

Comments

Phil Weber said:

OK, I'll bite. How about:

Name
Description
Priority
Stakeholder

What else? Do you want to track required resources? Estimated time/cost to implement?
# September 25, 2003 7:21 PM

SBC said:

I like the works of Karl Wiegers. Check out -
http://www.processimpact.com/goodies.shtml#reqs
# September 25, 2003 7:46 PM

Randy Holloway said:

According to Alan Cooper, requirements are "the sum total of all demands of a program." Read more here- http://www.ftponline.com/vsm/2003_01/magazine/departments/softwarearchitect/
# September 25, 2003 8:12 PM

brady gaster said:

All very good suggestions, especially the idea of a requirement having a stakeholder. How do you think a stakeholder should be dealt with? should Requirements be associated with multiple Stakeholders, you think?

Let's keep this going, and not provide links, if possible. Rather, let's try to stamp out "the requirements of a requirement" together.
# September 25, 2003 8:43 PM

TrackBack said:

# September 26, 2003 6:19 AM

TrackBack said:

# September 26, 2003 6:21 AM

Darrell said:

Hey Brady, I had a decent-sized set of comments so I blogged about it. Check out the second link from my blog above (the first link errors out). Great topic!
# September 26, 2003 6:24 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)