| 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 |
| SEN2022 | Software Engineering Analysis and Design | Spring | 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 : | Assoc. Prof. AYLA GÜLCÜ |
| Recommended Optional Program Components: | None |
| Course Objectives: | After taking this course, the student will have the ability of analyzing and designing a software development process such as defining scope, describing problems, gathering system requirements, constructing data, object and process models and identifying alternative solutions to apply feasibility analysis for the decision-making purposes. In this course, you will engage in various methodologies, processes, techniques, and tools used to handle the phases of the Software Development Life Cycle (SDLC). Teaching Methods and Techniques Used in the Course: Lecture, reading, implementation, individual study, problem solving |
|
The students who have succeeded in this course; At the end of the course, the students will be able to: 1. Describe systems analysis and design concepts for information systems; 2. Describe the essential phases of systems development; 3. Describe project management tools and a number of systems analysis approaches for solving information system problems; 4. Define scope of information system problems; 5. Identify the problems, opportunities and directives that trigger the project; 6. Define functional and nonfunctional system requirements, apply fact-finding technique; 7. Define actors and use cases, construct context and use case model diagrams; 8. Construct data models and UML diagrams; 9. Define the basic concepts and constructs of a process model and construct context, data flow, event and system diagrams; 10. Identify alternative system solutions, define six types of feasibility, prepare cost-benefit analyses and system proposal reports. |
| The course content is composed of the basic concepts of systems analysis and design, the components of information systems, methods for developing information systems, project management, systems analysis approaches, scope definition phase, problem analysis phase , requirements analysis phase, use-cases, data modeling and analysis, process modeling, feasibility analysis and the system proposal. |
| Week | Subject | Related Preparation |
| 1) | Introduction to Systems Analysis and Design | |
| 2) | Systems Analysis and Design for Information Systems | |
| 3) | Project Management, Scope Definition | |
| 4) | Problem Analysis, Scheduling Tools | |
| 5) | Problem Discovery, Requirements Discovery, Requirements Analysis | |
| 6) | Use Cases and Use Case Diagrams | |
| 7) | Use Case Descriptors | |
| 8) | Structural Modeling | |
| 9) | Midterm Exam | |
| 10) | Behavioral Modeling | |
| 11) | Validating and Evolving Analysis Models | |
| 12) | Physical Architecture Layer Design | |
| 13) | Construction: Programming, Documenting and Testing | |
| 14) | Post implementation activities |
| Course Notes / Textbooks: | Textbook: Systems Analysis and Design: An Object-Oriented Approach with UML, 6th Edition Alan Dennis, Barbara Wixom, David Tegarden, Wiley, ISBN: 978-1-119-56121-7 October 2021 (5th Edition can also be used) Supplementary Resource: Systems Analysis & Design for the Global Enterprise 7ed, Lonnie D. Bentley and Jeffrey L. Whitten, McGraw Hill, ISBN-13 978-0-07-110766-2, 2007 |
| References: | Yok |
| Semester Requirements | Number of Activities | Level of Contribution |
| Quizzes | 5 | % 20 |
| Homework Assignments | 3 | % 15 |
| Midterms | 1 | % 25 |
| Final | 1 | % 40 |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 60 | |
| PERCENTAGE OF FINAL WORK | % 40 | |
| Total | % 100 | |
| 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. | 5 |
| 2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | 5 |
| 3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | 2 |
| 4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | 2 |
| 5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | 2 |
| 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. | 2 |
| 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. | 4 |
| 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. | 5 |
| 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. | 2 |
| 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. | 2 |
| 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. |