HumIT ex2gr1

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(Created page with "= Exercise 2 - Group 1 = === Sample learning activities mapped to particular courses === # Could use the entire sequence of activities in a '''Software Engineering''' course,...")
 
 
Line 41: Line 41:
 
CON:   
 
CON:   
 
# Students need to download and configure these tools.
 
# Students need to download and configure these tools.
 +
[[Category:History]]
 +
[[Category:HumIT]]

Latest revision as of 16:42, 13 November 2021

Contents

Exercise 2 - Group 1

Sample learning activities mapped to particular courses

  1. Could use the entire sequence of activities in a Software Engineering course, or a Software Engineering 2 course.
  2. Could use some of these activities in an HCI' course, too.
  3. Earlier, easier activities could be used in the intro courses (data structures).
  4. Networking courses
  5. Could use the code libraries to illustrate concepts taught in a discrete math class (e.g., directory tree structure).
  6. Could use the code libraries to illustrate professional practice in a Technical Communication course.

PRO:

  1. motivation for students is a big plus.
  2. Very useful item to place on a resume.

CON:

  1. could be issues with FERPA regulations regarding putting student work in a public place.
  2. There could be Intellectual Property issues (Does the college assert ownership of all student work?)
  3. Shy students could be very intimidated by putting their work in a public forum, and by communicating with the developers.
  4. Faculty mindset (in favor of the status quo)

REMOTE HFOSS PROJECTS

PRO:

  1. institutional bragging rights
  2. access to a world-wide developer base
  3. public recognition

CON:

  1. lack of face-to-face communication with the "client".
  2. The source code project could use advanced features/idioms that make it harder for students to understand what the code is doing (e.g.,  ?: ++ callbacks )

RESOURCES

PRO:

  1. all of the tools are free.
  2. no in-house servers needed (can use GitHub, e.g.),
  3. no support from IT services needed
  4. students often have their own computers that are powerful enough to do development work
  5. students can download and configure FOSS development tools

CON:

  1. Students need to download and configure these tools.
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox