CS 40800, Fall 2015
ANNOUNCEMENTS
(Last changed Sunday, August 23)
-
Here are the CS 40800 Software Testing teams so far. The first person is the team leader, whose purdue id is also listed.
-
(1) Logan Gore (gorel), Kyle Rodd, Sang Rhee, Geonhee Lee, Stephen Hong, Tyler Springer ( Project Coordinator: Dohyeong Kim)
-
(2)Joshua Selbo (jselbo), Don Phan, Anant Goel, Joshua Selbo, Jon Egeland, Levi Heilman,
Sean McCullough ( Project Coordinator: Dohyeong Kim)
-
(3) Mason Everett (me), Rashmi Iyer, Eric Theller, Deepsaran Singh, Bruce Nguyen, Gage Black ( Project Coordinator: Dohyeong Kim)
-
(4) Kean Jye Tan (tan126), Jiaping Qi, Aaron Ho, Kaijun He, Lingyu Kong, Qi Zhang ( Project Coordinator: Dohyeong Kim)
-
(5) Kunal Agrawa (kagrawa), John Masterson, Sharoon Srivastava, Ankush Jain, Olumide Awofeso,
Garrick James Buckley (gbuckle)( Project Coordinator: Sayali Salvi)
-
(6) Greg Yogan (gyogan), Christian Nitz, Alex Hamm, Kyle Fischer, Stephen Lien Harrell (sharrel),
Charles Cho (ccho93 AT gmail)( Project Coordinator: Sayali Salvi)
-
(7) Cmd+Q: Yao Xiao (xiao67), Joseph Bruckne, Nathan Chang, Zilun Mai, Saranyu Phusit, Sargun Vohra ( Project Coordinator: Sayali Salvi)
-
(8) Sahil Singh (singh226), Cody Phrampus, Somi choi, Bekmurat Spayev, Tejaswi Namuduru, Mark William (willi864) ( Project Coordinator: Alex Birkey)
-
(9) Aishwarya Ajay (aajay), David Olaves-Mullican, Simon Smith, Brian Shrawder, Nikhil Mehta, Vijay Srinivas Balasubramanian ( Project Coordinator: Alex Birkey)
-
(10) Ivan Zhang (izhang),
Andrew Shildmyer,
Levi Starrett,
Spencer Brown,
Corey Pitzo,
Austin Ottinger ( Project Coordinator: Alex Birkey)
-
(11) Craig Wilhite (cwilhit), Adam Worthington, Grant Jochums, Dylan brashear, Chris Doak (doak),
Robbie Mantzoros (smantzor) ( Project Coordinator: Yuying Wang)
-
(12) Caleb Corey (ccorey), Hunter Martin (marti584), Calvin Sauer (csauer), Elliott Mantock (jmantock),
Christopher Hsieh (hsieh11), Samuel Presnal (spresnal) ( Project Coordinator: Yuying Wang)
-
(13) Vishal Gill (vgill), Adrian Buchmann (adrian.buchman AT gmail.com), Graham Otte (graham.otte AT gmail.com), Nate Dunning (ndunning), Jordan Mounts (mounts), Jintao Zeng (zeng40) ( Project Coordinator: Yuying Wang)
Welcome to CS 40800 Software Testing
CS 40800 Website <https://www.cs.purdue.edu/homes/xyzhang/cs408fall15/>
Course Work
Project |
70% |
Midterm Exam |
25% |
Daily Quizzes |
5% |
Project Grade Composed of
Product Backlog |
5% |
Test Plan |
5% |
Sprint 1 Design Inspection, Code Inspection, Unit Testing |
7.5% |
Sprint 1 Incremental Testing, Regression Testing |
7.5% |
Sprint 2 Design Inspection, Code Inspection, Unit Testing |
7.5% |
Sprint 2 Incremental Testing, Regression Testing |
7.5% |
Seed Project with at least 25 Defects |
10% |
Project Demo |
10% |
Second Test Plan |
10% |
Higher-Order Testing |
10% |
Black Box Testing |
10% |
Final Project Presentation |
10% |
Total |
100% |
Team Member Contributions
What you earn on the 100 team points above will be subject to a
multiplier based on peer evaluation of your team members. Read more
about Team Member Contributions
including how we will compute them.
Textbook
The Art of Software Testing, Third Edition, Glen Myers, Wiley, 2012.
You do not have to buy this book.
It is available online (PDF files) from the Purdue University Libraries from their "Ebrary":
Go to the Purdue Libraries Website at
http://www.lib.purdue.edu.
In the search field type in "Glenford Myers Art of Software Testing".
Click on the link that says "Click here to view 2 versions".
In the first entry click on the link "Find Online".
Click on the link "Ebrary".
The book in PDF form appears....
Teaming Experience Reflection Paper
At the end of the semester each of you is required to submit a Teaming
Experience Reflection Paper. There will be a dropbox on Blackboard to
do this. The dropbox will be open from Tuesday, Dec 8th until Friday,
Dec 18th. Your paper must be submitted as a PDF file. These will be
graded by Prof. Zhang and not by your Project Coordinator. You
will receive comments from Prof. Zhang and an indication if the
paper answers the nine questions well enough. There is no grade for
this, but anyone who does not submit an acceptable Teaming Experience
Reflection Paper will receive an Incomplete in the course until this
is done.
To remind yourself about the things you learned about Teaming
principles (specifically the KOLB learning style inventory), you can
review Lynne Horngren's
Teaming and Collaboration Requirement
slides.
The Teaming Experience Reflection Paper should be fairly short. Just
answer the 9 questions posed on slide 4 of Lynne's slides:
- Using the KOLB learning style inventory discuss your contributions
to your team. Include discussion of the strengths and areas of
weakness in regards to your preferred learning style. Discuss the
roles you most like to fulfill while teaming and those that you would
like to defer to other team members. Further discuss your insights
into the learning styles of your team members, focusing on perceived
strengths and weaknesses.
- What trait or traits regarding learning styles did each team member
bring to your team that influenced its functioning either positively
or negatively? Give examples of their impact.
- Who did what on your team? How were roles determined? Did
everyone contribute equally? How was this decided?
- Describe an instance where a team member(s) created an obstacle
that had to be overcome in order to allow your team to perform
effectively.
- What stumbling blocks relating to team cohesiveness did you
encounter in working on your project? How did you overcome them? How
do you believe learning styles impacted your team's ability to work
collaboratively together and towards team goals?
- Did you gain skills in conflict resolution while working on the
team? Were you able to use these skills effectively to enhance your
team's performance? Illustrate with an example.
- Did your team struggle with personal agendas? Were you able to
work toward a common purpose? How?
- In your teaming experience, did you gain any insights into how
cultural differences have an impact on teamwork? If so, please
describe.
- How might your teaming experience affect your future --- with
regard to academic, social, career, and/or personal choices?
A 1-2 page paper with short answers to the above will be fine. This
is not meant to be a major writing assignment.
Because of the team project and this paper, CS 40800 satisfies the
College of Science Teaming Experience Requirement.
© 2015 by Purdue University Department of Computer Science.
All rights reserved.