This syllabus and the course schedule are subject to change.

 

ITFN 3314 Testing and Quality Assurance – Summer 2008

 

CRN 53014

 

ELMS (MSDNAA) is located at https://msdn06.e-academy.com/clayton_it/

 

http://cims.clayton.edu/itfn3314

 

Junfeng Qu, Ph.D.

E-mail: jqu[at]clayton[dot]edu

Phone: 678 466 4406

Office: UC339

Office hours: Tuesday and Wednesday 11:00am – 6:00pm, email, “Open door policy” and by appointment.

 

Course Description    (3-0-3)

 

Testing and Quality Assurance

 

A high-level class in testing and quality assurance emphasizing the planned development of software and the nature of test development and implementation. Topics include: test strategies, test planning, functionality testing, stability testing and debugging techniques.

 

Prerequisites

 

ITFN 2123; ITFN 1301/2/3; ITFN 2012; ITFN 2601; English and Math (see the DUCK for more info)

 

 

Outcomes

Students are expected to refine their mastery of project management (1, 4, 8), programming and algorithms to a proficient level as they apply them to real-world projects (5, 6).  Students will attain a maturing level of skills with regard to test terminology, strategy, planning (2, 3), and debugging (5, 6).  Students will demonstrate the ability to integrate their existing skills to complete problems that require problem solving and critical thinking (7).  In addition to working independently on assigned tasks, students will integrate their components as a team member and develop communication (9) and leadership skills.  Students will also develop communication skills among their teams (9).

 

Objectives

Students coming out of this class will have understanding of:

  1. the basics of applied project management
  2. status reporting
  3. project planning
  4. requirements elicitation
  5. test plan generation (including white-box and black-box testing, regression testing, and integration testing)
  6. test case and use case generation
  7. modern software development processes (including waterfall, spiral, and RAD models)
  8. progress tracking
  9. and presentation skills.

 

Meeting Times

 

Lecture

            Monday - Thursday 1:30pm - 3:50 (T116)

 

Given the project-based nature of this course, we will meet less often later in the semester.  Note the schedule as to when attendance is required.  When you’re not in lecture, you are to meet with your team to do project work.  Failure to meet with your team will result in poor performance in this course and a low grade.

 

Each week, you will be required to meet with your team and update all members on the progress and status of your responsibilities.  The time and location of these “outside of lecture” meetings will be determined by the team but will most likely occur during the “course” time when you aren’t in lecture.

 

Required Textbooks

 

Dr. Jon Preston has assembled a book from SafariU that is available in the bookstore.  The title is "Building Better Systems Using Modern Methods".  You cannot order this book online or elsewhere as it is an assembled text specific to this semester's course.  We will read this entire 150 page book, so you are free to read ahead.

 

Additionally, you will have various readings pertaining to Software Engineering and Testing and Quality Control as assigned during the semester.  Be sure to listen in class and watch the course Web site for more information.

 

The optional textbook for the course is On Time, Within Budget: Software Project Management Practices and Techniques by Bennatan (Wiley-QED, 2000).

 

Assessment

 

It is up to you to keep current on all readings and assignments (including in-class announcements).

If you fall behind, you will most assuredly fail this course!

 

Because this is a project-based course, there will be no midterm or final exam.  You are thus expected to demonstrate mastery of the concepts in this course by applying them in your project work.

 

You are expected to be working about 30 hours a week outside of class.  Some weeks will be higher, some weeks will be lower… but amortized, you should expect to work approximately 100 hours in this class.  If you don’t put in these hours, it will show and you will receive a poor grade.  This is not a “coast by” kind of class.

 

It is up to you to make your accomplishments known to the IA and the instructor.  If it seems like you’ve just done an average job on your project, you’ll receive a C (average).  If you stand out and show excellent work, you’re more likely to get an A (excellent).  If you are counting on passing this course (or getting a high grade), then you must work diligently and perform well.  Your grade is determined on performance, not effort.

 

Grading will be based upon the following scale:

 

           

Letter Grade

Average

A

>= 90%

B

80% - 90%

C

70% - 80%

D

60% - 70%

F

< 60%

 

Assignment                                         

