meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
reactjs2017january [2018/01/02 21:21]
cc_wiki_update
reactjs2017january [2018/01/02 21:51]
cc_wiki_update
Line 5: Line 5:
 Topic: React.js & Redux  Topic: React.js & Redux 
  
-====== Course TODO list ======+====== Course TODO list AKA requiremetns to pass the course ======
   * A short list of things to cover to pass the course (for the 3 credits):   * A short list of things to cover to pass the course (for the 3 credits):
     * Participation in the Tueasday lectures     * Participation in the Tueasday lectures
Line 11: Line 11:
     * Preparing the team and it's members (3-4 persons) presentation slide set and have it ready and sent for course teacher before 16:00 Thursday 04.01.2018     * Preparing the team and it's members (3-4 persons) presentation slide set and have it ready and sent for course teacher before 16:00 Thursday 04.01.2018
     * Prepare team project presentation slide set     * Prepare team project presentation slide set
-    * Project presentation as a team in Friday afternoon 05.01.2018+    * Project presentation as a team in Friday afternoon 05.01.2018 (maximum of 15 minutes per a group)
     * Having a course reflection document written and returned for the course teacher before 19.01.2018 23:59 (detailed instructions shall be given on Friday 05.01.2018)     * Having a course reflection document written and returned for the course teacher before 19.01.2018 23:59 (detailed instructions shall be given on Friday 05.01.2018)
     * Do a project team Wiki page & project short video (15sek to 120sek)      * Do a project team Wiki page & project short video (15sek to 120sek) 
Line 18: Line 18:
   Manuals, help and so on:   Manuals, help and so on:
  
-  * +  * Project presentation could include e.g. 
 +    * Idea, motivation, goals, solutions used, what was actually implemented and so on 
 +    * Also you could consider presenting: Vision, Value proposition, Customer journey (story of a customer using the solution) 
 +    * Benefits of your solution over competition 
 +    * "nice coding trick" that could be handy to others in future 
 +    * Live demonstration of your solution and so on 
 + 
 + 
 +  * In reflection report, you might want to write about 
 +    * The ideal application flow and features created 
 +    * The user experience aspects considered with the application 
 +    * Showcase(s) of your solutions best features / ideas and explain how they are "cool" and/or useful 
 +     
 +  
 + 
 + 
  
 \\  \\ 
Line 36: Line 52:
 | [[:reactjs2017january:group9:start|Group 1]] | GroupTeamName | Group member 1 | Group member 2| Group member 3| Group member 4| | [[:reactjs2017january:group9:start|Group 1]] | GroupTeamName | Group member 1 | Group member 2| Group member 3| Group member 4|
 \\ \\
-==== Course requiremetns (to pass) (under construction) ==== 
-  * **On Friday, at the end of the course, you need to have** 
-    * 15 minutes presentation about your team project & Setup (idea, motivation, goals, solutions used, what was actually implemented etc.) 
-      * //Proposed talk topics// 
-      * Scenario and Vision incl. benefits & value proposition 
-      * Ideal customers 
-      * Experiences about the platform 
-      * One or two things in the source code that you are most proud of and think that might be useful to others 
-    * Five minutes demonstration of your //working// program 
-      * //Proposed talk topics// 
-      * The application flow and features 
-      * The user experience with the application 
-      * Showcase your best features and explain how they are cool or useful 
-    * Five minutes explanation of a home automation protocol 
-      * Detailed explanation of a protocol (each group chooses a different protocol) 
-    * Short Explanation of FHEM and impression 
-    * **= Total presentation time of 30 minutes** 
-    * Finished your wiki page and linked it to this one. Use [[dotnet2010:grp3:start|this]] or [[otsocase2015:group2:start|this]] as an example for your wiki page. 
-      * Group members 
-      * Idea 
-      * Motivation 
-      * Features (with screen captures!) 
-      * Which kind of technology, platforms, access methods you have used 
-      * One-Page Poster for your Scenario & Setup 
-      * Some explanatory charts (optionally) 
-      * Your project folder compressed and uploaded to the wiki **OR** //a public link to your Git or Mercurial repository// 
-  * **In one week, (i.e. 7 days from from your final presentations) ** 
-    * Update your wiki page with: 
-      * Project report on the same themes as your wiki pages. Write more on these themes and also put the content back on your wiki page.  
-        * Use the same criteria as in the wiki page. Use a seminar paper template. (except no literature review required here, of course)  
-      * One page poster about your project (see examples from previous years, also upload this poster to the wiki) 
-        * Make this more like an advertisement. Try to sell your idea and solution in here! Also: Try to make it so that it'd look good in your CV.  
-      * Project source code **OR** a link to your public repository (good places are Github or Bitbucket) 
  
-====== Discussion and the Q&A ====== +
-  * See our new team platform for team status (link upcoming) +
-  * Group 4 +
-  * WE are working on the meeting room scenario +
-  * We want to provide comfort and efficiency during meeting time slots+
  
 ====== FAQ ====== ====== FAQ ======
  
 === I have an exam in Code Camp week ? === === I have an exam in Code Camp week ? ===
-You are free to go exam, but code camp in intensive course and idea is to focus coding during the well, so it is recommended you prepare to exam before the code camp week. You are fully evaluated based on your working during the code camp.+You are free to go exam, but code camp in intensive course and idea is to focus coding during the week, so it is recommended you do prepare to any possible exams before the code camp week. You are fully evaluated based on your working during the code camp and please remember, results speak for your group and results tend to take time :) 
  
 === Grading ? === === Grading ? ===
 Grading 1-5 from Grading 1-5 from
-  * Idea and presentation of the Idea in wiki: 25+  * Idea presentation in wiki: 10% 
-  * Coding of the implementation: 25+  * Idea and presentation in Tuesday afternoon session 10% 
-  * Presentation: 10% +  * Code camp reflection report 20
-  * Code Camp Spirit: 20+  * Coding of the implementation: 20
-  * Code camp report 20% +  * Group evaluation done by "non technically trained person" 10% 
- +  * Presented implementation in Friday event 30
 +  * Improvement done after Friday is mandatory to pass the course, BUT it can also earn you additional bonus into final evaluation too)  
 +    * and how you report this improvement in the wiki page