Talk:Requirements management - Revision history

Eniram: /* NobodyKnows Peer Review */

2014-12-01T17:31:56Z

NobodyKnows Peer Review

← Older revision		Revision as of 17:31, 1 December 2014
Line 1:		Line 1:
			'''My answer to the reviews is written in bold'''

	= NobodyKnows Peer Review=		= NobodyKnows Peer Review=
	I have gone through the wiki article and the review will be based from a chapter overview and finally an overall review. There are only comments if a section is shown below.		I have gone through the wiki article and the review will be based from a chapter overview and finally an overall review. There are only comments if a section is shown below.

	~~'''I will reply to your feedback in bold.'''~~

Eniram: /* Content */

2014-12-01T13:21:55Z

Content

← Older revision		Revision as of 13:21, 1 December 2014
Line 122:		Line 122:

	Otherwise I think that the article is great and gave me some new knowledge. Keep up the good work!		Otherwise I think that the article is great and gave me some new knowledge. Keep up the good work!
			* '''Thank you very much for your review! I also learnt a lot when doing this article ;)'''

Eniram: /* Content */

2014-12-01T13:15:51Z

Content

← Older revision		Revision as of 13:15, 1 December 2014
Line 117:		Line 117:

	Chapter 4 is a bit confusing. I think that you should look further into your use of layout and/or use appropriate figures.		Chapter 4 is a bit confusing. I think that you should look further into your use of layout and/or use appropriate figures.

	~~Lastly I feel that the article ends rather abruptly. Either think about rounding the last partition or add a fifth chapter.~~

	BTW you mention stakeholders. This subject is covered [[Mapping Stakeholders]] code: <nowiki>[[Mapping Stakeholders]]</nowiki>		BTW you mention stakeholders. This subject is covered [[Mapping Stakeholders]] code: <nowiki>[[Mapping Stakeholders]]</nowiki>
			* '''There are a lot of wiki articles about stakeholders! But I will try to find one to link here, because it is relevant.'''

	Otherwise I think that the article is great and gave me some new knowledge. Keep up the good work!		Otherwise I think that the article is great and gave me some new knowledge. Keep up the good work!

Eniram: /* Formal aspect */

2014-12-01T13:13:49Z

Formal aspect

