1 The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.

Slides:



Advertisements
Similar presentations
Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)
Advertisements

1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Software Project Management
 2004 by SEC Chapter 2 Software Development Process Models.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Waterfall Model H.M.Shahzad MS(CS) from COMSATS Institute of Information Technology, Lahore.
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Reuse and Reusability (Chapter 8 of maintenance text) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Image from
Software Process and Problem Statements CSSE 371, Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 3, 2004.
1 Software Maintenance and Evolution CSSE 575: Session 4, Part 1 Software Maintenance – Big Issues served up, Side order of Reifer Steve Chenoweth Office.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
CS 5150 Software Engineering
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
1 Program Understanding Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
User Documentation (no quiz) Tori Bowman CSSE 375 October 8 th, 2007.
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.
CS 501: Software Engineering
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 IS371 WEEK 8 Last and Final Assignment Application Development Alternatives to Application Development Instructor Online Evaluations.
1 Software Change Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Ref M , 4 - In progress -
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.
DECISION SUPPORT SYSTEM DEVELOPMENT
Maintenance Framework Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Ref M 2.
1 Maintenance Management and Organization Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Maintaining Information Systems Class 27. SDLC Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design.
Acquiring Information Systems and Applications
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
INFO 637Lecture #81 Software Engineering Process II Integration and System Testing INFO 637 Glenn Booker.
Objectives:  To define RAD  Describe RAD as a system development method  List the advantages of RAD as a method  List the disadvantages of RAD  State.
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.

CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 1 Chapter 16 Maintaining Information Systems.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
CHAPTER 13 Acquiring Information Systems and Applications.
QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Module 4: Systems Development Chapter 14: Design And Implementation.
LehighUML Project John Pequeno, Adam Balgach, Sally Moritz & Professor Glenn Blank.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
September 30, 2010COMS W41561 COMS W4156: Advanced Software Engineering Prof. Gail Kaiser
1 Proposal and Observation Handling Ravi Sankrit (User Support Scientist) SSSC May 11, 2011.
1 Maintenance of Documentation and Documentation of Maintenance Quiz 7 Tori Bowman CSSE 375, Rose-Hulman October 1, 2006.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
System Maintenance Modifications or corrections made to an information system after it has been released to its customers Changing an information system.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Software Testing Process
ASUG SAP Adoption Influence Council The focus is on how to increase awareness, adoption and implementation of SAP enhancements that are delivered as part.
CS223: Software Engineering Lecture 16: The Agile Methodology.
1 Software Maintenance and Evolution CSSE 575: Session 4, Part 2 Software Maintenance Process Steve Chenoweth Office Phone: (812) Cell: (937)
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
Public Management Information Systems Implementation and Maintenance Friday, June 10, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
CSE403 Software Engineering Autumn 2001 Gary Kimura Lecture #2 October 3, 2001.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Software Process Models
Information Systems Development
Presentation transcript:

1 The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

2 Today Friday’s lab – How’d it go? Friday’s lab – How’d it go? Project assignments & what to do next – questions? Project assignments & what to do next – questions? Tomorrow’s class – Tori Tomorrow’s class – Tori HW2 – Thurs HW2 – Thurs Maintenance process - this Maintenance process - this

3 Outline Short Review Short Review Maintenance Process Models Maintenance Process Models Quick-fix Quick-fix Boehm’s Boehm’s Osborne’s Osborne’s Iterative Iterative Reuse Reuse

4 Short Review

5 Software Maintenance Framework Components User Requirements User Requirements Organizational Environment Organizational Environment Operational Environment Operational Environment Maintenance Process Maintenance Process Software Product Software Product Maintenance Personnel Maintenance Personnel

6 Maintenance Process (extended to real life) Ingredients of such a process (in general, Steve’s experience): Processing requests before starting to work on them, like: Processing requests before starting to work on them, like:  Capturing maintenance requests  Investigating those requests – like testing to verify a bug and decide how hard to fix it  Deciding the time / cost to do, getting customer ok  Prioritizing requests – versus other requests!  Assigning to a sub-team to do Coding and documenting (as per standards) Coding and documenting (as per standards) Testing with various configurations, other legacy code issues Testing with various configurations, other legacy code issues Deciding to send it out (special, or in which sub-release) Deciding to send it out (special, or in which sub-release)

7 An example… Note the amount of “pre-fixing” & other communication activity! Note the amount of “pre-fixing” & other communication activity! From nance_process.asp. nance_process.asp

8 Another example… Ditto… Ditto… From

9 Basic Strategies for Software Enhancement (one more review topic) New versions coming out at regular intervals New versions coming out at regular intervals Ongoing (technical) support – between or instead of releases Ongoing (technical) support – between or instead of releases

10 The Theoretical Maintenance Process Models Varying sophistication…

11 Quick-Fix Advantages Advantages Fast Fast Can be useful for small projects Can be useful for small projects Disadvantages Disadvantages Little or no documentation Little or no documentation Any design becomes less useful over time Any design becomes less useful over time

12 Boehm’s Advantages Advantages Controlled process Controlled process Emphasis on feedback Emphasis on feedback Disadvantage Disadvantage Slower than quick-fix Slower than quick-fix

13 Osborne’s Advantages Advantages Involves all life- cycle phases Involves all life- cycle phases Documentation is updated Documentation is updated Disadvantages Disadvantages Complicated Complicated Lots of Overhead Lots of Overhead

14 Iterative Advantages Advantages Relatively simple Relatively simple Allows for analysis Allows for analysis Disadvantage Disadvantage Management decisions are not explicitly included Management decisions are not explicitly included Appears informally to be on a tilt! Appears informally to be on a tilt!

15 Reuse Advantages Advantages Can use components from other projects Can use components from other projects Code is modular Code is modular Disadvantages Disadvantages Overhead in designing for reuse Overhead in designing for reuse

16 Quiz Exercise! Do in small groups…

17 Steve’s alternative Maintenance process model… Self-improvement, a 12-step approach (only 6 shown): Self-improvement, a 12-step approach (only 6 shown):