SOFTWARE ENGINEERING SOFTWARE MAINTENANCE
|
|
- Pamela Corey Owens
- 6 years ago
- Views:
Transcription
1 SOFTWARE ENGINEERING SOFTWARE MAINTENANCE Software maintenance is the process of modification or making changes in the system after delivery to overcome errors and faults in the system that were not uncovered during the early stages of the development cycle. LEARNING OBJECTIVES To study on why maintenance is an issue. To study on reverse engineering and limitations. To organize data. To check what the system does. SOFTWARE MAINTENANCE The IEEE Standard for Software Maintenance (IEEE 1219) gave the definition for software maintenance as The process of modifying a software system or component after delivery to correct faults, improves performance or other attributes, or adapt to a changed environment.
2 Percent of total cost Maintenance Principles Hardware Software Development Maintenance The IEEE/EIA Standard defines maintenance as modification to code and associated documentation due to a problem or the need for improvement. Nature of Maintenance Modification requests are logged and tracked, the impact of proposed changes are determined, code and other software artifacts are modified, testing is conducted, and a new version of the software product is released. Maintainers can learn from the developer s knowledge of the software. Need for Maintenance Maintenance must be performed in order to: Correct faults. Improve the design. Implement enhancements. Interface with other systems. Adapt programs so that different hardware, software, system features, and telecommunications facilities can be used. Migrate legacy software. Retire software
3 Tasks of a maintainer The maintainer does the following functions: Maintain control over the software s day-to-day functions. Maintain control over software modification. Perfecting existing functions. Preventing software performance from degrading to unacceptable levels. Majority of Maintenance Costs Maintenance consumes a major share of software life cycle financial resources. But studies and surveys have shown that over 80% of the maintenance effort is used for non-corrective actions. Quality of software design, construction, documentation, and testing affects software maintenance costs. Evolution of Software Lehman has studied software maintenance and evolution for over 20 years, leading to Lehman s Laws. E.g. increasing complexity as a program is evolved, its complexity increases unless work is done to maintain or reduce it. CATEGORIES OF MAINTENANCE Maintenance can be categorized into the follwing: o Corrective maintenance o Adaptive maintenance o Perfective maintenance o Preventive maintenance Corrective maintenance: Reactive modification of a software product performed after delivery to correct discovered problems. Adaptive maintenance: Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment.
4 Perfective maintenance: Modification of a software product after delivery to improve performance or maintainability. Preventive maintenance: Modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults. KEY TO MAINTENANCE The key to effective maintenance lies in development. Depending upon the development of the product the maintenance of the product is determined. Higher quality less (corrective) maintenance Anticipating changes less (adaptive and perfective) maintenance Better tuning to user needs less (perfective) maintenance Less code less maintenance The distribution of maintenance activities are shown in the figure below: corrective 21% perfective 50% adaptive 25% preventive 4% Major causes of maintenance problems Some of the major factors which causes problem in maintenance is as follows: Unstructured code Insufficient domain knowledge Insufficient documentation
5 The key issues in software maintenance include: Limited Understanding Shift in type of maintenance Impact Analysis Maintainability Alignment with organizational objectives Staffing Process Organizational aspects of maintenance Outsourcing Cost Estimation Specific Measures Limited Understanding The maintainers make changes or corrections to software that they did not write, so they should quickly understand the software. 40%-60% of the maintenance effort is devoted to understanding the software. Comprehension is difficult in the absence of documentation and when the original developers are unavailable. The maintainers must quickly understand the software and should make modifications to overcome the issues in the system. Shift in type of maintenance Shift in type of maintenance over time can be projected as follows: Introductory stage: emphasis on user support. Growth stage: emphasis on correcting faults. Maturity: emphasis on enhancements. Decline: emphasis on technology changes. Impact Analysis The objectives of impact analysis are: Determination of the scope of the change in order to plan and implement the work.
6 Development of accurate estimates of resources needed to perform the work. Analysis of the cost/benefits of the requested change. Communication to others of the complexity of a given change. Maintainability IEEE [IEEE ] defines maintainabiliy as the ease with which software can be maintained, enhanced, adapted, or corrected to satisfy specified requirements and the presence of systematic and mature processes, techniques, and tools helps to enhance the maintainability of a system
Software Maintenance. Main Points. Relative Distribution of Software/Hardware Costs
Percent of total cost Software Maintenance Main Points Why maintenance is such an issue Reverse engineering and its limitations How to organize maintenance Maintenance is very different from development
More informationWHAT DO YOU NEED TO KNOW ABOUT SOFTWARE MAINTENANCE
WHAT DO YOU NEED TO KNOW ABOUT SOFTWARE MAINTENANCE Alain April, A. Abran and R. Dumke Software accounts now for a increasing share of the content of modern equipments and tools, and must similarly be
More informationSoftware Maintenance. (Chapter 14) Relative distribution of Point to ponder #1
Software Maintenance Software Maintenance (Chapter 14) Mark van den Brand Main issues: why maintenance is such an issue reverse engineering and its limitations how to organize maintenance Relative distribution
More informationChapter 6: Software Evolution and Reengineering
Chapter 6: Software Evolution and Reengineering Harald Gall Software Engineering Group www.ifi.unizh.ch/swe/ Universität Zürich Institut für Informatik Ian Sommerville 2004 Software Engineering, 7th edition.
More informationSoftware Engineering & Architecture
Software Engineering & Architecture 10. SOFTWARE EVOLUTION Martin Kropp University of Applied Sciences Northwestern Switzerland Institute for Mobile and Distributed Systems References Based on the PowerPoint
More informationSoftware Maintenance *
OpenStax-CNX module: m14717 1 Software Maintenance * Trung Hung VO This work is produced by OpenStax-CNX and licensed under the Creative Commons Attribution License 2.0 1 Introduction In software engineering,
More informationSoftware Maintenance *
OpenStax-CNX module: m14719 1 Software Maintenance * Trung Hung VO This work is produced by OpenStax-CNX and licensed under the Creative Commons Attribution License 2.0 1 Introduction In software engineering,
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More informationSOFTWARE ENGINEERING IT 0301 Semester V B.Nithya,G.Lakshmi Priya Asst Prof SRM University, Kattankulathur. School of Computing, Department of IT 1
SOFTWARE ENGINEERING IT 0301 Semester V B.Nithya,G.Lakshmi Priya Asst Prof SRM University, Kattankulathur School of Computing, Department of IT 1 School of Computing, Department 2 SOFTWARE CHANGE Software
More informationManaging System Performance
Managing System Performance System performance directly affects users. Centralized operations are easier to measure than complex networks and client/server systems. Various statistics can be used to assess
More informationChapter 9 Software Evolution and Maintenance. Chapter 9 Software evolution
Chapter 9 Software Evolution and Maintenance 1 Topics covered Evolution processes Change processes for software systems Program evolution dynamics Understanding software evolution Software maintenance
More informationOverview of Maintenance. CPRE 416-Software Evolution and Maintenance-Lecture 3
Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3 1 Need to Study Software Maintenance Software Maintenance is the single most expensive activity in software engineering requiring
More informationSoftware Evolution und Reengineering!
Martin Glinz!Harald Gall Herbstsemester 2010 Kapitel 12 Software Evolution und Reengineering! Universität Zürich Institut für Informatik 2010 by Harald Gall. Alle Rechte vorbehalten. Reproduktion, Speicherung
More informationProduct definition, product vision, product life cycle
Product definition, product vision, product life cycle Tommi Mikkonen Dept. Computer Science University of Helsinki, Helsinki. Finland tommi.mikkonen@helsinki.fi www.cs.helsinki.fi Content Product definition,
More informationChapter 16 Software Reuse. Chapter 16 Software reuse
Chapter 16 Software Reuse 1 Topics covered What is software reuse? Benefit and problems with reuse. The reuse landscape Application frameworks Software product lines COTS product reuse 2 Software reuse
More informationTest Workflow. Michael Fourman Cs2 Software Engineering
Test Workflow Michael Fourman Introduction Verify the result from implementation by testing each build Plan the tests in each iteration Integration tests for every build within the iteration System tests
More informationTECHRISK A DECISIONAL FRAMEWORK TO MEASURE TECHNICAL DIMENSIONS OF LEGACY APPLICATION FOR REJUVENATION THROUGH REENGINEERING
TECHRISK A DECISIONAL FRAMEWORK TO MEASURE TECHNICAL DIMENSIONS OF LEGACY APPLICATION FOR REJUVENATION THROUGH REENGINEERING Er. Anand Rajavat 1 and Dr. (Mrs.) Vrinda Tokekar 2 1 Department of Computer
More informationChapter 16 Software Reuse. Chapter 16 Software reuse
Chapter 16 Software Reuse 1 Topics covered The reuse landscape Application frameworks Software product lines COTS product reuse 2 Software reuse In most engineering disciplines, systems are designed by
More informationIntroduction to Software Product Lines Patrick Donohoe Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213
Introduction to Software Product Lines Patrick Donohoe Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 2014 by Carnegie Mellon University Copyright 2014 Carnegie Mellon University
More informationSoftware Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a comple
Estimation for Software Projects 1 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a complex technical project.
More informationThe Open Group Exam OG0-091 TOGAF 9 Part 1 Version: 7.0 [ Total Questions: 234 ]
s@lm@n The Open Group Exam OG0-091 TOGAF 9 Part 1 Version: 7.0 [ Total Questions: 234 ] https://certkill.com Topic break down Topic No. of Questions Topic 1: Volume A 100 Topic 2: Volume B 134 2 https://certkill.com
More informationLeading the Evolution. HSBC Secures International Competitive Advantage
Leading the Evolution Case Study: HSBC HSBC Secures International Competitive Advantage While Driving Down IT Costs Across the Enterprise Challenge Global financial services provider HSBC Group was devoting
More informationSE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics E-mail: Keti@ii.edu.mk What is Software Engineering? SE is the discipline concerned
More informationChapter 4 Software Process and Project Metrics
Chapter 4 Software Process and Project Metrics 1 Measurement & Metrics... collecting metrics is too hard... it's too time-consuming... it's too political... it won't prove anything... Anything that you
More informationMBA BADM559 Enterprise IT Governance 12/15/2008. Enterprise Architecture is a holistic view of an enterprise s processes, information and
Enterprise Architecture is a holistic view of an enterprise s processes, information and information technology assets as a vehicle for aligning business and IT in a structured, more efficient and sustainable
More informationRequirements Engineering: Part I. Software Requirements & Project Management CITS3220
Requirements Engineering: Part I Software Requirements & Project Management CITS3220 The Problems of Requirements What goal(s) are we trying to satisfy? How do we identify the scope and properties of the
More informationPolicy Administration Transformation
Financial Services the way we do it Policy Administration Transformation Helping insurers capture dramatic improvements in time-to-market, product or price leadership and operational excellence The insurance
More information6. Capability Maturity Method (CMM)
WAT IS TE C? 6. aturity ethod (C) Concept: The application of process management and quality improvement concepts to software development and maintenance odel: A model for organizational improvement Guidelines:
More informationCGEIT Certification Job Practice
CGEIT Certification Job Practice Job Practice A job practice serves as the basis for the exam and the experience requirements to earn the CGEIT certification. This job practice consists of task and knowledge
More informationThis chapter illustrates the evolutionary differences between
CHAPTER 6 Contents An integrated approach Two representations CMMI process area contents Process area upgrades and additions Project management concepts process areas Project Monitoring and Control Engineering
More informationE-PROCUREMENT OPERATIONS
E-PROCUREMENT OPERATIONS Post-launch capabilities to ensure your success Introduction: E-procurement operations capabilities that will enable your success Automating the processes your organization uses
More informationUnit-V Chapter-1 PROJECT CONTROL & PROCESS INSTRUMENTATION
Unit-V Chapter-1 PROJECT CONTROL & PROCESS INSTRUMENTATION INTERODUCTION: Software metrics are used to implement the activities and products of the software development process. Hence, the quality of the
More informationPassit4Sure.OG Questions. TOGAF 9 Combined Part 1 and Part 2
Passit4Sure.OG0-093.221Questions Number: OG0-093 Passing Score: 800 Time Limit: 120 min File Version: 7.1 TOGAF 9 Combined Part 1 and Part 2 One of the great thing about pass4sure is that is saves our
More informationINF 3121 Software Testing - Lecture 05. Test Management
INF 3121 Software Testing - Lecture 05 Test Management 1. Test organization (20 min) (25 min) (15 min) (10 min) (10 min) (10 min) INF3121 / 23.02.2016 / Raluca Florea 1 1. Test organization (20 min) LO:
More informationChapter 1. Software Engineering Supporting Processes
Chapter 1 Software Engineering Supporting Processes 1. Introduction to IEEE/EIA Standard 12207.0-1996 IEEE/EIA Standard 12207.0-1996 establishes a common framework for software life cycle processes. The
More informationEnterprise Systems for Management. Luvai Motiwalla Jeffrey Thompson Second Edition
Enterprise Systems for Management Luvai Motiwalla Jeffrey Thompson Second Edition Pearson Education Limited Edinburgh Gate Harlow Essex CM20 2JE England and Associated Companies throughout the world Visit
More informationABB Month DD, YYYY Slide 1
Aldo Dagnino, Will Snipes, Eric Harper, ABB Corporate Research RA Software/SAM WICSA, April 7 th of 2014 Metrics for Sustainable Software Architectures An Industry Perspective Month DD, YYYY Slide 1 Agenda
More informationCrucial Questions Every Wealth Business Should Ask When Defining its Growth Strategy
4 Crucial Questions Every Wealth Business Should Ask When Defining its Growth Strategy Nearly half of financial firms say their current technology isn t strong enough to support their growth plans 1. That
More informationSoftware Quality. Unit 6: System Quality Requirements
Software Quality Unit 6: System Quality Requirements System Requirements Best products, from users point of view, are those which have been developed considering organizational needs, and how product is
More informationSOFTWARE MAINTENANCE PROCESS MODEL AFTER DELIVERY WITH QUALIFIED OUTPUT
SOFTWARE MAINTENANCE PROCESS MODEL AFTER DELIVERY WITH QUALIFIED OUTPUT SALEEM AL-ZOUBI Faculty of Information Technology, Irbid National University E-mail: it@inu.edu.jo Abstract-Software maintenance
More informationAverage Span & Comment Ratio for Maintenance of Model Using Fuzzy Technique
Average Span & Comment Ratio for Maintenance of Model Using Fuzzy Technique *Rupali Malhotra & **Naveen Jindal *Head, Department of Computer Sciences & Engineering, Sat Priya Group of Institutions, Rohtak,
More informationAcquisition Overview: The Challenges
Acquisition Overview: The Challenges Rita Creel Robert J. Ellison June 2007 ABSTRACT: The challenges of acquiring software-intensive systems continue to grow along with the increasingly critical role software
More informationPART THREE: Work Plan and IV&V Methodology (RFP 5.3.3)
PART THREE: Work Plan and IV&V Methodology (RFP 5.3.3) 3.1 IV&V Methodology and Work Plan 3.1.1 NTT DATA IV&V Framework We believe that successful IV&V is more than just verification that the processes
More informationThe Evolution of Analytics
The Evolution of Analytics Ed Colet Capital One Financial Corporation SAS Global Forum, Executive Track Presentation April, 2011 Outline Looking back at the evolution of analytics Standard views, and the
More informationTest Strategies Around the World Winning the War on Bugs Through Strategy
Winning the War on Bugs Through Strategy Test Strategies A test strategy is a general, project-independent pattern for how testing is done The various test strategies discussed here are in use by test
More informationRequirements Engineering
Requirements Engineering Professor Ray Welland Department of Computing Science University of Glasgow E-mail: ray@dcs.gla.ac.uk The Importance of Requirements Identifying (some) requirements is the starting
More information2010 ERP REPORT. Organizational Change Management
2010 ERP REPORT Organizational Change Management LLC. All reserved. No unauthorized reproduction without the author s written consent. All references to this publication must cite Panorama Consulting Group
More informationGathering Network Requirements
Gathering Network Requirements Designing and Supporting Computer Networks Chapter 2.1 Copyleft 2012 Vincenzo Bruno (www.vincenzobruno.it) Released under Creative Commons License 3.0 By-Sa Cisco name, logo
More informationLecture 12. Maintenance. Lecture Objectives. System Costs to IS Department. Transition to Maintenance. What is Maintenance. Corrective Maintenance
Lecture Objectives IMS1002 /CSE1205 Systems Analysis and Design Lecture 12 Maintenance At the completion of this lecture you should: be aware of the significance of maintenance activity in the work of
More informationRequirements Gathering using Object- Oriented Models
Requirements Gathering using Object- Oriented Models Software Quality Assurance What is software? According to the IEEE (Institute of Electrical and Electronics Engineers) A software is: Programs, procedures,
More informationChapter 8. Systems Development. Ralph M. Stair George W. Reynolds
Ralph M. Stair George W. Reynolds Chapter 8 Systems Development An Overview of Systems Development Managers and employees in all functional areas work together and use business information systems Corporations
More informationSoftware MEIC. (Lesson 12)
Software Architecture @ MEIC (Lesson 12)! Last class Scenarios + Tactics for the Graphite system (finish) Scenarios and Tactics for the other qualities Today Revisiting the Fénix Case Study from the business
More informationProject Management Methodology. Construct & Unit Test SubPhase
Project Management Methodology & Unit Test SubPhase Course Purpose Familiarize team members with the & Unit Test Sub- Phase processes. Understand process flows, team member roles, and artifacts employed.
More informationWhat are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.
What are requirements? Basics of Requirement Engineering Muzaffar Iqbal Farooqi A requirement is a necessary attribute in a system, a statement that identifies a capability, characteristic, or quality
More informationDomain Driven Data Mining: An Efficient Solution For IT Management Services On Issues In Ticket Processing
International Journal of Computational Engineering Research Vol, 03 Issue, 5 Domain Driven Data Mining: An Efficient Solution For IT Management Services On Issues In Ticket Processing 1, V.R.Elangovan,
More informationLos Rios Community College District Adopted: November 2013 Revised: June 2014
Adopted: November 2013 Revised: June 2014 INFORMATION TECHNOLOGY BUSINESS/TECHNICAL ANALYST Series Specification Information Technology Business/Technical Analyst I Information Technology Business/Technical
More informationA Decision Making Tool for the Selection of Service Oriented-Based Legacy Systems Modernization Strategies
A Decision Making Tool for the Selection of Service Oriented-Based Legacy Systems Modernization Strategies Rafik A. Salama, Sherif G. Aly The American University in Cairo raamir@aucegypt.edu, sgamal@aucegypt.edu
More informationA Survey on the Flexibility Requirements related to Business Processes and Modeling Artifacts. Selmin Nurcan, HICCS 08, Waikoloa,, Hawaii
1 A Survey on the Flexibility Requirements related to Business Processes and Modeling Artifacts Selmin Nurcan, CRI, Université Paris 1 - Panthéon Sorbonne Sorbonne Graduate Business School (IAE de Paris)
More informationTOGAF Foundation Exam
TOGAF Foundation Exam TOGAF 9 Part 1 (ESL) Time Limit 90 minutes Number of questions 40 Pass-through 22 1. Which of the following best describes the meaning of "Initial Level of Risk" in Risk Management?
More informationNAVIGATING PMO IMPROVEMENT WITH OPM3
NAVIGATING PMO IMPROVEMENT WITH OPM3 MAY 8, 2014 PITTSBURGH PMI CHAPTER CHRIS ULDRIKS PRESIDENT & PRINCIPAL CONSULTANT OPM3, PMBOK, and PMI are registered trademarks of the Project Management Institute
More informationEnterprise Architecture and COBIT
Enterprise and COBIT The Open Group October 22, 2003 www.realirm.co.za reducing risk, adding value, driving change Agenda 2 Introduction Case Study Enterprise and IT Governance Conclusion Business Orientation
More informationSoftware Development Methodologies. CSC 440: Software Engineering Slide #1
Software Development Methodologies CSC 440: Software Engineering Slide #1 Topics 1. The Waterfall Model 2. Agile Software Development 3. The Unified Process 4. Object-Oriented Analysis and Design 5. The
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationA4. That is a typical ratio. A survey by IDC showed an even more extreme 22:78 ratio.
Summary Translation of Question & Answer Session at Briefing on Applying Manufacturing Innovation to Software Development: Application Operation/Maintenance Innovation Date: October 7, 2008 Location: Shiodome
More informationSoftware Sustainment. Defense Acquisition University Jason Hamilton Professor, Information Technology 7 June PSM Workshop [7 June 2017] 1
Software Sustainment Defense Acquisition University Jason Hamilton Professor, Information Technology 7 June 2017 2017 PSM Workshop [7 June 2017] 1 Why does Software Sustainment Matter? Most DoD systems
More informationDecision Support System (DSS)
Decision Support System (DSS) Decision support systems are computer based information systems that provide interactive information support to managers and business professionals during the decision making
More informationSoftware Quality Factors
Software Quality Factors The need for a comprehensive software quality requirements There are some characteristic common : All the software projects satisfactory fulfilled the basic requirements for correct
More informationBasics of Software Engineering. Carmen Navarrete
Basics of Software Engineering Carmen Navarrete Basics of Software Engineering Outline: Overview Software Development Life Cycle Project management Requirements Analysis and design Implementation Testing
More informationSoftware Quality Management
Software Quality Management CONTENTS I. Basic Quality Concepts II. Software Quality Assurance (SQA) 1. Definition of SQA 2. SQA Activities III. Quality Evaluation Standards 1. Six sigma for software 2.
More informationOrganizing For Systems Management
Organizing For Systems Management By Rich Schiesser in conjunction with Harris Kern s Enterprise Computing Institute Factors to Consider in Designing IT Organizations Few employees enjoy departmental re-structuring,
More informationSoftware Engineering Unit - 1 (Lecture Notes)
Software Engineering Unit - 1 (Lecture Notes) Prepared by Jay Nanavati, Assistant Professor, SEMCOM Topics Program vs. Software Software Software Engineering (Definition & Objective) Phases in Software
More informationEstablishing Requirements for Exception Handling Herbert Hecht SoHaR Incorporated
Establishing Requirements for Exception Handling Herbert Hecht SoHaR Incorporated 1. Introduction Software for embedded systems is expected to protect the system from a wide range of conditions that can
More informationExam Questions OG0-091
Exam Questions OG0-091 TOGAF 9 Part 1 https://www.2passeasy.com/dumps/og0-091/ 1. According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of an overall
More informationAcceptance Testing & Delivery. Acceptance Testing
Acceptance Testing & Delivery Acceptance Testing The complete system, including documentation, training materials, installation scripts, is tested against the requirements by the client, assisted by the
More informationWhat s in the Code Unraveling the Enigma of Legacy Systems. logical solutions. adjusted to the need
What s in the Code Unraveling the Enigma of Legacy Systems logical solutions adjusted to the need Wouldn t it be brilliant to have a logical solution to: IDENTIFY SERVICES: Start with your business analysis,
More informationChapter 5 Part Test progress monitoring and control. 4. Configuration management. 5. Risk and testing. 6. Incident management
INF 3121 Software Testing Test progress monitoring and Chapter 5 Part 2 3.3 Test Test progress monitoring and LO: Recall common metrics used tor test preparation and execution LO: Explain and compare metrics
More informationDesigning To Avoid Human Error Consequences
HESSD 98 90 Designing To Avoid Human Error Consequences S.L.N. Chen-Wing and E.C. Davey Atomic Energy of Canada Ltd., Canada Abstract: AECL and CANDU utilities have developed a process for minimizing human
More informationAdvantages and Disadvantages of. Independent Tests. Advantages. Disadvantages
8.0 Test Management Outline 8.1 Test organisation 8.2 Test planning and estimation 8.3 Test program monitoring and control 8.4 Configuration management 8.5 Risk and testing 8.6 Summary Independent Testing
More informationTest Management: Part I. Software Testing: INF3121 / INF4121
Test Management: Part I Software Testing: INF3121 / INF4121 Summary: Week 6 Test organisation Independence Tasks of the test leader and testers Test planning and estimation Activities Entry and exit criteria
More informationTen steps to effective requirements management
IBM Software Requirements definition and management July 2013 Ten steps to effective requirements management 2 Ten steps to effective requirements management Introduction Requirements definition and management
More informationUsing Pilots to Assess the Value and Approach of CMMI Implementation
Using Pilots to Assess the Value and Approach of CMMI Implementation Godfrey, S., Andary, J., Rosenberg, L. NASA Goddard Space Flight Center, Greenbelt, Maryland, USA, 20771 Sara.H.Godfrey.1@gsfc.nasa.gov
More informationISSN (Print) Original Research Article. *Corresponding author Prodip Kumar Sarker
Scholars Journal of Engineering and Technology (SJET) Sch. J. Eng. Tech., 2016; 4(1):40-48 Scholars Academic and Scientific Publisher (An International Publisher for Academic and Scientific Resources)
More informationISM 50 - Business Information Systems
ISM 50 - Business Information Systems Lecture 7 Instructors: Mary Doyle, Goeff Ryder UC Santa Cruz April 20, 2009 Class Announcements Business Paper Proposal Due Wednesday! Wednesday presentation: Juliana
More informationIT Strategic Plan. Executive Summary. Introduction
IT Strategic Plan Supporting the Mission of the University with Planned and Managed Information Technology Resources and Services Executive Summary Introduction The Information Systems Security Policy
More informationI hate Maintenance! Maintenance SUCKS!
I hate Maintenance! Maintenance SUCKS! Agile Maintenance Naresh Jain Copyright ThoughtWorks, 2005 Agenda of this discussion Glossary Why maintain software Types of Software Maintenance Traditional v/s
More informationCOBIT Control Assessment Questionnaire
The key to maintaining profitability in a technologically changing environment is how well you maintain control. COBIT's Control Objectives provides the critical insight needed to delineate a clear policy
More informationQUESTIONS NUMBER ONE (Total marks 20) NUMBER TWO (Total marks 20) NUMBER THREE
NUMBER ONE QUESTIONS The growth of telecommunications has made information a key organisational resource, which requires careful management. a. Give your definition of an Information System. (5 b. The
More informationTEMPLATE FOR A SOFTWARE MAINTENANCE PLAN Second Edition ISBN
Sample Pages for TEMPLATE FOR A SOFTWARE MAINTENANCE PLAN Second Edition ISBN 0-9748987-8-3 Author: Thomas M. Pigoski 1 Sample Pages for Template for a Software Maintenance Plan Second Edition ISBN 0-9748987-8-3
More informationTOGAF 9.1 Phases E-H & Requirements Management
TOGAF 9.1 Phases E-H & Requirements Management By: Samuel Mandebvu Sources: 1. Primary Slide Deck => Slide share @ https://www.slideshare.net/sammydhi01/learn-togaf-91-in-100-slides 1. D Truex s slide
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationRealize and Sustain the Value of Your Micro Focus Implementation
White Paper Professional Services Realize and Sustain the Value of Your Micro Focus Implementation Micro Focus Professional Services provides Solution Management Services to help you fully utilize, manage,
More informationWork Product Dependency Diagram
Work Product Dependency Diagram Project Definition System Context Subject Area Model Architectural Decisions Requirements Matrix Use Case Model Service Model Non Functional Requirements Component Model
More informationCHAPTER 4 PRODUCT DEVELOPMENT LIFE CYCLE
CHAPTER 4 PRODUCT DEVELOPMENT LIFE CYCLE 1 Learning Objectives Review the Systems Development Life Cycle (SDLC). Examine the problems and alternatives with SDLC. Know the key issues in ERP implementation
More informationEnterprise DevOps at Scale
Enterprise DevOps at Scale 12/19/2012 Gap Inc Engineering Cool Geeks DevOps Meetup PRE- AMBLE WARNINGS: "DEVOPS" IS A ORGANIZATIONAL CULTURAL CHANGE AND MINDSET, NOT A THING YOU CAN BUY. THIS SH** IS HARD
More informationBest Practices for Technology Renewal in Banking Institutions
A SERIES OF ARTICLES, WHITE PAPERS AND BEST PRACTICES Best Practices for Technology Renewal in Banking Institutions Mitigating Risk, Lowering TCO and Enabling Technology Advancement through Disciplined
More informationIEEE s Recommended Practice for Architectural Description
IEEE s Recommended Practice for Architectural Description IEEE Architecture Working Group ieee-awg@spectre.mitre.org http://www.pithecanthropus.com/~awg 30 March 1999 Outline What is it? History Goals
More informationSoftware Engineering QUESTION BANK
Software Engineering QUESTION BANK UNIT - 1 1. What is software? Explain the two fundamental types of software products. 2. What is software engineering? What is the difference between software engineering
More informationPASW Modeler. Achieve Your Goals with Deep, Predictive Insight
PASW Modeler Achieve Your Goals with Deep, Predictive Insight PASW Modeler * transforms data into a decision-making asset Imagine if you could lower your marketing costs by 30 percent, or reduce delinquent
More informationPPI Capabilities Overview
PPI Capabilities Overview About Us PPI is a Performance Improvement consulting firm 150 Specialists, service both Domestic & Global clients Blue-chip client list, e.g. MetLife Wachovia Wyeth AIG HealthNet
More informationArchitecture. By Glib Kutepov Fraunhofer IESE
Architecture By Glib Kutepov Glib.kutepov@iese.fraunhofer.de Outline 1. Why Architecture? 2. What is Architecture? 3. How to create an Architecture? Alignment Modeling and Structuring Architectural Views
More information