Programmification XXX
From apppm
(Difference between revisions)
|
|
| (14 intermediate revisions by one user not shown) |
| Line 1: |
Line 1: |
| − | ==Abstract==
| |
| | | | |
| − | == Note to TA ==
| |
| − | In order to explain the origin of the phenomenon, Programmification, linking to a wiki regarding Projectification would be relevant. However, nothing is written on Projectification yet.
| |
| − | Due to this situation, I'll shortly describe the origin of the expression, Projectification, in my wiki article in order to '''1.)''' have a reference point for my article/argumentation and '''2.)''' to give the reader an understanding of the 'current situation' from where the need for/interest in/tendency towards Programmification arose.
| |
| − |
| |
| − |
| |
| − | ==Note to self ==
| |
| − | I'll add the correct title when I have decided which context to explorer Programmification within. (= create a new wiki article by c/p content).
| |
| − |
| |
| − | == Big idea ==
| |
| − | Describe the tool, concept or theory and explain it's purpose. The section should reflect the current state of the art on the topic.
| |
| − |
| |
| − | == Application ==
| |
| − | Provide guidance on how to use the tool/concept/theory and when it's applicable.
| |
| − |
| |
| − | == Limitations ==
| |
| − | Critically reflect on the tool/concept/theory. When possible, substantiate your claims with literature.
| |
| − |
| |
| − | == Recommendations ==
| |
| − |
| |
| − | == Annotated bibliography ==
| |
| − | Provide key references (3-q9), where a reader can find additional information on the subject. Summarize and outline the relevance of each reference to the topic (around 100 words per reference). The bibliography is not counted in the suggested 3000 words target length of the article
| |
| − |
| |
| − | == References ==
| |
Latest revision as of 17:09, 27 February 2018
