Web apps, design patterns in web apps, development tools and version control systems, Spring framework, dependency injection, MVC, Junit, hibernate ORM, spring+hibernate integration, Middleware ve HTTP protocol, HTTP Protocol, Spring controllers, spring filters, REST APIs, HTML, CSS, Javascript, and jquery, ajax. The teaching methods of the course include lectures, group work, technology-assisted learning, project preparation, and practice.
|
| Week |
Subject |
Related Preparation |
| 1) |
Introduction + background: historical perspective, what is a web app?, intro to design patterns in web apps, development tools and version control systems
|
|
| 2) |
Java recap and introduction to the Spring Framework: spring components used in web applications, dependency injection, MVC, Junit unit testing
|
|
| 3) |
Database Interactions and the hibernate ORM: Relational databases, ORM concept, integration of spring+hibernate
|
|
| 4) |
Middleware and the HTTP protocol: Application servers, HTTP Protocol, HTTP Requests, HTTP Responses, Sessions and cookies, Spring controllers, spring filters, REST APIs and content types
|
|
| 5) |
Presentation Layer and User interfaces: HTML, CSS, Javascript and jquery, Spring views and template engines, ajax
|
|
| 6) |
MidTerm
|
|
| 7) |
applied project (blog engine) iteration 1: General requirements of the application, user interface design, stories for registration and login, discussion about the design of the features, source code management and deployment/development environment discussions.
|
|
| 8) |
applied project (blog engine) iteration 2 / Demo and retrospective of iteration 1, stories for composing a blog post, displaying a blog post
|
|
| 9) |
applied project (blog engine) iteration 3: Demo of iteration 2 and retro. Stories for updating a blog post and deleting a blog post.
|
|
| 10) |
applied project (blog engine) iteration 4: Demo of iteration 3. Stories for adding, removing tags to a post
|
|
| 11) |
applied project (blog engine) iteration 5: Demo of iteration 4. Stories for posting, updating, deleting comments for a post.
|
|
| 12) |
applied project (blog engine) iteration 6: Demo of iteration 5. Stories for adding analytics for the blog engine.
|
|
| 13) |
Final project presentations
|
|
| 14) |
Final project presentations
|
|
| |
Program Outcomes |
Level of Contribution |
| 1) |
Be able to specify functional and non-functional attributes of software projects, processes and products. |
|
| 2) |
Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. |
|
| 3) |
Be able to develop a complex software system with in terms of code development, verification, testing and debugging. |
|
| 4) |
Be able to verify software by testing its program behavior through expected results for a complex engineering problem. |
|
| 5) |
Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
| 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. |
|
BAHÇEŞEHİR UNIVERSITY BİLGİ PAKETİ / DERS KATALOĞU
