Software Change Management Chapter 27 Homework 10 Points

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Software Change Management Chapter 27 Homework 10 Points"

Transcription

1 SE-27-Software-Change-Management-HW.doc 1 CSCI 3321 Initials Written homework will be assigned regularly throughout the semester. Since there is little or no serious programming involved in the homework, there is little reason to give credit to late work. All written homework is to be completed individually. None of the written homework assignments are team related. The normal late penalty is 50% per day. This written homework should help prepare you to take exams and quizzes. No answer key will be provided. Homework will be spot checked for completeness. Although Homework may be spot checked for accuracy, it will not be graded question by question. If more than 10% of a homework assignment is late or incorrect, the grade will be a 0. This written homework is not a team assignment. It is a violation of academic integrity to provide others with access to your copy of this homework while you are taking this class. It is a violation of academic integrity to provide others with access to your copy of this homework after you have completed this class. You may get together with your study group and discuss your answers if and only if every member of your study group has completed at least 90% of the lab and has submitted it for credit; I encourage you to do this regularly! Homework must be answered neatly in either pen or pencil; electronic solutions will not be accepted or honored. All of the work in this project is my own! Neither have I, nor will I knowingly make this available to others outside the provisions described above. Print Name Signature (pledged) Software Change Management Chapter 27 Homework 10 Points 1] Which of these are valid software configuration items? A) software tools B) documentation C) executable programs D) test data E) all of the above 2] Which of the following is not considered one of the four important elements that should exist when a configuration management system is developed? A) component elements B) human elements C) process elements D) validation elements 3] {T/F} Once a software engineering work product becomes a baseline it cannot be changed again. 4] Which configuration objects would not typically be found in the project database? A) design specification B) marketing data C) organizational structure description D) test plans E) both b and c 5] {T/F} Modern software engineering practice suggests that a software team maintain SCI's in a project database or repository. 6] A data repository metamodel is used to determine how A) information is stored in the repository B) data integrity can be maintained C) the existing model can be extended D) All of the above

2 SE-27-Software-Change-Management-HW.doc 2 CSCI 3321 Initials 7] {T/F} Many data repository requirements are the same as those for a typical database application. 8] {T/F} The ability to track relationships and changes to configuration objects is one of the most important features of the SCM repository. 9] Which of the following tasks is not part of software configuration management? A) change control B) reporting C) statistical quality control D) version control 10] A basic configuration object is a _?_ created by a software engineer during some phase of the software development process. A) program data structure B) a software component C) unit of information D) all of the above 11] A new _?_ is defined when major changes have been made to one or more configuration objects. A) entity B) item C) variant D) version 12] {T/F} Change control is not necessary if a development group is making use of an automated project database tool. 13] When software configuration management is a formal activity, the software configuration audit is conducted by the A) development team B) quality assurance group C) senior managers D) testing specialists 14] The primary purpose of configuration status reporting is to A) allow revision of project schedules and cost estimates by project managers B) evaluate the performance of software developers and organizations C) make sure that change information is communicated to all affected parties D) none of the above 15] CM is an acronym for both C Management and C Management 16] SCM is an acronym for _?_. 17]?_ is the art of controlling software development to minimize confusion; it is an umbrella activity applied throughout the software life cycle. 18] Software _?_ is a set of tracking and control activities that are initiated when a software engineering project begins and terminates only when the software is taken out of operation.

3 SE-27-Software-Change-Management-HW.doc 3 CSCI 3321 Initials 19] Software _?_ is the set of software engineering activities that occur after the software has been delivered to the customer and has been put into operation. 20] {T/F} Software Configuration Management is the same as Software Support. 21] {T/F} The slides say that Change is inevitable when computer software is built! 22] The slides describe 4 situations in which change tends to increases the confusion among the software engineers working on a project. If this is a homework question, list them. If this is an exam question, list 2 of them. Changes are Not A before they are made Changes are Not R before they are implemented Changes are Not R after they are implemented [Even Worse] Changes are Not C in a manner that will improve/maintain quality 23] According to the slides, software change strategies fall into 3 major classifications; list them. Software M - changes are made in response to changed requirements but the fundamental software structure is stable. Architectural T - the architecture of the system is modified generally from a centralized architecture to a distributed architecture. Software R - no new functionality is added to the system but the architecture is restructured and reorganized to facilitate future changes. 24] E D Program Evolution Dynamics is the study of the processes of system change 25] E D Program Evolution Dynamics is the study of the processes of system change 26] Which of the Lehman s laws for large systems in large organizations says that Program evolution is a self-regulating process. System attributes, such as size, time between releases, and the number of reported errors are approximately invariant for each system release. 27] Which of the Lehman s laws for large systems in large organizations says that A program that is used in a real-world environment necessarily must change or become progressively less useful in that environment.

