ECTS - Software Requirements Engineering
Software Requirements Engineering (SE221) Course Detail
| Course Name | Course Code | Season | Lecture Hours | Application Hours | Lab Hours | Credit | ECTS |
|---|---|---|---|---|---|---|---|
| Software Requirements Engineering | SE221 | 3. Semester | 3 | 0 | 0 | 3 | 6 |
| Pre-requisite Course(s) |
|---|
| N/A |
| Course Language | English |
|---|---|
| Course Type | Compulsory Departmental Courses |
| Course Level | Bachelor’s Degree (First Cycle) |
| Mode of Delivery | Face To Face |
| Learning and Teaching Strategies | Lecture. |
| Course Lecturer(s) |
|
| Course Objectives | The objective of this course is to cover the state-of-the-art processes, methods, and techniques in software requirements engineering. It also provides comprehensive knowledge and skills needed to develop high quality software requirements specification which is vital in successful software development projects. |
| Course Learning Outcomes |
The students who succeeded in this course;
|
| Course Content | Basics of software requirement, requirements from the customer's perspective, applications in requirements engineering, the role of requirements analyst, forming product vision and project scope, understanding customer and user requirements, documenting requirements, risk reduction through prototyping, setting requirement priorities, validating |
Weekly Subjects and Releated Preparation Studies
| Week | Subjects | Preparation |
|---|---|---|
| 1 | Software Process and SDLC | Ch.1 |
| 2 | Software Requirements and Types | Ch.2 |
| 3 | Requirements Engineering Processes | Ch.2 |
| 4 | Problem analysis and Requirements Inception | Ch. 2 |
| 5 | Requirements Elicitation | Ch. 2 |
| 6 | Requirements Analysis and Specification | Ch. 4 |
| 7 | Use Case Models | Ch. 3, Ch. 4 |
| 8 | Requirements Negotiation and Prioritization | Ch. 2 |
| 9 | User Interface Design | Ch. 7 |
| 10 | Data Modelling | Ch. 8 |
| 11 | Requirements Verification and Validation | Ch. 2 |
| 12 | Requirements Management, Tracing requirements and managing change | Ch. 2, Ch. 9 |
| 13 | Lab. | |
| 14 | Lab. | |
| 15 | Final Examination Period | Review of topics |
| 16 | Final Examination Period | Review of topics |
Sources
| Course Book | 1. Leffingwell, D. & Widrig, D., Managing Software Requirements: A Use Case Approach, Addison Wesley, 2nd ed., 2003. |
|---|---|
| Other Sources | 2. Maciaszek, Leszek. Requirements Analysis and System Design. Pearson Education, 3rd ed., 2007 |
| 3. van Lamsweerde, A., Requirements Engineering: From System Goals to UML Models to Software Specifications, Wiley, 2009 | |
| 4. Pilone, D., Pitman, N., UML 2.0 in a Nutshell, O'Reilly Media, Inc, 2005 | |
| 5. Young, R. R., The Requirements Engineering Handbook, Artech House, 2004 | |
| 6. Hull, E., Jackson, K. & Dick, J., Requirements Engineering, Springer, 3rd Ed., 2017 | |
| 7. Sommerville, I., Software Engineering, Addison-Wesley, 10th. Ed., 2015 | |
| 8. R. Pressman, R. D. Maxim, Software Enginee4ing, 8th. Ed., McGraw-Hill, 2014 |
Evaluation System
| Requirements | Number | Percentage of Grade |
|---|---|---|
| Attendance/Participation | - | - |
| Laboratory | - | - |
| Application | 2 | 15 |
| Field Work | - | - |
| Special Course Internship | - | - |
| Quizzes/Studio Critics | - | - |
| Homework Assignments | - | - |
| Presentation | - | - |
| Project | 1 | 20 |
| Report | - | - |
| Seminar | - | - |
| Midterms Exams/Midterms Jury | 1 | 30 |
| Final Exam/Final Jury | 1 | 35 |
| Toplam | 5 | 100 |
| Percentage of Semester Work | 65 |
|---|---|
| Percentage of Final Work | 35 |
| Total | 100 |
Course Category
| Core Courses | X |
|---|---|
| Major Area Courses | |
| Supportive Courses | |
| Media and Managment Skills Courses | |
| Transferable Skill Courses |
The Relation Between Course Learning Competencies and Program Qualifications
| # | Program Qualifications / Competencies | Level of Contribution | ||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 1 | Gains adequate knowledge in mathematics, science, and subjects specific to the software engineering discipline; acquires the ability to apply theoretical and practical knowledge of these areas to complex engineering problems. | |||||
| 2 | Gains the ability to identify, define, formulate, and solve complex engineering problems; selects and applies proper analysis and modeling techniques for this purpose. | X | ||||
| 3 | Develops the ability to design a complex system, process, device, or product under realistic constraints and conditions to meet specific requirements; applies modern design methods for this purpose. | |||||
| 4 | Demonstrates the ability to select, and utilize modern techniques and tools essential for the analysis and determination of complex problems in software engineering applications; uses information technologies effectively. | X | ||||
| 5 | Develops the ability to design experiments, gather data, analyze, and interpret results for the investigation of complex engineering problems or research topics specific to the software engineering discipline. | X | ||||
| 6 | Demonstrates the ability to work effectively both individually and in disciplinary and interdisciplinary teams in fields related to software engineering. | X | ||||
| 7 | Demonstrates the ability to communicate effectively in Turkish, both orally and in writing; to write effective reports and understand written reports, to prepare design and production reports, to deliver effective presentations, and to give and receive clear and understandable instructions. | |||||
| 8 | Gains knowledge of at least one foreign language; acquires the ability to write effective reports and understand written reports, prepare design and production reports, deliver effective presentations, and give and receive clear and understandable instructions. | |||||
| 9 | Acquires an awareness of the necessity of lifelong learning; the ability to access information, follow developments in science and technology, and continuously improve oneself. | |||||
| 10 | Acts in accordance with ethical principles and possesses knowledge of professional and ethical responsibilities. | |||||
| 11 | Knows the standards used in software engineering practices. | |||||
| 12 | Knows about business practices such as project management, risk management and change management. | |||||
| 13 | Gains awareness about entrepreneurship and innovation. | |||||
| 14 | Gains knowledge on sustainable development. | |||||
| 15 | Has knowledge about the universal and societal impacts of software engineering practices on health, environment, and safety, as well as the contemporary issues reflected in the field of engineering. | |||||
| 16 | Acquires awareness of the legal consequences of engineering solutions. | |||||
| 17 | Applies knowledge and skills in identifying user needs, developing user-focused solutions and improving user experience. | |||||
| 18 | Gains the ability to apply engineering approaches in the development of software systems by carrying out analysis, design, implementation, verification, validation, and maintenance processes. | X | ||||
ECTS/Workload Table
| Activities | Number | Duration (Hours) | Total Workload |
|---|---|---|---|
| Course Hours (Including Exam Week: 16 x Total Hours) | 16 | 3 | 48 |
| Laboratory | |||
| Application | 2 | 2 | 4 |
| Special Course Internship | |||
| Field Work | |||
| Study Hours Out of Class | 16 | 3 | 48 |
| Presentation/Seminar Prepration | |||
| Project | 1 | 15 | 15 |
| Report | |||
| Homework Assignments | |||
| Quizzes/Studio Critics | |||
| Prepration of Midterm Exams/Midterm Jury | 1 | 20 | 20 |
| Prepration of Final Exams/Final Jury | 1 | 25 | 25 |
| Total Workload | 160 | ||