BYZ653 - PERSONAL SOFTWARE PROCESS
Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
---|---|---|---|---|---|---|
PERSONAL SOFTWARE PROCESS | BYZ653 | Any Semester/Year | 3 | 0 | 3 | 6 |
Prequisites | None | |||||
Course language | Turkish | |||||
Course type | Must | |||||
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 teach the Personal Software Process (PSP) maintained by the Software Engineering Institute (www.sei.cmu.edu) and its usage in personal performance management. | |||||
Learning outcomes |
| |||||
Course Content | Basic principles of the personal software development by using Personal Software Process. PSP0, PSP1 and PSP2 processes; six process versions, and the concepts underlying them. All PSP materials are pre-defined and provided by the official website of the Software Engineering Institute. | |||||
References | ? Watts S. Humphrey, Self-Improvement Process for Software Engineers, Addison-Wesley Professional, 2005. ? Software Engineering Institute?s official web site: http://www.sei.cmu.edu/tsp/psp.html |
Course outline weekly
Weeks | Topics |
---|---|
Week 1 | Personal Software Process: Overview (PSP0) |
Week 2 | Software Metrics |
Week 3 | Process Measurement (PSP0.1) |
Week 4 | Size Estimating I |
Week 5 | Size Estimating I (PSP1) |
Week 6 | Size Estimating II |
Week 7 | Size Estimating II (PSP1.1) |
Week 8 | Using PSP Data |
Week 9 | Midterm Exam |
Week 10 | Software Quality |
Week 11 | Software Quality (PSP 2) |
Week 12 | Software Design - I |
Week 13 | Software Design ? I (PSP 2.1) |
Week 14 | Review of the concepts covered during the semester |
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 | 15 |
Presentation | 0 | 0 |
Project | 0 | 0 |
Seminar | 0 | 0 |
Midterms | 2 | 45 |
Final exam | 1 | 40 |
Total | 100 | |
Percentage of semester activities contributing grade succes | 7 | 60 |
Percentage of final exam contributing grade succes | 1 | 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 | 3 | 42 |
Presentation / Seminar Preparation | 0 | 0 | 0 |
Project | 0 | 0 | 0 |
Homework assignment | 5 | 7 | 35 |
Midterms (Study duration) | 2 | 15 | 30 |
Final Exam (Study duration) | 1 | 25 | 25 |
Total Workload | 36 | 53 | 174 |
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