Lecturer: Prof. Dr. Ir. Riri Fitri Sari MM MSc EE Department University of Indonesia This slide was initially set by M. Salman, ST, MSc Session #1 – 4 Sept 2011 INTRODUCTION SOFTWARE ENGINEERING (Rekayasa Perangkat Lunak)

Slide - 2 RPL Lecture # Introduction  Lecturer:  Riri Fitri Sari (work) – rektorat lt 7 (only for assignment)  Course website

Slide - 3 RPL Lecture # Introduction  Availability: 7 st Floor, Rektorat Universitas Indonesia  Lectures time: Wednesday, , S205 Wednesday, , S205

Slide - 4 RPL Lecture # Contents   Web Engineering VS Software Engineering   System Behavior   Structured Analysis   Unified Modeling Language (UML)

Slide - 5 RPL Lecture # Assesment 40% project 30% mid-exam 30% Final Test A pass grade in the examinations, assignment and project exercises is a hurdle requirement for successful completion of this course.

Slide - 6 RPL Lecture # Texbook Software Engineering: An Object-Oriented Perspective Eric J. Braude, Boston University Software Engineering: A Practitioner Approach Roger Pressman, Prentice Hall - UML Books

Slide - 7 RPL Lecture # Your Responsibility & Right Active Communication Attendance Individual/Group activities Self Motivation Code of Ethics (Cheating, Plagiarism, Collusion etc) Hand in the assignment on time

Slide - 8 RPL Lecture #

Slide - 9 RPL Lecture # Architecting a dog house Can be built by one person Requires Minimal modeling Simple process Simple tools

Slide - 10 RPL Lecture # Architecting a house Built most efficiently and timely by a team Requires Modeling Well-defined process Power tools

Slide - 11 RPL Lecture # Architecting a high rise

Slide - 12 RPL Lecture #

Slide - 13 RPL Lecture # Early architecture Progress - Limited knowledge of theory

Slide - 14 RPL Lecture # Modern architecture Progress - Advances in materials - Advances in analysis Scale - 5 times the span of the Pantheon - 3 times the height of Cheops

Slide - 15 RPL Lecture # Modeling a house

Slide - 16 RPL Lecture #

Slide - 17 RPL Lecture # The 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) * Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

Slide - 18 RPL Lecture # Dimensions of software complexity 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 Higher management complexity - Large scale - Contractual - Many stake holders - “Projects” Lower management complexity - Small scale - Informal - Single stakeholder - “Products” Defense MIS System Defense Weapon System Telecom Switch CASE Tool National Air Traffic Control System Enterprise IS (Family of IS Applications) Commercial Compiler Business Spreadsheet IS Application Distributed Objects (Order Entry) Small Scientific Simulation Large-Scale Organization/Entity Simulation An average software project: people month duration external interfaces - Some unknowns & risks Embedded Automotive Software IS Application GUI/RDB (Order Entry)

Slide - 19 RPL Lecture # Forces in Software Technology churn Our enemy is complexity, and it’s our goal to kill it. Jan Baan PerformanceThroughput Capacity Availability Fail safe Fault tolerance Functionality CostCompatibility Resilience The 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