Software Configuration Management SEII - Lecture 21

Software Configuration ManagementSEII-Lecture 21Dr. Muzafar KhanAssistant ProfessorDepartment of Computer ScienceCIIT, Islamabad.RecapChange managementSoftware configuration managementSCM scenarioElements of SCMComponent, process, construction, and human elementsSCM repositorySCM processIdentification of objects2Version ControlProcedures and tools to manage different versions of objectsFour major capabilitiesProject repositoryVersion management capabilityMake facilityIssue/bug trackingEstablish a change set- a collection of all changes3Change Control [1/3]Balanced approachUncontrolled change leads to chaos in large projectsCombines human procedures and toolsChange request is submitted and evaluated to Assess technical meritPotential side effectsOverall impact on other objects and system functionsThe projected cost of the change4Change Control [2/3]Change reportChange control authorityFinal decision on the status and priority of changeEngineering change orderDescribes the change to be madeThe constraints that must be respectedThe criteria for review and auditVersion control system updates the original file after the change5Change Control [3/3]Change control and version controlAccess controlAuthority to access and modify the objectSynchronization controlParallel changes are not overwriteInformal change control prior to SCI becomes baselineFormal change control after the product delivery 6Configuration Audit [1/2]Identification, version control, and change controlHow to ensure changes are implementedTechnical reviews Software configuration auditSC audit compliments technical reviewsQuestions to answer7Configuration Audit [2/2]Has the change specified in the ECO been made? Have any additional modifications been incorporated?Has a technical review been conducted to assess technical correctness? Has the software process been followed and have software engineering Standards been properly applied?Has the change been "highlighted" in the SCI? Have the change date and change author been specified? Do the attributes of the configuration object reflect the change?Have SCM procedures for noting the change, recording it, and reporting it been followed?Have all related SCIs been properly updated?8Status ReportingConfiguration status reporting / status accountingWhat happened?How did it?When did it happen?What else will be affected?CSR entry is made in case of updated SCIWhen configuration audit is conducted, results are reported as a part of CSR taskOutput from CSR is placed online for useCSR report is generated for regular intervals9Configuration Management for WebApp [1/2]More frequent changesContentVariety of contentChallenge is to organize it rationally Conventional data modeling techniquesPeopleAd hoc manner No SE backgroundNo change management10Configuration Management for WebApp [2/2]ScalabilitySize and complexity growChanges may have larger impactPoliticsWho “owns” a WebApp?Who assumes responsibility for the accuracy of the information on the website?Who ensures that quality control processes have been followed before information is published to the site?Who is responsible for making changes?Who assumes the cost of change?11Content Management [1/2]Related to configuration managementDynamic WebAppCollection subsystemCreate / acquire contentConvert content to presentable formOrganize content into packetsManagement subsystemContent databaseDatabase capabilitiesConfiguration management functions12Content Management [2/2]Publishing subsystemStatic elementsPublication serviceExternal services13Change Management [1/2]Classification of changesClass 1Corrects an error or enhance local content or functionalityClass 2An impact on other content objects or functional objectsClass 3Broad impact on WebAppClass 4Major design change14Change Management [2/2]15Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 607Version ControlA central repository for the webApp project should be establishedEach Web engineer creates his or her own working folderThe clocks on all developer workstations should be synchronizedAs new configuration objects are developed or existing objects are changed, they are imported into the central repositoryAs objects are imported or exported from the repository, an automatic, time-stamped log message is made16Auditing and ReportingLog should be maintained for check-in and check-outComplete log report for all team membersAn automated email notification to stakeholders for every check-in and check-out17SummaryVersion controlProject repository, version management capability, make facility, issue/bug trackingChange controlConfiguration auditcompliments technical reviewsStatus reportingConfiguration management for WebAppContent, people, scalability, politics18