CEN 4021 Software Engineering II Instructor: Peter Clarke Spring 2005.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

SDLC Software Development Life Cycle. SDLC Acronym for system development life cycle. Acronym for system development life cycle. Is the process of developing.
Project Management Based on Sommerville’s “Software Engineering” textbook.
Project Management.
SAK5102 SOFTWARE EVALUATION Semester II 2008/ credits Tuesday 6.30 pm – 9.30 pm (BK1) Assoc. Prof Dr. Abdul Azim Abd Ghani 1.
Software Engineering Chapter 2: Software Project Management
Week 1 intro to PM Project Management Introduction to Project Management and the Software Development Lifecycle Week 1 Winter quarter 1/7/02 SOS.
School of Computing, Dublin Institute of Technology.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Software Project Transition Planning
Software Engineering General Project Management Software Requirements
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 COMP201 Project Management.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
7M701 1 Software Engineering Project Management Sommerville, Ian (2001) Software Engineering, 6 th edition Ch. 4
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
Chapter 17 Acquiring and Implementing Accounting Information Systems
Chapter 3 Project Management
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
S/W Project Management
Project Management Chapter 5, PG 92. Introduction Why is software management particularly difficult?  The product is intangible Cannot be seen or touched.
PGD-1303 Software Project Management?. What is software? Software  Computer programs and associated documentation Documentation includes  requirements.
Software Project Management Introduction to Project Management.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Software System Engineering: A tutorial
Instructor: Peter Clarke
CEN st Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi What.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project.
Chapter 13 Software Project Management. Project Management “Process” Why do we need project management? Why can’t we just follow one of the software development.
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Software Engineering 1 Some Definitions Lesson 2.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Software Acquisition and Project Management Lesson I: Introduction.
Request for Proposal (RFP)
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Microsoft Visual Basic 2010: Reloaded Fourth Edition Overview An Introduction to Programming.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
Organization of Process Review Class 15 Processes –Configuration Management –Introduction and Education CEN 4021 Class 16 – 03/07.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Software Engineering (CSI 321) Introduction. Introduction Course Title: Software Engineering Course Code: CSI-321 Credit Hours: 3 Section: 1 2.
1 test10b Software Testing Necessary to measure and certify quality in software.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
IS Development Methodology
Project management assignment, Spring 2017
Introduction to System Analysis and Design
Software Engineering and Best Practices
Software Engineering (CSI 321)
Definitions.
Introduction to Problem Solving
CEN 4021 Software Engineering II
Software Quality Assurance 2015
PPT4: Requirement analysis
The Software Development Process
What is Software Engineering?
Chapter 13: Software Project Management
SOFTWARE ENGINEERING CS-5337: Introduction
Presentation transcript:

CEN 4021 Software Engineering II Instructor: Peter Clarke Spring 2005

CEN 4021 Class /102 Course Introduction Syllabus Project Questions What is Software Project Management?

CEN 4021 Class /103 What is Software Project Management (SPM)? Software project management is concerned with ensuring that, for a software project, the most appropriate process and methodologies are chosen, the desired internal product structure is attained and the external product properties are achieved. In addition, the project management constraints of schedule and resources must be met. [Tsui ’04] (5/5 points)

CEN 4021 Class /104 SPM Terminology Software artifact – A unit of material, in the form of a document, presentation, or code, that is developed as a part of, or as a contribution to, the final solution to the users. Code – A set of instructions to a device, possibly a computing device, to perform a desired set of instructions. Software – A set of software artifacts that includes code, i.e., software includes the instruction codes and data necessary to accomplish some task on a computer.

CEN 4021 Class /105 SPM Terminology Software engineering – the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software; that is, the application of engineering to software. (Source: IEEE Std , IEEE Standard Glossary of Software Engineering Terminology)

CEN 4021 Class /106 SPM Terminology Software development process – the sequence or order of the activities, along with the entrance and the exit criteria of these activities. Software development life cycle – A set of transformations, starting with requirements, that converts each incoming software artifact into an artifact closer to the final result, until the final set of artifacts that satisfy the requirements are met. (USDP?)

CEN 4021 Class /107 SPM Terminology Software product life cycle – A period during which a software artifact is initially developed, supported, revised through multiple development life cycles, and finally unsupported and/or taken out of the market. Why software project management?

CEN 4021 Class /108 Why SPM? Why software project management? Cost, cost, cost!!! $250 Billion is spent each year on approx. 175,000 information technology (IT) application projects. 31% of all the above projects will fail and 53% of the projects will overrun the original cost estimates i.e. $81 billion wasted or canceled projects. (Page 1 of text) US. Standish Group’s Chaos report.

CEN 4021 Class /109 Why is SPM difficult? 1. The product is intangible: Software cannot be seen or touched. It is difficult to see and measure progress. 2.There are no standard software processes. –S/w process varies from one organization to another. –Effect are readily seen when the s/w project is part of a wider systems engineering project.

CEN 4021 Class /1010 Why is SPM difficult? 3. Large software projects are often ‘one- off’ projects. Usually s/w projects differ in some ways from previous projects. Experience gained on one project may not work for another project. Technological changes in computers and communications can make a manager’s experience obsolete. [Sommerville ’04]

CEN 4021 Class /1011 Phases of SPM The SPM management activities include: Proposal writing Project planning and scheduling Project cost Project monitoring and reviews Personnel selection and evaluation Report writing and presentations

CEN 4021 Class /1012 Phases of SPM The previous management activities are captured using the acronym POMA: –Planning –Organizing –Monitoring –Adjusting