lecturer: prof. dr. ir. riri fitri sari mm msc ee department university of indonesia
DESCRIPTION
Session #1 – 4 Sept 2011. Lecturer: Prof. Dr. Ir. Riri Fitri Sari MM MSc EE Department University of Indonesia This slide was initially set by M. Salman, ST, MSc. INTRODUCTION SOFTWARE ENGINEERING (Rekayasa Perangkat Lunak). Introduction. Lecturer: Riri Fitri Sari - PowerPoint PPT PresentationTRANSCRIPT
Lecturer: Lecturer: Prof. Dr. Ir. Riri Fitri Sari MM MScProf. Dr. Ir. Riri Fitri Sari MM MSc
EE DepartmentEE DepartmentUniversity of IndonesiaUniversity of Indonesia
This slide was initially set This slide was initially set by M. Salman, ST, MScby M. Salman, ST, MSc
Session #1 – 4 Sept 2011Session #1 – 4 Sept 2011
INTRODUCTIONINTRODUCTION
SOFTWARE ENGINEERINGSOFTWARE ENGINEERING
(Rekayasa Perangkat Lunak)(Rekayasa Perangkat Lunak)
Slide - Slide - 22RPL Lecture #1 - 2009RPL Lecture #1 - 2009
IntroductionIntroduction
Lecturer: Lecturer: Riri Fitri SariRiri Fitri Sari
021-7863463 (work) – rektorat lt 7021-7863463 (work) – rektorat lt 7
[email protected]@eng.ui.ac.id
[email protected]@ee.ui.ac.id (only for (only for assignment)assignment)
Course website Course website http://staff.ui.ac.id/.../132127785
Slide - Slide - 33RPL Lecture #1 - 2009RPL Lecture #1 - 2009
IntroductionIntroduction
Availability:Availability:
77stst Floor, Rektorat Universitas Floor, Rektorat Universitas IndonesiaIndonesia
Lectures time:Lectures time:
Wednesday, Wednesday, 1313.00-.00-1515..330, S2050, S205
Slide - Slide - 44RPL Lecture #1 - 2009RPL Lecture #1 - 2009
ContentsContents
Web Engineering VS Software Engineering System Behavior Structured Analysis Unified Modeling Language (UML)
Slide - Slide - 55RPL Lecture #1 - 2009RPL Lecture #1 - 2009
AssesmentAssesment
440% project 0% project 3030% mid-exam% mid-exam3030% Final Test% Final Test
A pass grade in the examinations, assignment A pass grade in the examinations, assignment and project exercises is and project exercises is a hurdle requirement for a hurdle requirement for successful completion successful completion of this course. of this course.
Slide - Slide - 66RPL Lecture #1 - 2009RPL Lecture #1 - 2009
TexbookTexbook
Software Engineering: An Object-Oriented Perspective Eric J. Braude, Boston University
Software Engineering: A Practitioner ApproachRoger Pressman, Prentice Hall
- UML Books
Slide - Slide - 77RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Your Responsibility & Right Your Responsibility & Right
Active CommunicationActive Communication
AttendanceAttendance
Individual/Group activitiesIndividual/Group activities
Self MotivationSelf Motivation
Code of Ethics (Cheating, Code of Ethics (Cheating, Plagiarism, Collusion etc)Plagiarism, Collusion etc)
Hand in the assignment on timeHand in the assignment on time
Slide - Slide - 88RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Slide - Slide - 99RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Architecting a dog house Architecting a dog house
Can be built by one personCan be built by one personRequiresRequires
Minimal modelingMinimal modelingSimple processSimple processSimple toolsSimple tools
Slide - Slide - 1010RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Architecting a houseArchitecting a house
Built most efficiently and timely by a teamRequires
ModelingWell-defined processPower tools
Slide - Slide - 1111RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Architecting a high riseArchitecting a high rise
Slide - Slide - 1212RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Slide - Slide - 1313RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Early architectureEarly architecture
Progress - Limited knowledge of theory
Slide - Slide - 1414RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Modern architectureModern architecture
Progress - Advances in materials - Advances in analysis
Scale - 5 times the span of the Pantheon - 3 times the height of Cheops
Slide - Slide - 1515RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Modeling a houseModeling a house
Slide - Slide - 1616RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Slide - Slide - 1717RPL Lecture #1 - 2009RPL Lecture #1 - 2009
The Four “P’s” of Software EngineeringThe Four “P’s” of Software Engineering
People
(by whom it is done)
Process(the manner
in which it is done)
Project
(the doing of it)
Product
(the application artifacts)
Elaboration
Unified Process Matrix
Inception Construction Transition
Requirements
Analysis
Jacobson et al: USDP
Prelim.iterations
Iter.#1
Iter.#n
Iter.#n+1
Iter.#m
Iter.#m+1
Iter.#k
….. …..
Design
Implemen-tation
Test
..*
Slide - Slide - 1818RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Dimensions of software Dimensions of software complexitycomplexity
Higher technical complexity - Embedded, real-time, distributed, fault-tolerant - Custom, unprecedented, architecture reengineering - High performance
Lower technical complexity - Mostly 4GL, or component-based - Application reengineering - Interactive performance
Highermanagement complexity - Large scale - Contractual - Many stake holders - “Projects”
Lowermanagement complexity - Small scale - Informal - Single stakeholder - “Products”
Defense MIS System
Defense Weapon SystemTelecom
Switch
CASE Tool
National Air TrafficControl System
Enterprise IS(Family of ISApplications)
CommercialCompiler
BusinessSpreadsheet
IS ApplicationDistributed Objects
(Order Entry)
Small ScientificSimulation
Large-ScaleOrganization/Entity
Simulation
An average software project: - 5-10 people - 10-15 month duration - 3-5 external interfaces - Some unknowns & risks
EmbeddedAutomotive
Software
IS ApplicationGUI/RDB
(Order Entry)
Slide - Slide - 1919RPL Lecture #1 - 2009RPL Lecture #1 - 2009
Forces in SoftwareForces in Software
Technology churn
Our enemy is complexity, and it’s our goal to kill it.Jan Baan
Performance Throughput
Capacity
Availability
Fail safe
Fault tolerance
FunctionalityCost Compatibility
ResilienceThe challenge over the next 20 years will not be speed or cost or performance;it will be a question of complexity.Bill Raduchel, Chief Strategy Officer, Sun Microsystems