By Ramon Webb,2014-04-14 03:07
23 views 0
1) Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Craig Larman Publisher: Prentice Hall, 2005,


    SYLLABUS Instructor: Beyhan Akporay

    Office Hours: Monday 14:40 15:30 and Thursday 10:40 11:30

    E-Mail: Web:

    Tel: +90 312 290 5233


    This course prepares students to real world software development as an engineering

    discipline. It covers the software development techniques, software development life

    cycle, UML modeling, project management, requirements elicitation, analysis, system

    decomposition, object design, coding, and testing. The main objective of this course is to

    teach students how a large and complex software system can be designed and

    implemented in such a way that it conforms to the requirements. Since these software

    systems must be built by teams, projects are assigned to groups of 4 (usually; sometimes

    3 or 5 depending on the project) students.


Object-Oriented Software Engineering, Using UML, Patterns, and Java ndBernd Bruegge & Allen H. Dutoit, 2004 Prentice Hall; 2 edition

    ISBN-10: 0130471100, ISBN-13: 973-0130471109


    1) Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design

    and Iterative Development

    Craig Larman Publisher: Prentice Hall, 2005, Third Edition

    ISBN-10: 0131489062, ISBN-13: 9780131489066

2) Object-Oriented Analysis and Design With Applications

    Grady Booch Publisher: Addison Wesley, 1994, Second Edition

    ISBN: 0805353402

    3) UML Schaum’s Outlines Series Simon Bennet, John Skelton, Ken Lun Publisher: McGraw-Hill, 2005, Second Edition

    ISBN: 0-07-710741-1


    Grading Weight Date

     Individual Exams %50 thMidterm %25 10 Week (TBA) thFinal %25 18 Week (TBA) YOU HAVE TO HAVE A PASSING GRADE ON THE INDIVIDUAL EXAMS TO PASS


    Team Project %50

    Initial Project Plan %5 Friday October 9

    Software Requirements Specification %10 Monday November 2


    Software Project Management Plan %10 Tuesday November 24


    Software Design Description (SDD) %10 Friday December 18

    Prototype Implementation %10 Monday Tuesday

    December 21-22

    Demo %5 Monday Tuesday

    December 21-22


    ? CTIS459 is a very intense course with lots of software engineering documentation;

    so do not fall behind; otherwise you may not catch-up.

    ? It is each student’s responsibility to regularly check the course web site and his/her e-mail account to follow-

    up on the course.

    ? I have posted the power point slides of the book. I will post more slides,

    documentation, examples, and links etc. as we go along.

    ? Midterm & Final are closed book and in-class exams.

    ? Each project team should email the soft copies and also turn-in the deliverables to

    me as hard copies (put them into my mailbox at the department secretary’s office).

    Soft copies are due noon (by 12pm) and hard copies are due by 5pm. ? Late submission will not be accepted nor graded. So, schedule your time


    ? Choose your team members very carefully; you will spend many days, nights,

    weekends working together for this semester and the next semester. It is not

    required, but it is better to choose a project manager for your team.

    ? Each project team should have “Project Web Site” to publish their deliverables.

    So, if your team number is 8, then you will have your web site at I will email the team password to your project


    ? Other than the class lectures, you need to work as a team in the lab or project

    rooms (if you have any other place to work as a team, that is fine too). You need

    to reserve project rooms through the department secretary. You are free to use any

    CASE (Computer Aided Software Engineering) tool for your project i.e. MS

    Microsoft Project, MS Visio, Rational Rose, Telelogic Developer etc.


    ? Remember the Bilkent University “Code of Discipline” and do not attempt

    cheating and plagiarism. Bilkent University has subscribed to Turnitin


    o Turnitin is a database renowned for its plagiarism detection service.

    Teachers may submit essays to the Turnitin website which will be

    compared to both current and archived pages on the internet, millions of

    student papers previously submitted to Turnitin, and commercial

    electronic databases of journal articles, periodicals and e-books.”


    Make-ups may be given for the Midterm and Final exams with a University Health

    Center approved doctor’s certificate.


    Week 1: Course Overview

    Software Engineering Fundamentals Review Chapter 1

    Week 2: Project Organization and Communication Chapter 3

    Tasks, work products, deliverables, and different project communication mechanisms.

    Project Management Chapter 14

    Work Breakdown Structure (WBS), Software Project Management Plan (SPMP), and

    project control.

    Week 3: Software Life Cycle Chapter 15

    Activities and work products of software life cycle models and Capability Maturity


    Week 4: Modeling with UML Chapter 2

    The purpose of the Unified Modeling Language (UML) for software system analysis and

    design, use-case, class, sequence, state-chart, activity diagrams

    Deliverable 1: Initial Plan

    Week 5: Requirements Elicitation Chapter 4

    Functional and non-functional requirements, identifying actors, scenarios, and use-cases,

    traceability, Software Requirements Specification (SRS)

    Week 6: Analysis Chapter 5

    Analysis model, mapping use-cases to objects and sequence diagrams, identifying


    Week 7: Analysis Continued Chapter 5


    Week 8: Software Project Management Plan (SPMP) Chapter 13

    Configuration Management (CM), Software Cost Estimation, Verification & Validation

    (V&V), Software Quality Assurance (SQA), and Software Process Improvement (SPI)

    Week 9: Software Project Management Plan (SPMP) Continued

    Testing Chapter 11

    Testing activities, reliability, unit, integration, and system (functional, performance, and

    acceptance) testing Deliverable 2: Software Requirements Specification (SRS)

    Week 10: Midterm Exam

    Week 11: System Design Chapter 6, 7

    Architectural styles, sub-system identification, coupling & cohesion

    Hardware/software mapping, data management, access control, control flow, boundary

    conditions, Software Design Description (SDD)

    Week 12: System Design Continued Chapter 6, 7

    Deliverable 3: Software Project Management Plan (SPMP)

    Week 13: Object Design Chapter 8

    Subsystem realization, identification of the COTS components, frameworks, design

    patterns (existing classes), service specifications, optimization for performance


    Week 14: Object Design (Continued)

    Week 15: Mapping Models to Code Chapter 10

    Transformation of object design and interfaces to code

    Deliverable 4: Software Design Description (SDD)

    Week 16: Prototype Implementation and Demo


Report this document

For any questions or suggestions please email