Talk:Systems Engineering versus Project Management, a comparative study

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 2: Line 2:
 
'''Fist impression:''' <br>
 
'''Fist impression:''' <br>
 
* The article is very well structured, and invites the reader to read along.  
 
* 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
+
* 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.
  
'''Overall structure''' <br>
+
'''Formal aspects'''
i miss some more WIKI formatting, ie.  
+
*I would put the introduction before the content to provide a read threat.
**bullet points (*),
+
*i miss some more WIKI formatting, ie.  
 
**Categories: <nowiki>[[Categories:Management]]</nowiki>
 
**Categories: <nowiki>[[Categories:Management]]</nowiki>
**References: <nowiki>[[project management]]</nowiki>
+
**References to other wiki sites: <nowiki>[[project management]]</nowiki>
**Additional reading section
+
**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:''' <nowiki>[[File:FILENAME.png‎|200px|thumb|right|FIGURE TEXT]]</nowiki>
 +
** I miss figure text. Could be solved by the method above.
 +
* 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.
 +
 
 +
'''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, especially when stating
 +
 
 +
 
 +
'''Used for reference example'''
 +
<references/>

Revision as of 18:46, 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, especially when stating


Used for reference example

  1. 1.0 1.1 1.2 1.3 Hasan, Helen, and Alanah Kazlauskas. "The Cynefin framework: putting complexity into perspective." (2014): 55.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox