Fifteenth Lecture Hour 10:30 – 11:20 am, Sunday, September 16 Tailoring the Process (from Chapter 14 of Royce’ book)

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Software Project Management Peking University Fall Semester, 2001.
Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good.
RUP/UP Software Development Method Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
Chapter 2 The Software Process
Last Class Meeting Final Examination.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Iterative Process Planning
Rational Unified Process
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Iterative development and The Unified process
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
COMP 350: Object Oriented Analysis and Design Lecture 2
Software Project Management By Assistant Prof. Samana Zehra
Chapter 6– Artifacts of the process
Chapter 14- tailoring the process
Chapter : Software Process
Project management DeSiaMore 1.
Sixteenth Meeting 6:30 – 9:20 pm, Thursday, September 20, 2001 Review - Looking Forward (from Part IV, Chapter 15 of Royce’ book) Final Examination.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
HANDLED BY Ms.k.CHITHARTHANI L/IT. Aim: To present the concept regarding how the sotware projects are planned, monitored and controlled. Objective: 
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Third Hour Lecture 10:30 – 11:20 am September 8 Improving Software Economics (continuing from Chapter 3 of Royce’ book)
Chapter – 9 Checkpoints of the process
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Iterative process planning. Overview Introductory Remarks 10.1 Work breakdown structure 10.2 Planning Guidelines 10.3 The cost & Schedule estimating process.
Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Second Hour Lecture 9:30 – 10:20 am, September 8, 2001 Evolution of Software Economics Improving Software Economics (from Chapters 2 and 3 of Royce’ book)
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 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)
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Course Introduction CEN 5016 Software Engineering Dr. David A. Workman School of EE and Computer Science January 9, 2007.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management 1/30/2016ICS 413 – Software Engineering1.
1 11/2004 – N.Campanis for MPUG Western NY Chapter Working Session Nick Campanis Presented to MPUG – Western NY Chapter Working Session November 10, 2004.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Rational Unified Process Fundamentals Module 5: Implementing Rational Unified Process Rational Unified Process Fundamentals Module 5: Implementing Rational.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Project management (2) By: Zhou Chunlin School of Tourism, Conference and Exhibitions Henan University of Economics and Law.
TK2023 Object-Oriented Software Engineering
Introduction to Software Engineering
(from Chapter 14 of Royce’ book)
Presentation transcript:

Fifteenth Lecture Hour 10:30 – 11:20 am, Sunday, September 16 Tailoring the Process (from Chapter 14 of Royce’ book)

Review –The Four Parts of the Course Software Management Renaissance –The conventional software management process. –Five improvements to make the waterfall process work. A Software Management Process Framework –Phases –Artifacts –Workflows –Checkpoints Software Management Disciplines –Planning –Organization –Automation –Process control and instrumentation –Tailoring Looking Ahead –Modern project profiles –Next-generation software economics –Modern process transitions

Topics for Today Process Discriminants for Tailoring Small-Scale Project versus Large-Scale Project

Two Primary Dimensions of Process Variability

Priorities for Tailoring

Project Scale Management is more important in the large projects than in the small projects. –Large projects have numerous mundane jobs, especially in the overhead workflows, and more communications. –The probability of recruiting, maintaining, and retaining a large number of exceptional people is small. The number of people needed is more important than the project cost for tailoring the project. Size is the most important parameter in the effort formula (generally, lines of source code) and in determining project scale and the number of people needed.

Process Discriminators – Project Size

Process Discriminators – Stakeholder Cohesion

Process Discriminators - Flexibility

Process Maturity

Architecture Risk

Domain Experience

Small Versus Large Projects

Workflow

Key Discriminators for Success Design is key for both small and large projects. –Small commercial projects – good design provides good marketability and good profits. –Large projects – good design provides for predictable, cost-efficient construction. Management. –Most important for large projects where consequences of planning and resource errors can be catastrophic. Deployment. –Most important in small projects where there is a large and diverse customer base.

Artifacts

Assignment for Next Class Meeting Read Chapters 14 of Royce’ book, on tailoring the process. –Learn and discuss the dimensions and priorities for tailoring software projects. –Learn and discuss the differences in tailoring for large, contract projects versus small, commercial projects. –Prepare for in-class final exam which covers Chapters 9-14 of Royce’ book.

Sample Final Exam Do the 7 questions as indicated from the list below. Questions to answer: __, __, __, __, __, __, __. –1. Discuss briefly the four major milestones of a modern software development process. –2. Discuss briefly the primary purpose of each of the four major milestones. –3. Discuss briefly the six topics of periodic status assessment reviews. –4. Discuss briefly the similarities and the differences of top-level organization of a conventional WBS and the top-level organization of a modern WBS. –5. Discuss briefly the similarities and the differences between the four steps for a top-down cost and schedule estimate and the three steps for a bottom-up cost and schedule estimate. –6. Discuss briefly the similarities and the differences of the contents of the iterations in each of the four development phases.

–7. Discuss briefly the similarities and the differences between the Line-of.-Business organization and the Software Project organization. –8. Discuss briefly the responsibilities of the software management organization. –9. Discuss briefly the types of automation tools which should be used. –10. Discuss briefly the elements of organization policy. –11. Discuss briefly the elements of organization environment. –12. Discuss briefly the pros and cons of extension to the stakeholder environment. Sample Final Exam (cont’d)

–13. Discuss briefly the three core management metrics. –14. Discuss briefly the four core quality metrics. –15. Discuss briefly the three primary causes of excessive personnel attrition. –16. Discuss briefly the dimensions and priorities for tailoring software projects. –17. Discuss briefly the differences in tailoring for large, contract projects versus small, commercial projects. –18. Discuss briefly what you have learned in this course about software project management.