User:Nnapier
(→2.6 Exercise Response) |
m |
||
(3 intermediate revisions by one user not shown) | |||
Line 13: | Line 13: | ||
In addition to teaching, Dr. Napier leads several initiatives on campus to recruit and retain students in Information Technology including [http://hercules.ggc.edu/ggctechcamp/ GGC Tech Camp], [https://hercules.ggc.edu/s3/ Super Saturday Series for Middle School Girls], and Technology Ambassadors Program. | In addition to teaching, Dr. Napier leads several initiatives on campus to recruit and retain students in Information Technology including [http://hercules.ggc.edu/ggctechcamp/ GGC Tech Camp], [https://hercules.ggc.edu/s3/ Super Saturday Series for Middle School Girls], and Technology Ambassadors Program. | ||
+ | |||
+ | === Sahana Project Team === | ||
+ | [[SahanaGroupNotes]] | ||
=== Bug Tracker Exercise === | === Bug Tracker Exercise === | ||
Line 34: | Line 37: | ||
# Gain proficiency in creating comphrehensive unit testing (JUnit, PUnit) | # Gain proficiency in creating comphrehensive unit testing (JUnit, PUnit) | ||
* Types of activities | * Types of activities | ||
− | # Read about the domain -- summarize what is known, compare and contrast existing software packages, what features exist? Have multiple groups and have them each report so that students get a broader understanding | + | # Read about the domain -- summarize what is known, compare and contrast existing software packages, what features exist? Have multiple groups and have them each report so that students get a broader understanding. Explore the business model -- why would IBM be a part of Open Source project? |
# Have them follow Sahana on twitter as well as the Google Group | # Have them follow Sahana on twitter as well as the Google Group | ||
# Ask them what they already know about FOSS. What OSS projects have they used already | # Ask them what they already know about FOSS. What OSS projects have they used already | ||
Line 49: | Line 52: | ||
* Other ideas | * Other ideas | ||
# Have a core set of activities that all students have to do. Then, have optional activities students can choose from under categories | # Have a core set of activities that all students have to do. Then, have optional activities students can choose from under categories | ||
+ | |||
+ | |||
+ | [[Category:POSSE 2013-06]] |
Latest revision as of 10:07, 7 February 2017
Contents |
Nannette Napier
Nannette Napier is a faculty member at Georgia Gwinnett College. She engages in action research that addresses challenges of software development firms such as effectively managing software projects, creating and managing software requirements, and using agile development methodologies. Prior to attending graduate school, she worked professionally as a senior software engineer.
At GGC, Dr. Napier has taught a variety of courses including
- ITEC 1001 Introduction to Computing
- ITEC 2120 Introduction to Programming
- ITEC 2150 Intermediate Programming (beginning Fall 2013)
- ITEC 3860 Software Development I
- ITEC 4260 Software Quality Assurance & Testing (beginning Spring 2014, hopefully)
Dr. Napier's strives to create relevant courses that engage students through active learning and enrichment experiences. These courses intentionally incorporate connections between course material and "the real world".
In addition to teaching, Dr. Napier leads several initiatives on campus to recruit and retain students in Information Technology including GGC Tech Camp, Super Saturday Series for Middle School Girls, and Technology Ambassadors Program.
Sahana Project Team
Bug Tracker Exercise
- Severity column: blo - blocker, cri - critical, maj - major, nor - normal, min - minor, tri - trivial, enh - enhancement
- Priority column: low, normal, high, urgent
- Operating System: all, linux, OpenSolaris, Mac OS, Windows, Solaris
- Product column:
- Status column:
- Resolution column:
- Summary column:
2.6 Exercise Response
- Course to target: ITEC 4260 QA Class
- Learning outcomes for students to achieve:
- Acquire proficiency with basic tools used in open source projects. More specifically, GitHub, WordPress blog, forums and possibly IRC (if this is a big form of communication for the project)
- Understanding the mechanisms for operating in open source projects (submitting code, using bug tracking software)
- Participate as a good citizen within an open source community -- more than just lurking
- Distinguish between Free and open source software and proprietary software development, focusing on tools and software processes
- Understanding a specific domain (emergency prepardness)that the project addresses
- Acquire proficiency in using an automated test script (Selenium Web Driver)
- Gain proficiency in creating comphrehensive unit testing (JUnit, PUnit)
- Types of activities
- Read about the domain -- summarize what is known, compare and contrast existing software packages, what features exist? Have multiple groups and have them each report so that students get a broader understanding. Explore the business model -- why would IBM be a part of Open Source project?
- Have them follow Sahana on twitter as well as the Google Group
- Ask them what they already know about FOSS. What OSS projects have they used already
- Assign students to join the Google Group on Sahana-Eden: Pick 5 or 6 topics for the students. Read and analyze a specific topic. Summarize for the class
- Require students to introduce themselves on the community forum. Read about proper etiquette
- Code inspection/review
- Starter assignment: Have them update the installation documentation
- Make them a user in a specific task: Have them update the user documentation
- Sonal: Usability testing
- Have students create 'how to' videos on getting started
- Interview a FOSS developer -- AFTER the students have had some experience, say towards the end of the class
- Look for design patterns in the code, use that when talking about design patterns in SD I
- Try to generate test cases from the existing requirements documentation. Analyze how complete the requirements are compared to what we say in our templates
- Other ideas
- Have a core set of activities that all students have to do. Then, have optional activities students can choose from under categories