Portion of Grade

 

Team

Requirements

15%

Demos  (7.5% each)

15%

Design Document and development plan

20%

Test Plan

10%

 

Individual

Participation (contribution, meetings & accomplishments)
This part is determined based upon your role in the project

35%

Team meetings and contributions during the meeting

5%

 

 

 

PORTFOLIO

 

Since this course has you build solutions that demonstrate your knowledge of core-IT skills, I advise you to keep a copy of everything you submit to be later placed into your portfolio.  This portfolio is a requirement for the ITFN2001 and ITFN4003 course, and if you keep a copy of your submitted solutions, you will be more easily able to fill this portfolio showing your work and IT skills.

 

 

Midterm Grade - given the schedule and when midterm falls, the requirements document and some status reports will be graded; thus approximately 30% of your overall grade will be determined by midterm.

 

Notice that 40% of your grade is individual effort and 60% of your grade is team effort.

 

Please be advised that no credit will be given for late assignments.  If you have a problem that arises during the course of the semester, please contact me as soon as possible.

 

Writing Guidelines

 

I expect that your deliverables are professional.  Grammar and spelling are important, and clarity is critical.  Please follow the CCSU writing guidelines published at  http://a-s.clayton.edu/langlit/guidelines/handbook.html.

 

 

Words of Wisdom (TAKE THIS PART SERIOUSLY!)

 

I expect your active participation in class.  Class attendance is expected because it’s much easier to learn if you’re coming to class and asking questions in lecture about things that confuse you.  Remember – if you knew all of this, you’d be teaching and I’d be hiking in the mountains! J

 

Start assignments early.  This way, you can ask questions and clarify things that are confusing.  Assignments are intentionally “open” so that you can come up with creative solutions, but this also means it’s often easy to misread what I’m looking for in the correct solution.  Better to ask and learn than to get a low grade!

 

Also notice that the only way to do well in this course is to work well with your team.  If you have problems (someone’s not doing his part, etc.), please come talk with me immediately or the entire team will “sink” and it’ll be too late to get back on track.

 

Your grade in this course is determined completely on performance, not on effort. 

 

 

Academic Misconduct

 

If a student is found obtaining or granting inappropriate help in this course on any assignment (test, quiz, exam, homework, etc.) he will receive an F in the course.  The offense will go on permanent record with the university.  If this is not the student’s first academic misconduct offense at CSU, he will be recommended for suspension from the university for two full terms.  This is in full accord with CSU’s policy, and we encourage you to read and review the university’s policy in your student handbook.

 

Instructor Assessment:

 

In this course you will have the opportunity to evaluate the instructor.  This will be done electronically through the DUCK website.

 

ITP Choice Information

 

Beginning Fall Semester 2001, all students at CSU are required to state that they have on-demand access to a notebook computer that meets the recommended hardware/software specifications that have been established by Clayton State faculty. Academic penalties may be incurred for not meeting this requirement.  See http://itpchoice.clayton.edu/ for more information.

 

Students must abide by policies in the University Catalog, Student Handbook, and if applicable, program handbook.  Academic misconduct will not be tolerated. 

Students should read and understand the Basic Student Responsibilities policy posted at

http://adminservices.clayton.edu/registrar/BasicUndergraduateStudentResponsibilities.doc.  These responsibilities should be considered part of this class syllabus and should be adhered to.

Students must activate their CSU email account and are expected to check their email on a regular basis

 

Religious Observance

Religiously observant students wishing to be absent on holidays that require missing class and/or exam should notify the instructor at least two weeks in advance and discuss acceptable ways of making up any work missed because of the absence.

 

Attendance Policy

You are strongly encouraged to attend class, but I do not require or reward/penalize for missing a class meeting.  Of course, you are expected to be in attendance if/when you are presenting an assignment or taking a test.

 

Disability Services

 

Students with disabilities who require reasonable accommodations need to register with Disability Services (DS) in order to obtain their accommodations. You can contact them at 678-466-5445 or disabilityservices@clayton.edu. If you are already registered with DS and are seeking accommodations for this course, please make an appointment with me to discuss your specific accommodation needs for this course and give me your accommodations letter.