SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Collaborative Learning in Object-Oriented Languages & Systems

imelda avatar
imelda
30 diapositives · 393 Views · Aug 30, 2014

Learn about Ruby, Ruby on Rails, O-o design fundamentals, UML, design patterns, and collaborative learning using pair programming and agile methodologies. Understand effective programming through software design patterns and refactoring techniques.

#collaborative learning in object-oriented languages & systems #collaborative learning in object-oriented languages & systems ppt #powerpoint #presentation
Collaborative Learning in Object-Oriented Languages & Systems - slide 1
01 / 30Collaborative Learning in Object-Oriented Languages & Systems
1 / 17

Télécharger la présentation

Collaborative Learning in Object-Oriented Languages & Systems
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. CSC/ECE 517: Object-Oriented Languages & Systems Web site:http://courses.ncsu.edu/csc517/lec/001 http://courses.ncsu.edu/ece517/lec/001 http://courses.ncsu.edu/csc517/lec/601 http://courses.ncsu.edu/ece517/lec/601 http://www.csc.ncsu.edu/faculty/efg/517/f11

  2. Live Question • Used as a “backchannel” during class • http://cyber.law.harvard.edu/questions/CSC517

  3. Google forms • To respond toquestions from me during class …

  4. Major course topics • Ruby • Ruby on Rails • O-o design fundamentals and UML • O-o design principles • Design patterns

  5. Collaborative learning • Based on … • Pair programming • Agile methodologies • Educational research

  6. What’s wrong with working alone? • Industry doesn’t do it that way • Learn more from peers • Less threatening to work with others • Raises burden on TAs • So I don’t have to do all evaluation • Increase burden of • interface • integration

  7. What’s wrong with working alone? • Too easy to cheat!

  8. Why do students nevertheless … • work individually? • Individual accountability…

  9. Why nevertheless (cont.)… • Time …

  10. Why nevertheless (cont.) … • Place …

  11. Syllabus: Course goals • Learn to design programs with classes that work together with maximum cohesion and minimum coupling, • Learn how design methodologies, such as CRC cards, and the Uniform Modeling Language, can be used to express the interaction betweeen program components. • Understand the differences between statically and dynamically typed object-oriented languages, and be able to program in both, • Learn how an understanding software design patterns can be used to structure programs so that they are robust and extensible, and • Appreciate how programs can be restructured ("refactored") to improve their adherence to the principles of good design.

  12. TAs • Aysu Ezen • David Young • Xibin Gao

  13. Textbooks

  14. Textbooks

  15. Textbooks

  16. Textbooks

  17. Webassign • Used for quizzes, exams • Account costs $19.95 for semester

  18. Attendance requirement • Everyone responsible for “attending” 25 of 27 class sessions. • Satisfy this by … Responding to ½ of Google forms during class (min. 2), or Passing post-quiz w/in 1 week On-campus students must do Google forms ≥ 12x during semester

  19. Audit requirement • Do one homework, or take one test (not post-quiz), before fall break and score at least 50%; then • do one homework, or take one test, after fall break and score at least 50%. • You can choose which homework or test to take, and if you take one and fail to score 50%, you can try another.

  20. Assignments and weighting

  21. Programming assignments

  22. Wiki textbook

  23. Textbook chapter

  24. Teaming requirement • Work with a minimum of 6 other students during the semester • Wiki 1 • Live Question app (Program 1) • OSS project (Program 2) • Wiki 2 • Semester project (Program 3) in teams of 2 up to 3 up to 3 up to 2 up to 4

  25. Penalty for lateness • 10 pts./day

  26. Academic integrity • See http://www.csc.ncsu.edu/faculty/efg/517/f11/integrity

  27. Technological support (summary) • For questions in class … • Your questions to me • My questions to you

  28. Technological support (summary) • For questions outside of class • Piazza • Webassign

  29. For us to work together • Synchronously: VCL, Skype • Asynchronously: Wiki, Expertiza

  30. Exercise • Read one of these wiki pages on use cases: • Rows 1, 5, etc.: http://tinyurl.com/row-1-page • Rows 2, 6, etc.: http://tinyurl.com/row-2-page • Rows 3, 7, etc.: http://tinyurl.com/row-3-page • Row 4, 8, DE: http://tinyurl.com/row-4-page • Then fill out the rubric linked to today’s exercises.