Description
Objectives and Learning outcomes:
1. Learn the basics of the software engineering (SE) process life cycle.
2. Learn what the object-oriented (OO) approach to software development is, through OO principles and design patterns.
3. Learn UML (Unified Modeling Language) that is part of most CASE (Computer Aided Software Engineering) tools and the benefits of visual modeling / diagramming.
4. Practice the application of principles of object-oriented software development through the course group project.
5. Develop teamwork and communication skills through the course group project.
Objectives and Learning outcomes
1. Learn the basics of the software engineering (SE) process life cycle.
2. Learn what the object-oriented (OO) approach to software development is, through OO principles and design patterns.
3. Learn UML (Unified Modeling Language) that is part of most CASE (Computer Aided Software Engineering) tools and the benefits of visual modeling / diagramming.
4. Practice the application of principles of object-oriented software development through the course group project.
5. Develop teamwork and communication skills through the course group project.
Weekly Lectures (subject to change)
1. Introduction to SE (Ch 1)
2. Modeling w/ UML (Ch 2)
3. Project Organization and Communication (Ch 3)
4. Requirements Elicitation (Ch 4)
5. Analysis (Ch 5)
6. System Design (Ch 6 & 7)
7. Object Design (Ch 8 & 9)
8. Mapping Models to Code (Ch 10)
9. Testing (Ch 11)
10. Rational Management (Ch 12)
11. Configuration Management (Ch 13)
12. Project Management (Ch 14)
13. Project Life Cycle (Ch 15)
General Information
Sec2: Wed 15:20-17:10 (L111) and Thu 10:20-11:10 (L111)
Announcements
Due to the exam, there will be no classes tomorrow (Apr 17) and Thursday (Apr 18th).
Good luck to all in the exam(s).
-Erdoüan
GitHub "to do" for all projects (must do):
1) Use your team repo's Project area to manage the project (Tasks, To do, In progress, Done)
2) Use Issues area to communicate with the team and the professor. Add my github account (edogdu) as collaborator to your team. So that I can comment on issues and Wiki reports.
You will be greaded on GitHub usage (Wiki, Code, Project, Issues) individually (for each team member) as well as a team. So, each team member should try to be active in GitHub to grab the points :-)
-Erdogan
You want to earn money for the summer with a great experience? Apply now:
https://summerofcode.withgoogle.com
Hi all,
We are starting the term projects now. You need to read the requirements first:
https://github.com/edogdu/software_engineering_course/wiki/Projects
Then form a team of 4 students this week and submit your initial project ideas here by replying to this post (one message from each group). In your post, write the following:
Team Name: (some cool name! ex: HackersFromCankaya)
Project Title: (short title, explaining or giving hint to your project idea, such as Class Attendance App)
Team Members:
- Name and Email
- Name and Email
- Name and Email
- Name and Email
Project Idea: (4-5 sentences explaining what the software app will do)
This is due by Tuesday noon next week (March 5th) (so that I have time to reply all with a message ok or not ok, revise/redo).
Hope you will all do some cool projects this semester.
Good luck all.
Erdogan
| Name | Office Hours | |
|---|---|---|
Erdoğan Doğdu | When? Where? |