CMPE 412 Software Engineering

Slides:



Advertisements
Similar presentations
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided with permission by R.S.
Advertisements

Ch.1 Introduction to Software Engineering The Evolution 1.1 The Evolving Role of Software 1/15 In the early days: User Computer Software = Place a sequence.
Lecture 2 1 Introduction to Software Engineering.
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
Systems Analysis, Prototyping and Iteration Systems Analysis.
CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
1 SWE Introduction to Software Engineering Lecture 3 Introduction to Software Engineering.
SWE Introduction to Software Engineering
1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
Introduction Course outline / Recommended books Course objectives Marks distribution / Schedule Basic concepts of SE and PM Project management framework.
Effective Methods for Software and Systems Integration
INTROSE Introduction to Software Engineering Raymund Sison, PhD College of Computer Studies De La Salle University Software: Definitions,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SOFTWARE ENGINEERING Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
Chapter : Introduction to Software Engineering Ref. book : Software Engineering by Roger Pressman.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
DEFECTS By K.KARTHIKE. WHAT IS DEFECTS? Software bug, a failure of computer software to meet requirements Software bug The term defect and its relationship.
Lecture 1 Introduction to Software Engineering
System Development Life Cycle. The Cycle When creating software, hardware, or any kind of product you will go through several stages, we define these.
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.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Chapter 1 The Product. 2 Product  What is it?  Who does it?  Why is it important?  How to ensure it be done right?
1M.Sc(I.T.) VNSGU, Surat. Software is instructions (computer programs) that when executed provide desired function and performance, data structures that.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
CMSC 345 Fall 2000 Software Design and Development.
Scheduling Work I love deadlines. I love the sound they make as they fly by. -- Douglas Adams.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Click to add text Systems Analysis, Prototyping and Iteration.
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
Herriman High Computer Programming 1A Software Development Cycle Things to Know.
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.
PestPac Software. Multi Unit & Portal Training The Multi Unit module allows users the flexibility to handle larger properties, such as Apartment Complexes.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Rekayasa Perangkat Lunak Kuliah 2. Outline of this presentation Attributes of Good Software Why Software Engineering ? What is Software Product ? Software.
1 slc5 TTYP – C++ revisited 1 Which of the following statements are reasonable after the following statement: char* fred = new char[5]; a. fred = bill;
Part 1 Introduction to Software Engineering 1 copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY.
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.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
1 Chapter 1 Software and Software Engineering Software Engineering: A Practitioner’s Approach, 7th edition by Roger S. Pressman.
Chapter 8: Understanding Collections Textbook: Chapter 4.
Software Development.
CS616 Software Engineering I BoNY
CMPE 412 Software Engineering
Rekayasa Perangkat Lunak Part-2
Chapter : Introduction to Software Engineering
Chapter : Introduction to Software Engineering
Software What Is Software?
Software Engineering B.E IT Sem-VII
Software Engineering (CSE 314)
Software Myths Deep Mann.
Chapter : Introduction to Software Engineering
Rekayasa Perangkat Lunak
Overview: Software and Software Engineering
Chapter : Introduction to Software Engineering
Chapter : Introduction to Software Engineering
Software Testing and Maintenance Maintenance and Evolution Overview
I love the sound they make as they fly by.
Software Engineering (CSI 321)
Rekayasa Perangkat Lunak
Introduction Software Engineering.
Chapter 2 Software Engineering
Presentation transcript:

CMPE 412 Software Engineering Asst.Prof.Dr.Duygu Çelik Ertuğrul Room: CMPE 206 Email: duygu.celik@emu.edu.tr

Software Myths (Source: Pressman, R. Software Engineering: A Practitioner’s Approach. McGraw-Hill, 2005)

Software Myths (There are some misleading beliefs that have caused serious problems for managers and programmers.) 1. Books that indicate standards and procedures for building software are enough to produce good programs. REALITY: Software people do not look at the standards and procedures, and sometimes standards and procedures are out of date or incomplete. 2. The software group has got the newest and fastest computers so they should be able to produce good programs. REALITY: Computer Aided Software Eng.(CASE) Tools are more important than Hardware for achieving good quality and productivity. Therefore, latest model of PC is not enough.

3. If we get behind the schedule in a software project, we can add more programmers and finish on time. REALITY: Adding people to a late software project makes it later! (As new people are added, they have to be trained by the others, and this reduces their time.) 4. A general statement of objectives is enough to begin writing programs. We can fill in the details later. REALITY: This is major cause of failure in software projects. We need a formal and detailed description of the system modules , interfaces, and design criteria first.

5. Project requirements are changing continuously 5. Project requirements are changing continuously. However, we can easily handle the changes since software is flexible. REALITY:

6. Once we write the program and it works, our job is done. REALITY: «The sooner you begin writing code, the longer it will take you to complete» 50-70 % of the effort is spent after delivery to customer. Also, the final product should include documents and data. Because, Proper documentation is very important for success, and it guides the maintenance.