Stage 2 Activities/Stage 3 Planning - OpenMRS Team 1

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
(Questions or concerns you have about implementing your activity)
m
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
== Group Participants ==  
 
== Group Participants ==  
Dale, Tom, George, Ron
+
 
 +
* Dale <djskrien@colby.edu>
 +
* Ron <ron.mccleary@avila.edu>
 +
* George <thomasg@uwosh.edu>
 +
* Tom <naps@uwosh.edu>
 +
* Janet <davisj@whitman.edu>
  
 
== Planning an Initial HFOSS Learning Activity ==
 
== Planning an Initial HFOSS Learning Activity ==
Please discuss and record your group's approach for an initial learning activity.  When you have a good draft description of the learning activity using the sections below, you could create a learning activity page for it by copying the template here:
+
Please discuss and record your group's approach for an initial learning activity.  When you have a good draft description of the learning activity using the sections below, you could create a learning activity page for it by copying the [[Learning Activity Format with Directions]].
[http://foss2serve.org/index.php/Stage_2_Activities/Activity_Template Learning Activity Template]
+
  
 
=== Course targeted for the activity ===  
 
=== Course targeted for the activity ===  
  
*Sofware Engineering
+
*Software Engineering
  
 
=== Brief description of the activity ===
 
=== Brief description of the activity ===
  
*Students read coding conventions associated with the project
+
*Students read coding conventions associated with the project -- [https://wiki.openmrs.org/display/docs/Coding+Conventions  for example in OpenMRS]
 
*Students review 1 or more samples of code to see how close sample(s) are to conventions
 
*Students review 1 or more samples of code to see how close sample(s) are to conventions
 +
*Possible follow-up activity could be fixing the code and submitting it
  
 
=== Time you expect the HFOSS activity to take ===
 
=== Time you expect the HFOSS activity to take ===
Line 42: Line 47:
  
 
=== Support you will need to implement your activity ===
 
=== Support you will need to implement your activity ===
 +
 +
*Input from the project community about good sources of the code
  
 
== Planning Stage 3 Activities ==
 
== Planning Stage 3 Activities ==
  
 
=== Meetings ===
 
=== Meetings ===
<Identify meeting times. Find out HFOSS project meeting times.>
+
We are joining the OpenMRS POSSE Alumni Google Group to keep in touch. That will be our primary (for now) method for setting up future meetings.
  
 
===Specific Tasks===
 
===Specific Tasks===
<What will various group members do.>  
+
<What will various group members do.>
 +
 
 +
* Janet will try fleshing out the rubric based on her prior experience with a somewhat similar assignment.
 +
* George will use this assignment in his fall SE class.
 +
* Dale hopes to use this assignment in his fall OODI class.
  
 
=== Resources ===
 
=== Resources ===
Line 57: Line 68:
  
 
Prior related POSSE groups, if any:
 
Prior related POSSE groups, if any:
 
 
 
  
  
 
[[Category:POSSE]]
 
[[Category:POSSE]]

Latest revision as of 16:46, 27 February 2017

Contents

Group Participants

  • Dale <djskrien@colby.edu>
  • Ron <ron.mccleary@avila.edu>
  • George <thomasg@uwosh.edu>
  • Tom <naps@uwosh.edu>
  • Janet <davisj@whitman.edu>

Planning an Initial HFOSS Learning Activity

Please discuss and record your group's approach for an initial learning activity. When you have a good draft description of the learning activity using the sections below, you could create a learning activity page for it by copying the Learning Activity Format with Directions.

Course targeted for the activity

  • Software Engineering

Brief description of the activity

  • Students read coding conventions associated with the project -- for example in OpenMRS
  • Students review 1 or more samples of code to see how close sample(s) are to conventions
  • Possible follow-up activity could be fixing the code and submitting it

Time you expect the HFOSS activity to take

  • One homework assignment

Relationship of this activity to course goals/objectives

  • Learn about coding conventions
  • Get practice reading existing code
  • Experience with code from large code base

What students will submit upon completion of the activity

  • Using a template supplied, students will turn in written analysis of the code sample

Approach for assessing the student work

  • Instructor supplies rubric that could include number of violations and some discussion of the seriousness of the violations

Questions or concerns you have about implementing your activity

  • How much knowledge will students need about the FOSS project (e.g. OpenMRS)
  • How much knowledge will the students need about the language
  • The size of the conventions list
  • How much code will be given
  • How much instructor time will be required to find the the code samples

Support you will need to implement your activity

  • Input from the project community about good sources of the code

Planning Stage 3 Activities

Meetings

We are joining the OpenMRS POSSE Alumni Google Group to keep in touch. That will be our primary (for now) method for setting up future meetings.

Specific Tasks

<What will various group members do.>

  • Janet will try fleshing out the rubric based on her prior experience with a somewhat similar assignment.
  • George will use this assignment in his fall SE class.
  • Dale hopes to use this assignment in his fall OODI class.

Resources

<List any resources that you find>

Other Notes

Prior related POSSE groups, if any:

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