← Older revision		Revision as of 13:13, 1 December 2014
Line 92:		Line 92:
	When rereading your article be mindful of your english, especially when using the suffix -s		When rereading your article be mindful of your english, especially when using the suffix -s
	e.g.: "As a matter of fact, a new designed product need (not:needs) to fulfil the customer’s expectations"		e.g.: "As a matter of fact, a new designed product need (not:needs) to fulfil the customer’s expectations"
			* '''why not needs? I do not understand this rule...'''

	As mentioned by NobodyKnows, you should not use acronyms (don't, shouldn't). But I am sure that was just a slip up, since it only happened once ;-)		As mentioned by NobodyKnows, you should not use acronyms (don't, shouldn't). But I am sure that was just a slip up, since it only happened once ;-)
			* '''Now corrected!'''

	Also remember that [:] forces capital on the following letter. You have a title saying: "Requirements management: how to make a project successful?"		Also remember that [:] forces capital on the following letter. You have a title saying: "Requirements management: how to make a project successful?"
			* '''I did not know this rule (in French, colons call for lowercase!). I think I corrected it everywhere.'''
	Further more; this is not a question. Since this is the only title with a colon [:] it looks weird. Consider rewriting the other titles to the same format or rephrase the title to something like: How to make a successful using requirements management		Further more; this is not a question. Since this is the only title with a colon [:] it looks weird. Consider rewriting the other titles to the same format or rephrase the title to something like: How to make a successful using requirements management
			* '''You are right, I did not really know how to turn this title. I think I have now found a better one.'''
	Other than those I only stumbled a few times. 8/10 on your english.		Other than those I only stumbled a few times. 8/10 on your english.
			* '''Thank you! That's good to know, I was kind of worried about this :\'''

	'''Figures'''		'''Figures'''
	I feel that most of your partitions could use some figures to illustrate their points, especially chapter 3 and 4, where you discuss some very valid points, which are also though to read since they are very complex.		I feel that most of your partitions could use some figures to illustrate their points, especially chapter 3 and 4, where you discuss some very valid points, which are also though to read since they are very complex.
			* '''You are absolutely right. I know I should put figures and I would have liked to add some but unfortunately I could not find very accurate ones and I lacked time, so I wanted to focus on the text...'''

	= Content =		= Content =

Eniram: /* NobodyKnows Peer Review */

2014-12-01T13:07:03Z

NobodyKnows Peer Review

← Older revision		Revision as of 13:07, 1 December 2014
Line 3:		Line 3:

	'''I will reply to your feedback in bold.'''		'''I will reply to your feedback in bold.'''


	== Overview ==		== Overview ==

Eniram: /* Overall feedback */

2014-12-01T13:06:14Z

Overall feedback

← Older revision		Revision as of 13:06, 1 December 2014
Line 71:		Line 71:
	* Please read the article for grammatical errors (not many, but a few).		* Please read the article for grammatical errors (not many, but a few).
	* I would properly introduce the section "Main steps of requirements management" earlier so when reading the different areas, where this approach is relevant the reader will already have an idea of what it is.		* I would properly introduce the section "Main steps of requirements management" earlier so when reading the different areas, where this approach is relevant the reader will already have an idea of what it is.
			** '''You are right, it makes more sense to explain the steps first, and add the application chapter as examples in the end.'''
	* Please be more critical throughout the article		* Please be more critical throughout the article
	** state strength, weaknesses and controversial points.		** state strength, weaknesses and controversial points.
			*** '''I wrote my article as an 'introduction and overview' article. It is open to discussion but I do not think it is the purpose of my article.'''
	* An example for how to apply requirements management would be very nice, so the reader could get an idea of how to implement this in his/her project.		* An example for how to apply requirements management would be very nice, so the reader could get an idea of how to implement this in his/her project.
	* An overall comment is that there a missing a lot of references, when doing this kind of article.		* An overall comment is that there a missing a lot of references, when doing this kind of article.
	* Please be aware of copy&paste.		* Please be aware of copy&paste.
	* Please attach "categories".		* Please attach "categories".
			** '''Two categories were already attached.'''






	= MartinKruck peer review =		= MartinKruck peer review =

Eniram: /* Requirements change management */

2014-12-01T13:03:06Z

Requirements change management

← Older revision		Revision as of 13:03, 1 December 2014
Line 66:		Line 66:
	* Very interesting aspect to consider!		* Very interesting aspect to consider!
	* There are no references assigned to this section.		* There are no references assigned to this section.
			** '''I have now assigned my references'''

	=Overall feedback=		=Overall feedback=

Eniram: /* Product development projects */

2014-12-01T12:53:21Z

Product development projects

← Older revision		Revision as of 12:53, 1 December 2014
Line 47:		Line 47:

	* Good informative chapter!		* Good informative chapter!
			** '''I have now added references'''

	== Construction projects ==		== Construction projects ==

Eniram: /* Application context */

2014-12-01T12:52:09Z

Application context

← Older revision		Revision as of 12:52, 1 December 2014
Line 34:		Line 34:
	== Application context ==		== Application context ==
	* An idea would be to make a reference to a wiki article regarding "System Engineering"		* An idea would be to make a reference to a wiki article regarding "System Engineering"
			** '''This is true, a link to the article comparing systems engineering and project management is absolutely justified here and can be a good complement to my article. So I have now added the link!'''

	== System engineering processes ==		== System engineering processes ==

Eniram: /* Definition of project success */

2014-12-01T12:48:46Z

Definition of project success

← Older revision		Revision as of 12:48, 1 December 2014
Line 24:		Line 24:
	* Please add a reference for this. A strong statement needs a reference.		* Please add a reference for this. A strong statement needs a reference.
	** "The success of a project can be described in different ways, but the common criteria is the ability of a project manager to deliver a project in respecting time and budget constraints as well as respecting the customer's expectations. The system or product that have been promised must be the one to be delivered; this is only possible when all the requirements are fulfilled."		** "The success of a project can be described in different ways, but the common criteria is the ability of a project manager to deliver a project in respecting time and budget constraints as well as respecting the customer's expectations. The system or product that have been promised must be the one to be delivered; this is only possible when all the requirements are fulfilled."
			*** '''Actually, this is my own point of view on how to define the success of a project. Of course, I was also helped by the readings I have done, but I cannot add one reference for this statement...'''

	=== Overall impression of the ''project success'' ===		=== Overall impression of the ''project success'' ===
	* It would be very nice if a definition of "customers" regarding projects could be made and maybe a few examples.		* It would be very nice if a definition of "customers" regarding projects could be made and maybe a few examples.
			** '''I think it was obvious but it seems that it is not, so I added explanation.'''
	* Please consider if it is only the customers expectations that needs to be satisfied - if yes - please state why?		* Please consider if it is only the customers expectations that needs to be satisfied - if yes - please state why?
			** '''I do not understand what you mean here? I detailed 4 criteria to define project success, customer's satisfaction is one of them but there are still 3 other, but they are detailed. I meant here that the customers' requirements are one main aspect to consider in a project in order for it to be successful.'''

	== Application context ==		== Application context ==