SE 470 Software Development Processes James Nowotarski 2 June 2003.

Slides:



Advertisements
Similar presentations
Project Management with VIVA PPM Tool (Project Portfolio Management)
Advertisements

Gwinnett Teacher Effectiveness System Training
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
[Title of meeting] [Name of sponsor] [Date] For guidance on working with PowerPoint and reformatting slides, click on Help, then Microsoft PowerPoint Help,
QUALITY ASSURANCE IMPROVEMENTS CURTIN UNIVERSITY LIBRARY Curtin University is a trademark of Curtin University of Technology CRICOS Provider code 00301J.
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)
GAI Proprietary Information
James Nowotarski 13 April 2004 IS 553 Advanced Systems Development Practices.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
IS 421 Information Systems Analysis James Nowotarski 11 November 2002.
Capability Maturity Model (CMM) Done By :Delayel Alhajeree.
IS 421 Information Systems Analysis James Nowotarski 4 November 2002.
James Nowotarski 11 May 2004 IS 553 Advanced Systems Development Practices.
March 22, 2004CS WPI1 CS 509 Design of Software Systems Lecture #9 Monday, March 22, 2004.
Iterative development and The Unified process
Project Management Methodology (PMM)
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
SE 470 Software Development Processes James Nowotarski 19 May 2003.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
SE 470 Software Development Processes James Nowotarski 28 April 2003.
Chapter 8: Development of Business Intelligence
QS 702 Phase II: Encouraging the Integration of Technology Into Higher Education.
The Evergreen, Background, Methodology and IT Service Management Model
COMPGZ07 Project Management Presentations Graham Collins, UCL
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Quality Connection 2002, Helsinki Poznan University of Technology Poznan,
Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.
THE ROLE OF PROCESS IN SOFTWARE QUALITY By K.KARTHIKEYAN.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
The Challenge of IT-Business Alignment
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Epiphany Partners Corporation HealthTechNet ClerePath TM Solution July 21, 2006.
IS 556 Enterprise Project Management Spring 2008 Instructor – Dr. Olayele Adelakun Lecture 1.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
CPSC 2150 August 21, Chapter 1 Object Oriented Software Development This is an introductory course In this chapter we will look at 3 topics Challenges.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Rational Unified Process Fundamentals Module 5: Implementing RUP.
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)
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Project Management 6e..
Testing Maturity Model (TMM). Introduction For the past decade, the software industry has put substantial effort in improving the quality of its products.
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.
THE DILEMMA BETWEEN SOFTWARE ENGINEERING AND SYSTEMS ANALYSIS & DESIGN MOHAMMAD A. ROB MANAGEMENT INFORMATION SYSTEMS UNIVERSITY OF HOUSTON-CLEAR LAKE.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Introduction to ITIL and ITIS. CONFIDENTIAL Agenda ITIL Introduction  What is ITIL?  ITIL History  ITIL Phases  ITIL Certification Introduction to.
44222: Information Systems Development
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Web Applications and Services.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
Lecture 15 Chapter 8 Managing IT Project Delivery.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Systems Development Process and Methodologies Dr. T. Ravichandran.
Chapter Objectives To understand the operational environment in which you execute your project To understand the need and role of oversight in managing.
Proposed Software Development Process
Employee engagement Delivery guide
Topic 1: Introduction to the Module and an Overview of Agile
LEARNING & DEVELOPMENT STRATEGY: PROCESS OVERVIEW
Presentation transcript:

SE 470 Software Development Processes James Nowotarski 2 June 2003

Course Map Overview. Introduction. History Content. Rational Unified Process. Extreme Programming Implementation. Tools, Training, Roles. CMM, Metrics. Selection & Evaluation Briefings (Term Papers) Assignments Quizzes Week Memorial Day

Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

Assignment 4 - Medco Breadth GradeB Observations+Addresses (in varying levels of detail) the major phases of the development life cycle: Analysis Design Development Testing Deployment Maintenance +At least mentions project management activities (misnamed “Project Plan”), though no further detail is provided -Does not address: Architecture Conversion planning, preparation, or execution Development environment Various facets of project management (e.g., risk management) QA

Assignment 4 - Medco Depth GradeD Observations+Provides high-level view of the process + Includes rudimentary deliverable flow -Need 1-2 additional levels of detail to ensure common understanding. Too much is left to interpretation. -Other than rectangle, no further detail on project planning/mgmt. In particular, more needed on how multiple releases will be managed simultaneously

Assignment 4 - Medco Alignment with Best Practices GradeC Observations+Addresses (to some extent) the following best practices: Iterative development Visual modeling Reviews Testing User involvement Deployment -Does not address: Architecture Component-based development Requirements management Change control

Assignment 4 - Medco Conceptual Integrity GradeA Observations+No major inconsistencies found + Process is basically vanilla structured analysis/design (proven, well understood), limits exposure to integrity issues -When there is not much depth, it is relatively easy to maintain conceptual integrity

Assignment 4 - Medco Fit with Project and Organization GradeF Observations+Process is at least documented, which it had not been before -This is a complex, mission-critical system; this methodology is far too sketchy for a project of this magnitude - Reliance on outside contractors makes it even more important to have a better document process -Intricacies of delivering releases every 2 months need to be planned out in further detail -This process seems to reflect an informal, entrepreneurial culture; but organization is growing/maturing and needs “methodology for grown-ups” -- the stakes are higher

Assignment 4 - Medco Summary Grade and Recommendations GradeD RecommendationsConsider replacing data flow diagrams with use cases Provide additional detail for existing coverage areas – Possibly use outside contractor/consultant Add coverage for key areas: – Project management – Development environment – Architecture – Conversion – QA process Ensure project team is trained on the methodology

Topic Duration Quiz #410 minutes Assignment 4 Recap15 minutes Term Paper Presentation #135 minutes *** Break15 minutes Term Paper Presentation #235 minutes Term Paper Presentation #335 minutes Housekeeping/Wrap-up?? minutes Today’s agenda

Extra Slides

CMM Levels Repeatable (2) Repeatable (2) Defined (3) Defined (3) Managed (4) Managed (4) Optimized (5) Optimized (5) Initial (1)

Key process areas (KPAs) Maturity levels Process capability Indicate Key process areas Contain Key practices Contain Goals Achieve

Appraisal Methods Software Process Assessments (SPA) –Performed in open, collaborative environment –Focuses on improving the organization’s software process –Now called CMM-Based Appraisal for Internal Process Improvement (CBA-IPI) Software Capability Evaluations (SCE) –Performed in a more audit-oriented environment –Focuses on identifying risks associated with a contractor –Team’s recommendation will help select contractors or set fees

CMM Issues in the Real-World “Level envy” Areas not addressed –Business strategy and linkage to IT –Operations, help desk, support –Management of the IT human resource –Application portfolio –Tools –Risk Many question whether it is worth the effort to pursue levels 4 and 5

CMM Maturity Profile 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% Initial 19.3% Repeatable 43.2% Defined 23.4% Managed 7.3% Optimized 6.8% % of Organizations August 2002 Based on assessments from of 1124 organizations

Time to Move Up to to to to 5 Largest observed value that is not an outlier 75th percentile Median (50th percentile) 25th percentile Smallest observed value that is not an outlier Recommended time between appraisals (18-30 mos) Number of months to move to next maturity level