Object-Oriented Software Engineering, ch13lect1.ppt

《Object-Oriented Software Engineering, ch13lect1.ppt》由会员分享，可在线阅读，更多相关《Object-Oriented Software Engineering, ch13lect1.ppt（55页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、Using UML,Patterns,and JavaObject-Oriented Software EngineeringChapter 13Configuration ManagementBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 2Outline of the LecturePurpose of Software Configuration Management(SCM)wMotivation:Why software configuratio

2、n management?wDefinition:What is software configuration management?wActivities and roles in software configuration managementSome TerminologywConfiguration Item,Baseline,SCM Directory,Version,Revision Release.Software Configuration Management ActivitieswPromotion Management,Release Management,Change

3、 ManagementOutline of a Software Configuration Management PlanswStandards(Example:IEEE 828-1990)wBasic elements of IEEE 828-1990Configuration Management ToolsBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 3Why Software Configuration Management?The probl

4、em:wMultiple people have to work on software that is changingwMore than one version of the software has to be supported:tReleased systemstCustom configured systems(different functionality)tSystem(s)under developmentwSoftware must run on different machines and operating systemsNeed for coordinationSo

5、ftware Configuration Management wmanages evolving software systemswcontrols the costs involved in making changes to a systemBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 4What is Software Configuration Management?Definition:wA set of management discipl

6、ines within the software engineering process to develop a baseline.Description:wSoftware Configuration Management encompasses the disciplines and techniques of initiating,evaluating and controlling change to software products during and after the software engineering process.Standards(approved by AN

7、SI)wIEEE 828:Software Configuration Management PlanswIEEE 1042:Guide to Software Configuration ManagementForward Definition!Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 5Software Configuration Management is a Project FunctionSCM is a Project Function(

8、as defined in the SPMP)with the goal to make technical and managerial activities more effective.Software Configuration Management can be administered in several ways:wA single software configuration management team for the whole organizationwA separate configuration management team for each projectw

9、Software Configuration Management distributed among the project memberswMixture of all of the aboveBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 6Configuration Management ActivitiesSoftware Configuration Management Activities:wConfiguration item identi

10、fication wPromotion managementwRelease managementwBranch managementwVariant managementwChange management No fixed rules:wActivities are usually performed in different ways(formally,informally)depending on the project type and life-cycle phase(research,development,maintenance).Bernd Bruegge&Allen H.D

11、utoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 7Configuration Management Activities(continued)Configuration item identification wmodeling of the system as a set of evolving componentsPromotion managementwis the creation of versions for other developersRelease managementwis th

12、e creation of versions for the clients and usersChange management wis the handling,approval and tracking of change requestsBranch managementwis the management of concurrent developmentVariant managementwis the management of versions intended to coexistThis lectureReadingBernd Bruegge&Allen H.Dutoit

13、Object-Oriented Software Engineering:Using UML,Patterns,and Java 8Configuration Management RolesConfiguration ManagerwResponsible for identifying configuration items.The configuration manager can also be responsible for defining the procedures for creating promotions and releasesChange control board

14、 memberwResponsible for approving or rejecting change requestsDeveloperwCreates promotions triggered by change requests or the normal activities of development.The developer checks in changes and resolves conflictsAuditorwResponsible for the selection and evaluation of promotions for release and for

15、 ensuring the consistency and completeness of this releaseBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 9TerminologyWe will define the following terms wConfiguration ItemwBaselinewSCM DirectorieswVersionwRevisionwReleaseThe definition of the terms foll

16、ows the IEEE standard.Different configuration management systems may use different terms.Example:CVS configuration management system used in our projects uses terms differeing from the IEEE standard.Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 10Termi

17、nology:Configuration Item “An aggregation of hardware,software,or both,that is designated for configuration management and treated as a single entity in the configuration management process.”all type of code filesdrivers for testsanalysis or design documentsuser or developer manualssystem configurat

18、ions(e.g.version of compiler used)vIn some systems,not only software but also hardware configuration items(CPUs,bus speed frequencies)exist!Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 11Tasks for the Configuration Managers Define configuration itemsB

19、ernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 12Finding Configuration ItemsLarge projects typically produce thousands of entities(files,documents,data.)which must be uniquely identified.Any entity managed in the software engineering process can potentia

20、lly be brought under configuration management controlBut not every entity needs to be under configuration management control all the time.Two Issues:wWhat:Selection of Configuration ItemstWhat should be under configuration control?wWhen:When do you start to place entities under configuration control

21、?Conflict for the Project Manager:wStarting with CIs too early introduces too much bureaucracywStarting with CIs too late introduces chaosBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 13Finding Configuration Items(continued)Some items must be maintaine

22、d for the lifetime of the software.This includes also the phase,when the software is no longer developed but still in use;perhaps by industrial customers who are expecting proper support for lots of years.An entity naming scheme should be defined so that related documents have related names.Selectin

23、g the right configuration items is a skill that takes practicewVery similar to object modelingwUse techniques similar to object modeling for finding Cis!tFind the CIstFind relationships between CIsBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 14Which o

24、f these Entities should be Configuration Items?Problem Statement Software Project Management Plan(SPMP)Requirements Analysis Document(RAD)System Design Document(SDD)Project Agreement Object Design Document (ODD)Dynamic ModelObject modelFunctional Model Unit testsIntegration test strategySource codeA

25、PI SpecificationInput data and data basesTest planTest dataSupport software(part of the product)Support software(not part of the product)User manualAdministrator manualBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 15Possible Selection of Configuration

