Talk:Systems Engineering versus Project Management, a comparative study
From apppm
(Difference between revisions)
LasseMadsen (Talk | contribs) |
LasseMadsen (Talk | contribs) |
||
| Line 13: | Line 13: | ||
* I would consider to use the references more than once like: this <ref name="Example">Hasan, Helen, and Alanah Kazlauskas. "The Cynefin framework: putting complexity into perspective." (2014): 55. </ref>, then the same reference could be used here <ref name="Example"/> and here <ref name="Example"/> and even here <ref name="Example"/> as well :-). (look into the code of this to see how it could be done, if you are interested. | * I would consider to use the references more than once like: this <ref name="Example">Hasan, Helen, and Alanah Kazlauskas. "The Cynefin framework: putting complexity into perspective." (2014): 55. </ref>, then the same reference could be used here <ref name="Example"/> and here <ref name="Example"/> and even here <ref name="Example"/> as well :-). (look into the code of this to see how it could be done, if you are interested. | ||
* Maybe include figure references, if the figures is not reproduced by the author of the article. | * Maybe include figure references, if the figures is not reproduced by the author of the article. | ||
| + | * | ||
'''Content aspects''' | '''Content aspects''' | ||
* The article clearly relates to the course, and provides a good overview of methods of systems enginnering vs. project management. | * The article clearly relates to the course, and provides a good overview of methods of systems enginnering vs. project management. | ||
| − | * The references used including the way of referring is very good. I would though suggest to use the references more than once | + | * The references used including the way of referring is very good. I would though suggest to use the references more than once. |
| + | * I would have enjoyed to read examples of uses of the V-model and how this could help practioneers in relations to other models. | ||
| + | * I like that the author of the article finishes off with reflections of practise. | ||
'''Used for reference example''' | '''Used for reference example''' | ||
<references/> | <references/> | ||
Revision as of 18:55, 25 November 2014
Feedback by Lasse Madsen
Fist impression:
- The article is very well structured, and invites the reader to read along.
- The grammar and spelling is very good, and the content is easy to understand, due to the structure and grammar. I would though, suggest to make it bullet proof by adding additional "," where sentences get long. Especially towards the end of the article.
Formal aspects
- I would put the introduction before the content to provide a read threat.
- i miss some more WIKI formatting, ie.
- Categories: [[Categories:Management]]
- References to other wiki sites: [[project management]]
- Figures could alternatively be in the right hand side in stead of as part of the text. The problem is, that if you have a small screen, the figures will go out of the screen. Code: [[File:FILENAME.png|200px|thumb|right|FIGURE TEXT]]
- I miss figure text. Could be solved by the method above.
- I would consider to use the references more than once like: this [1], then the same reference could be used here [1] and here [1] and even here [1] as well :-). (look into the code of this to see how it could be done, if you are interested.
- Maybe include figure references, if the figures is not reproduced by the author of the article.
Content aspects
- The article clearly relates to the course, and provides a good overview of methods of systems enginnering vs. project management.
- The references used including the way of referring is very good. I would though suggest to use the references more than once.
- I would have enjoyed to read examples of uses of the V-model and how this could help practioneers in relations to other models.
- I like that the author of the article finishes off with reflections of practise.
Used for reference example
