COURSE SYLLABUS

OO ANALYSIS AND DESIGN

Instructor
Name

: Dana Indra Sensuse

Sofian Lusa
Goenawan Brotosaputro
E-mail
: Tgsubl@gmail.com
Subject: MKOM Tugas1 XC Nama_Kelompok

Why is this Course Important?

Most error (54%) are detected after coding and

testing
Almost half of all errors in software (45%) are in
requirement and design
Most errors made during requirement analysis are
non-clerical and may arise because of incorrect
facts, inconsistency, omissions, and ambiguities
Requirement error can cost up to 100 times more
to fix if they are not caught early on than
implementation error.

Description
This course focuses on the Analysis and

Design of the System

It involves understanding of how to develop
an Information Systems (IS) that can support
organizations in order to achieve their goals
by delivering benefits.
The development of IS should be an integrated
approaches within the organization.
The methods used in ADIS can be applied to a wide
variety of problem domains.

Cont..
The course will deal with how to develop

Information Systems so that it can improve the

competitiveness of an organization.
This course will explore the role of IS that has
moved from having a peripheral function in
business, to having a core function in driving
profitability in many ways - producing new
products, speeding up time-to market, producing
cost efficiency, promoting or creating customer
loyalty, etc.

Course Objectives

The objectives of the course are:

to understand the process of ADIS,
to explore the various approaches in developing IS,
to exercise the use of concept, technique, and method in
developing IS and
to exercise the development of IS in the real world.

Required Reading

Dennis, Alan and Barbara Haley Wixom.

System Analysis and Design. With UML

Version 2.0: An Object-Oriented Approach,
2nd ed. 2005. John Wiley & Sons, Inc.

Evaluation
Evaluation will be based on participation, case

analysis assignments, a group project and midterm

exam.

 Your final grade will not rest on one or two

assignments but will be based on how many

points you accumulate throughout the
semester. The weights assigned to each
component are as follows:

Attendance
Group Project Report 1
Group Project Report 2
Midterm exam
Presentation UAS
Final Group Report
Total

10%
10%
10%
30%
30%
10%
100%

Cont..
Academic dishonesty and Incompletes. Each

student should be familiar with the guidelines set in

the Code of Student Ethics for issues pertaining
to academic dishonesty.
No incompletes (I) will be assigned.
There will be no makeup exam unless prior notice
is given and documentation of emergency is given.

Lesson Plan: I. Planning Phase

Week 1

Class Introduction
System Development Life Cycle (Chp 1)

System Development Methodology

Project Team Skills and Roles
Group Assignment #1

Week 2

Introduction to Object-Oriented Analysis and

Design (Chp 2)
Project Initiation (Chp 3)
- Project Identification
- Feasibility Analysis
- Project Selection

Cont..
Week 3
Project Management (Chp 4)
Creating and Managing the Work-plan
Staffing the Project
Coordinating Project Activities

II. Analysis Phase

Week 4
Requirements Determination (Chp 5)

Requirements Analysis Techniques

Requirements-Gathering Techniques
Group Assignment #1 due
Group Assignment #2
Functional Modeling (Chp 6)

Cont..
Week 5
Structural Modeling (Chp 7)
Week 6
Behavioral Modeling (chp 8)
Week 7
UTS

III. Design Phase

Week 8
Move on to Design (Chp 9)
- Design Strategies
- Moving from Logical to Physical Models
Group Assignment #2 due
Group Assignment (Final Report)
Week 9
Class and Method Design (Chp 10)
- Creating an Architecture Design
- Hardware and Software Specification
Week 10
Data Management Layer (Chp 11)

Cont..
Week 11
User Interface Design (Chp 12)
- User Interface Design Process
- I/O design

Week 12
Physical Architecture Layer (Chp 13)

IV. Implementation Phase

Prototype

Week 13-16: Group Presentation

Week 16 (Final Report)

Laporan I (Planning)
Laporan I berkaitan dengan kegiatan Planning.
Isi laporan I mencakup:

Identifying business value

Analyze feasibility
Develop workplan
Staff the project
Control and direct project

Laporan II (Analysis)
Laporan II berkaitan dengan kegiatan Analysis
Isi laporan II mencakup:

Requirements determination

Functional requirement
Non-functional requirement

Functional modeling
Structural modeling
Behavioral modeling

Laporan III (Design)

Laporan III (Akhir) berkaitan dengan semua

tahapan Planning sampai dengan Implementation

Isi laporan III (Akhir) mencakup:

Laporan I dan II ditambah dengan:

Class and method design
Package diagram
Data management layer design
Human computer interaction layer design
Physical architecture layer design

Presentasi Proyek Pengembangan Sistem

Dilakukan pada 3-4 minggu terakhir
Satu kelompok terdiri atas maks 4 orang
Tidak ada UAS, sebagai pengganti nilai UAS adalah

presentasi proyek
Tunjukan prototipe yang dibuat
Tugas masing-masing anggota:

Anggota #1 mempresentasikan Planning

Anggota #2 mempresentasikan Analysis
Anggota #3 mempresentasikan Design
Anggota #4 mempresentasikan Prototipe