Breaking News
Design How-To

Dissecting the requirements document

8/19/2010 04:04 PM EDT
2 comments
NO RATINGS
1 saves
Page 1 / 5 Next >
More Related Links
View Comments: Newest First | Oldest First | Threaded View
Manu31415
User Rank
Rookie
re: Dissecting the requirements document
Manu31415   8/27/2010 12:07:06 PM
NO RATINGS
The process discussed in your article to make requirements more and more precise is interesting. But I have the feeling it is sometimes mixing up Requirements, Specification, and Design. Isn't Specification a precise description of WHAT a user wants (requirements); and Design a description of HOW to implement the Specification (the WHAT) ? So what you are describing looks like what happens in an an iterative development process.

Luis Sanchez
User Rank
Rookie
re: Dissecting the requirements document
Luis Sanchez   8/22/2010 2:13:54 AM
NO RATINGS
Congratulations Kevin! This is a very good and educational article. I learned one or two things here. Of my special interest was in regards the user interface design. Defining the relation between the frequency of use of a function and the number of clicks or menu deepness level is a very good point. One call of attention though (and I hope you consider it as constructive criticism) is that on page 4, table 3.1 the frequency of use is reverse to what you recommended on the previous paragraph. You stated to put the most frequently used on top and the least on bottom. Though I’m now thinking perhaps you did this on purpose to get some comments? Not needed though, your article is good for what it says… looking forward for part 2.

Flash Poll
Radio
LATEST ARCHIVED BROADCAST
EE Times editor Junko Yoshida grills two executives --Rick Walker, senior product marketing manager for IoT and home automation for CSR, and Jim Reich, CTO and co-founder at Palatehome.
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed