Informatics 43 – April 21, 2015. Things to know Midterm on Thursday – Closed book, closed notes, bring pen/pencil – Questions available on web site (updated)

Slides:



Advertisements
Similar presentations
Effort metrics: Man-month. Mythical Man Month – the book Brooks lead development of OS/360 and reflected on the problems experienced in the project. The.
Advertisements

Robert Lockyer.
Figures-Chapter 2.
Project Management Information Systems and Management.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
brought to you by: jeremy miller brought to you by: jeremy miller.
Software Process Models
The Mythical Man-Month By: Zac Lippard CS 470. What is the “Man-Month”? This is the idea that men and months are interchangeable between each other. This.
1 projman7b How to Fail in Project Management (Without Really Trying) Jeffrey Pinto and Om Kharbanda Business Horizons, July-Aug 96.
Software Engineering Management Main issues:  Plan - as much as possible, but not too much, up front  Control - continuously.
Informatics 43 – May 12, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases 
Introduction to Software Engineering Dr. Basem Alkazemi
Software Engineering About the Course Software Engineering Qutaibah Malluhi Computer Science and Engineering Department Qatar University.
CS 501: Software Engineering Fall 2000 Lecture 4 Management I: Project Management.
CS189A/172 - Winter 2008 Lecture 5: Project Management.
Course Introduction and Overview of Software Engineering Richard N. Taylor ICS 221 Fall 2002.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
CSE 230: Introduction to Software Engineering Topics covered: Introduction.
1 Mouse Cases M.Ellis/Y.Torun Wednesday 31 st March 2004.
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Ch 2: Software Life-Cycle Models CSCI Ideal Software Development.
1 Software Process Lecture Outline Nature of software projects Engineering approaches Software process A process step Characteristics of a good.
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
Why is software engineering worth studying?  Demand for software is growing dramatically  Software costs are growing per system  Many projects have.
CSC 354 – Software Engineering, Spring 2013, Week 2 Mythical Man-Month Ch. 1-5 Tar Pit, Mythical Man-Month, Surgical Team, Aristocracy / Democracy & System.
CSE 436 Software Engineering Workshop Course Overview Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering.
Slide TMMM.1/28 The Mythical Man-Months. Slide TMMM.2/28 Overview Fred Brooks and OS/360 The Mythical Man-Month What has and has not changed? No Silver.
Industrial Software Project Management Some views on project managing industrial and business software projects.
Prescriptive Process Models
Course Introduction Software Engineering
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Software Requirements The starting point of software development “He kept changing the requirements on us” 1 540f07tmproj6sep11.
1.1 The Evolving Role of Software
Managing Resources Program Evaluation and Review Technique (PERT) Production Process.
CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Software Life Cycle (SLC) formalizing the process of software development 1 540f07tmproj6sep11.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Project Schedules Chapter 4 Applied Software Project Management, Stellman & Greene See also:
CS251 – Software Engineering Lecture 9: Software Design Slides by Mohammad El-Ramly, PhD
CMSC 345 Fall 2000 Software Design and Development.
Mythical Man Month By Ryan Ruzich.  More software projects have gone awry for lack calendar time than all other reasons combined.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
Software Engineering Process Models Models for Guiding the Development of Software.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
CSE-332 Software Design Methods The Mythical Man-Month 박성우 POSTECH October 20, 2015.
1 FPB 11/24/13 Nuggets from The Mythical Man-Month Fred Brooks University of North Carolina at Chapel Hill
Project Management IS301 – Software Engineering Lecture #5 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
Informatics 43 – April 5, Announcements 1.Discussions did meet on Friday, April 1. 1.Oh no, I missed discussion!? 2.Discussion again on Friday,
Best 20 jobs jobs sites.
The Software Development Process. Contents  Product Components  Software project staff  Software development lifecycle models.
Why is software engineering worth studying?
Lecture 3 Prescriptive Process Models
Lecture 0 Software Engineering Course Introduction
Informatics 43 – May 10, 2016.
Software Myths Software is easy to change
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Informatics 43 – April 19, 2016.
© Ian Davis 2017 Spring (c) Ian Davis.
Informatics 43 Discussion 13 May, 2016
Nuggets from The Mythical Man-Month Fred Brooks University of North Carolina at Chapel Hill ONR_Updated.
Software Process Models
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
CSE 403 Scheduling These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides written by Valentin Razmov. They.
Presentation transcript:

Informatics 43 – April 21, 2015

Things to know Midterm on Thursday – Closed book, closed notes, bring pen/pencil – Questions available on web site (updated) – Special seating plan Lectures are videotaped and student notes are on web site No discussions this Friday Readings for next Tuesday

What is Software Engineering? Informatics 43: The process of constructing software. Phases of development other than programming. Principles and qualities of enduring value. Also of interest: Managing software development teams. Making money – business models. Software’s impact on users, organizations, and society.

The Process of Constructing Software Software Process Models The Software Lifecycle

The Process of Constructing Software The Process of Dining at a Restaurant Activities (in alphabetical order): Eat Pay Select Serve

RestaurantType of Restaurant Order of Activities Eat, Pay, Select, Serve

We just modeled The Process of Dining at a Restaurant Was anything left out? Is the model too simple? Is the model useful?

A Programming-centric Software Process Model Application domain problem Programming problem Figure 4.1 A simple process

The Waterfall Software Process Model Figure 4.2 A waterfall model

Incremental Software Process Model

Spiral Model

The Mythical Man-Month Causes for scheduling disasters: 1.We expect that all will go well. 2.We confuse effort with progress, and think that people and months are interchangeable. 3.Managers are often insufficiently stubborn. 4.Schedule progress is poorly monitored. 5.When schedule slippage is recognized, more people are added. Brooks’s Law: Adding manpower to a late software project makes it later.

The Mythical Man-Month Why is the man-month as a unit for measuring the size of a job a dangerous and deceptive myth?