4 SE-27-Software-Change-Management-HW.doc 4 CSCI 3321 Initials 28] Which of the Lehman s laws for large systems in large organizations says that Over a program s lifetime, its rate of development is approximately constant and independent of the resources devoted to the system development. 28] Which of the Lehman s laws for large systems in large organizations says that Over the program s lifetime, the incremental change in each release is approximately constant. 28] Which of the Lehman s laws for large systems in large organizations says that As an evolving program changes, its structure tends to become More Complex. Extra resources must be devoted to preserving and simplifying the structure.

5 SE-27-Software-Change-Management-HW.doc 5 CSCI 3321 Initials 29] {T/F} We know that Lehman s laws are only applicable to large systems in large organizations. 30] It is the _?_ s role in Software Configuration Management to work effectively as well as use tools that help to build a consistent software product and maintain version control when available. 31] It is the _?_ s role in Software Configuration Management to monitors the progress of development as well as recognizes & reacts to problems 32] It is the _?_ s role in Software Configuration Management to ensure that the procedures and policies for creating, changing, and testing code are followed as well as evaluate and authorize changes 33] The slides describe the 4 basic components of a software configuration management system. List them. C Elements - a set of tools coupled within a file management system (e.g., a database) that enables access to and management of each software configuration item. P Elements - a collection of procedures and tasks that define an effective approach to change management (and related activities) for all constituencies involved in the management, engineering and use of computer software. C Elements - a set of tools that automate the construction of software by ensuring that the proper set of validated components (i.e., the correct version) have been assembled. H Elements - a set of tools and process features (encompassing other CM elements) which help the software team to implement effective SCM 34] The IEEE (IEEE Std. No ) defines a _?_ as: a specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures 35] A baseline is a milestone in the development of software that is marked by _?_ and the approval of these SCIs that is obtained through a formal technical review. 36] Software _?_ is modifying a program after it has been put into use. 37] According to the slides, software maintenance changes are implemented by M existing components and A new components 38] {T/F} Software maintenance changes does normally involve major changes to the system s architecture. 39] According to the slides, the three major reasons we do software maintenance are to Maintenance to R Software Faults Maintenance to A Software to a Different Operating Environment Maintenance to Add to or Modify the System s F

6 SE-27-Software-Change-Management-HW.doc 6 CSCI 3321 Initials 40] According to the slides, about the same amount of the maintenance time in activities _?_ and _?_. A) Fault Repair B) Software Adaptation C) Function Addition or Modification 41] According to the slides, about 65% of the maintenance time relates to A) Fault Repair B) Software Adaptation C) Function Addition or Modification 42] According to the slides, m aintenance costs are usually _?_ {Greater/Less} than development costs (2* to 100* depending on the application) 43] Maintenance Costs Increase as Software is Maintained because 44] C R Which of the 5 major maintenance software maintenance cost factors are described by the developers of a system may have no contractual responsibility for maintenance so there is no incentive to design for future change 45] T S Which of the 5 major maintenance software maintenance cost factors are described by maintenance costs are reduced if the same staff are involved with them for some time 46] P A & S Which of the 5 major maintenance software maintenance cost factors are described by as programs age, their structure is degraded and they become harder to understand and change 47] S S Which of the 5 major maintenance software maintenance cost factors are described by maintenance staff are often inexperienced and have limited domain knowledge 48] D Which of the 5 major maintenance software maintenance cost factors are described by well maintained and accurate documentation helps to reduce costs! 49] C R Software C_?_ R_?_ are requests for system alterations from users, customers or management 50] The slides list 9 reasons not all change requests are accepted/implemented! If this is a homework question, list them. If this is an exam question, list 6 of them. L Costs Lost R H Costs Projected R Number of system C that will have to be changed Significance of each C Change Future M P R Gain or Loss How C Is The Change

