Software Change Management Chapter 27 Homework 10 Points



Similar documents
Software Engineering. So(ware Evolu1on

Chapter 9 Software Evolution

WHAT IS CHANGE MANAGEMENT

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

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

How to realize software evolution of existing BOSS via ZTE SEEM

Software Configuration Management

Software Configuration Management.

SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK

CHAPTER 7 Software Configuration Management

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

IT3205: Fundamentals of Software Engineering (Compulsory)

Software Engineering. Software Evolution und Reengineering! Kapitel 12

Software Engineering talk

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

Chapter 13 Configuration Management

Lecture 20: Software Evolution

YIIP1100 PROJECT MANAGEMENT

Chapter 13 Configuration Management

CONFIGURATION MANAGEMENT (CM) GUIDELINES

CONFIGURATION MANAGEMENT PLAN GUIDELINES

JOURNAL OF OBJECT TECHNOLOGY

Software Test Plan (STP) Template

Software Design Document (SDD) Template

Configuration Management in Software Development Life Cycle

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

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

SOE. managing change in system development projects: configuration management

Introduction for Software Configuration Management Training

Configuration & Build Management

Appendix H Software Development Plan Template

CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN

Example IEEE software project management plan (SPMP)

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

Software Configuration Management. Addendum zu Kapitel 13

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

Enhance State IT Contract Expertise

College of Business Department of Accounting and Management Information Systems

A Configuration Management Model for Software Product Line

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

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

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

Data Classification Technical Assessment

Computer Tech Support

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

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

Time Monitoring Tool Software Development Plan. Version <1.1>

Results Oriented Change Management

NOTICE: This publication is available at:

Darshan Institute of Engineering & Technology Unit : 7

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

Department of Computer & Information Sciences. CSCI-445: Computer and Network Security Syllabus

Software Project Management Plan (SPMP)

DRAFT REGULATORY GUIDE

Software Configuration Management. Visiting Lecture Tero Kojo

Software Engineering UNIT -1 OVERVIEW

STSG Methodologies and Support Structure

Biology AP Edition - Campbell & Reece (8th Edition)

Change Management: Automating the Audit Process

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

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

BUS 3525 Strategic Management Online

Software Configuration Management Plan

Project Quality Planning

<name of project> Software Project Management Plan

Configuration Management - The Big Picture

Theme 1 Software Processes. Software Configuration Management

AD Management Survey: Reveals Security as Key Challenge

MERCER COUNTY COMMUNITY COLLEGE. Division of Business and Technology NET 240

CMS Policy for Configuration Management

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

ITRM Guideline CPM Date: January 23, 2006 SECTION 5 PROJECT CLOSEOUT PHASE

Organization. Project Name. Project Overview Plan Version # Date

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

Complying with the Federal Information Security Management Act. Parallels with Sarbanes-Oxley Compliance

19 Configuration Management

PM Planning Configuration Management

Software Configuration Management, Software Product lines and Summary

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

Intland s Medical Template

Software Development Life Cycle (SDLC)

MATH 140 HYBRID INTRODUCTORY STATISTICS COURSE SYLLABUS

8. Master Test Plan (MTP)

Evolving a Software Configuration Management Ontology

CODING and CODING LABORATORY Health Information Technology Program. Course Number: John A. Logan College HIT 204 Shawnee Community College HIT 204

Lecture 1: Introduction to Software Quality Assurance

CA Service Desk Manager

Android Application for Visual Communication Software Project Management Plan

Correlation and Phishing

Document Storage Tips: Inside the Vault

MAC 1105 FLEX SYLLABUS

NETW 193 Syllabus. MCSE Windows 2000 Directory Services Administration. Revised 31 May 2002 Professor Andrew H. Andersen, Jr.

A Capability Maturity Model (CMM)

Prerequisite: CIS 271 with a minimum grade of C or consent of department.

Iterative Project Management 1

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

PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:

Appendix O Project Performance Management Plan Template

Basic Trends of Modern Software Development

MNLARS Project Audit Checklist

Transcription:

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

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.

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.

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.

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. 610.12-1990) 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

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

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

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. 61-63] Put initials at top of each and every page. Staple this homework. Fold in half length-wise. Put Name On Outside.