PROYEK PERANGKAT

LUNAK
Teknik Informatika UNS
Deskripsi Mata Kuliah
Menumbuhkan kemampuan standar
dalam rekayasa perangkat lunak
terutama dengan paradigma
berorientasi objek berorientasi objek
Melengkapi presentasi pekerjaan
merekayasa perangkat lunak dengan
dokumentasi yang baik
Mempresentasikan hasil pekerjaannya
dalam membangun SW sederhana
Deskripsi Mata Kuliah
Software Process
Overview tentang OOSE
Overview tentang Unified Process (UP)
UP : Fase Inception UP : Fase Inception
UP : Fase Elaboration
UP : Fase Construction
UP : Fase Transition
Deskripsi Mata Kuliah
Projects
Individual Projects : 20%
Group Projects : 50%
Midterm Test : 30% Midterm Test : 30%
Deskripsi Mata Kuliah
Inception Phase
Elaboration Phase
Construction Phase
Transition Phase Transition Phase
Deskripsi Mata Kuliah
Penilaian berdasarkan pada:
Software Document
Presentation
User Document User Document
Personal Level
Deskripsi Mata Kuliah
Roger S Pressman, 2002.
Software Engineering: A Practitioners
Approach. McGraw-Hill.
Thomas A Pender, 2002. Thomas A Pender, 2002.
UML Weekend Crash Course. Wiley
Publishing.
Deskripsi Mata Kuliah
Alat:
Rational Rose/Argo UML
Visio 2003/2007
Net beans with UML plugin Net beans with UML plugin
Bahasa Pemrograman
Java
PHP Object
INTRODUCTION
Teknik Informatika - UNS
Why Project?
Starting date
Terminate date
Starting date
Continuous, no
Project Development
Terminate date
Must Delivered
Unmaintainable
Continuous, no
terminate date
Sometimes undelivered
Maintainable
Why Project?
Start Process End
Why Project?
start process
process
maintain
start
What will we discuss?
Software Process Model
Object Oriented Software Engineering
Introduction to Unified Process
Unified Process Unified Process
Inception
Elaboration
Construction
Transition
Process Model
Prescriptive Models
The Waterfall Model
Incremental Model
Evolutionary Process Model Evolutionary Process Model
Specialized Models
Component Based Development
Formal Methods Models
Aspect Oriented Programming
Unified Process
Precriptive Model
Originally proposed to bring order to the chaos of
software development
Called prescriptive because:
prescribe a set of process elements (activities, actions, tasks,
work products, quality assurance etc for each project) work products, quality assurance etc for each project)
each process model also prescribes a workflow
They brought order to software engineering work and
provide reasonable guidance to software teams
Yet, they have not provided a definitive answer to the
problems of software development in an ever changing
computing environment
Waterfall Model
Old fashioned but reasonable approach when
requirement are well defined/understood
Waterfall Model
Analysis
Design Design
Implementation
Testing
RUP
Business Modeling
Implementation
Analysis & Design
Phases
Process Workflows
Requirements
Elaboration Transition Inception Construction
Management
Environment
Implementation
Test
Preliminary
Iteration(s)
Iter.
#1
Supporting Workflows
Iter.
#2
Iter.
#n
Iter.
#n+1
Iter.
#n+2
Iter.
#m
Iter.
#m+1
Deployment
Configuration Mgmt