a5103a6df82832dcbc0703b2aa3076d1.ppt
- Количество слайдов: 16
Experience from the maintenance phase in international projects Dragan Bojić University of Belgrade
General Projects Characteristics 4 Both for software market and for known customer (outsourcing) 4 Geographically distributed development/testing/deployment • Most communication via Internet (emails, ftp, . . . ) • Offline integration (no web VCS) 4 Iterative development • • • Alpha release (Prototype) Beta release Production release 1. 0. 1 (patch for user XY) Production release 1. 1 (new functionality). . . 4 „maintenance“ – moving from one release to another Dragan Bojić, Experience from the maintenance phase in international projects 2
Supporting processes for the maintenance phase 4 Configuration management & Change Request Management 4 Purpose: „control change to, and maintain integrity of, project artifacts“ (Rational Unified Process) 4 Artifact: intermediate or final work products produced and used during a project • • Models Documents Source code. . . Dragan Bojić, Experience from the maintenance phase in international projects 3
Configuration Management 4 Process organization at Ristan. CASE, Gmb. H • About 30 team members • Telejob working environment 4 Offline integration Dragan Bojić, Experience from the maintenance phase in international projects 4
CM with offline integration – team member actions baseline 1: Store baseline from delivery media to local repository with tailoring DAC_5_0_A 100 Team Member NN Local CM baseline DAC_5_0_A 100 repository 2: Checkout to local workspace branch A 100 NN 1 delta file 3: Verify & resolve integration conflicts 4: Make some changes 5: Checkin to repository 6: Send delta for integration NN's Workspace FTP server Dragan Bojić, Experience from the maintenance phase in international projects 5
CM with offline integration 2: Store deltas to local repository 1: Send integration notice FTP server Integrator 3: Checkout to workspace 4: Merge NN 1 changes 6: Resolve integration conflicts Integration Workspace 5: Merge XY 4 changes 7: Checkin new baseline DAC_5_0_A 100 branch A 100 NN 1 delta file branch A 100 XY 4 delta file Local CM baseline repository DAC_5_0_A 101 8: Create distribution Dragan Bojić, Experience from the maintenance phase in international projects 6
Configuration Management- Access Control 4 A Workspace: defines access rights to individual artifacts (not accessible at all, read only, read-write). 4 Associated with groups of team members: • w. DEV – developers workspace (source code files, models, etc) • w. DEV_Subsystem. X – part od w. DEV assoc with a particular subsystem (component) • w. TST – test team member workspace (test specs, test cases, etc) • w. DOC – user documentation workspace • w. MGR – manager workspace (plans, reports, etc) 4. access file for mapping project directories and individual artifacts to workspaces: diadgdicadglib | w. DEV_ADG+ diadgdicadgmdlconfiguration. cat | w. DEV_ADG 4. workspace file for mapping workspaces to team members DB w. MNG w. DEV_SA w. DEV_MTR w. DOC DG w. DEV_PM w. DEV_UDA w. DEV_SUP w. DEV_SC 4 Chmod like tool for integrator to manage access rigths Dragan Bojić, Experience from the maintenance phase in international projects 7
Configuration Management- Baseline and branch identification DAC_5_0_A 001 NN 2 • • • Project Name (DAC) Mayor release (5) Minor release (0) Promotion level (explained below) (A) Baseline identifier (001) For branches, initials of team member and branch number (NN 2) 4 Promotion level: • • • an attribute of the baseline Indicates its quality or stability A – alpha (internal integration, instable working baseline) B – beta (distributed to selected outside users) R – release candidate (released after testing and decision of product team) Dragan Bojić, Experience from the maintenance phase in international projects 8
Change Management 4 Change Request: submitted request for new features, enhancements, defect elimination, . . . 4 Submitted by customers (via support), developers, testers, managers, . . . 4 Several hundred change requests between two mayor releases 4 Need to formalize and systematically process each Dragan Bojić, Experience from the maintenance phase in international projects 9
CR Submitter Project Manager Product Team Change M. - Assesment Assigns id NNNN, opens topic #36 CRNNNN# Status: Open Sends RCLS mail topic #50 CRALL# Forms 1 and 2 need more info Submitter replies Assesment PT decides Sends request via topic #36 CRNNNN# forms 1 i 2 Status: Open rejected Form 1 -3 Status: PT to decide Study CR deferred accepted rejected Decision Fills in form 3, status Dissaproved Fills in form 3, status Deffered Sends notice via topic #36 CRNNNN# deferred Status: Approved, fills in form 3 accepted Planning the realization Dragan Bojić, Experience from the maintenance phase in international projects 10
CR Submitter Project Manager Implementer Updates plans Inititates implementation via #36 CRNNNN/DEV# (form 4) Status Assigned Verifier Chg M. - Realization Assesment, then implementation Completion report (succeed fail) via #36 CRNNNN/DEV# form 4 more activities needed Status Assesment Success Failure Status: Completed form 5 u #36 CRNNNN/SQA# Sends report (Form 4) via #36 CRNNNN# Status: Rejected Verification Completion report (succed, fail) via #36 CRNNNN/SQA# (form 2) Verif. failed Sends Report (form 4) via #36 CRNNNN/ DEV# Status: Verification Failed Status assesment Verification Passed Send report (Form 4) via #36 CRNNNN# Status: Closed Dragan Bojić, Experience from the maintenance phase in international projects 11
Chg M. – Change Request States Dragan Bojić, Experience from the maintenance phase in international projects 12
Form 1: for CR Submitter Dragan Bojić, Experience from the maintenance phase in international projects 13
Form 2: for Verifier Dragan Bojić, Experience from the maintenance phase in international projects 14
Form 3: for Managers Dragan Bojić, Experience from the maintenance phase in international projects 15
Form 4: for Implementer Dragan Bojić, Experience from the maintenance phase in international projects 16