7 SE-27-Software-Change-Management-HW.doc 7 CSCI 3321 Initials 51] Changing the architecture tends to be extensive and expensive. The slides list half a dozen business questions that should be ask when considering an architecture revision. List two of them. 52] A D The older the system, the more difficult and costly it will be to modify it s A_?_ because previous changes will have D_?_ the initial structure of the system. 53] A The more modular the system, the {easier/harder} it will be to change the architecture. 54] Managers hate surprises that have unexpectedly high costs; software maintenance provides a great opportunity for surprises. According to the slides, maintenance prediction is concerned with Predicting Likely C R Predicting what Parts Of The System are likely to cause the most P O Maintenance Costs Of A System over a specified period of time 55] S C Studies have shown that most maintenance effort is spent on a relatively small number of S_?_ C_?_. 56] D R Studies have shown implementing software change requests, normal software maintenance, D_?_ the system and R_?_ its maintainability. 57] Project Managers must predict the number of changes that must be made to associated with a change request; this requires an understanding of the relationships between a system and its environment. Among the factors influencing the relationships between a system and its environment are N and C of system interfaces The B processes where the system is used 58] The SCM _?_ is the set of mechanisms and data structures that allow a software team to manage change in an effective manner. 59] The slides describe six SCM Repository functions. If this is a homework question, list them. If this is an exam question, list 4 of them. Data I I Sharing T Integration D Integration Methodology E D Standardization

8 SE-27-Software-Change-Management-HW.doc 8 CSCI 3321 Initials 60] The slides describe five major Repository Features. If this is a homework question, list them. If this is an exam question, list 4 of them. V control - saves all of these versions to enable effective management of product releases and to permit developers to go back to previous versions. D tracking and change management. The repository manages a wide variety of relationships among the data elements stored in it. R Tracing - provides the ability to track all the design and construction components and deliverables that result from a specific requirement specification C Management. Keeps track of a series of configurations representing specific project milestones or production releases. A Trails. Establishes additional information about when, why, and by whom changes are made ] Put initials at top of each and every page. Staple this homework. Fold in half length-wise. Put Name On Outside.

