Revision as of 21:25, 25 November 2014

Review by MrP

General remarks

• Very relevant topic, thorough and well researched article, with a lot of substance for the reviewer to work on :-)
• Good sample of references and links to other material
• You introduce a lot of (apparently cross- and interrelated) concepts, notions, phases etc in which the reader easily gets lost - And therefore sometimes misses your good points on how to conduct proper requirements assessment and definition
• Some general advice for improvement of the article: 1)Make it clearer for the reader if "requirements engineering" should be understood as a well defined discipline and a coherent standard method of practice resembling e.g. Systems engineering, or is it just a collective term for a set of useful tools ? 2) Consider making your introduction/abstract and discussion/conclusion a bit sharper and mutually coherent

Specific remarks

Below please find som specific remarks, adressing particular sections in your article

Introductory paragraph

• Second sentence: Are you referring to requirements as "formalities"? Difficult to understand.
• See also general remark, consider rephrasing the paragraph to set the scene for your article better

Application context

• First sentence: You write that requirements defines the stakeholders, users and customers - is it not the other way round ?
• Second sentence: You state the importance of understanding the requirements "completely and unambiguously. That is probably the core of requirements management and requirements "engineering", therefore you should consider elaborating the statement at this point in the article, maybe referring to the section "Req. elicitation" later in the article
• Sentences no. 8 and 9 are difficult to understand, consider rephrasing

Acceptance and use

• In general, this section (and even the header itself) is a bit difficult to understand.
• As mentioned in the general remarks you indicate that "requirements engineering" is a defined discipline or process, but you do not elaborate on or describe it's definition
• What is the point of your references to software development issues in the first half of the paragraph?
• It is a good idea to give examples like the one of the railway system, but the point is difficult to grasp

Creating requirements

• In this section you introduce a definition of "requirements engineering" as a Deming-type circular process. Is that correctly understood by the reader? -If so you should consider using the graphic representation more, elaborating on all 4 steps in the circle as they are named on the diagram. As the article is written now it is difficult to see the connection between the "RE Lifecycle" and the issues you elaborate on in the following sections.

Major concepts

You should consider deleting this header, it does not contribute to the reader's overview of the article, as long as you don't show a coherent whole framework for those "concepts"

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

Design and validation

• It becomes a little unclear where we are now in the RE lifecycle?

Context

• You refer to this item as a "phase", bur for the reader it is very unclear where in your RE lifecycle this phase belongs. The considerations you mention in this section is probably clever and relevant, but the reader is lost at this point.

Functional requirements

• Again you refer to this as a "phase in requirements engineering". What phase in what model? I'm afraid many readers would be lost at this point.
• If you believe the snow card is an good example of an applicable method you should consider showing a larger and readable picture, and to explain and elaborate on it. Otherwise don't show it.

Non-functional requirements

• Your definition of non-functional requirements as "qualities" is interesting, you should consider giving some (authoritative?) references to this definition.
• 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.

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 ?

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.

=