DOC PREVIEW
WVU CS 430 - Change Management

This preview shows page 1-2-3-4-5 out of 14 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 14 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

WVU CSEEWVU CSEECS 430CS 430Change ManagementChange Managementcopyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.For University Use OnlyMay be reproduced ONLY for student use at the university levelThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051May be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.The “First Law”The “First Law”No matter where you are in the system No matter where you are in the system yyyylife cycle, the system will change, and the life cycle, the system will change, and the desire to change it will persist throughout desire to change it will persist throughout the life cycle.the life cycle.Bersoff, et al, 1980Bersoff, et al, 1980These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052What Are These Changes?What Are These Changes?changes in changes in changes in changes in business requirementsbusiness requirementsotherotherdocumentsdocumentsProjectProjecttechnical requirementstechnical requirementschanges inchanges inuser requirementsuser requirementssoftware modelssoftware modelsThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053datadatacodecodeTestTestProjectProjectPlanPlanThe Software ConfigurationThe Software ConfigurationprogramsprogramsdocumentsdocumentsdatadataThe piecesThe piecesThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054datadatappBaselinesBaselines The IEEE (IEEE Std. No. 610.12The IEEE (IEEE Std. No. 610.12--1990) defines a 1990) defines a baseline as:baseline as:baseline as:baseline as: A specification or product that has been formally reviewed and A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change development, and that can be changed only through formal change control procedures.control procedures. a baseline is a milestone in the development of software a baseline is a milestone in the development of software that is marked by the delivery of one or more softwarethat is marked by the delivery of one or more softwareThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055that is marked by the delivery of one or more software that is marked by the delivery of one or more software configuration items and the approval of these SCIs that configuration items and the approval of these SCIs that is obtained through a formal technical reviewis obtained through a formal technical reviewBaselinesBaselinesSCIsmodifiedProject databaseSCIsSoftwareengineeringtasksFormaltechnicalreviewsSCIsapprovedSCIsextractedSCMcontrolsSCIsstoredThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056System SpecificationSoftware RequirementsDesign SpecificationSource CodeTest Plans/Procedures/DataOperational SystemBASELINES:Software Configuration ObjectsSoftware Configuration ObjectsDesign specificationData modeldata designarchitectural designmodule designinterface designComponent Ninterface descriptionalgorithm descriptionPDLTest specificationtest plantest procedureThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20057test proceduretest casesSource codeSCM RepositorySCM Repository The SCM repository is the set of mechanisms and data structures that allow a software team to manage changestructures that allow a software team to manage change in an effective manner The repository performs or precipitates the following functions [FOR89]: Data integrity Information sharingTool integrationThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20058Tool integration Data integration Methodology enforcement Document standardizationRepository ContentRepository Contentbusine ss rules busine ss fu n ct ion s organization struct ure information archit e ctureuse-cases an aly sis m od e l scenario-based diagrams flow-oriented diagrams class-b ased d iagram s source cod e obje ct code sy st em b uild inst ruct ion s Bu s in es s ContentModel ContentV&V ContentProject Management CttConstruction Content be h av io ral d iagram s design model arch it e ct u ral d iagram s interface diagrams component-level diagrams t echn ical me t rics t est cases t est script s t est resu lt s q u alit y m e t ricsThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20059ContentDocumentsproject estimat es project schedule SCM requirements change requests change reports SQA requirements project reports/audit reports project met ricsProject Plan SCM/ SQA Plan System Spec Requirement s Spec Design Docu m e n t Test Plan and Procedure Support documents Use r m an u alRepository FeaturesRepository Features Versioning. saves all of these versions to enable effective management of product releases and to permit developers to go back to previous versionsDependenc tracking and change managementDependency tracking and change management. The


View Full Document

WVU CS 430 - Change Management

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download Change Management
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Change Management and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Change Management 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?