VBM647 - SOFTWARE CONFIGURATION MANAGEMENT
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| SOFTWARE CONFIGURATION MANAGEMENT | VBM647 | 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 Case Study | |||||
| Instructor (s) | To be determined by the institute | |||||
| Course objective | This course presents the principles of software configuration management. | |||||
| Learning outcomes |
| |||||
| Course Content | ? Introduction to configuration management, ? Configuration management with respect to software enginnering and project management, ? Configuration identification and application, ? Configuration verification and audit, ? Configuration management and data management relations, ? Configuration metrics | |||||
| References | ? Jessica Keyes, Software Configuration Management, Auerbach Publications, 2004 ? Stephen P. Berczuk, Brad Appleton, Kyle Brown, Software Configuration Management Patterns: Effective Teamwork, Practical Integration, Addison-Wesley, 2003 | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Introduction |
| Week 2 | Configuration management with respect to software enginnering |
| Week 3 | Configuration management with respect to project management |
| Week 4 | Configuration identification |
| Week 5 | Configuration application |
| Week 6 | Midterm exam I |
| Week 7 | Configuration verification |
| Week 8 | Configuration audit |
| Week 9 | Configuration management and data management relations |
| Week 10 | Configuration management and data management relations (cont?d.) |
| Week 11 | Configuration metrics |
| Week 12 | Configuration metrics (cont?d.) |
| Week 13 | Midterm exam II |
| Week 14 | Case Study |
| Week 15 | Case Study (cont?d.) |
| 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 | 0 | 0 |
| Presentation | 0 | 0 |
| Project | 0 | 0 |
| Seminar | 0 | 0 |
| Midterms | 2 | 60 |
| Final exam | 1 | 40 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 0 | 60 |
| Percentage of final exam contributing grade succes | 0 | 40 |
| 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 | 2 | 28 |
| Presentation / Seminar Preparation | 0 | 0 | 0 |
| Project | 0 | 0 | 0 |
| Homework assignment | 0 | 0 | 0 |
| Midterms (Study duration) | 2 | 33 | 66 |
| Final Exam (Study duration) | 1 | 44 | 44 |
| Total Workload | 31 | 82 | 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