Rea - Android Course (Proposal)

(Difference between revisions)
Jump to: navigation, search
Line 34: Line 34:
 
An assortment of smaller activities will contribute to the project's overall goals.  
 
An assortment of smaller activities will contribute to the project's overall goals.  
  
These are in addition to labs in the course that focus on particular advanced Android programming techniques and approaches such as encryption, network management, lifecycle control, etc.
+
These are in addition to labs in the course that focus on particular advanced Android programming techniques and approaches such as encryption, network management, life-cycle control, etc.
  
 
Lab assignments will relate to the overall project needs and can be shared on the Wiki as part of the overall deliverable.
 
Lab assignments will relate to the overall project needs and can be shared on the Wiki as part of the overall deliverable.
Line 40: Line 40:
 
All other activities listed below are planned and will have deliverables associated with them and shared via the Wiki.
 
All other activities listed below are planned and will have deliverables associated with them and shared via the Wiki.
  
===Community Interaction===
+
===Course Assignments===
  
* '''Understand FOSS communities:''' We will take time to explore all the Ushahidi offerings and compare it to other FOSS communities. Each student will write a short essay within the class project Wiki discussing this.
+
Project assignments will account for 40% of the course grade with an additional 10% in exercises designed to help them master FOSS fundamentals.
* '''Understand FOSS development processes:''' We will attempt to mirror FOSS processes using GitHub, collaborative technologies, and agile programming.
+
* '''Participate in FOSS communities:''' Students will at a minimum take part in IRC or other weekly Ushahidi discussions at least twice during the semester and write about it in the class project Wiki or their blog.
+
* '''Master a FOSS development processes:''' Perhaps not completely master, but a reflective paper at the end of the semester on the project discussing what the student has learned.
+
  
===Technology Implementation===
+
====Community Interaction====
 +
 
 +
* '''Understand FOSS communities:''' We will take time to explore all the Ushahidi offerings and compare it to other FOSS communities. Each student will write a short essay within the '''class project Wiki''' discussing how the Ushahidi offering compares to at least two other FOSS projects. Special emphasis on the project's wiki, documentation, and code repository so that students will understand how to develop and maintain usueful FOSS offerings.
 +
 
 +
* '''Understand FOSS development processes:''' We will mirror FOSS processes using GitHub, collaborative technologies (e.g., IRC or Slack), and agile programming. More on this in the '''Technology Implementation''' section.
 +
 
 +
* '''Participate in FOSS communities:''' Students will at a minimum take part in IRC or other weekly Ushahidi discussions at least twice during the semester and write about the experience in their '''blog'''.
 +
 
 +
* '''Master a FOSS development processes:''' Perhaps not completely master, but a '''reflective paper''' at the end of the semester on the project discussing what the student has learned as a result of working with FOSS communities and building an HFOSS project.
 +
 
 +
====Technology Implementation====
  
 
In addition to the focus on developing advanced Android programming techniques, approaches, and designs such as fragment use, communication tools, and encryption, students will need to complete assignments and exercises that allow them to experience the following:
 
In addition to the focus on developing advanced Android programming techniques, approaches, and designs such as fragment use, communication tools, and encryption, students will need to complete assignments and exercises that allow them to experience the following:
  
