Talk:Requirements engineering - Revision history

TigR at 15:32, 2 December 2014

2014-12-02T15:32:40Z

← Older revision		Revision as of 15:32, 2 December 2014
Line 379:		Line 379:
	*Consider what size is appropriate (you can re-size them, code is found in help)		*Consider what size is appropriate (you can re-size them, code is found in help)

	*~~'''''DO NOT USE COPYRIGHTED MATERIAL!!!!''''' It is not just a small blunder to put up a picture~~ with the (c) in it..		*When using materials with the (c) in the picture, at least make a note about how it is permitted ;)

TigR: /* Re-Review by TigR */ new section

2014-12-02T15:30:04Z

Re-Review by TigR: new section

← Older revision		Revision as of 15:30, 2 December 2014
Line 369:		Line 369:

	*'''''Thank you for your review, I can definitely see the language in the article has improved due to you catching my grammatical errors. :-) '''''		*'''''Thank you for your review, I can definitely see the language in the article has improved due to you catching my grammatical errors. :-) '''''

			== Re-Review by TigR ==

			===Layout===
			two major things..

			*Try to make your pictures stay in the right side, so it does not take up a lot of space where the text could be

			*Consider what size is appropriate (you can re-size them, code is found in help)

			*'''''DO NOT USE COPYRIGHTED MATERIAL!!!!''''' It is not just a small blunder to put up a picture with the (c) in it..

Joh: /* Strength and weaknesses */

2014-12-01T22:17:59Z

Strength and weaknesses

← Older revision		Revision as of 22:17, 1 December 2014
Line 367:		Line 367:
	:"but it is" => "but"		:"but it is" => "but"
	*'''''Fixed'''''		*'''''Fixed'''''

			*'''''Thank you for your review, I can definitely see the language in the article has improved due to you catching my grammatical errors. :-) '''''

Joh: /* General remarks */

2014-12-01T22:15:13Z

General remarks

← Older revision		Revision as of 22:15, 1 December 2014
Line 84:		Line 84:
	;Layout		;Layout
	:Be attentive of how your final article looks, use preview to make sure that what you have written is also displayed in that way.. I have found that sometimes an extra "enter" is needed to convince wiki to give me the next line. Also, start your headers from level 2 '==' as level 1 is reserved the title of your page (according to the [http://www.mediawiki.org/wiki/Help:Formatting Help page on formatting])		:Be attentive of how your final article looks, use preview to make sure that what you have written is also displayed in that way.. I have found that sometimes an extra "enter" is needed to convince wiki to give me the next line. Also, start your headers from level 2 '==' as level 1 is reserved the title of your page (according to the [http://www.mediawiki.org/wiki/Help:Formatting Help page on formatting])
	* ''''''This should be fixed now, ~~thank~~ highlighting that. :-)''''''		* '''''This should be fixed now, thanks highlighting that. :-)''''''

	==Specific remarks==		==Specific remarks==

Joh: /* General remarks */

2014-12-01T22:14:42Z

General remarks

← Older revision		Revision as of 22:14, 1 December 2014
Line 84:		Line 84:
	;Layout		;Layout
	:Be attentive of how your final article looks, use preview to make sure that what you have written is also displayed in that way.. I have found that sometimes an extra "enter" is needed to convince wiki to give me the next line. Also, start your headers from level 2 '==' as level 1 is reserved the title of your page (according to the [http://www.mediawiki.org/wiki/Help:Formatting Help page on formatting])		:Be attentive of how your final article looks, use preview to make sure that what you have written is also displayed in that way.. I have found that sometimes an extra "enter" is needed to convince wiki to give me the next line. Also, start your headers from level 2 '==' as level 1 is reserved the title of your page (according to the [http://www.mediawiki.org/wiki/Help:Formatting Help page on formatting])
			* ''''''This should be fixed now, thank highlighting that. :-)''''''

	==Specific remarks==		==Specific remarks==

Joh: /* Discussion */

2014-12-01T22:13:39Z

Discussion

← Older revision		Revision as of 22:13, 1 December 2014
Line 73:		Line 73:
	** '''''Hmm again I'm not to sure what you mean, but as said earlier I have reworked but the introduction and discussion part in order to make it a little more coherent'''''		** '''''Hmm again I'm not to sure what you mean, but as said earlier I have reworked but the introduction and discussion part in order to make it a little more coherent'''''

	** '''''Thank your for your review, it was very helpfull and gave new perspective! :-)'''''		* '''''Thank your for your review, it was very helpfull and gave new perspective! :-)'''''

	== Review by TigR ==		== Review by TigR ==

Joh: /* Discussion */

2014-12-01T22:13:26Z

Discussion

← Older revision		Revision as of 22:13, 1 December 2014
Line 72:		Line 72:
	*It seems to this reviewer that in this section you just repeat your arguments from the "Background" introduction for particular effort on requirements engineering in project work. Consider instead to make some application advice or reflections on the practices and methods you have described, e.g. describe a link between your "requirements engineering" and project management standard practices.		*It seems to this reviewer that in this section you just repeat your arguments from the "Background" introduction for particular effort on requirements engineering in project work. Consider instead to make some application advice or reflections on the practices and methods you have described, e.g. describe a link between your "requirements engineering" and project management standard practices.
	** '''''Hmm again I'm not to sure what you mean, but as said earlier I have reworked but the introduction and discussion part in order to make it a little more coherent'''''		** '''''Hmm again I'm not to sure what you mean, but as said earlier I have reworked but the introduction and discussion part in order to make it a little more coherent'''''

			** '''''Thank your for your review, it was very helpfull and gave new perspective! :-)'''''

	== Review by TigR ==		== Review by TigR ==

Joh: /* Discussion */

2014-12-01T22:12:22Z

Discussion

← Older revision		Revision as of 22:12, 1 December 2014
Line 71:		Line 71:
	===Discussion===		===Discussion===
	*It seems to this reviewer that in this section you just repeat your arguments from the "Background" introduction for particular effort on requirements engineering in project work. Consider instead to make some application advice or reflections on the practices and methods you have described, e.g. describe a link between your "requirements engineering" and project management standard practices.		*It seems to this reviewer that in this section you just repeat your arguments from the "Background" introduction for particular effort on requirements engineering in project work. Consider instead to make some application advice or reflections on the practices and methods you have described, e.g. describe a link between your "requirements engineering" and project management standard practices.
			** '''''Hmm again I'm not to sure what you mean, but as said earlier I have reworked but the introduction and discussion part in order to make it a little more coherent'''''

	== Review by TigR ==		== Review by TigR ==

Joh: /* Non-functional requirements */

2014-12-01T22:07:26Z

Non-functional requirements

← Older revision		Revision as of 22:07, 1 December 2014
Line 62:		Line 62:
	===Non-functional requirements===		===Non-functional requirements===
	*Your definition of non-functional requirements as "qualities" is interesting, you should consider giving some (authoritative?) references to this definition.		*Your definition of non-functional requirements as "qualities" is interesting, you should consider giving some (authoritative?) references to this definition.
			** '''''I'm not exactly sure what you mean, but I have tried to elborate a little more on this section and provide examples'''''
	*You should give the source reference for your list of "qualities", it is unclear if the list comes from the ISO standard mentioned - also unlisted in the references.		*You should give the source reference for your list of "qualities", it is unclear if the list comes from the ISO standard mentioned - also unlisted in the references.
			**'''''Fixed'''''

	===Requirements management===		===Requirements management===
	*Again you denote this as a "phase" - however this time I believe that we are back on the previously shown RE lifecycle again ?. You should consider explaining to the reader how these "management" (your own denotion) processes you describe here corresponds with the "engineering" processes of your RE lifecycle. Is "Requirement Management" an element or a process within Requirements engineering ?		*Again you denote this as a "phase" - however this time I believe that we are back on the previously shown RE lifecycle again ?. You should consider explaining to the reader how these "management" (your own denotion) processes you describe here corresponds with the "engineering" processes of your RE lifecycle. Is "Requirement Management" an element or a process within Requirements engineering ?

Joh: /* Requirements elicitation */

2014-12-01T22:05:39Z

Requirements elicitation

← Older revision		Revision as of 22:05, 1 December 2014
Line 47:		Line 47:
	===Requirements elicitation===		===Requirements elicitation===
	*This is an interesting section, apparently introducing learning and skills from the domain of psychology into the world of "engineering". The human factor ! It would be even more interesting if you could elaborate on this "shift of mindset" a bit more, and maybe reflect on how an engineering or project management practitioner can apply these methods in his practice, in particular how to handle the "translation" of the "elicitated requirements" into engineering specifications		*This is an interesting section, apparently introducing learning and skills from the domain of psychology into the world of "engineering". The human factor ! It would be even more interesting if you could elaborate on this "shift of mindset" a bit more, and maybe reflect on how an engineering or project management practitioner can apply these methods in his practice, in particular how to handle the "translation" of the "elicitated requirements" into engineering specifications
			**'''''Thank you - Well yes I could elaborate more on this, but a have ALOT of text in that section already. So I don't think it is necessary to cover this futher, as well as there is further reading material if one would be more interested in this method.'''''

	===Design and validation===		===Design and validation===