Rekayasa Perangkat Lunak

Slides:



Advertisements
Similar presentations
Lecture 2 1 Introduction to Software Engineering.
Advertisements

CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
1 SWE Introduction to Software Engineering Lecture 3 Introduction to Software Engineering.
SWE Introduction to Software Engineering
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SWE Introduction to Software Engineering
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Software Engineering Rekayasa Perangkat Lunak Kuliah 05.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Introduction Course outline / Recommended books Course objectives Marks distribution / Schedule Basic concepts of SE and PM Project management framework.
INTROSE Introduction to Software Engineering Raymund Sison, PhD College of Computer Studies De La Salle University Software: Definitions,
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
SOFTWARE ENGINEERING Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
OHTO -99 SOFTWARE ENGINEERING “SOFTWARE PRODUCT QUALITY” Today: - Software quality - Quality Components - ”Good” software properties.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
An Introduction to Software Engineering. What is Software?
Software Engineering SM ? 1. Outline of this presentation What is SM The Need for SM Type of SM Size Oriented Metric Function Oriented Metric 218/10/2015.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
1M.Sc(I.T.) VNSGU, Surat. Software is instructions (computer programs) that when executed provide desired function and performance, data structures that.
Software Engineering (CSI 321) Introduction to Software Engineering 1.
CMSC 345 Fall 2000 Software Design and Development.
IS444: Modern tools for applications development Dr. Azeddine Chikh.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Rekayasa Perangkat Lunak Kuliah 2. Outline of this presentation Attributes of Good Software Why Software Engineering ? What is Software Product ? Software.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 1 Introduction to Software Engineering.
INTRODUCTION CSE 470 : Software Engineering. Goals of Software Engineering To produce software that is absolutely correct. To produce software with minimum.
1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 7th edition by Roger S. Pressman.
Chapter 1: Software and Software Engineering The Nature of Software... Software is intangible  Hard to understand development effort Software.
Advanced Software Engineering Dr. Cheng
Rekayasa Perangkat Lunak Part-6
CompSci 280 S Introduction to Software Development
Software Engineering Rekayasa Perangkat Lunak
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
Rekayasa Perangkat Lunak Part-2
Rekayasa Perangkat Lunak Part-3
Software What Is Software?
Software Engineering (CSE 314)
Rekayasa Perangkat Lunak
Software Myths Deep Mann.
Software Engineering Rekayasa Perangkat Lunak
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Rekayasa Perangkat Lunak
Chapter : Introduction to Software Engineering
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
An Introduction to Software Engineering
Overview: Software and Software Engineering
Software Testing and Maintenance Maintenance and Evolution Overview
CMPE 412 Software Engineering
CIS 375 Bruce R. Maxim UM-Dearborn
Software Engineering Rekayasa Perangkat Lunak
Software Engineering Rekayasa Perangkat Lunak
Software Engineering Rekayasa Perangkat Lunak
Software Engineering (CSI 321)
CS385T Software Engineering Dr.Doaa Sami
CS310 Software Engineering Lecturer Dr.Doaa Sami
Rekayasa Perangkat Lunak
Rekayasa Perangkat Lunak
Requirements Management - I
Rekayasa Perangkat Lunak
Software Engineering Rekayasa Perangkat Lunak
Chapter 1: Software and Software Engineering
Presentation transcript:

Rekayasa Perangkat Lunak Kuliah 2

Outline of this presentation Attributes of Good Software Why Software Engineering ? What is Software Product ? Software Myths 2

Attributes of Good Software Maintainability Dependability Efficiency Usability 3

Attributes of Good Software Maintainability more than 50% of software cost is due to maintenance Easy to maintain Good Documentation Good Design 4

Attributes of Good Software Dependability Reliability, Do the Right Process Security, Good Thread Protection Safety No Surprise On-line & Off-line Help 5

Attributes of Good Software Efficiency Memory, Small Memory Usage CPU time Efficient cycle time Storage Minimum Amount of Storage 6

Attributes of Good Software Usability User Interface Familiar Look Nice & Complete Incorporate Message Alert Documentation User Guide Thorough & Complete 7

Why Software Engineering ? Analogy with bridge building: Over a stream easy, one person job Over River Severn … ? (the techniques do not scale) 8

Why Software Engineering ? ...to get away from ad hoc and unpredictable software development towards a systematic, understood one… 10

What is Software Product ? a general market Software products may be developed for : or may be developed for a particular customer 11

What is Software Product ? Software products may be Generic (for general market) developed to be sold to a range of different customers e.g. Excel or Word or Power Point etc 12

What is Software Product ? Software products may be Bespoke / Custom (for particular customer) developed for a single customer according to their specification. e.g. ……….. 13

New software can be created by Developing new programs, or Reusing existing software Configuring generic software systems 14

New software can be created by Developing new programs, Starting from scratch one full development cycle 15

New software can be created by Reusing existing software Not starting from scratch Using own working software Modifying & Adapting with the New Requirement 16

New software can be created by Configuring generic software systems Not starting from scratch Using on the shelve software Tailoring with the requirement 17

Software Myths Wrong Assumption From Management Cost - Schedule - Quality Customer Use Developer Build 18

Management Myths Myth Fact Standard and procedures are already exist for producing software Fact Standards are rarely used Developers rarely know about them Standards are often out-of date and incomplete 19

Management Myths (cont.) Myth Fact State-of-the-art tool are the solution Fact A fool with a tool is still a fool 20

Management Myths (cont.) Myth If we get behind schedule, we can always add more peoples and thus catch up Fact Software development is not a mechanistic process like manufacturing. Adding people to a late software project makes it later. What about Training - Integration - Social Aspect 21

Developer Myth Myth Fact The only deliverable is the working program(s). Fact A working program is only one part of a software configuration that includes requirements and specification documents, testing information and other developmental and maintenance information. 22

Developer Myth (cont.) Myth Fact Once the program is written and it works, then the job is done. Fact Between 50 and 70 percent of all effort expended on a program will be expended after it is delivered to the customer. 23

Developer Myth (cont.) Myth Fact Until the program is running, there is no way to assess its quality. Fact One of the most effective software quality assurance mechanisms is the formal technical review and this can be applied from the inception of the project. 24

Customer Myth Myth Fact A general statement of objectives is sufficient to begin writing programs - we can fill in details later. Fact Thorough communication between customer and developer needed 25

Customer Myth (cont.) Myth Fact Changes can be easily accommodated because software is flexible Fact Changes happen as a fact of life late changes are expensive 26

Finished, Questions?

Terimakasih….. Untuk mahasiswa/i yang tidak ngantuk dan tetap konsentrasi Mengikuti Perkuliahan.