BÄ°L781 - SOFTWARE QUALITY MANAGEMENT
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| SOFTWARE QUALITY MANAGEMENT | BÄ°L781 | Any Semester/Year | 3 | 0 | 3 | 8 |
| Prequisites | None. | |||||
| Course language | English | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Discussion Team/Group Work Preparing and/or Presenting Reports | |||||
| Instructor (s) | Department Responsible (bbm-bologna@cs.hacettepe.edu.tr) | |||||
| Course objective | To introduce quality management concepts, software verification and validation concepts and selected methods, and requirements of a Quality Management System as specific to software engineering. | |||||
| Learning outcomes |
| |||||
| Course Content | Quality Management Basics; total quality and quality management, the scope of software quality management, software quality assurance, verification, and validation, quality management within software development life-cycle. Software Quality Assurance; reviews and types, product and process audit, software quality assurance process and its outputs. Verification and Validation; the concepts of verification and validation, verification methods, validation methods, V Model and test levels (unit, integration, functional, acceptance). Quality Management System (QMS); the principles of QMS, process management, ISO 9001:2008 standard and its application to software engineering, QMS infrastructure and features. | |||||
| References | Software Engineering, Ian Somerville, 8th Ed., Addison-Wesley, 2006. (ISBN-10: 0321313798, ISBN-13: 978-0321313799) Software Quality Assurance: Principles And Practice, Nina S. Godbole, Alpha Science International Ltd., 2004. (ISBN-10: 1842651765, ISBN-13: 978-1842651766) Independent Verification and Validation, Robert O. Lewis, John Wiley & Sons, 2001 (ISBN-10: 0471570117, ISBN-13: 978-0471570110) ?ISO 9001: Quality Management System - Requirements?, International Standards Organization, 2008. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Quality Fundamentals |
| Week 2 | Software Quality Fundamentals |
| Week 3 | Software Quality Management Processes |
| Week 4 | Software Verification, Validation, and Testing |
| Week 5 | Software Quality Attributes |
| Week 6 | Software Quality Management Techniques |
| Week 7 | Midterm |
| Week 8 | Software Process Management |
| Week 9 | Software Process Measurement |
| Week 10 | Process Reference Models (CMMI and ISO 12207) |
| Week 11 | Quality Management System Requirements and ISO 9001 |
| Week 12 | Student presentations |
| Week 13 | Student presentations |
| Week 14 | Student presentations |
| 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 | 1 | 15 |
| Specific practical training | 0 | 0 |
| Assignments | 5 | 10 |
| Presentation | 1 | 5 |
| Project | 0 | 0 |
| Seminar | 0 | 0 |
| Midterms | 1 | 20 |
| 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 | 1 | 42 | 42 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 14 | 3 | 42 |
| Presentation / Seminar Preparation | 1 | 16 | 16 |
| Project | 0 | 0 | 0 |
| Homework assignment | 5 | 8 | 40 |
| Midterms (Study duration) | 1 | 16 | 16 |
| Final Exam (Study duration) | 1 | 16 | 16 |
| Total Workload | 37 | 104 | 214 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Graduates should have a mastery of computer science as described by the core of the Body of Knowledge. | X | ||||
| 2. Graduates need understanding of a number of recurring themes, such as abstraction, complexity, and evolutionary change, and a set of general principles, such as sharing a common resource, security, and concurrency. | X | ||||
| 3. Graduates of a computer science program need to understand how theory and practice influence each other. | X | ||||
| 4. Graduates need to think at multiple levels of detail and abstraction. | X | ||||
| 5. Students will be able to think critically, creatively and identify problems in their research. | X | ||||
| 6. Graduates should have been involved in at least one substantial project. | X | ||||
| 7. Graduates should realize that the computing field advances at a rapid pace. | X | ||||
| 8. Graduates should conduct research in an ethical and responsible manner. | X | ||||
| 9. Graduates should have good command of technical terms in both Turkish and English. | X | ||||
| 10. Graduates should understand the full range of opportunities available in computing. | X | ||||
| 11. Graduates should understand that computing interacts with many different domains. | X | ||||
| 12. Graduates should develop the knowledge acquired at master level and apply scientific methods in order to solve scientific problems. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest