Stage 2 Activities/2.3 OpenMRS

(Difference between revisions)
Jump to: navigation, search
(Please answer each of the following questions as it relates to your activity.)
Line 1: Line 1:
 
= Planning for HFOSS Participation =
 
= Planning for HFOSS Participation =
 
Workshop Participants: James W, Jeff W. Lori P, James M, Darci B, Patti O, Karl W, Camm
 
Workshop Participants: James W, Jeff W. Lori P, James M, Darci B, Patti O, Karl W, Camm
 
  
 
== Please answer each of the following questions as it relates to your activity. ==
 
== Please answer each of the following questions as it relates to your activity. ==
 
See [https://titanpad.com/OpenMRSgroup https://titanpad.com/OpenMRSgroup]
 
See [https://titanpad.com/OpenMRSgroup https://titanpad.com/OpenMRSgroup]
 
 
===Brainstorming===
 
===Brainstorming===
 
*upper div and grad CS security courses. code review, penetration tests like [https://www.owasp.org/index.php/FLOSSHack_Returns|FLOSSHack]
 
*upper div and grad CS security courses. code review, penetration tests like [https://www.owasp.org/index.php/FLOSSHack_Returns|FLOSSHack]
Line 16: Line 14:
 
**Software Process artifacts
 
**Software Process artifacts
 
**Software Testing artifacts
 
**Software Testing artifacts
 
 
===Questions===
 
===Questions===
 
# Identify the course(s) the activity would be appropriate for.
 
# Identify the course(s) the activity would be appropriate for.
Line 26: Line 23:
 
# How does this activity relate to course goals/objectives?
 
# How does this activity relate to course goals/objectives?
 
##Describe difference between data structure and implementation thereof.
 
##Describe difference between data structure and implementation thereof.
 +
##Explain the application of a data structure in a specific large complex software system
 +
##Evaluate tradeoffs in selection of data structures.
 +
##Analyze the time complexity of algorithm that uses the data structure.
 
# What will students submit upon completion of the activity?
 
# What will students submit upon completion of the activity?
##
+
##A link to a place where the code is found in the codebase <ref name=githublink>
 +
You can link  directly to a line of the code in GitHub in a particular commit. For example,  taking marvinyan's link to CohortSearchHistory.java (which links to the  file itself, in a particular commit - in this case commit  7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the  end of the URL to link directly to (and highlight) lines 130 through  137, i.e.:
 +
https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137
 +
The  fact that it is in a particular commit (version) means that you don't  have to worry about the code being changed in the future, and the  example code you are interested in going away or being changed.</ref>
 +
##A written description of the data structure used within the code and how the code works.
 
# How will you assess the submission?  
 
# How will you assess the submission?  
##carefully
+
##very carefully
 +
##We need to create a rubric, what are the Learning Objectives?
 
# List any question or concerns you have about implementing your activity.
 
# List any question or concerns you have about implementing your activity.
 
##
 
##
 
# What type of support will you need to implement your activity?
 
# What type of support will you need to implement your activity?
 
##Darci
 
##Darci
 
 
==Misc Notes==
 
==Misc Notes==
 
[http://www.google-melange.com/gsoc/projects/list/google/gsoc2014|Google Summer of Code 2014 project list], search under organization for OpenMRS and 13 projects should appear
 
[http://www.google-melange.com/gsoc/projects/list/google/gsoc2014|Google Summer of Code 2014 project list], search under organization for OpenMRS and 13 projects should appear
 
 
You can link directly to a line of the code in a particular version. For example, taking marvinyan's link to CohortSearchHistory.java (which links to the file itself, in a particular commit - in this case commit 7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the end of the URL to link directly to (and highlight) lines 130 through 137, i.e.:
 
You can link directly to a line of the code in a particular version. For example, taking marvinyan's link to CohortSearchHistory.java (which links to the file itself, in a particular commit - in this case commit 7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the end of the URL to link directly to (and highlight) lines 130 through 137, i.e.:
 
https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137
 
https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137
 
The fact that it is in a particular commit (version) means that you don't have to worry about the code being changed in the future, and the example code you are interested in going away or being changed.
 
The fact that it is in a particular commit (version) means that you don't have to worry about the code being changed in the future, and the example code you are interested in going away or being changed.
 
+
{{reflist}}
==Misc Notes==
+
[http://www.google-melange.com/gsoc/projects/list/google/gsoc2014|Google Summer of Code 2014 project list], search under organization for OpenMRS and 13 projects should appear
+
 
+
You can link directly to a line of the code in a particular version. For example, taking marvinyan's link to CohortSearchHistory.java (which links to the file itself, in a particular commit - in this case commit 7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the end of the URL to link directly to (and highlight) lines 130 through 137, i.e.:
+
https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137
+
The fact that it is in a particluar commit (version) means that you don't have to worry about the code being changed in the future, and the example code you are interested in going away or being changed.
+

Revision as of 17:35, 29 May 2014

Contents

Planning for HFOSS Participation

Workshop Participants: James W, Jeff W. Lori P, James M, Darci B, Patti O, Karl W, Camm

Please answer each of the following questions as it relates to your activity.

See https://titanpad.com/OpenMRSgroup

Brainstorming

  • upper div and grad CS security courses. code review, penetration tests like [1]
  • introduce forest of computing to first semester fresh. in seminar course
  • help with CS2 data structures course
  • CS0/1 - mobile app class
  • sabbatical HFOSS work
  • OpenMRS for multiple courses:
    • Capstone project
    • Software Process artifacts
    • Software Testing artifacts

Questions

  1. Identify the course(s) the activity would be appropriate for.
    1. CS2 Data Structures Project based on the work of Darci's student Structure Example
  2. Briefly describe the activity.
    1. Find use of a specified data structure in the OpenMRS code base using a tool like [2], explain the task that the data structure is used to accomplish, and explain why the data structure is a good or poor choice for accomplishing this task.
  3. How much time do you expect the HFOSS activity to take (# classes, # homework assignments, # lab activities, etc.)? Will the activity be completed in class or out of class?
    1. One homework assignment or lab activity.
  4. How does this activity relate to course goals/objectives?
    1. Describe difference between data structure and implementation thereof.
    2. Explain the application of a data structure in a specific large complex software system
    3. Evaluate tradeoffs in selection of data structures.
    4. Analyze the time complexity of algorithm that uses the data structure.
  5. What will students submit upon completion of the activity?
    1. A link to a place where the code is found in the codebase <ref name=githublink>

You can link directly to a line of the code in GitHub in a particular commit. For example, taking marvinyan's link to CohortSearchHistory.java (which links to the file itself, in a particular commit - in this case commit 7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the end of the URL to link directly to (and highlight) lines 130 through 137, i.e.: https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137 The fact that it is in a particular commit (version) means that you don't have to worry about the code being changed in the future, and the example code you are interested in going away or being changed.</ref>

    1. A written description of the data structure used within the code and how the code works.
  1. How will you assess the submission?
    1. very carefully
    2. We need to create a rubric, what are the Learning Objectives?
  2. List any question or concerns you have about implementing your activity.
  3. What type of support will you need to implement your activity?
    1. Darci

Misc Notes

Summer of Code 2014 project list, search under organization for OpenMRS and 13 projects should appear You can link directly to a line of the code in a particular version. For example, taking marvinyan's link to CohortSearchHistory.java (which links to the file itself, in a particular commit - in this case commit 7b6e6e2f776aafc3ad397ab6430c77ed25a20857), you can add #L130-137 to the end of the URL to link directly to (and highlight) lines 130 through 137, i.e.: https://github.com/openmrs/openmrs-core/blob/7b6e6e2f776aafc3ad397ab6430c77ed25a20857/api/src/main/java/org/openmrs/cohort/CohortSearchHistory.java#L130-137 The fact that it is in a particular commit (version) means that you don't have to worry about the code being changed in the future, and the example code you are interested in going away or being changed. Template:Reflist

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