Project & Risk Management For next class -- Pressman: 3, 5.1-5.5, 5.8, 6.1-6.3, 6.6 Introductions Software Development Processes Software Maturity Models.

Slides:



Advertisements
Similar presentations
CS5714 Usability Engineering An Iterative, Evaluation- Centered Life Cycle For Interaction Development Copyright © 2003 H. Rex Hartson and Deborah Hix.
Advertisements

Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
CS3773 Software Engineering Lecture 01 Introduction.
Paper Prototyping.
University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
Introduction to Software Engineering Lecture 3 André van der Hoek.
Project Planning and Control Main issues:  How to plan a project?  How to control it?
Project Planning and Control Main issues:  How to plan a project?  How to control it? ©2008 John Wiley & Sons Ltd. vliet.
Informatics 43 – April 28, Fun with Models Fashion Student Model = Ideal.
Paper Prototyping.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
Lecturer: Dr. AJ Bieszczad Chapter 33-1 Planning and managing the project Tracking project progress Project personnel and organization Effort and schedule.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Software Engineering.
Chapter 6 Systems Development.
Creator: ACSession No: 9 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringNovember 2005 Risk Management CSE300 Advanced Software Engineering.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
Paper Prototyping.
Picture 1 model: ICT lifecycle in a company 1. business needs & business strategy 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical.
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 6 Development Plans Quality Plans.
Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.
Chapter 2 The process Process, Methods, and Tools
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Software Project Management Introduction to Project Management.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
SPEAKER : KAI-JIA CHANG ADVISER : QUINCY WU DATA : Spiral Model.
Software System Engineering: A tutorial
Introduction to Information and Computer Science Information Systems Lecture b This material (Comp4_Unit9b) was developed by OHSU, funded by the Department.
Makefile Visualization The Team: Sarah Baugh Hongyu Chen Brandon Otto Martin Strobel William Tran Our Client: Ahmed Tamrawi.
1 Project Risk Management Project Risk Management Dr. Said Abu Jalala.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
Chapter 3 Project Management Concepts
Chapter 3 Project Management Details Tracking Project Progress Project Estimation Project Risk Analysis Project Organization RUP Project Management Workflow.
© The McGraw-Hill Companies, Software Project Management 4th Edition Risk management Chapter 7.
Introduction to Software Engineering ECSE-321 Unit 4 – Project Management 10/19/2015Introduction to Software Engineering – ECSE321Unit 4 – Project Management/1.
Pre-Project Components
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Project Management in the Software Development Environment CIS490.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
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.
Component 4: Introduction to Information and Computer Science Unit 9: Components and Development of Large Scale Systems Lecture 2 This material was developed.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different 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.
Software Project Management Lecture 5 Software Project Risk Management.
Prototyping. Outline Risk Management Prototyping Kinds of Prototypes Example Activity 1.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Sistemas de Información Agosto-Diciembre 2007 Sesión # 9.
PROJECT PLANNING & MANAGEMENT Brittany Hamilton. PROGRESS TRACKING Do we understand customer’s needs? Can we design a system to solve customer’s problems.
PLANNING AND MANAGING THE PROJECT CODY STANISH. 3.1 TRACKING PROGRESS Do you understand the customer’s needs? Can you design a system to solve customer’s.
Copy of the slides: (will also be put on the esse3 website)
Configuration Control (Aliases: change control, change management )
Informatics 43 – April 26, Announcements Apply to be an AppJam+ Summer Mentor! AppJam+ Partners with local universities and Colleges to recruit.
Slide 3.1 © The McGraw-Hill Companies, 2002 SOFTWARE LIFE-CYCLE MODELS.
Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.
Advanced Software Engineering Dr. Cheng
Information Systems Development
Copy of the slides: (will also be put on the esse3 website)
Introduction to Systems Analysis and Design
CS 577b: Software Engineering II
Pragmatics 4 Hours.
RISK MANAGEMENT.
Lecture 0 Software Engineering Course Introduction
CS4311 Spring 2011 Process Improvement Dr
Software Life Cycle “What happens in the ‘life’ of software”
Information Systems Development
MBI 630: Systems Analysis and Design
Software Development Process
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

Project & Risk Management For next class -- Pressman: 3, , 5.8, , 6.6 Introductions Software Development Processes Software Maturity Models Risk Management Project Management

Introduce Yourselves Name Game Interests Team or … Still Looking for a Team?

Software Development Processes Waterfall Process Prototyping / RAD Incremental Development

Software Maturity Models SEI Capability Maturity Model IBM STL’s Maturity Model

Risk Management Sources of Risk Risk Management

Top 10 Sources of Risk 1.Personnel shortfalls. 2.Unrealistic schedules and budgets. 3.Developing the wrong software functions. 4.Developing the wrong user interface. 5.Gold plating. 6.Continuing stream of requirements changes. 7.Shortfalls in externally performed tasks. 8.Shortfalls in externally furnished components. 9.Real-time performance shortfalls. 10.Straining computer science capabilities. Source: Boehm 1991 cited in Pfleeger text.

Three Risk Management Concepts (Rook 1993) Risk impact. Risk probability. Risk control. Source: Rook 1993 cited in Pfleeger text.

Project Management Plan vs. Reality People Management W 5 HH

Typical Project Plan Elements 1.Scope 2.Schedule 3.Team organization 4.Technical description of proposed system 5.Standards, procedures, tools, & techniques 6.Quality assurance plan 7.Configuration management plan 8.Documentation plan 9.Data management plan 10.Resource management plan 11.Test plan 12.Training plan 13.Security plan 14.Risk management plan 15.Maintenance plan Source: Pfleeger text.

The Right-to-Left Schedule

A Capsule Course in Human Relations 1.Five most important words in the English Language: “I am proud of you.” 2.Four most important words: “What is your opinion?” 3.Three most important words: “If you please.” 4.Two most important words: “Thank you.” 5.Least important word: “I.” Source: Robert Woodruff, Retired Chairman, The Coca-Cola Company in Edler text.