BYZ658 - SOFTWARE TESTING TECHNIQUES
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| SOFTWARE TESTING TECHNIQUES | BYZ658 | Any Semester/Year | 3 | 0 | 3 | 6 |
| Prequisites | BYZ 681. | |||||
| Course language | Turkish | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Discussion Preparing and/or Presenting Reports Problem Solving Project Design/Management | |||||
| Instructor (s) | To be determined by the institute | |||||
| Course objective | To teach the concepts of software testing techniques. | |||||
| Learning outcomes |
| |||||
| Course Content | Introduction to software testing, Software failure teminologies, Software development life cycle, Software testing process, Static testing technique, Dynamic test techinque, Black box testing technique, White box testing technique, Validation testing, Test case preparation, Bug reports, Bug life cycle, Cost of bugs in software. | |||||
| References | ? Ron Patton, Software testing, Sams, 2005. ? William E. Perry, Effective Methods for Software Testing, John Wiley & Sons, 2006. ? Edward Kit, Susannah Finzi, Software testing in the real world: improving the process, Addison-Wesley Pub. Co., 1995. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Introduction to Course |
| Week 2 | Introduction to software testing, Software failure teminologies |
| Week 3 | Software development life cycle |
| Week 4 | Software testing process |
| Week 5 | Static testing technique |
| Week 6 | Dynamic test techinque |
| Week 7 | Black box testing technique |
| Week 8 | Midterm exam |
| Week 9 | White box testing technique |
| Week 10 | Validation testing, Test case preparation |
| Week 11 | Bug reports |
| Week 12 | Bug life cycle |
| Week 13 | Cost of bugs in software |
| Week 14 | Project Presentation |
| Week 15 | Project Presentation |
| Week 16 | Final exam |
Assesment methods
| Course activities | Number | Percentage |
|---|---|---|
| Attendance | 0 | 0 |
| Laboratory | 0 | 0 |
| Application | 0 | 0 |
| Field activities | 0 | 0 |
| Specific practical training | 0 | 0 |
| Assignments | 5 | 10 |
| Presentation | 0 | 0 |
| Project | 1 | 20 |
| Seminar | 0 | 0 |
| Midterms | 1 | 20 |
| Final exam | 1 | 50 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 7 | 50 |
| Percentage of final exam contributing grade succes | 1 | 50 |
| Total | 100 | |
WORKLOAD AND ECTS CALCULATION
| Activities | Number | Duration (hour) | Total Work Load |
|---|---|---|---|
| Course Duration (x14) | 14 | 3 | 42 |
| Laboratory | 0 | 0 | 0 |
| Application | 0 | 0 | 0 |
| Specific practical training | 0 | 0 | 0 |
| Field activities | 0 | 0 | 0 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 10 | 3 | 30 |
| Presentation / Seminar Preparation | 0 | 0 | 0 |
| Project | 1 | 48 | 48 |
| Homework assignment | 5 | 2 | 10 |
| Midterms (Study duration) | 1 | 20 | 20 |
| Final Exam (Study duration) | 1 | 30 | 30 |
| Total Workload | 32 | 106 | 180 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Has comprehensive knowledge in fundamental areas of software engineering. | X | ||||
| 2. Has knowledge in the area of software requirements understanding process planning, output specification, resource planning, risk management and quality planning. | X | ||||
| 3. Understands the interplay between theory and practice and the essential links between them. | X | ||||
| 4. Defines real life problems by identifying functional and non-functional requirements a software has to satisfy. | X | ||||
| 5. Overcomes technical or scientific software engineering problems on their own and is in a position to propose the most suitable solution; has good communication skills to explain the completeness of their solution and clearly state the assumptions that were made. | X | ||||
| 6. Completes a project on a larger scale than an ordinary course project in order to acquire the skills necessary to work efficiently in a team. | X | ||||
| 7. Identifies, evaluates, measures and manages changes in software development by applying software engineering processes. | X | ||||
| 8. Understands the social, legal, ethical and cultural issues involved in the deployment and use of software engineering and conducts all occupational pursuits in an ethical and responsible manner. | X | ||||
| 9. Has good command of technical terms in both Turkish and English, where they have the ability to make succinct presentations (including face-to-face, written or electronic) to a range of audiences about technical/scientific problems and their solutions. | X | ||||
| 10. Identifies and conducts research by applying scientific methods in order to solve scientific problems. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest