This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
I think the following structure would simplify the page. What do you people think?
IEEE, IIBA, SWEBOK, etc definitions. Possibly in a table form to show the similarities and differences.
Common attribute lists for requirements, probably sourced from IEEE journals
Again, likely from IEEE; a description of how the term entered the world of product development. Perhaps some milestones along the way such as;
What are the implications of these competing views?
A User Story isn't a requirement, but many people use them in lieu of requirements. What they are missing is that the requirements are often in this context transmitted orally or in temporary media.
Some groups such as IIBA recommend distinguishing the elicitation and analysis of requirements. Others have a model where requirements are discovered - with elicitation and analysis conflated.
The continuing research that says requirements and testing should be tightly coupled, and industry's general failure to do this well or consistently.
Where does architecture fall into this model?
What is the difference between a project and product requirement and why do people get them confused? This is related to the multiple definitions of 'scope' in the project and product management world.
Craigwbrown ( talk) 11:40, 16 January 2012 (UTC)
This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
I think the following structure would simplify the page. What do you people think?
IEEE, IIBA, SWEBOK, etc definitions. Possibly in a table form to show the similarities and differences.
Common attribute lists for requirements, probably sourced from IEEE journals
Again, likely from IEEE; a description of how the term entered the world of product development. Perhaps some milestones along the way such as;
What are the implications of these competing views?
A User Story isn't a requirement, but many people use them in lieu of requirements. What they are missing is that the requirements are often in this context transmitted orally or in temporary media.
Some groups such as IIBA recommend distinguishing the elicitation and analysis of requirements. Others have a model where requirements are discovered - with elicitation and analysis conflated.
The continuing research that says requirements and testing should be tightly coupled, and industry's general failure to do this well or consistently.
Where does architecture fall into this model?
What is the difference between a project and product requirement and why do people get them confused? This is related to the multiple definitions of 'scope' in the project and product management world.
Craigwbrown ( talk) 11:40, 16 January 2012 (UTC)