Software Engineering. So(ware Evolu1on

Software Engineering. So(ware Evolu1on Software Engineering So(ware Evolu1on 1 Software change Software change is inevitable New requirements emerge when the software is used; The business environment changes; Errors must be repaired; New computers

More information

Chapter 9 Software Evolution

Chapter 9 Software Evolution Chapter 9 Software Evolution Summary 1 Topics covered Evolution processes Change processes for software systems Program evolution dynamics Understanding software evolution Software maintenance Making changes

More information

WHAT IS CHANGE MANAGEMENT

WHAT IS CHANGE MANAGEMENT WHAT IS CHANGE MANAGEMENT It is a set of activity designed to manage change by identifying the work products that are likely to change reestablishing relationships among them; defining mechanisms for managing

More information

Software Evolution, Reengineering and Reverse Engineering

Software Evolution, Reengineering and Reverse Engineering Software Evolution, Reengineering and Reverse Engineering King Fahd University of Petroleum & Minerals SWE 316: Software Design & Architecture Semester: 072 Objectives To explain why change is inevitable

More information

Computer programs (both source and executable) Documentation (both technical and user) Data (contained within the program or external to it)

Computer programs (both source and executable) Documentation (both technical and user) Data (contained within the program or external to it) CHAPTER 27 CHANGE MANAGEMENT Overview Changes are inevitable when software is built. A primary goal of software engineering is to improve the ease with which changes can be made to software. Configuration

More information

Software Configuration Management. Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman

Software Configuration Management. Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Chapter 22 Software Configuration Management Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman

More information

How to realize software evolution of existing BOSS via ZTE SEEM

How to realize software evolution of existing BOSS via ZTE SEEM How to realize software evolution of existing BOSS via ZTE SEEM Zhan Zhang Abstract Due to long-term construction and accumulation for different purposes, telecom carriers normally have very complex IT

More information

Software Configuration Management

Software Configuration Management Software Engineering Courses (University of Kansas, Spring 2004) Slide 1 Software Configuration Management Software Configuration: All items that constitute the software while under the development (e.g.,

More information

SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK

SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost

More information

CHAPTER 7 Software Configuration Management

CHAPTER 7 Software Configuration Management CHAPTER 7 Software Configuration Management ACRONYMS CCB CM FCA MTBF PCA SCCB SCI SCM SCMP SCR SCSA SEI/CMMI SQA SRS USNRC INTRODUCTION Configuration Control Board Configuration Management Functional Configuration

More information

Chapter 5. Choose the answer that mostly suits each of the sentences given:

Chapter 5. Choose the answer that mostly suits each of the sentences given: Chapter 5 Software Configuration Management Choose the answer that mostly suits each of the sentences given: 1. No matter where you are in the system lifecycle, the system will change, and the desire to

More information

IT3205: Fundamentals of Software Engineering (Compulsory)

IT3205: Fundamentals of Software Engineering (Compulsory) INTRODUCTION : Fundamentals of Software Engineering (Compulsory) This course is designed to provide the students with the basic competencies required to identify requirements, document the system design

More information

Software Test Plan (STP) Template

Software Test Plan (STP) Template (STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This

More information

Software Configuration Management. http:\\www.francisxavier.ac.in

Software Configuration Management. http:\\www.francisxavier.ac.in Software Configuration Management Outline Introduction what is SCM, who are involved, why it is imp? what are the steps? Basic Concepts of SCM Configuration Management Activities Configuration Management

More information

CONFIGURATION MANAGEMENT PLAN GUIDELINES

CONFIGURATION MANAGEMENT PLAN GUIDELINES I-680 SMART CARPOOL LANE PROJECT SYSTEM ENGINEERING MANAGEMENT PLAN CONFIGURATION MANAGEMENT PLAN GUIDELINE SECTIONS: PLAN GUIDELINES 1. GENERAL 2. ROLES AND RESPONSIBILITIES 3. CONFIGURATION MANAGEMENT

More information

Software Engineering talk

Software Engineering talk Software Engineering talk Title: Lean or Agile software engineering process: an industry perspective By Keith Hanson, CEO, Twin Engine Labs Time & Place: 5:30pm, Jan 9 2014, Bogard Hall 1/7/14 1 ITEC420:

More information

Configuration management. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 29 Slide 1

Configuration management. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 29 Slide 1 Configuration management Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 29 Slide 1 Objectives To explain the importance of software configuration management (CM) To describe key CM activities

More information

copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.

copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. WVU CSEE CS 430 Change Management copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction

More information

CONFIGURATION MANAGEMENT (CM) GUIDELINES

CONFIGURATION MANAGEMENT (CM) GUIDELINES CONFIGURATION MANAGEMENT (CM) GUIDELINES Prepared by: S. E. Snook Software Quality Engineering 330 Corporate Way Suite 300 Orange Park, FL, USA 32073 Configuration Management Guidelines 1 1. PURPOSE STATEMENT

More information

Software Engineering. Software Evolution und Reengineering! Kapitel 12

Software Engineering. Software Evolution und Reengineering! Kapitel 12 Martin Glinz Harald Gall Software Engineering Kapitel 12 Software Evolution und Reengineering! 2010, 2011 Harald Gall. Alle Rechte vorbehalten. Speicherung und Wiedergabe für den persönlichen, nicht kommerziellen

More information

Software Design Document (SDD) Template

Software Design Document (SDD) Template (SDD) Template Software design is a process by which the software requirements are translated into a representation of software components, interfaces, and data necessary for the implementation phase.

More information

Chapter 13 Configuration Management

Chapter 13 Configuration Management Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 13 Configuration Management Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software

More information

Chapter 13 Configuration Management

Chapter 13 Configuration Management Chapter 13 Configuration Management Using UML, Patterns, and Java Object-Oriented Software Engineering Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software

More information

JOURNAL OF OBJECT TECHNOLOGY

JOURNAL OF OBJECT TECHNOLOGY JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2007 Vol. 6, No. 1, January-February 2007 CM Configuration Change Management John D.

More information

YIIP1100 PROJECT MANAGEMENT

YIIP1100 PROJECT MANAGEMENT YIIP1100 PROJECT MANAGEMENT PLANNING THE PROJECT - DEVELOPING PROJECT MANAGEMENT PLAN EXECUTING, CONTROLLING & MONITORING THE PROJECT JOUNI HUOTARI, JUHA HAUTANEN & JOHN MUSSER BASED ON PMBOK, SECTIONS

More information

Software Project Management Plan (SPMP)

Software Project Management Plan (SPMP) Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.

More information

Air Force Mentor-Protégé Program. Configuration Management & Control. ERP Methodology and Project Management. Professor Duane Truex III.

Air Force Mentor-Protégé Program. Configuration Management & Control. ERP Methodology and Project Management. Professor Duane Truex III. Air Force Mentor-Protégé Program Configuration Management & Control Ronald E. Giachetti, Ph.D. Associate Professor Industrial and Systems Engineering Florida International University Duane P. Truex, Ph.D.

More information

Appendix H Software Development Plan Template

Appendix H Software Development Plan Template Appendix H Software Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms

More information

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute

More information

Example IEEE software project management plan (SPMP)

Example IEEE software project management plan (SPMP) Example IEEE software project management plan (SPMP) Source: Object Oriented & Classical Software Engineering, 7 th edition, Stephen R. Schach, pg. 590 594 This plan is for development of the MSG product

More information

SOE. managing change in system development projects: configuration management

SOE. managing change in system development projects: configuration management SOE managing change in system development projects: configuration management 2 3 understanding the problem of change change is one of the most fundamental characteristics in any software development process

More information

TEMPLATE. U.S. Department of Energy. Project Name. Configuration Management Plan. September 2002 U. S. DEPARTMENT OF ENERGY

TEMPLATE. U.S. Department of Energy. Project Name. Configuration Management Plan. September 2002 U. S. DEPARTMENT OF ENERGY U.S. Department of Energy Project Name Configuration Management Plan September 2002 TEMPLATE U. S. DEPARTMENT OF ENERGY Organizational Title 1 Organizational Title 2 Change Control Page The following information

More information

Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?

Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management? Books: Software Configuration Management 1. B. Bruegge and A. H. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns, and Java (Chapter 13) Outline of the Lecture Purpose of Software Configuration

More information

Configuration & Build Management

Configuration & Build Management Object-Oriented Software Engineering Using UML, Patterns, and Java Configuration & Build Management Outline of the Lecture Purpose of Software Configuration Management (SCM) Some Terminology Software Configuration

More information

Chapter 25 Configuration Management. Chapter 25 Configuration management

Chapter 25 Configuration Management. Chapter 25 Configuration management Chapter 25 Configuration Management 1 Topics covered Change management Version management System building Release management 2 Configuration management Because software changes frequently, systems, can

More information

<name of project> Software Project Management Plan

<name of project> Software Project Management Plan The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor

More information

Lecture 20: Software Evolution

Lecture 20: Software Evolution Lecture 20: Software Evolution Basics of Software Evolution Laws of software evolution Requirements Growth Software Aging Basics of Change Management Baselines, Change Requests and Configuration Management

More information

Software Configuration Management. Professor Hossein Saiedian EECS811: Software Project Management

Software Configuration Management. Professor Hossein Saiedian EECS811: Software Project Management Software Configuration Management Professor Hossein Saiedian EECS811: Software Project Management 1 Software Configuration Items Software configuration: All items that constitute the software while under

More information

IT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3

IT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document

More information

To introduce software process models To describe three generic process models and when they may be used

To introduce software process models To describe three generic process models and when they may be used Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software

More information

Introduction for Software Configuration Management Training

Introduction for Software Configuration Management Training Introduction for Software Configuration Management Training I thought I knew it all! History of 12207 ISO/IEC 12207 1995: Standard for Information Technology Software Life Cycle Processes IEEE/EIA 12207.0

More information

Introduction to Software Configuration Management. CprE 556 Electrical and Computer Engineering Department Iowa State University

Introduction to Software Configuration Management. CprE 556 Electrical and Computer Engineering Department Iowa State University Introduction to Software Configuration Management CprE 556 Electrical and Computer Engineering Department Iowa State University 1 Example Initially, implementation is in Modula-2 on a Mac. A11 B11 A12

More information

27. Software Change. Objectives. Contents. Software change 1

27. Software Change. Objectives. Contents. Software change 1 Software change 1 27. Software Change Objectives The objectives of this chapter are to introduce software change and to describe a number of ways of modifying software. When you have read this chapter,

More information

Software Configuration Management. Addendum zu Kapitel 13

Software Configuration Management. Addendum zu Kapitel 13 Software Configuration Management Addendum zu Kapitel 13 Outline Purpose of Software Configuration Management (SCM) Motivation: Why software configuration management? Definition: What is software configuration

More information

The Role of CM in Agile Development of Safety-Critical Software

The Role of CM in Agile Development of Safety-Critical Software The Role of CM in Agile Development of Safety-Critical Software Tor Stålhane1, Thor Myklebust 2 1 Norwegian University of Science and Technology, N-7491, Trondheim, Norway 2 SINTEF ICT, Strindveien 2,

More information

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name

More information

Configuration Management. Software Configuration Management. Example of System Families. Configuration Management

Configuration Management. Software Configuration Management. Example of System Families. Configuration Management Configuration Management Software Configuration Management New versions of software systems are created as they change: For different machines/os; Offering different functionality; Tailored for particular

More information

WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING

WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING June 28, 1999 WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING Subject: Tray Management System Software Management () As part of an ongoing audit of the Tray Management System, the Office of Inspector General

More information

Configuration Management in Software Development Life Cycle

Configuration Management in Software Development Life Cycle 13 Configuration Management in Software Development Life Cycle Tejinder Kaur Sanjay Bhatnagar Deepali StudentComputer Application Associate Prof. Computer Assistant Prof. Computer Department, GZS PTU Applications

More information

CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN

CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN by Group LaPaix Subject on COMPUTERIZED READING SYSTEM FOR BLINDS DEPARTMENT OF COMPUTER ENGINEERING METU ANKARA 28.03.2003

More information

Software Configuration Management Plan

Software Configuration Management Plan For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.

More information

AD Management Survey: Reveals Security as Key Challenge

AD Management Survey: Reveals Security as Key Challenge Contents How This Paper Is Organized... 1 Survey Respondent Demographics... 2 AD Management Survey: Reveals Security as Key Challenge White Paper August 2009 Survey Results and Observations... 3 Active

More information

What is a life cycle model?

What is a life cycle model? What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

More information

PM Planning Configuration Management

PM Planning Configuration Management : a Project Support Function As stated throughout the Project Planning section, there are fundamental components that are started during the pre-performance stage of the project management life cycle in

More information

8. Master Test Plan (MTP)

8. Master Test Plan (MTP) 8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across

More information

Time Monitoring Tool Software Development Plan. Version <1.1>

Time Monitoring Tool Software Development Plan. Version <1.1> Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page

More information

Configuration Management. Main issues: manage items during software life cycle usually supported by powerful tools

Configuration Management. Main issues: manage items during software life cycle usually supported by powerful tools Configuration Management Main issues: manage items during software life cycle usually supported by powerful tools Configuration management tasks identification and definition of configuration items, such

More information

Software Development Life Cycle (SDLC)

Software Development Life Cycle (SDLC) Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process

More information

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville Software Engineering Software Processes Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software process models To describe three generic process models and when

More information

Assessing the Audit Impact of Cloud Computing. kpmg.com

Assessing the Audit Impact of Cloud Computing. kpmg.com Assessing the Audit Impact of Cloud Computing kpmg.com 1 Assessing the Audit Impact of Cloud Computing Cloud Computing Cloud computing is becoming an important IT strategy for entities that need varying

More information

Lecture 10 CS5702. Requirements Engineering. Managing change optimising Value - A bit more about Agile RE. Requirements Engineering.

Lecture 10 CS5702. Requirements Engineering. Managing change optimising Value - A bit more about Agile RE. Requirements Engineering. Requirements Engineering Overview Lecture 10 CS5702 Requirements Engineering Semester 1 2009/10 Professor Kevin Ryan 1. Introduction (Week 1) 2. Elicitation of requirements (2 & 3) 3. Standards, Templates

More information

Appendix I Hardware Development Plan Template

Appendix I Hardware Development Plan Template Appendix I Hardware Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms

More information

College of Business Department of Accounting and Management Information Systems

College of Business Department of Accounting and Management Information Systems College of Business Department of Accounting and Management Information Systems Syllabus for ACCT530 Financial Planning, Control and Performance Evaluation Using SAP Spring 2012 Instructor Nancy Jones,

More information

ADAPTIVE SOA INFRASTRUCTURE BASED ON VARIABILITY MANAGEMENT. Peter Graubmann, Mikhail Roshchin

ADAPTIVE SOA INFRASTRUCTURE BASED ON VARIABILITY MANAGEMENT. Peter Graubmann, Mikhail Roshchin 70 ADAPTIVE SOA INFRASTRUCTURE BASED ON VARIABILITY MANAGEMENT Peter Graubmann, Mikhail Roshchin Abstract: In order to exploit the adaptability of a SOA infrastructure, it becomes necessary to provide

More information

DRAFT REGULATORY GUIDE

DRAFT REGULATORY GUIDE U.S. NUCLEAR REGULATORY COMMISSION August 2012 OFFICE OF NUCLEAR REGULATORY RESEARCH Division 1 DRAFT REGULATORY GUIDE Contact: K. Sturzebecher (301) 251-7494 DRAFT REGULATORY GUIDE DG-1206 (Proposed Revision

More information

Project Quality Planning

Project Quality Planning The PROJECT PERFECT White Paper Collection Project Quality Planning Neville Turbit Overview Every project should have a quality plan. In reality, very few do. It is something that has puzzled me for some

More information

Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan

Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan INL/EXT-09-17141 Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan October 2009 The INL is a U.S. Department of Energy National Laboratory operated by Battelle

More information

STSG Methodologies and Support Structure

STSG Methodologies and Support Structure STSG Methodologies and Support Structure STSG Application Life Cycle Management STSG utilizes comprehensive lifecycle tools that are fully integrated and provide capabilities for most of the roles in its

More information

Configuration Management - The Big Picture

Configuration Management - The Big Picture Configuration Management - The Big Picture Consists of: 1. Product s aligned to system development life cycle comprised of hardware and software configuration items described by specifications, design

More information

Configuration Management

Configuration Management What is CM? CM processes in practice CM and organizational context CM technology Configurations How are versions created? Versions SCM vs. PDM Configuration Management CM: a process for maintaining the

More information

ALS Configuration Management Plan. Nuclear Safety Related

ALS Configuration Management Plan. Nuclear Safety Related Westinghouse Non-Proprietary Class 3 Advanced Logic System 6002-00002-NP, Rev. 10 Function Author Nuclear Safety Related July 2014 APPROVALS Name and Signature Anthony C. Pagano* Integrated Process Lead,

More information

Department of Computer & Information Sciences. INFO-450: Information Systems Security Syllabus

Department of Computer & Information Sciences. INFO-450: Information Systems Security Syllabus Department of Computer & Information Sciences INFO-450: Information Systems Security Syllabus Course Description This course provides a deep and comprehensive study of the security principles and practices

More information

Android Application for Visual Communication Software Project Management Plan

Android Application for Visual Communication Software Project Management Plan Android Application for Visual Communication Software Project Management Plan (gmirsky@student.utdallas.edu) Tucker Smith (tss063000@utdallas.edu) (jacobalsaleh55@yahoo.com) Tom Langford (etom1002@hotmail.com)

More information

A Tool for Mining Defect-Tracking Systems to Predict Fault-Prone Files

A Tool for Mining Defect-Tracking Systems to Predict Fault-Prone Files A Tool for Mining Defect-Tracking Systems to Predict Fault-Prone Files Thomas J. Ostrand AT&T Labs - Research 180 Park Avenue Florham Park, NJ 07932 ostrand@research.att.com Elaine J. Weyuker AT&T Labs

More information

MNLARS Project Audit Checklist

MNLARS Project Audit Checklist Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?

More information

Darshan Institute of Engineering & Technology Unit : 7

Darshan Institute of Engineering & Technology Unit : 7 1) Explain quality control and also explain cost of quality. Quality Control Quality control involves the series of inspections, reviews, and tests used throughout the software process to ensure each work

More information

ERP Systems: Audit and Control Risks

ERP Systems: Audit and Control Risks ERP Systems: Audit and Control Risks Jennifer Hahn Deloitte & Touche ISACA Spring Conference April 26, 1999 Session Learning Objectives At the end of this session, the participant should be able to: Understand

More information

Software Engineering. So#ware Processes

Software Engineering. So#ware Processes Software Engineering So#ware Processes 1 The software process A structured set of activities required to develop a software system. Many different software processes but all involve: Specification defining

More information

Lecture 1: Introduction to Software Quality Assurance

Lecture 1: Introduction to Software Quality Assurance Lecture 1: Introduction to Software Quality Assurance Software Quality Assurance (INSE 6260/4-UU) Winter 2009 Thanks to Rachida Dssouli for some slides Course Outline Software Quality Overview Software

More information

Software Processes. Topics covered

Software Processes. Topics covered Software Processes cmsc435-1 Topics covered Systems vs. software engineering Software process models Process iteration Process activities Computer-aided software engineering cmsc435-2 What is a system?

More information

ISO 9001 for Small Projects

ISO 9001 for Small Projects Chapter 8 ISO 9001 for Small Projects INTRODUCTION TO ISO 9001 FOR SMALL PROJECTS Many organizations are intimidated by the amount of documentation associated with ISO 9001 conformance requirements. The

More information

CS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.

CS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping

More information

Intland s Medical Template

Intland s Medical Template Intland s Medical Template Traceability Browser Risk Management & FMEA Medical Wiki Supports compliance with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC 60601 and more INTLAND codebeamer ALM is

More information

Information Technology Branch Information Technology Systems Acquisition, Development and Maintenance Technical Standard

Information Technology Branch Information Technology Systems Acquisition, Development and Maintenance Technical Standard Information Technology Branch Information Technology Systems Acquisition, Development and Maintenance Technical Standard Information Management, Administrative Directive A1461 Cyber Security Technical

More information

A Configuration Management Model for Software Product Line

A Configuration Management Model for Software Product Line A Configuration Management Model for Software Product Line Liguo Yu 1 and Srini Ramaswamy 2 1 Computer Science and Informatics Indiana University South Bend South Bend, IN 46634, USA ligyu@iusb.edu 2 Computer

More information

Creating an SQA Program at NREL A DOE FFRDC Program based on the NDIA/DoD Sponsored CMMI

Creating an SQA Program at NREL A DOE FFRDC Program based on the NDIA/DoD Sponsored CMMI Creating an SQA Program at NREL A DOE FFRDC Program based on the NDIA/DoD Sponsored CMMI CMMI Conference 2011 Tim Kasse 16 November 2011 NREL is a national laboratory of the U.S. Department of Energy,

More information

Enhance State IT Contract Expertise

Enhance State IT Contract Expertise Enhance State IT Contract Expertise Chris Estes State Chief Information Officer Office of Information Technology Services March 2015 1 P a g e Table of Contents 1. Legislative Request... 3 2. Introduction...

More information

Configuration Management

Configuration Management Configuration Management (CM) is the organized control of engineering change involving the proposing, approving and incorporating of design changes into product development documentation. Although CM can

More information

Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan

Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan INL/EXT-09-17141 Rev. 1 Independent Verification and Validation of SAPHIRE 8 Software Configuration Management Plan February 2010 The INL is a U.S. Department of Energy National Laboratory operated by

More information

Software Project Management

Software Project Management Software Project Management CONTENTS I. Introduction to Software Project Management and its need. II. The Management Spectrum 4 Ps and their Significance III. Project Scheduling 1. Concept of Project Scheduling

More information

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II)

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which

More information

Iterative Project Management 1

Iterative Project Management 1 Iterative Project Management Module 2 Objectives Understand issues for Project Managers (PM) who use iterative development by: Learning how the PM monitors and steers an iterative project towards success.

More information

5 FAH-5 H-520 LIFE CYCLE MANAGEMENT

5 FAH-5 H-520 LIFE CYCLE MANAGEMENT 5 FAH-5 H-520 LIFE CYCLE MANAGEMENT (CT:ITS-5; 02-05-2013) (Office of Origin: (IRM/BMP/SPO/PM) 5 FAH-5 H-521 CONFIGURATION MANAGEMENT REQUIREMENTS Configuration management (CM) is a function deployed throughout

More information

Ten questions to ask when evaluating SAP change management solutions

Ten questions to ask when evaluating SAP change management solutions Ten questions to ask when evaluating SAP change management solutions Organizations with SAP systems use a variety of different processes and tools to help them address the challenges outlined in this white

More information

CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT

CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT John A. Scott and David Nisse Lawrence Livermore National Laboratory 7000 East Avenue P.O. Box 808, L-632 Livermore, CA 94550, USA (925) 423-7655 scott7@llnl.gov

More information

Configuration Management

Configuration Management Configuration Management Co Al Florence This presenter s affiliation with the MITRE Corporation is provided for identification purposes only and is not intended to convey or imply MITRE s concurrence with

More information

BUS 3525 Strategic Management Online

BUS 3525 Strategic Management Online New York City College of Technology Of the City University of New York Department of Business Dr. Roy D. Iraggi N 1026 x5776 BUS 3525 Strategic Management Online Text: Strategic Management in Action, 6th

More information

A Capability Maturity Model (CMM)

A Capability Maturity Model (CMM) Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability

More information

Outsourcing: Maintaining the Business Case. IEEE Technology Management Council, Bonn Peter Snowdon April 11, 2008

Outsourcing: Maintaining the Business Case. IEEE Technology Management Council, Bonn Peter Snowdon April 11, 2008 Outsourcing: Maintaining the Business Case IEEE Technology Management Council, Bonn An Introduction... Electrical Engineer, 1993 Full time MBA (HEC Paris), 2005 2006 : Vodafone Management & advisory functions

More information

Change Management: Automating the Audit Process

Change Management: Automating the Audit Process Change Management: Automating the Audit Process Auditing Change Management for Regulatory Compliance Abstract Change management can be one of the largest and most difficult tasks for a business to implement,

More information