The following course information is taken from the official course description.
Catalog course description
This course provides an introduction to team-based software development and quality assurance processes, integrating activities such as team formation, planning, requirements analysis, design, implementation and testing. Course concepts are reinforced by application of software engineering tools to estimation, planning, tracking, change control, quality assurance, and continuous integration. (prereq: SE-2800, SE-2832)
On successful completion of this course, the student will:
- Be able to work as a developer on a team software project to achieve project milestones
- Be able to generate software process artifacts that are necessary in software quality assurance
- Be able to apply software tools needed in the lifecycle of a team software project
- Be able to identify the key objectives and deliverables of the phases defined by an agile development process
- Be able to contribute to the success of a team software project while fulfilling one or more assigned roles
Textbooks and reference materials
(In the course schedule, the all-caps abbreviation is used to refer to each text.)
- Essential Scrum: A Practical Guide to the Most Popular Agile Process, Kenneth S. Rubin, Pearson, 2013 (should have from SE-2800, also available in Kindle format)
- Agile Testing: A Practical Guide for Testers and Agile Teams,
Lisa Crispin & Janet Gregory, Addison-Wesley, 2009 (also available in Kindle format)
This book is a little repetitive and some topics are scattered across chapters, so you may need to search or use the index to find information relevant to a specific topic. Some parts of this book are intended as an introduction to agile and Scrum development for testers who are not familiar with these processes; in many cases, the SCRUM book provides better coverage of these topics.
- Continuous Integration: Improving Software Quality and Reducing Risk, Paul Duvall, Steve Matyas, & Andrew Glover, Addison-Wesley, 2007 (also available in Kindle format)
- Atlassian documentation
- Bitbucket documentation
- Git documentation
- Karl Wiegers article, Improving Quality Through Software Inspections
My general course policies apply to this course.
- Quizzes and class exercises: 30%
- Homework assignments: 30%
- Final report and presentation: 40%
Note that this algorithm indicates how a grade will be determined for students who have successfully demonstrated mastery of the course outcomes. An acceptable level of success in meeting all course outcomes is a prerequisite for a passing grade in the course.