VBM648 - SOFTWARE VERIFICATION, VALIDATION, and TEST MANAGE
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| SOFTWARE VERIFICATION, VALIDATION, and TEST MANAGE | VBM648 | Any Semester/Year | 3 | 0 | 3 | 6 |
| Prequisites | None | |||||
| Course language | Turkish | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Discussion Preparing and/or Presenting Reports | |||||
| Instructor (s) | Ayça Tarhan | |||||
| Course objective | To introduce the basic concepts of software quality assurance and create an awareness on the systematic ways of developing quality software. | |||||
| Learning outcomes |
| |||||
| Course Content | Basic concepts and approaches of assuring software quality within the software development life-cycle. Basic terms and concepts of software quality assurance. Software verification, validation, and testing. The concepts of error, fault, and failure. Software verification and validation methods and standards. Software reviews and inspections. Overview of metrics used to measure software quality. The levels and methods of software testing. Functional and structural testing. Integration and system testing. Object-oriented testing. | |||||
| References | ? Somerville I., Software Engineering, 9th Ed., Addison-Wesley, 2011. ? Godbole N.S., Software Quality Assurance: Principles and Practice, Alpha Science International Ltd., 2004. ? Lewis R.O., Independent Verification and Validation, John Wiley & Sons, 2001. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | The Quality Concept |
| Week 2 | Software Development Models and Development Life Cycle |
| Week 3 | The Concept and Scope of Software Quality Assurance |
| Week 4 | Software Defect and Types |
| Week 5 | The Concepts of Software Verification and Validation (V&V) |
| Week 6 | Software V&V Processes and Standards |
| Week 7 | Midterm |
| Week 8 | Software Quality Models and Metrics |
| Week 9 | Software Testing Concept and Levels |
| Week 10 | Software Testing Processes and Standards |
| Week 11 | Midterm |
| Week 12 | Software Structural Testing and Techniques |
| Week 13 | Software Functional Testing and Techniques |
| Week 14 | Software Integration Testing and System Testing |
| Week 15 | Preparation to Final Exam |
| 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 | 0 | 0 |
| Seminar | 0 | 0 |
| Midterms | 2 | 40 |
| Final exam | 1 | 50 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 0 | 50 |
| Percentage of final exam contributing grade succes | 0 | 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) | 14 | 3 | 42 |
| Presentation / Seminar Preparation | 0 | 0 | 0 |
| Project | 0 | 0 | 0 |
| Homework assignment | 5 | 8 | 40 |
| Midterms (Study duration) | 2 | 16 | 32 |
| Final Exam (Study duration) | 1 | 16 | 16 |
| Total Workload | 36 | 46 | 172 |
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