The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

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.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Ch 3 System Development Environment
W5HH Principle As applied to Software Projects
THE ABILITY OF IT PROJECT MANAGER. Learning Objectives Defining project management The importance of IT project management Skills for a successful project.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Chapter 21 Project Management Concepts
June 1, 2004Computer Security: Art and Science © Matt Bishop Slide #18-1 Chapter 18: Introduction to Assurance Overview Why assurance? Trust and.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
CHAPTER 9: LEARNING OUTCOMES
Project Management Concepts
Software Engineering Lecture No:12. Lecture # 7
Chapter 1 The Systems Development Environment
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Project Management Fundamentals Project Organization and Integration
Advanced Project Management PM Processes and Framework
The Software Development Life Cycle: An Overview
Project Management: Madness or Mayhem
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Comp 245 Data Structures Software Engineering. What is Software Engineering? Most students obtain the problem and immediately start coding the solution.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Project Management: Still More Art Than Science Presented By Donald W. Larson AC Bronze, CL June 6, 2007.
Project Management Project Management involves the planning, monitoring, and control of the people, process, and events that occur as software evolves.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
CSEB233: Fundamentals of Software Engineering
MSF Overview (Microsoft Solutions Framework) Eran Kolber Vice President – LIH Ltd Regional Director – Microsoft Product Management Advisor – MSF Development.
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 3 Project Management Concepts
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Software Project Management By Deepika Chaudhary.
PROJECT MANAGEMENT FUNDAMENTALS Page 2 Why Project Management? Current Issues: n Complex nature of business today — More cross-functional efforts — Need.
1 Requirements Management - General concepts - Noureddine Abbadeni King Saud University College of Computer and Information Sciences Based on “Software.
Lecture 16: Chapter 24 Project Management Concepts
PROJECT MANAGEMENT CONCEPTS. The Management Spectrum The key concept behind the an effective software engineering process is the management spectrum.
Project Management For the Non Project Manager 1.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
Project Management Concepts By: Sohaib Ejaz Lecturer,UoS.
Information System Project Management Lecture three Chapter one
Chapter : Project Management Concept
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
Programming Techniques Lecture 15 Project Management Based on: Software Engineering, A Practitioner’s Approach, 6/e, R.S. Pressman Lecture 4 An Introduction.
Interacting with consumer Software Engineering. So far… What is Software Engineering? Different software process models waterfall, incremental, spiral.
Chapter : Project Management Concept
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Software Quality Assurance. Software Quality Software quality is defined as the quality that ensures customer satisfaction by offering all the customer.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Project Management
INTRODUCTION: Project management involves the planning, monitoring, and control of the people, process, and events that occur as – software evolves from.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 4 Supplementary Slides for Software Engineering: A Practitioner's.
Slide #18-1 Introduction to Assurance CS461/ECE422 Fall 2008 Based on slides provided by Matt Bishop for use with Computer Security: Art and Science.
1 Project management Organising, planning and scheduling software projects.
Software Project Management
Assistant Professor of Computer Science Washington State University
Software engineering Lecture 21.
Chapter 3 Project Management
SE 3800 Note 10 Project Management
Introduction to Software Engineering
Chapter 31 Project Management Concepts
Software Project Management
Presentation transcript:

The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program

Last Time Key Ideas and Terminology of Software Engineering Phases of the Software Development Life Cycle Software Process Models Introduction to the Microsoft Solutions Framework (MSF) Introduction to the Rational Unified Process (RUP)

Session 2: Agenda Project Management Concepts The Schwan’s Information Services Deliverables Guide Initial Statement of Work Project Management Techniques Project Management in MSF and RUP

The Four P’s Effective project management focuses on People Product Process Project In that order!

People Software Development is an intensely human endeavor. The Players Senior Managers Project or Technical Managers Practitioners Customers End Users

The Project Manager Skills needed include Team Building Organization Innovation Problem Solving Discernment Communication Must plan, motivate, organize and control the development team

Where do they come from? The Software Engineering Institute has developed a People Management Capability Model (PM-CMM) “to enhance the readiness of software organizations to undertake increasingly complex applications by helping to attract, grow, motivate, deploy and retain the talent needed to improve software development.” Curtis, B., et al., People Management Capability Model, Software Engineering Institute, 1994

Product At the beginning of a project a manager is faced with developing a plan but has little or no solid information on which to base the plan Analysis takes time Requirements can be fluid The first management activity should always be the determination of software scope.

Scope Context How does it fit in and what are the constraints? Information Objectives What output is required? What input is required? Function and Performance How is the input transformed into output by the software?

Project Failure In 1998, industry data indicated that 26% of software projects failed outright. Another 46% experienced significant cost and schedule overruns. Reel, J.S. “Critical Success Factors in Software Projects”, IEEE Software, May, 1999

Factors Contributing to Failure 10. Team members lack appropriate skills 9. Users are resistant 8. Chosen technology changes 7. Sponsorship is lost 6. Deadlines are unrealistic

Factors (continued) 5. Managers avoid best practices 4. Changes are poorly managed 3. Software people didn’t understand customers needs 2. Project is ill-conceived in the first place 1. The project scope is poorly defined

Process Requirements analysis and definition System design Program design Program Implementation Unit testing Integration testing System testing System delivery Maintenance

Process Activity Organization Activities in a project should be organized to produce tangible outputs by which progress can be measured Milestones are the end-points of process activities Deliverables are project results delivered to customers The waterfall process model allows for the straightforward definition of progress milestones

Initial Statement of Work The objective of the Initial Statement of Work is to bring together information from the Project Scoping Phase and get approval from the customer to proceed with Analysis.