| Course Title | Code | Semester | L+U Hour | Credits | ECTS |
|---|---|---|---|---|---|
| Object Oriented Analysis And Design | BM208 | 4. Semester | 3 + 0 | 3.0 | 4.0 |
| Prerequisites | None |
| Language of Instruction | Turkish |
| Course Level | Undergraduate |
| Course Type | |
| Mode of delivery | Lecture, Practise, presentation |
| Course Coordinator |
Assoc. Prof. Dr. Arafat ŞENTÜRK |
| Instructor(s) |
Arafat ŞENTÜRK |
| Assistants | |
| 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. To ensure 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. |
| Learning Outcomes |
- x - x - x - - - - - - |
| Week | Topics | Learning Methods |
|---|---|---|
| 1. Week | x | |
| 2. Week | x | |
| 3. Week | x | |
| 4. Week | x | |
| 5. Week | x | |
| 6. Week | x | |
| 7. Week | x | |
| 8. Week | x | |
| 8. Week | x | |
| 10. Week | x | |
| 12. Week | x | |
| 13. Week | x | |
| 14. Week | x |
| “UML and The Unified Process, Practical Object-Oriented Analysis and Design”, Second Edition; Jim Arlow & Ila Neustadt; Pearson Education, 2005. |
| “Object-Oriented Analysis and Design: Understanding System Development with UML 2.0”, Mike O'Docherty, John Wiley & Sons, Ltd., 2005. |
| “Head First Object-Oriented Analysis and Design”; Brett D. McLaughlin, Gary Pollice, David West; O’Reilly, 2007. |
| Program Requirements | Contribution Level | DK1 | DK2 | Measurement Method |
|---|---|---|---|---|
| PY1 | 2 | 0 | - | - |
| PY2 | 4 | 0 | - | - |
| PY3 | 2 | 0 | - | - |
| PY4 | 4 | 0 | - | - |
| PY5 | 1 | 0 | - | - |
| PY6 | 1 | 0 | - | - |
| PY7 | 5 | 0 | - | - |
| PY8 | 5 | 0 | - | - |
| PY9 | 3 | 0 | - | - |
| PY10 | 2 | 0 | - | - |
| PY11 | 5 | 0 | - | - |
| PY12 | 5 | 0 | - | - |
| 0 | 1 | 2 | 3 | 4 | 5 | |
|---|---|---|---|---|---|---|
| Course's Level of contribution | None | Very Low | Low | Fair | High | Very High |
| Method of assessment/evaluation | Written exam | Oral Exams | Assignment/Project | Laboratory work | Presentation/Seminar |
| Event | Quantity | Duration (Hour) | Total Workload (Hour) |
|---|---|---|---|
| Course Hours | 14 | 3 | 42 |
| Midterm 1 | 1 | 20 | 20 |
| Homework 1 | 1 | 14 | 14 |
| Final | 1 | 26 | 26 |
| Total Workload | 102 | ||
| ECTS Credit of the Course | 4.0 | ||
