Demo schedule for the projects is given below.

You need to be prepared for the following items:

• Scope of your project
• Requirements and functional model
• Object model and Dynamic model
• System Design (Top Level Architecture)
• Design Patterns applied
• Implementation - Demo
• Lessons Learned

Please come with your demo environment (Laptop, executable application, source code, development environment, etc.). All group members must be present during demonstration.

The deadline of project final report is 7th of December.

You are expected to upload your reports to your Github projects, and send the link to your TA, keeping your instructor in the cc.

Your mail should reach before 7th of December, 23:59.

Late submission policy: Late submissions will not be accepted.

In the final report of your project, you will be appending the object design section to your second report. Object Design section will be Section 5. Also, you are required to update the Conclusion section, which will be Section 6 in this report.

The outline of Section 5 and 6 is as follows:

5. Object Design
    5.1 Pattern applications
    5.2 Class Interfaces
    5.3 Specifying Contracts
6. Conclusions and Lessons Learned

In Section 5.1, you are expected to apply 3 suitable design patterns to your design. You need to check the suitability, apply the pattern to your design and provide sufficient explanation.

In Section 5.2, you are expected to describe the classes in your design and their public interfaces (visibility and type signatures).

In Section 5.3, you are expected to define contracts. You are required to provide contracts for at least 5 classes, and provide at least 30 contracts in total. Each contract should be described with sufficient explanation.

Section 6 should present overall summary, conclusions, along with lessons learned, and other parts related with conclusion.

As with other reports, the layout of the report has some importance: Section headers, Caption of Figures, Captions of Tables, Proper References and citing, proper page numbering, consistent formatting, and other relevant formatting shall be present in a good looking report.

The deadline of project design report is November 20.

You are expected to send soft copies of your report till 20th of November, 23:59. You need to upload your reports to your GitHub projects and send the link of your report to your TA, and instructor.

Late submission policy: Late submissions will not be accepted.

The outline of Section 4 is as follows:

4. Design
4.1 Design Goals
4.2 Sub-System Decomposition
4.3 Architectural Patterns
4.4 Hardware/Software Mapping
4.5 Addressing Key Concerns
    4.5.1 Persistent Data Management
    4.5.2 Access Control and Security
    4.5.3 Global Software Control
    4.5.4 Boundary Conditions
    4.5.5 Another important concern for your case (Rename title) - Optional
                    

The outline of Analysis Report is as follows:

1. Introduction
2. Requirement Analysis
    2.1. Overview
    2.2. Functional Requirements
    2.3. Non-Functional Requirements
    2.4. Constraints
    2.5. Scenarios
    2.6. Use Case Models
    2.7. User Interface
3. Analysis
    3.1. Object Model
        3.1.1. Domain Lexicon
        3.1.2. Class Diagram(s)
    3.2. Dynamic Models
        3.2.1. State Chart
        3.2.2. Sequence Diagram
4. Conclusion
                    

Layout of the report (ie. page numbering, figure naming-numbering, spell checking, page structure) is also important for grading.

The deadline of project analysis report is 28th of October.

You are expected to send soft copies of your report till 28th of October, 23:59. You need to upload your reports to your GitHub projects and send the link of your report to your TA, and instructor.

You can check the assigned TA of your project here

Late submission policy: Late submissions will not be accepted.

Due date for your project descriptions is Sep 22 (Tuesday).

You are required to check your team, contact with your teammates and choose your project title till 22 September.

You need to submit your project titles with short descriptions to your TA's and instructor till this deadline.

You can find your TA by clicking here.

You are also strongly advised to read Project Description.

Fatma Balcı
fatma.balci at bilkent dot edu dot tr

İstemi Bahçeci
istemi.bahceci at gmail dot com

Marzieh Eslami Rasekh
marzieh.eslami at cs dot bilkent dot edu dot tr

(Required) Object-Oriented Software Engineering, Using UML, Patterns, and Java, 3rd Edition, by Bernd Bruegge and Allen H. Dutoit, Prentice-Hall, 2010, ISBN-10: 0136066836.

(Recommended) Applying UML and Patterns - An Introduction to Object-Oriented Analysis and Design and Iterative Development, by Craig Larman, Prentice Hall, 2004, ISBN: 0-13-148906-2.

(Recommended) Object-Oriented Software Engineering, by Timothy C. Lethbridge and Robert Laganiere, McGraw-Hill, 2001, ISBN: 0-07-709761-0.

(Recommended) Developing Software with UML, Object-Oriented Analysis and Design in Practice, by Bernd Oestereich, Addison-Wesley, 1999, QA76.9.03503713 1999.

(Recommended) Object-Oriented Analysis and Design with Applications, 2nd ed., by G. Booch, Benjamin/Cummings, Redwood City, CA, 1994, QA76.64.B66 1994.

(Recommended) Principles of Object-Oriented Software Development, by Anton Eliens, Addison-Wesley, 1995, ISBN: 0-201-62444-3.

Those students who fail to get a minimum of 30 (out of 75) points from the weighted average of the total grades (quiz, project, midterm exam) before the final exam will get the grade FZ. For instance, A/Q/A: 5/10, P: 20/100, M: 40/100 (0.2 * 50 + 0.4 * 20 + 0.15 * 40 = 24) fails, whereas, A/Q/A: 8/10, P: 30/100, M: 40/100 (0.2 * 80 + 0.4 * 30 + 0.15 * 40 = 34) will take the final exam.

• Project Description
• Template for reports
• Project Groups
• Demo Schedule TBA

• Previous Semester CS319 Page - Check for resources!