|
YZM1000 | Software Requirements Engineering | 2+0+0 | ECTS:4 | Year / Semester | Spring Semester | Level of Course | First Cycle | Status | Compulsory | Department | DEPARTMENT of SOFTWARE ENGINEERING | Prerequisites and co-requisites | None | Mode of Delivery | | Contact Hours | 14 weeks - 2 hours of lectures per week | Lecturer | Arş. Gör. Hakan AYDIN | Co-Lecturer | | Language of instruction | Turkish | Professional practise ( internship ) | None | | The aim of the course: | The purpose of this course, the most up to date software requirements engineering processes, methods and techniques to manufacture. In addition, requirements for software development projects that are vital for the identification of high-quality software also provides the necessary information and skills. |
Learning Outcomes | CTPO | TOA | Upon successful completion of the course, the students will be able to : | | | LO - 1 : | Mathematics, science, and solving the problems of software engineering, the ability to apply knowledge in the areas of computing. | 4 | 1, | LO - 2 : | Analyzing and modeling domain-specific issues, identifying and describing ability of software requirements for solutions. | 4 | 1, | LO - 3 : | A software system to meet the specified requirements, the system part, process or program design, development and evaluation skills. | 4 | 1, | LO - 4 : | Knows and use UML diagrams | 4 | 1, | LO - 5 : | Manage the requirements | 4 | 1, | LO - 6 : | learn how be written of the specification document | 4 | 1, | CTPO : Contribution to programme outcomes, TOA :Type of assessment (1: written exam, 2: Oral exam, 3: Homework assignment, 4: Laboratory exercise/exam, 5: Seminar / presentation, 6: Term paper), LO : Learning Outcome | |
Principles of software requirements. Requirements from the perspective of the customer. Requirements engineering applications. Requirements analyst role. Product development vision and scope of the project. Understanding the needs of customers and users. Requirements to be documented. Prototyping risk reduction method. Need for setting priorities. Validation requirements. Yazılımgereksinimleri management. Engineering application requirements. Formal reasoning and specification of requirements engineering. |
|
Course Syllabus | Week | Subject | Related Notes / Files | Week 1 | the problem of requirements | | Week 2 | Introduction to management requirements | | Week 3 | Requirements and the software life cycle | | Week 4 | Problem analysis | | Week 5 | Business Model | | Week 6 | Extraction of requirements, system functions and interviews | | Week 7 | Use the definition of the state requirement | | Week 8 | Organization of information requirements | | Week 9 | Midterm Exam | | Week 10 | Determining the scope of the project | | Week 11 | Use additional specification refinement and development status | | Week 12 | Requires the use of technical methods to determine the | | Week 13 | Transition to the application conditions of use | | Week 14 | Transition states use test cases | | Week 15 | Monitoring requirements and change management | | Week 16 | Final Exam | | |
1 | Leffingwell, D. Widrig, D., Managing Software Requirements: A Use Case Approach, Addison Wesley, 2nd edn, 2003. | | |
1 | Chenuturi M, Requirements Engineering and Management for Software Development Projects, 2013, Springer | | 2 | Hull, E et al., Requirements Engineering, 2011, Springer | | |
Method of Assessment | Type of assessment | Week No | Date | Duration (hours) | Weight (%) | Mid-term exam | 9 | | 2 | 50 | End-of-term exam | 16 | | 2 | 50 | |
Student Work Load and its Distribution | Type of work | Duration (hours pw) | No of weeks / Number of activity | Hours in total per term | Yüz yüze eğitim | 2 | 14 | 28 | Sınıf dışı çalışma | 2 | 14 | 28 | Laboratuar çalışması | 0 | 0 | 0 | Arasınav için hazırlık | 1 | 12 | 12 | Arasınav | 1 | 1 | 1 | Uygulama | 0 | 0 | 0 | Klinik Uygulama | 0 | 0 | 0 | Ödev | 0 | 0 | 0 | Proje | 0 | 0 | 0 | Kısa sınav | 0 | 0 | 0 | Dönem sonu sınavı için hazırlık | 5 | 6 | 30 | Dönem sonu sınavı | 1 | 1 | 1 | Diğer 1 | 0 | 0 | 0 | Diğer 2 | 0 | 0 | 0 | Total work load | | | 100 |
|