26、ItemsProblem Statement Software Project Management Plan(SPMP)4Requirements Analysis Document(RAD)4System Design Document(SDD)Project Agreement 4Object Design Document (ODD)Dynamic ModelObject modelFunctional Model 4Unit testsIntegration test strategy4Source codeAPI Specification4Input data and data

27、basesTest plan4Test data4Support software(part of the product)Support software(not part of the product)User manualAdministrator manualOnce the Configuration Items are selected,they are usually organized in a treeBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and

28、 Java 16“The project”CIModelsSubsystemsDocumentsObject ModelDynamic ModelDatabaseUser Interface.CodeDataUnit TestRADODD.“The project”Configuration Item Tree(Example)Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 17Terminology:Version The initial release

29、 or re-release of a configuration item associated with a complete compilation or recompilation of the item.Different versions have different functionality.Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 18Terminology:Baseline “A specification or product

30、that has been formally reviewed and agreed to by responsible management,that thereafter serves as the basis for further development,and can be changed only through formal change control procedures.”Examples:Baseline A:All the API have completely been defined;the bodies of the methods are empty.Basel

31、ine B:All data access methods are implemented and tested.Baseline C:The GUI is implemented.Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 19More on BaselinesAs systems are developed,a series of baselines is developed,usually after a review(analysis revi

32、ew,design review,code review,system testing,client acceptance,.)wDevelopmental baseline (RAD,SDD,Integration Test,.)tGoal:Coordinate engineering activities.wFunctional baseline (first prototype,alpha release,beta release)t Goal:Get first customer experiences with functional system.wProduct baseline

33、(product)tGoal:Coordinate sales and customer support.Many naming scheme for baselines exist(1.0,6.01a,.)A 3 digit scheme is quite common:Release(Customer)Version (Developer)Revision(Developer)Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 20Baselines in

34、 SCMOfficial ReleaseBaseline A(developmental)Baseline B(functional,first prototype)Baseline C(functional,beta test)How do we manage changes in the baselines?TimeBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 21Change managementChange management is the h

35、andling of change requestswA change request leads to the creation of a new release General change processwThe change is requested(this can be done by anyone including users and developers)wThe change request is assessed against project goalswFollowing the assessment,the change is accepted or rejecte

36、dwIf it is accepted,the change is assigned to a developer and implementedwThe implemented change is audited.The complexity of the change management process varies with the project.Small projects can perform change requests informally and fast while complex projects require detailed change request fo

37、rms and the official approval by one more managers.Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 22Two types of controlling change:wPromotion:The internal development state of a software is changed.wRelease:A changed software system is made visible out

38、side the development organization.Approaches for controlling change(Change Policy)wInformal(good for research type environments and promotions)wFormal approach(good for externally developed CIs and for releases)Controlling ChangesPromotionReleaseSoftware RepositoryUserProgrammerPromotePolicyReleaseP

39、olicyMasterDirectoryBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 23Terminology:SCM DirectoriesProgrammers Directory(IEEE:Dynamic Library)wLibrary for holding newly created or modified software entities.wThe programmers workspace is controlled by the p

40、rogrammer only.Master Directory(IEEE:Controlled Library)wManages the current baseline(s)and for controlling changes made to them.wEntry is controlled,usually after verification.wChanges must be authorized.Software Repository(IEEE:Static Library)wArchive for the various baselines released for general

41、 use.wCopies of these baselines may be made available to requesting organizations.Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 24Foo95Foo98Standard SCM DirectoriesProgrammers Directory w(IEEE Std:“Dynamic Library”)wCompletely under control of one prog

42、rammer.Master Directory w(IEEE Std:“Controlled Library”)wCentral directory of all promotions.Software Repositoryw(IEEE Std:“Static Library”)wExternally released baselines.Central sourcecode archiveReleasePromotionBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,an

43、d Java 25.“The project”CIpromote()release()DocumentsODD“The project”CIModelsSubsystemsObject ModelDynamic ModelDatabaseUser InterfaceCodeDataUnit TestRAD.“The project”Promotion and Release are Operations on CIsBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and J

44、ava 26Lets Create a Model for Configuration Management ReleaseReleaseRepositoRepositoryryPromotionPromotionMaster Master DirectoryDirectory*We just learned that promotions are stored in the master directory and releases are stored in the repository Problem:There can be many promotions and many relea

45、ses Solution:Use Multiplicity Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 27Lets Create a Model for Configuration Management ReleaseReleasePromotionPromotionRepositoRepositoryryMaster Master DirectoryDirectory*Insight:Promotions and Releases are both

46、 versions VersionVersionSolution:Use Inheritance Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 28Lets Create a Model for Configuration Management ReleaseReleasePromotionPromotionRepositoRepositoryryMaster Master DirectoryDirectory*Problem:A configurati

47、on item has many versionsVersionVersionConfiguration ItemConfiguration Item*Solution:Create a 1-many association between Configuration Item and VersionBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 29Lets Create a Model for Configuration Management Rele

48、aseReleasePromotionPromotionRepositoRepositoryryMaster Master DirectorDirectory y*Problem:Configuration items can themselves be groupedVersionVersionSolution:Use the composite design pattern Configuration ItemConfiguration Item*Configuration itemConfiguration itemControlled itemControlled itemCM Agg

49、regateCM AggregateBernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 30Configuration Item Model(UML Class Diagram)VersionVersion*Controlled Controlled itemitem*CM AggregateCM AggregateConfigurationConfiguration item itemReleaseReleasePromotionPromotionRepos

50、itoryRepositoryMaster Master DirectoryDirectory*Bernd Bruegge&Allen H.Dutoit Object-Oriented Software Engineering:Using UML,Patterns,and Java 31Change PoliciesWhenever a promotion or a release is performed,one or more policies apply.The purpose of change policies is to guarantee that each version,re