Stage 2 Activities/2.3 OpenMRS

From Foss2Serve
Revision as of 17:05, 14 November 2014 by Bkoster (Talk | contribs)
Jump to: navigation, search

Contents

Planning for HFOSS Participation

Workshop Participants: Chris, Shamsi, Barrett, Kiran, Steve, Ruby, Darci

May 2014 POSSE notes

Planning Stage 3 Activities

Meetings

<Identify meeting times. Find out HFOSS project meeting times.>

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

  1. Identify the course(s) the activity would be appropriate for.

Introductory Software Engineering Course

  1. Briefly describe the activity.
  2. 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?
  3. How does this activity relate to course goals/objectives?
  4. What will students submit upon completion of the activity?
  5. How will you assess the submission?
  6. List any question or concerns you have about implementing your activity.
  7. What type of support will you need to implement your activity?

Specific Tasks

<What will group members do.>

Resources

OpenMRS code review guide: https://wiki.openmrs.org/display/docs/Code+Review

Notes

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

  1. Identify the course(s) the activity would be appropriate for.

Introductory Software Engineering Course We are focusing on the Android app for OpenMRS (OpenMRS Client)

  1. Briefly describe the activity.

Expose student to the OpenMRS Android client and have them reverse engineer the design of the module.

  1. 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?

3 class meetings to start. (75 minute classes) plus a homework assignment (and it that produces a good artifact, the design, then students have to interact with the community to get it accepted). Followup in-class activity to create a single high-quality design document that incorporates all of their designs and can be contributed back.

  1. How does this activity relate to course goals/objectives?

Creating a design is a course objective. They learn to evaluate a design based on standards for design.

  1. What will students submit upon completion of the activity?

This will include the architecture, UML of the structure (class diagrams). Also analysis of design-related concepts: coupling, cohesion. Perhaps identifying design patterns.

  1. How will you assess the submission?

Completeness Quality Correct notation Use of UML tools

  1. List any question or concerns you have about implementing your activity.

Prerequisite knowledge (Android). there are a variety of code-to-UML tools available; how do we know students won't use them?

  1. What type of support will you need to implement your activity?

Some android devices. And we will probably tap into The Community.

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