Contents Introduction Requirements Engineering Project Management

Slides:



Advertisements
Similar presentations
Configuration management
Advertisements

Software change management
Configuration management
Configuration Management
Configuration Management
Chapter 14 Maintaining Information Systems Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Software Configuration Management
Software Evolution Managing the processes of software system change
1 Software Configuration Management METU Computer Engineering CEng 492 Spring'2004.
Lecturer: Dr. AJ Bieszczad Chapter Lehman’s system types S-system: formally defined, derivable from a specification P-system: requirements based.
Contents Introduction Requirements Engineering Project Management Software Design Detailed Design and Coding Quality Assurance.
Contents Introduction Requirements Engineering Project Management
PVK-HT061 Contents Introduction Requirements Engineering Project Management Software Design Detailed Design and Coding Quality Assurance Software Maintenance.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 29 Slide 1 Configuration management.
The Waterfall Model A Case Study
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
Software evolution.
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.
Configuration Management
1 CMPT 275 Software Engineering Revision Control.
Software Configuration Management CSC-532 Chandra Shekar Kandi Chandra Shekar Kandi.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
Software maintenance Managing the processes of system change.
Software Re-engineering
This chapter is extracted from Sommerville’s slides. Text book chapter
Software Configuration Management (SCM)
Software Engineering Modern Approaches
Maintaining Information Systems Modern Systems Analysis and Design.
Software Configuration Management
Software Configuration Management
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 29Slide 1 Configuration management l Managing the products (code and documentation) of.
Software Engineering CS3003 Lecture 3 Software maintenance and evolution.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 29Slide 1 Configuration management l Managing the products of system change.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
1 Software Development Configuration management. \ 2 Software Configuration  Items that comprise all information produced as part of the software development.
Configuration Management (CM)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 29 Slide 1 Configuration management.
Creator: ACSession No: 16 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 (Software Quality) Configuration Management CSE300 Advanced.
Chapter 11 Maintaining the System System evolution Legacy systems Software rejuvenation.
Software Quality Assurance
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
1 Brief Introduction to Revision Control Ric Holt.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Chapter 5: Software Re-Engineering Omar Meqdadi SE 3860 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Configuration Management CSCI 5801: Software Engineering.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
System Maintenance Modifications or corrections made to an information system after it has been released to its customers Changing an information system.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Configuration Management
Software Engineering Lecture 9: Configuration Management.
1 / 14 CS 425/625 Software Engineering Software Change Based on Chapter 27 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed., Addison-Wesley,
CASE Tools and their Effect on Software Quality
Configuration Management
Software Project Configuration Management
Chapter 18 Maintaining Information Systems
Maintenance Issues in Software Engineering
Chapter 18 Maintaining Information Systems
Configuration Management
Managing the System PPT SOURCE : Shari L. Pfleeger Joann M. Atlee.
Maintaining Information Systems (SAD- 18)
Chapter 8 Software Evolution.
Lecture 06:Software Maintenance
Configuration management
Chapter 18 Maintaining Information Systems
Presentation transcript:

Contents Introduction Requirements Engineering Project Management Software Design Detailed Design and Coding Quality Assurance Software Maintenance PVK-HT05

Software Maintenance Process The most expensive part of the software lifecycle! Require- ments Change Request Impact Analysis Release Planning Change Design Implementation Test Release Change PVK-HT05

Ian Sommerville 1995  Software Engineering, 5th edition.

Types of Maintenance Corrective: Focuses on fixing defects Adaptive: Includes all changes to meet the evolving needs of the user and the environment Perfective: perfecting existing functions Preventive: Preventing system performance from degrading to unacceptable levels PVK-HT05

Use of Maintenance Time *See [Schach 97]. **See [Somm 96]. ***See [Pfleeger 98]. PVK-HT05

Maintenance Metrics Control complexity Data complexity Length of identifier names Program comments Coupling Cohesion Degree of user interaction PVK-HT05

Configuration Management New versions of software systems are created as they change For different machines/OS Offering different functionality Tailored for particular user requirements Configuration management is concerned with managing evolving software systems System change is a team activity CM aims to control the costs and effort involved in making changes to a system PVK-HT05

Version and Release Management Invent identification scheme for system versions Plan when new system version is to be produced Ensure that version management procedures and tools are properly applied Plan and distribute new system releases PVK-HT05

Storing Versions Naive: Separate files for each version Version handling by numbering schemes Double Maintenance Problem Solution: One original version plus deltas Shared Data Problem Simultaneous Update Problem Solution: Check-in/check-out mechanism Still a problem: Merging versions PVK-HT05

Tools for Version and Configuration Control General: History- and log-files Hierarchical file systems ... Version Control: Modification tracking Control of development branches Efficient storage and retrieval Access control Merging versions SCCS, RCS, CVS, ... File comparators Patch generators Configuration control: Dependency management and control System creation Integration with version control ... Make, makefile generators, ... PVK-HT05

Software Rejuvenation Redocumentation: static analysis adds more information Restructuring: transform to improve code structure Reverse engineering: recreate design and specification information from the code Reengineering: reverse engineer and then make changes to specification and design to complete the logical model; then generate new system from revised specification and design PVK-HT05