* '''Basic Git Usage''' with GitHub
+
* '''Basic Git Usage''' with GitHub: Similar to the Git Activity (http://foss2serve.org/index.php/Git_Activity) assignment but focusing more on code management. Students will be permitted to use GitHub desktop (https://desktop.github.com/).
* '''Advanced Version Control''' with GitHub
+
* '''Using Git with Android Studio'''
+
* '''Use Dia for App Architecture and Design''' (This will depend if students can install the software.)
+
* Install, document, and use a '''Wiki on OpenShift'''
+
* Install, document, and use an '''Ushahidi server on OpenShift'''
+
* Program, document, and implement an '''Android App using Ushahidi APIs'''
+
  
===Project Deliverables===
+
* '''Advanced Version Control''' with GitHub: In this assignment each student will create their own repository. Other students will fork this repository, make code changes, and then issue pull requests. The repository owner must then manage merges while maintaining code integrity.
  
* Working Android Application
+
* '''Using Git with Android Studio''': Android Studio allows for a Git plugin for code management. Similar to the '''Advnaced Version Control''' activity students will learn how to manage and maintain Android code within the Android Studio.
* Project Website and Wiki
+
 
* Project Documentation
+
* '''Use Dia for App Architecture and Design''' (This will depend if students can install the software.): Tentative assignment. Students usually must design interfaces as well as software processes via LucidChart (https://www.lucidchart.com/). This semester we will move the same assignment to Dia if possible.
* User Guide
+
 
 +
* Install, document the process, and use '''Wordpress on OpenShift''': Each student will set up their own individual blog for the class on OpenShift. A class directory will be published and shared with POSSE.
 +
 
 +
* Install, document the process, and use a '''Wiki on OpenShift''': The project will require students to install, configure, and maintain a project Wiki that should mirror comprehensive FOSS wikis complete with version information, usage guides, etc. This wiki will be made available to POSSE.
 +
 
 +
* Install, document, and use an '''Ushahidi server on OpenShift''': The project will require an Ushahidi server to maintain data, as well as interface with the mobile application the student team will create. Specific students will be assigned to the server group. These students will follow Ushahidi install documentation and discuss the install process on their blogs. In addition, students must create an install process and perhaps a cartridge for the specific project server installation.
 +
 
 +
* Program, document, and implement an '''Android Ushahidi App''': Although no one specific assignment is part of this deliverable, all previous activities discussed above are an essential component of developing a working deployed HFOSS Android app complete with documentation. This app will have been tested and deployed (at least as a prototype) by the end of the semester.
 +
 
 +
====Project Deliverables====
 +
 
 +
The final project demonstrates the power of FOSS technologies, processes, and approaches to mobile software development. Students will work to provide the robust resources found with the best FOSS offerings.
 +
 
 +
* Working Android Application: The application will be available on the project site and may be available on Google Play.
 +
 
 +
* Project Website and Wiki: The website will provide potential users with an overview of the application. The wiki will provide developer documentation as well as user information.
 +
 
 +
* User Guide: This will occupy a separate section of the wiki hosted on OpenShift.
  
 
==Evaluation==
 
==Evaluation==
Line 76: Line 94:
 
===POSSE Collaboration===
 
===POSSE Collaboration===
  
* Willing to work with POSSE to implement more across the board evaluation measures that will interface with larger FOSS learning questions and community.
+
Instructor will complete the Institutional Context Survey.
 +
 
 +
At the beginning of the project we will conduct the student survey. The following questions will be used:
 +
 
 +
* All HFOSS questions.
 +
* All General questions.
 +
* CS1-CS3, CS7-11
 +
* SE1-SE12
 +
* Specific Ushahidi and Android Questions
 +
 
 +
Post questions will be asked as determined via POSSE collaboration.
  
 
==Schedule==
 
==Schedule==
Line 82: Line 110:
 
===Spring2016===
 
===Spring2016===
  
 +
* Conduct pre- and post-surveys
 
* Develop assignments and materials
 
* Develop assignments and materials
 
* Run the project
 
* Run the project
 
* Post updates to blog
 
* Post updates to blog
* Submit Proposal to AMCIS
+
* Submit Proposal to MWAIS and AMCIS
  
 
===Summer2016===
 
===Summer2016===
Line 92: Line 121:
 
* Post all materials to Wiki
 
* Post all materials to Wiki
 
* Create section in the Teacher's Guide at http://teachingopensource.org
 
* Create section in the Teacher's Guide at http://teachingopensource.org
* Travel to AMCIS 2016 and present findings
+
* Travel to MWAIS 2016 and AMCIS 2016 and present findings
  
 
==Budget==
 
==Budget==
Line 106: Line 135:
 
===Travel (Summer16)===
 
===Travel (Summer16)===
  
$1000: Defray cost of travel to AMCIS 2016 (http://amcis2016.aisnet.org/) to present in the SIGED Track.
+
$1000: Defray cost of travel to MWAIS 2016 (http://mwais2016.sois.uwm.edu/) and AMCIS 2016 (http://amcis2016.aisnet.org/) to present in the SIGED Track.
  
 
==Contact Information==
 
==Contact Information==

Revision as of 13:43, 18 January 2016

Contents

Summary

Run a semester-long project in an upper-level Android development class.

This project will entail the use of many open source technologies to build an Android application (app) that interfaces via APIs with an Ushahidi (https://www.ushahidi.com/) server installed on OpenShift in order to enable a local community organization (to be determined) to track and report occurrences throughout a geographic area. Currently, we are looking at projects involving campus sustainability programs, voter registration initiatives, among other projects. Most likely this will be one large team of 10-15 students each performing various roles and contribution distinct modules to the overall Android Project.

This project will not only expose students to working with a FOSS community but also enable a local organization to experience the power that HFOSS can bring to the community.

Target Venue

CIS4700 Mobile Commerce Development

This is an advanced mobile programming course that focuses on advanced mobile commerce, or m-commerce, programming to include location-based services, mobile payment services and transactions, as well as designing and delivering advanced content and advertising for smartphones, tablets, and other mobile devices. Because m-commerce is constantly evolving, this course will integrate new topics as necessary as reflected in the mobile application development area.

Android App Development with Ushahidi

In addition to Android development and programming labs throughout the semester, a student team develops their own Android application throughout the course of the semester.

Student team leaders must convince others in the class to join their team according to the project being pitched to the class. Student teams then work to design, develop, present, and implement the Android application over the course of the semester.

Past student teams produced various mobile games, K-5 learning tools, bus route tracking, and customer loyalty apps.

However, this semester we will work as one team to create an HFOSS project for the community implementing an Android App via API connections to our own Ushahidi server.

Target Student Audience

This is an advanced programming and development course. Senior information systems and computer science majors take this course.

It is an elective course for majors and a required course for Business Mobile Development minors. CIS4700 requires students pass the pre-requisite course CIS2610: Business Mobile Programming.

Learning Activities

An assortment of smaller activities will contribute to the project's overall goals.

These are in addition to labs in the course that focus on particular advanced Android programming techniques and approaches such as encryption, network management, life-cycle control, etc.

Lab assignments will relate to the overall project needs and can be shared on the Wiki as part of the overall deliverable.

All other activities listed below are planned and will have deliverables associated with them and shared via the Wiki.

Course Assignments

Project assignments will account for 40% of the course grade with an additional 10% in exercises designed to help them master FOSS fundamentals.

Community Interaction

  • Understand FOSS communities: We will take time to explore all the Ushahidi offerings and compare it to other FOSS communities. Each student will write a short essay within the class project Wiki discussing how the Ushahidi offering compares to at least two other FOSS projects. Special emphasis on the project's wiki, documentation, and code repository so that students will understand how to develop and maintain usueful FOSS offerings.
  • Understand FOSS development processes: We will mirror FOSS processes using GitHub, collaborative technologies (e.g., IRC or Slack), and agile programming. More on this in the Technology Implementation section.
  • Participate in FOSS communities: Students will at a minimum take part in IRC or other weekly Ushahidi discussions at least twice during the semester and write about the experience in their blog.
  • Master a FOSS development processes: Perhaps not completely master, but a reflective paper at the end of the semester on the project discussing what the student has learned as a result of working with FOSS communities and building an HFOSS project.

Technology Implementation

In addition to the focus on developing advanced Android programming techniques, approaches, and designs such as fragment use, communication tools, and encryption, students will need to complete assignments and exercises that allow them to experience the following:

  • Advanced Version Control with GitHub: In this assignment each student will create their own repository. Other students will fork this repository, make code changes, and then issue pull requests. The repository owner must then manage merges while maintaining code integrity.
  • Using Git with Android Studio: Android Studio allows for a Git plugin for code management. Similar to the Advnaced Version Control activity students will learn how to manage and maintain Android code within the Android Studio.
  • Use Dia for App Architecture and Design (This will depend if students can install the software.): Tentative assignment. Students usually must design interfaces as well as software processes via LucidChart (https://www.lucidchart.com/). This semester we will move the same assignment to Dia if possible.
  • Install, document the process, and use Wordpress on OpenShift: Each student will set up their own individual blog for the class on OpenShift. A class directory will be published and shared with POSSE.
  • Install, document the process, and use a Wiki on OpenShift: The project will require students to install, configure, and maintain a project Wiki that should mirror comprehensive FOSS wikis complete with version information, usage guides, etc. This wiki will be made available to POSSE.
  • Install, document, and use an Ushahidi server on OpenShift: The project will require an Ushahidi server to maintain data, as well as interface with the mobile application the student team will create. Specific students will be assigned to the server group. These students will follow Ushahidi install documentation and discuss the install process on their blogs. In addition, students must create an install process and perhaps a cartridge for the specific project server installation.
  • Program, document, and implement an Android Ushahidi App: Although no one specific assignment is part of this deliverable, all previous activities discussed above are an essential component of developing a working deployed HFOSS Android app complete with documentation. This app will have been tested and deployed (at least as a prototype) by the end of the semester.

Project Deliverables

The final project demonstrates the power of FOSS technologies, processes, and approaches to mobile software development. Students will work to provide the robust resources found with the best FOSS offerings.

  • Working Android Application: The application will be available on the project site and may be available on Google Play.
  • Project Website and Wiki: The website will provide potential users with an overview of the application. The wiki will provide developer documentation as well as user information.
  • User Guide: This will occupy a separate section of the wiki hosted on OpenShift.

Evaluation

Planned

  • Students are required to fill out a course survey at the beginning and end of the semester to note if learning occurred.
  • Use CATME (http://info.catme.org/) to help students understand how well they perform on the team.
  • Rubrics and associated feedback on all project assignments as well as labs.

POSSE Collaboration

Instructor will complete the Institutional Context Survey.

At the beginning of the project we will conduct the student survey. The following questions will be used:

  • All HFOSS questions.
  • All General questions.
  • CS1-CS3, CS7-11
  • SE1-SE12
  • Specific Ushahidi and Android Questions

Post questions will be asked as determined via POSSE collaboration.

Schedule

Spring2016

  • Conduct pre- and post-surveys
  • Develop assignments and materials
  • Run the project
  • Post updates to blog
  • Submit Proposal to MWAIS and AMCIS

Summer2016

  • Finalize materials
  • Post all materials to Wiki
  • Create section in the Teacher's Guide at http://teachingopensource.org
  • Travel to MWAIS 2016 and AMCIS 2016 and present findings

Budget

Spring16

$1500: Develop Materials (Assignments, Rubrics, Videos, etc.), Run the Course, Post Updates to Blog

Summer16

$1500: Finalize Materials and Post to Wiki and Teacher's Guide

Travel (Summer16)

$1000: Defray cost of travel to MWAIS 2016 (http://mwais2016.sois.uwm.edu/) and AMCIS 2016 (http://amcis2016.aisnet.org/) to present in the SIGED Track.

Contact Information

  • Alan Rea (<rea> at <wmich> dot <edu>)
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox