1 / 19

Lecturer: Prof. Dr. Ir. Riri Fitri Sari MM MSc EE Department University of Indonesia

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

mikkel
Télécharger la présentation

Lecturer: Prof. Dr. Ir. Riri Fitri Sari MM MSc EE Department University of Indonesia

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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)

  2. Introduction • Lecturer: • RiriFitri Sari 021-7863463 (work) – rektoratlt 7 riri@eng.ui.ac.id riri@ee.ui.ac.id(only for assignment) • Course website http://staff.ui.ac.id/.../132127785

  3. Introduction • Availability: 7st Floor, RektoratUniversitas Indonesia • Lectures time: Wednesday, 13.00-15.30, S205

  4. Contents • Web Engineering VS Software Engineering • System Behavior • Structured Analysis • Unified Modeling Language (UML)

  5. 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.

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

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

  8. Architecting a dog house Can be built by one person Requires Minimal modeling Simple process Simple tools

  9. Architecting a house Built most efficiently and timely by a team Requires Modeling Well-defined process Power tools

  10. Architecting a high rise

  11. Early architecture Progress - Limited knowledge of theory

  12. Modern architecture Progress - Advances in materials - Advances in analysis Scale - 5 times the span of the Pantheon - 3 times the height of Cheops

  13. Modeling a house

  14. 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.

  15. An average software project: - 5-10 people - 10-15 month duration - 3-5 external interfaces - Some unknowns & risks Defense Weapon System Telecom Switch National Air Traffic Control System Commercial Compiler Embedded Automotive Software CASE Tool Large-Scale Organization/Entity Simulation Small Scientific Simulation IS Application Distributed Objects (Order Entry) Defense MIS System Enterprise IS (Family of IS Applications) IS Application GUI/RDB (Order Entry) Business Spreadsheet Dimensions of software complexity Higher technical complexity - Embedded, real-time, distributed, fault-tolerant - Custom, unprecedented, architecture reengineering - High performance Lower management complexity - Small scale - Informal - Single stakeholder - “Products” Higher management complexity - Large scale - Contractual - Many stake holders - “Projects” Lower technical complexity - Mostly 4GL, or component-based - Application reengineering - Interactive performance

  16. Capacity Fail safe Availability Fault tolerance Performance Throughput Technology churn Resilience Forces in Software Functionality Cost Compatibility 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 Our enemy is complexity, and it’s our goal to kill it. Jan Baan

More Related