Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

Test process essentials Riitta Viitamäki,
Software Engineering Software Engineering is the science and art of building significant software systems that are: 1) on time 2) on budget 3) with acceptable.
Software Engineering Session 14 INFM 603. Software Software represents an aspect of reality –Input and output represent the state of the world –Software.
Software Project Management Lecture 2. Laws of Project Management 4 No major project is ever installed on time, within budget and with the same staff.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Metrics for Process and Projects
Metrics for Process and Projects
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
“Not Fully Specified (Project) Objectives” CS524 – Software Engineering I Azusa Pacific University Professor Dr. Sheldon X. Liang Fall I 2007 Ernie Rosales.
Applied Software Project Management INTRODUCTION Applied Software Project Management 1 5/20/2015.
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Software Configuration Management
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
Software Engineering.
1 Software Engineering II Presentation Software Maintenance.
Creator: ACSession No: 9 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringNovember 2005 Risk Management CSE300 Advanced Software Engineering.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Maintenance = Software Evolution Any changes after the client has accepted the product is considered maintenance. n Any Changes? n What might these be?
12 Steps to Useful Software Metrics
Planning. SDLC Planning Analysis Design Implementation.
Chapter 9 – Software Evolution and Maintenance
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Software evolution. Objectives l To explain why change is inevitable if software systems are to remain useful l To discuss software maintenance and maintenance.
Software Quality Assurance Activities
Software Project Management Lecture # 8. Outline Earned Value Analysis (Chapter 24) Topics from Chapter 25.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Engineering Introduction and Overview Takes customer-defined goals and constraints and derives a representation of function, performance, interfaces,
Facts and Fallacies of Software Engineering (Rob Glass) CSE301 University of Sunderland Discussed by Harry R. Erwin, PhD.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
1Software Measurement Advanced Software Engineering COM360 University of Sunderland © 2001.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki 1 Machine Learning.
Slide 2.1 CHAPTER 2 THE SOFTWARE PROCESS. Slide 2.2 Overview l Client, Developer, and User l Requirements Phase l Specification Phase l Design Phase l.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution 1.
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
Advanced Software Engineering Lecture 4: Process & Project Metrics.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
Engineering Economics Lecture 18 Project Management 6 January 2010.
Risk Management Managing the Software Process - Risk Management Advanced Software Engineering COM360 University of Sunderland © 1998.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CS3320-Chap21 Office Hours TR 1:00-2:15 PM W 2:30-3:30 PM By appointment.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Word Guess Team (Team #4) October 8, Word Guess Team  Team Members  Chakib Kouhel:  Steve Mattingley:
Software Engineering Introduction Slide 1 Software Engineering Introduction.
INTRODUCTION CSE 470 : Software Engineering. Goals of Software Engineering To produce software that is absolutely correct. To produce software with minimum.
Software Configuration Management
Overview Software Maintenance and Evolution Definitions
Software Verification and Validation
Software Quality Assurance
IEEE Std 1074: Standard for Software Lifecycle
12 Steps to Useful Software Metrics
Project Management.
SQA for Individuals based on
Risk Analysis & Success Driven Project Management
Chapter 9 – Software Evolution and Maintenance
Quality Measurable characteristic Cyclomatic complexity Cohesion
Software Engineering I
Metrics for Process and Projects
Definition of Project “An organized endeavor aimed at accomplishing a specific non-routine or low-volume task.” Definition of Project Management “The.
Presentation transcript:

Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University of Sunderland © 2001

Advanced S/w Eng - s/w productivity issues 2 Problems with Software Complexity Conformity Changeability Invisibility

Advanced S/w Eng - s/w productivity issues 3 Complexity Software is more complex than any other construct made by humans. A product becomes difficult to understand.

Advanced S/w Eng - s/w productivity issues 4 Conformity Generally, software must conform to interfaces with existing systems.

Advanced S/w Eng - s/w productivity issues 5 Changeability There is always pressure to change software.

Advanced S/w Eng - s/w productivity issues 6 Invisibility Software is difficult to visualise. DFDs etc. don’t tell the whole story.

Advanced S/w Eng - s/w productivity issues 7 The Phases of Software Production Requirements Specification Planning Design Implementation Integration Maintenance Retirement

Advanced S/w Eng - s/w productivity issues 8 Software Engineering Technology Methods –Analysis –Design –Coding –Testing –MaintenanceProcedures – Proj. Mngt. – SQA – SCM – Metrics – Tracking Tools – CASE

Advanced S/w Eng - s/w productivity issues 9 What is Software Productivity? Producing acceptable products (outputs) using the processes and people (inputs) at your disposal and within agreed-upon schedule.

Advanced S/w Eng - s/w productivity issues 10 Productivity Data The SEI has asked the following questions about productivity for over TEN years: how much effort is spent in each task? for each product item, what effort was devoted? what is the cost of defect removal by each inspection and test method, and by defect type?

Advanced S/w Eng - s/w productivity issues 11 Productivity - “it varies” Productivity varies dramatically between organisations... Organisations define lines of code and effort expended differently... Language variations have to be accounted for... Some organisations count reused code, some only count it if it’s modified...

Advanced S/w Eng - s/w productivity issues 12 Software Success Attributes Delivered on Time Delivered Within Budget Works Meets Requirements (Correct) Usable by Normal People Maintainable Documented and Supported

Advanced S/w Eng - s/w productivity issues 13 Laws of Project Management 1 No major project is ever installed on time, within budget, with the same staff Projects progress quickly until 90% complete; then stay 90% complete forever. With fuzzy project objectives you can avoid estimating the corresponding costs.

Advanced S/w Eng - s/w productivity issues 14 Laws of Project Management 2 When things go well, something will go wrong. When things can’t get worse, they will. If things improve, you have missed something. If project content changes, the rate of change will exceed rate of progress. Attempts to debug a system introduce new bugs that are harder to find.

Advanced S/w Eng - s/w productivity issues 15 Laws of Project Management 3 A badly planned project takes three times longer to complete that expected; A well planned project takes only twice as long. Project teams detest progress reporting because it vividly manifests their lack of progress.