Version Control (Activity)

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(Overview)
 
(One intermediate revision by one user not shown)
Line 17: Line 17:
 
* Use at least one modern VCS to find, update, and create versioned files.
 
* Use at least one modern VCS to find, update, and create versioned files.
 
|process skills=
 
|process skills=
[[:Category:Information Processing|Information Processing]],
+
[[:Category:Information Processing|Information Processing]], [[:Category:Critical Thinking|Critical Thinking]], [[:Category:Communication|Communication]], [[:Category:Teamwork|Teamwork]]
[[:Category:Critical Thinking|Critical Thinking]],  
+
[[:Category:Communication|Communication]],  
+
[[:Category:Teamwork|Teamwork]]
+
 
}}
 
}}
  
Line 48: Line 45:
 
{{Learning Activity Info
 
{{Learning Activity Info
 
|acm unit=
 
|acm unit=
* [[SE Software Project Management]]
+
* [[:Category:SE Software Project Management|SE Software Project Management]]
 
|acm topic=
 
|acm topic=
 
|difficulty=
 
|difficulty=
Line 73: Line 70:
 
[[Category:Communication]]
 
[[Category:Communication]]
 
[[Category:Teamwork]]
 
[[Category:Teamwork]]
[[Category:Ready To Use]]
+
[[Category:SE Software Project Management]]
 +
[[Category:Ready to Use]]

Latest revision as of 12:35, 15 October 2018


Overview

Title

Version Control (Activity)

Overview

This POGIL activity will introduce some of the challenges of sharing & managing source code, and some useful approaches & procedures. Understanding concepts makes it easier to understand the features and differences of specific tools later in the activity.

Prerequisites

None

Learning
Objectives
After successfully completing this activity, the learner should be able to:
  • Describe the importance of & issues in sharing & managing source code.
  • Describe the advantages & disadvantages of a version control system (VCS), and the key operations.
  • Use at least one modern VCS to find, update, and create versioned files.
Process Skills
Practiced

Information Processing, Critical Thinking, Communication, Teamwork


Background, Directions, Deliverables

See details in the Student version of the POGIL activity.

Notes for Instructors

See details in the Teacher version of the POGIL activity.

Assessment

  • How will the activity be graded?
  • How will learning will be measured? Ideally, there should be a way to measure each of the objectives described above.
  • How will feedback to the student be determined?

This is a classroom POGIL activity, so all teams should complete it in class with correct answers. Thus, the activity is typically not graded, but there might be related quiz or exam questions later.

Suggestions for Open Source Community

N/A

Additional Information

ACM BoK
Area & Unit(s)
ACM BoK
Topic(s)
Difficulty

easy

Estimated Time
to Complete

1 hour

Environment /
Materials

paper activity (1-2 per team or 1 per student) or Google Doc activity (1 per team)

Author(s)

Clif Kussmaul

Source

http://cspogil.org/Software+Engineering (for sample version)

License

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

Creativecommons-by-nc-sa-40.png



Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox