Talk:Analysis of the current state

From apppm
(Difference between revisions)
Jump to: navigation, search
(review by student)
(Article review by student:: new section)
Line 1: Line 1:
 +
== Article review by student: ==
  
 +
*Nice overall structure, easy to follow
 +
*Nice idea to include a discussion section at the end
 +
*I recommend getting the text proofread by a native English speaker, frequent grammatical errors can be found throughout the text.
 +
*Check capital spelling of titles
 +
*'Situation analysis' is probably not the right title if the article focuses on analysis of current state only, as sit. analysis/ would include task analysis/future state and summary as well.
 +
*The analysis of the current state would further include analysis of strength & weakness of the system and cause effect analysis
 +
*In both abstract and introduction the first sentence explains what is part of what. Maybe it might sense to talk about the content of the article in the abstract (analysis of current state, what it is, what it contains, what its used for) and then in the introduction clearly describe the bigger picture (context) including solution analysis and the relation to the problem solving cycle.
 +
* I suggest to structure the chapter ‘analysis of the current state’ according to the tools presented e.g.
 +
**Short introduction
 +
**Demarcation of system
 +
**Adopting different point of views (information, energy etc.)
 +
**Black boxing
 +
**Add analysis of strength & weakness of the system and cause effect analysis as mentioned above
 +
**Maybe include stakeholder map here instead of the discussion part.
 +
*Underneath the demarcation picture you talk about five terms → there are six
 +
* I would move the tools you mention in the discussion part into the chapter above and than relate to it as you describe a step-by-step approach on how to conduct the analysis of the current state
 +
*In the summary/conclusion you could reflect whether the analysis has to be adapted to any project specific or if its generic tool or something alike.
 +
* I hope this helped a bit, sorry for little positive feedback

Revision as of 17:24, 25 November 2014

Article review by student:

  • Nice overall structure, easy to follow
  • Nice idea to include a discussion section at the end
  • I recommend getting the text proofread by a native English speaker, frequent grammatical errors can be found throughout the text.
  • Check capital spelling of titles
  • 'Situation analysis' is probably not the right title if the article focuses on analysis of current state only, as sit. analysis/ would include task analysis/future state and summary as well.
  • The analysis of the current state would further include analysis of strength & weakness of the system and cause effect analysis
  • In both abstract and introduction the first sentence explains what is part of what. Maybe it might sense to talk about the content of the article in the abstract (analysis of current state, what it is, what it contains, what its used for) and then in the introduction clearly describe the bigger picture (context) including solution analysis and the relation to the problem solving cycle.
  • I suggest to structure the chapter ‘analysis of the current state’ according to the tools presented e.g.
    • Short introduction
    • Demarcation of system
    • Adopting different point of views (information, energy etc.)
    • Black boxing
    • Add analysis of strength & weakness of the system and cause effect analysis as mentioned above
    • Maybe include stakeholder map here instead of the discussion part.
  • Underneath the demarcation picture you talk about five terms → there are six
  • I would move the tools you mention in the discussion part into the chapter above and than relate to it as you describe a step-by-step approach on how to conduct the analysis of the current state
  • In the summary/conclusion you could reflect whether the analysis has to be adapted to any project specific or if its generic tool or something alike.
  • I hope this helped a bit, sorry for little positive feedback
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox