1 Maintenance Management and Organization Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.

Slides:



Advertisements
Similar presentations
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Advertisements

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
For a Good User Experience UX Design Goals, Methods, Tools & Tales William Washington | Washington Kevin Makice| Indiana Kuali Student UX.
Reuse and Reusability (Chapter 8 of maintenance text) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Image from
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
1 CSSE 477: Swre Arch – This year’s course… Steve Chenoweth Tuesday, 11/8/11 Week 10, Day 2 Right – Sunset at the Louvre, in Paris From
The Software Team CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 7, 2004 In the book – This is Ch 4.
1 Software Maintenance and Evolution CSSE 575: Session 1, Part 1 Course Introduction Steve Chenoweth Office Phone: (812) Cell: (937)
1 Team Skill 4 - Team Skill 5 - Scope Refining the Systems Definition (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
1 Program Understanding Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Week 10 CSSE 375 Steve Chenoweth & Everybody. Today Get back Exam 2 This week’s schedule – this Reflection on the course Talk about final assignment Decide.
1 Maintenance Metrics and Measures (M 12) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.
Info1409 De Montfort University1 Lecture 4 Analysing the Business Case (1) System Users and their needs Systems Analysis & Design Academic Year 2008/9.
1 Course Intro Construction & Evolution CSSE 375 Steve Chenoweth.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
1 Software Change Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Ref M , 4 - In progress -
1 The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Team Skill 6 - Building The Right System Part 1: Applying Use Cases (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
1 Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman.
1 Detailed Design Representations (Chapter 9 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
CS351 - Software Engineering (AY2005)1 What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects.
Slide 1 Understanding Interaction, Users and Interfaces and Designing for Collaboration and Communication (Chapters 2-5 of Interaction Design text) CSSE.
Maintenance Framework Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Ref M 2.
Content Management Systems A content management system is software that loads on your web host’s server and manages all content on your web site dynamically.
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
SYSE 802 John D. McGregor Module 0 Session 1 Course Introduction.
Additional Unit 2 Lecture Notes New Instructional Design Focus School of Education Additional Unit 2 Lecture Notes New Instructional Design Focus School.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Module CC3002 Post Implementation Issues Lecture for Week 2 AY 2013 Spring.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Lecture 1Software Engineering1 (Trimester I Session 2002/2003) Lecturer / Tutor Name : Mr. R. Logeswaran
Project Focus Academy April 10, 2006 iVocalize Session #1 Click the ALL tab Add a comment in the text block, introducing yourself, your school and your.
CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Design Process for Architecture. Architectural Lifecycle Not all lifecycle plans support Architecture! It is hard to achieve architecture based design.
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
Project Management Michael L. Collard Department of Computer Science Kent State University.
05 Jul 2006CSE403, Summer'06, Lecture07 Administrivia Informal feedback meetings with LCO groups FantasySportsLeague: still to come today Individual assignment.
Quality Assurance Plans CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology April 6, 2007.
Organizing Your Information Chapter 7. Chapter 7 Contents Understanding Three Principles for Organizing Technical Information Using Basic Organizational.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Project Management Basics. 2 Please introduce yourself…  Name  Business Unit / Function / Process  Current Project / Process  Team Size  Ice Breaker.
Seasonal Adjustment E-learning tool Pilar Rey del Castillo Eurostat B1 Quality, Methodology and Research.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
Software Reuse Course: # The Johns-Hopkins University Montgomery County Campus Fall 2000 Lecture # 2 - September 14, 2004.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Proposal Template Project Based Learning Exercise Mehr 1386 Edmond Zahedi.
Unit 2 Computer Systems. The aim of this unit is to enable learners to:  Understand the components of computer systems and  Develop the skills needed.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Advanced Software Engineering Dr. Cheng
HRM 350 MART Successful Learning/hrm350mart.com
Chapter 18 Maintaining Information Systems
eLearning Approaches It’s about Time
The Development of Information Systems Chapter 8 page 348+
CMGT 445 Competitive Success/snaptutorial.com
CMGT 445 MASTER Lessons in Excellence--cmgt445master.com.
CMGT 445 Education for Service/snaptutorial.com
CMGT 445 Teaching Effectively-- snaptutorial.com.
Testing Services.
Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
Overview of BSSE at Rose-Hulman Institute of Technology
Presentation transcript:

1 Maintenance Management and Organization Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

2 Review: Software Maintenance Framework Components User Requirements Organizational Environment Operational Environment Maintenance Process Software Product Maintenance Personnel

3 Review: Examples of Software Enhancement New versions coming out at regular intervals Ongoing (technical) support

4 Maintenance Management M: Ch 10 It’s a job you’re likely to have

5 What could possibly go wrong? Here you are, arriving at work…

6 Greatest Management Issues Motivation/Turnover Rewards Supervision Assignment Patterns Recognition Career Structure Resources – “By the time we get the hardware, it’s too late to do the project” – Michael Blumenthal, former CEO, Burroughs Domain Knowledge – Who gets put in charge?

7 Maintenance Plan (What you’re doing tonight!) Done by the organization who will be doing the maintenance Should be started very early in the development life cycle Should address all aspects of the maintenance framework Sample Template (by Pigoski) is at (maybe) Your template for tonight – See course web page

8 Maintenance Organization Right - A maintenance organization structure, from m/planning- scheduling.htm. m/planning- scheduling.htm

9 Team Organization Models (different from text) Who does Maintenance? Solution 1: Development Team Solution 2: Separate Maintenance Organization Who does Quality Assurance? Solution 1: Same people as do maintenance Solution 2: Separate Quality Assurance group How does the type of maintenance (e.g. corrective) affect this? How does the type of enhancement (if applicable) affect this?

10 Maintenance Organization Exercise ( Optional)