| Course Title | Code | Language | Type | Semester | L+U Hour | Credits | ECTS |
|---|---|---|---|---|---|---|---|
| Object Oriented Analysis And Design | CE208 | English | Compulsory | 4. Semester | 3 + 0 | 3.0 | 4.0 |
| Prerequisite Courses | |
| Course Level | Undergraduate |
| Mode of delivery | face to face |
| Course Coordinator | Dr. Öğr. Üyesi Ekrem BAŞER |
| Instructor(s) | |
| Goals | Informing students about object-oriented approaches, object-oriented tools, methods and techniques. To provide students with the ability to create object-oriented models. Explain how UML is applied to Unified Process analysis and design processes. Explaining how software development can be done with object-oriented approaches using UML. Demonstrating requirements determination and use case modeling studies. Learning how to find classes belonging to the analysis and design stages with the concept of class and object. Explain how the concept of relationship is used by UML. Learning the concepts of inheritance and polymorphism. Explaining how use cases can be implemented. To learn to draw activity and state diagrams. To understand the design process, to grasp the concept and principles of design. To provide an understanding of object-oriented design methods. Learning sub-system, component, interface, and design patterns. Object-oriented software architecture design and understanding of layered architecture. Learning the use of interface definitions in the design process. Examination of file and database designs. Understanding how to document analysis and design work. Ensuring that the student has general knowledge about the analysis and design processes, methods, tools and applications. |
| Course Content | Object Oriented Software Development Lifecycle. Modeling Use-Cases and Software Requirements. Identification of Non-functional Requirements. Definition and Documentation of the Domain Model. System Sequence Diagrams. Transition from Requirements to Design. UML Interaction Diagrams. Determination of Design Objects and Responsibilities. Transition from Design to Code. |
| # | Öğrenme Kazanımı |
| 0 | Students know the basics of the software development lifecycle. |
| 1 | Students know object-oriented analysis and design techniques and apply their methodologies. |
| 2 | Students create requirements analysis documents with UML. |
| 3 | Students express analysis and design models with UML diagrams. |
| 4 | Students gain the ability to model a software project with UML |
| Week | Topics/Applications | Method |
|---|---|---|
| 1. Week | What is UML? | |
| 2. Week | What is the Unified Process? | |
| 3. Week | Requests workflow | |
| 4. Week | Use case modeling | |
| 5. Week | Analysis workflow, classes, and objects | |
| 6. Week | Finding analysis classes | |
| 7. Week | Analysis relationships | |
| 8. Week | Inheritance and polymorphism | |
| 9. Week | Use case realization and interaction schemes | |
| 10. Week | Activity charts, state machines | |
| 11. Week | Design classes | |
| 12. Week | Refinement of resolution relationships | |
| 13. Week | Interfaces and subsystems | |
| 14. Week | design patterns |
| Program Requirements | DK1 | DK2 | DK3 | DK4 | DK5 |
|---|
| Ders Kitabı veya Notu | Ders Kitabı veya Ders Notu bulunmamaktadır. |
|---|---|
| Diğer Kaynaklar |
|
| ECTS credits and course workload | Quantity | Duration (Hour) | Total Workload (Hour) | |
|---|---|---|---|---|
|
Sınavlar |
Midterm 1 | 5 | 16 | 80 |
| Homework 2 | 5 | 10 | 50 | |
| Total Workload | 130 | |||
| *AKTS = (Total Workload) / 25,5 | ECTS Credit of the Course | 4.0 | ||
