Search results

Create the page "ACM Body of Knowledge" on this wiki!

Page title matches

• Category:ACM Body of Knowledge
  ...he ACM/IEEE Joint Task Force on Computing Curricula, describes the body of knowledge needed for a CS curriculum, course exemplars, and other guidelines. CS2013 identifies a set of knowledge areas, divided into sub-areas, each with topics and learning outcomes for C
  3 members (3 subcategories, 0 files) - 20:39, 1 May 2019

Page text matches

• Career Planning
  An in-class exercise for students to think about the role of open source projects in their career planning. ...this exercise is to get students thinking about their future and the types of activities they can do as an undergraduate to make their resume and job app
  3 KB (475 words) - 12:11, 15 October 2018
• Category:ACM Body of Knowledge
  ...he ACM/IEEE Joint Task Force on Computing Curricula, describes the body of knowledge needed for a CS curriculum, course exemplars, and other guidelines. CS2013 identifies a set of knowledge areas, divided into sub-areas, each with topics and learning outcomes for C
  3 members (3 subcategories, 0 files) - 20:39, 1 May 2019
• Learning Activity Format with Directions
  # Categorize the page using tags at the bottom of the page. ...cussion''' tab (upper left of the page) to leave feedback to the author(s) of the activity, such as usage or suggestions for enhancements.
  4 KB (662 words) - 12:11, 15 October 2018
• Template:Learning Activity Info
  ! style="text-align:right;" | [[:Category:ACM Body of Knowledge|ACM BoK]]<br>Area & Unit(s) {{{acm unit}}}
  2 KB (253 words) - 17:43, 22 January 2019
• Intro to Copyright and Licensing (Activity)
  Participants will explore different types of licenses frequently used by open source projects. ...watching one or two on each topic: copyright and licensing. Here are a few of our favorites.
  3 KB (404 words) - 12:12, 15 October 2018
• Talk:Intro to Bash (Activity)
  ACM body of knowledge ACM classification
  198 B (32 words) - 17:44, 8 March 2017
• Talk:Intro to Bug Trackers (Activity)
  *ACM body of knowledge and ACM topics
  176 B (25 words) - 17:49, 8 March 2017
• Talk:Intro to Copyright and Licensing (Activity)
  No ACM body of knowledge or topics.
  125 B (18 words) - 17:52, 8 March 2017
• Talk:UX Review
  * ACM Body of Knowledge & Topics
  193 B (25 words) - 18:04, 8 March 2017
• Talk:Voting Program Activity
  * ACM Body of Knowledge & Topic, Difficulty Level, Completion Time, Environment, License (all in Ad
  220 B (31 words) - 18:10, 8 March 2017
• Talk:FOSS Background (Module)
  * Missing ACM Body of Knowledge and ACM Topics
  92 B (13 words) - 18:42, 8 March 2017
• Talk:Intro to GitHub (Activity)
  Missing assesment, ACM body of knowledge and topics.
  400 B (60 words) - 18:50, 8 March 2017
• Talk:FOSS Field Trip (Activity)
  * Needs ACM body of knowledge categories
  221 B (31 words) - 18:50, 8 March 2017
• Talk:FOSS Field Trip Activity V1
  * Missing ACM Body of Knowledge and Topics * Missing Level of Detail
  184 B (27 words) - 18:55, 8 March 2017
• Propose a New Feature
  ... they will need to learn and follow the coding and communication practices of the project community. All of this will likely depend on the community's guidelines for proposing feature
  4 KB (527 words) - 12:12, 15 October 2018
• Website Project-Activity
  basics of version control, basics of web-development ...l open source project: issue reporting, verification of issues, discussion of issues, claiming and fixing issues, making pull requests, resolving potenti
  8 KB (1,410 words) - 12:12, 15 October 2018
• Category:SE Software Project Management
  ** The role of risk in the lifecycle * Software quality assurance and the role of measurements
  9 members (0 subcategories, 0 files) - 12:21, 15 October 2018
• Category:SP Professional Communication
  Effective professional communication of technical information is rarely an inherited gift, ...encing with Human-Computer Interaction (HCI) and Software Engineering (SE) Knowledge Areas.
  4 members (0 subcategories, 0 files) - 12:38, 15 October 2018
• Category:SE Requirements Engineering
  The purpose of requirements engineering is to develop a common understanding of the needs, priorities, and constraints relevant to a software system. ... of requirements for the software to be developed or inadequate management of those requirements.
  12 members (0 subcategories, 0 files) - 13:38, 15 October 2018