Project management assignment, Spring 2017

Slides:

Advertisements

Similar presentations

CS3773 Software Engineering Lecture 8 Software Planning and Estimation.

Advertisements

So far.. We have covered a) Requirements gathering: observation & interview. b) Requirements specification. c) Requirements validation. d) Design/paper.

Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.

Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.

SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.

Software Process and Product Metrics

Task Analysis is Part of Planning Once we have completed planning on the deliverables and contents of the deliverables, we need to plan out “how to accomplish”

Task Analysis is Part of Planning Once we have completed our plan on what to deliver and the contents of deliverables (via requirements), we need to: plan.

Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.

1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.

After Lesson 6 next is Lesson 13 to fit topic on Software Development SOFTWARE PROJECT MANAGEMENT.

Chapter 6 : Software Metrics

CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.

Function Point Analysis What is Function Point Analysis (FPA)? It is designed to estimate and measure the time, and thereby the cost, of developing new.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.

1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.

Software Engineering SM ? 1. Outline of this presentation What is SM The Need for SM Type of SM Size Oriented Metric Function Oriented Metric 218/10/2015.

Lecture 4 Software Metrics

Chapter 9 Project Management. Introduction Effective project management requires a well-structured project and diligent oversight A well-structured project.

Cost Estimation. Problem Our ability to realistically plan and schedule projects depends on our ability to estimate project costs and development efforts.

Project Planning and Estimation

S/W Project Management Software Project Planning (POMA) Task Analysis.

Software Project Planning Part II. Troutman's Postulates Profanity is the one language understood by all programmers. Not until a program has been in.

SEG3300 A&B W2004R.L. Probert1 COCOMO Models Ognian Kabranov.

Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.

Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.

CSC 480 Software Engineering Lecture 6 September 11, 2002.

Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.

Project, People, Processes and Products Project management skills – schedule, monitoring, risk management, … People management skills – delegation, mentoring,

FUNCTION POINT ANALYSIS & ESTIMATION

Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.

1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.

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

Slide 1 Critical Success Factor : Project Management Project Management is the process of _______ the development of a system with a specified _____ frame.

CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.

CSC 480 Software Engineering Project Planning. Proposal writing Project planning and scheduling Project costing Project monitoring and reviews Personnel.

MADALINA CROITORU Software Engineering week 6 Madalina Croitoru IUT Montpellier.

1 Week 11 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.

INFSY 570 DR. R. OCKER Software Project Planning.

Software cost and effort estimation will never be an exact science. Estimation is very difficult to do, but is often needed Too many variables can affect.

Cost9b 1 Living with Function Points Bernstein and Lubashevsky Text pp

Cost23 1 Question of the Day u Which of the following things measure the “size” of the project in terms of the functionality that has to be provided in.

Ch. 13 Project Management “Process” Why do we need project management? Why can’t we just follow one of the software development process and be left alone?

Introduction To System Analysis and Design

THE FAMU-CIS ALUMNI SYSTEM

Chapter 33 Estimation for Software Projects

Project Cost Management

School of Business Administration

Chapter 5 Software Project Planning

Software Project Sizing and Cost Estimation

Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,

Function Point Analysis

Software Planning

Software Development & Project Management

Introduction to Software Testing

Personal Software Process Software Estimation

More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.

Chapter 3 Managing the Information Systems Project

Chapter 33 Estimation for Software Projects

Software metrics.

Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,

Software Effort Estimation

Chapter 26 Estimation for Software Projects.

Chapter 3 Managing the Information Systems Project

Chapter 3 Managing the Information Systems Project

Chapter 2: Building a System

Chapter 1: Creating a Program.

Chapter 13: Software Project Management

Presentation transcript:

Project management assignment, Spring 2017 Csc 355 Pre-assignment 1 Project management assignment, Spring 2017

Planning Items for assn1 (per POMA) Planning, Organizing, Monitoring, Adjusting Feature list 95%, 80%, [60-70]%, less than that Work effort / timeline / schedule Risk assessment (schedules, resources, personnel) Reliability of imported libraries (resources) Productivity & Stability of personnel (resources) Risk identification, priority, mitigate Test plan How to test features on list?

Textbook project management methodologies Essentials of Software Engineering, 3rd Edition, Tsui, Karam, Bernal Available in Rohrbach Library Textbook project management methodologies that we will not use. They are too big for our projects. COCOMO – Constructive Cost Model, Section 13.3.1 Based on “mode” of development, size of code in lines, & 15 cost-driver factors Function Point External inputs x Complexity weight + External outputs x Complexity weight + External inquiries x Complexity weight + Internal logical files x Complexity weight + External interface files x Complexity weight, each term with its own Complexity weight There are 14 distinct technical complexity factors in the Complexity weight terms Function point appears to be objectively quantifiable for a big system project

Simple Object-Oriented Effort Estimation Page 282 in Section 13.3.1 Estimate number classes C in problem domain (not imported classes) Categorize the User Interface (UI) & assign a weight W No UI 2.0, Simple text-based 2.25, Graphical UI (GUI) 2.5, Complex GUI 3.0 UI-weight classes U = C x W + C T = U x [15,20] Multiply the estimate U by a number P in the range of 15 through 20, where P is an estimate of the number of person-days required to develop a class. Time T is total number of days to develop a product. We will see how accurate these estimates are at the end of semester.

Work Breakdown Structure (WBS), Section 13.3.2 1. Determine external deliverables 2. Identify steps & tasks to produce each; include subtasks 3. Sequence the tasks; identify opportunities for parallel development 4. Estimate effort for each task in units of time 5. Estimate productivity for each person-task (work per unit time) This estimate includes the goodness-of-match of the exact person to the task 6. Compute time for each task (divide value #4 by #5) 7. For each external deliverable, lay out the timeline & label resources assigned to each task See next page

Work Breakdown Structure, Figure 13.4