| SOFTWARE ENGINEERING | |||||
| Bachelor | TR-NQF-HE: Level 6 | QF-EHEA: First Cycle | EQF-LLL: Level 6 | ||
| Course Code | Course Name | Semester | Theoretical | Practical | Credit | ECTS |
| SEN3003 | Software Project Management | Fall | 3 | 0 | 3 | 7 |
| Language of instruction: | English |
| Type of course: | Must Course |
| Course Level: | Bachelor’s Degree (First Cycle) |
| Mode of Delivery: | Face to face |
| Course Coordinator : | Dr. Öğr. Üyesi YÜCEL BATU SALMAN |
| Course Lecturer(s): |
Dr. Öğr. Üyesi YÜCEL BATU SALMAN Dr. Öğr. Üyesi PINAR BÖLÜK |
| Recommended Optional Program Components: | None |
| Course Objectives: | Defining the software project lifecycle and defining the usual stages of a software project management. Implementing a variety of cost benefit evaluation techniques for choosing among competing project proposals and evaluating the risk. The course covers project planning, program management, project evaluation, software effort estimation, activity planning, risk management, monitoring and controlling, managing contracts, managing people and organizing teams, and software quality. |
|
The students who have succeeded in this course; 1. Describe the contents of a typical business plan 2. Construct project planning in an organized step-by-step manner. 3. Select an appropriate process model 4. Describe the software effort estimation 5. Produce an activity plan for a project 6. Identify the factors putting a project at risk 7. Identifying the resources required for a project 8. Manage the progress of projects 9. Select new staff into a project. 10. Select the best communication genres to support the coordination needs of a project. |
| The course content is composed of the basics of software project management, project evaluation and programme management, project planning, selection of appropriate project approach, software effort estimation, activity planning, risk management, resource allocation, monitoring and control, managing contracts, managing people in software environment, working in teams, software quality. |
| Week | Subject | Related Preparation |
| 1) | Introduction to Software Project Management | |
| 2) | Project Evaluation and Programme Management | |
| 3) | An Overview of Project Planning | |
| 4) | Selection of Appropriate Project Approach | |
| 5) | Software Effort Estimation | |
| 6) | Activity Planning | |
| 7) | Activity Planning | |
| 8) | Risk Management | |
| 9) | Resource Allocation | |
| 10) | Monitoring and Control | |
| 11) | Managing Contracts | |
| 12) | Managing People in Software Environment | |
| 13) | Working in Teams | |
| 14) | Software Quality |
| Course Notes / Textbooks: | Bob Hughes, Mike Cotterell, Software Project Management, McGraw Hill, 5th Edition. Harold Kerzner, Project Management: A Systems Approach to Planning, Scheduling, and Controlling, John Wiley & Sons. |
| References: | Yok |
| Semester Requirements | Number of Activities | Level of Contribution |
| Project | 1 | % 25 |
| Midterms | 1 | % 25 |
| Final | 1 | % 50 |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 25 | |
| PERCENTAGE OF FINAL WORK | % 75 | |
| Total | % 100 | |
| Activities | Number of Activities | Duration (Hours) | Workload |
| Course Hours | 14 | 3 | 42 |
| Study Hours Out of Class | 5 | 15 | 75 |
| Project | 1 | 25 | 25 |
| Midterms | 1 | 14 | 14 |
| Final | 1 | 20 | 20 |
| Total Workload | 176 | ||
| No Effect | 1 Lowest | 2 Low | 3 Average | 4 High | 5 Highest |
| Program Outcomes | Level of Contribution | |
| 1) | Be able to specify functional and non-functional attributes of software projects, processes and products. | 4 |
| 2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | 4 |
| 3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | 4 |
| 4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | 3 |
| 5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | 3 |
| 6) | Be able to monitor and control changes in the complex software system, to integrate the software with other systems, and to plan and manage new releases systematically. | 3 |
| 7) | Be able to identify, evaluate, measure, manage and apply complex software system life cycle processes in software development by working within and interdisciplinary teams. | 4 |
| 8) | Be able to use various tools and methods to collect software requirements, design, develop, test and maintain software under realistic constraints and conditions in complex engineering problems. | 3 |
| 9) | Be able to define basic quality metrics, apply software life cycle processes, measure software quality, identify quality model characteristics, apply standards and be able to use them to analyze, design, develop, verify and test complex software system. | 4 |
| 10) | Be able to gain technical information about other disciplines such as sustainable development that have common boundaries with software engineering such as mathematics, science, computer engineering, industrial engineering, systems engineering, economics, management and be able to create innovative ideas in entrepreneurship activities. | 3 |
| 11) | Be able to grasp software engineering culture and concept of ethics and have the basic information of applying them in the software engineering and learn and successfully apply necessary technical skills through professional life. | 3 |
| 12) | Be able to write active reports using foreign languages and Turkish, understand written reports, prepare design and production reports, make effective presentations, give clear and understandable instructions. | 4 |
| 13) | Be able to have knowledge about the effects of engineering applications on health, environment and security in universal and societal dimensions and the problems of engineering in the era and the legal consequences of engineering solutions. |