Chapter 4 · Development Technology ▶ Video ကြည့်ပြီး
Video Lesson တွေက Haru အတန်းသားတွေအတွက်ပါ အတန်းမအပ်သေးပဲ
Haru ဆီမှာ အစမ်းသင်ကြည့်ချင်ပါသလား? သင်တန်းသားတွေရဲ့ စကားသံများ × Highlighted text? Practice this concept. Highlighted passages and figures open related questions.
Practice related questions (1) Progress & bookmarks ⌄ Current section
3-3-2 Change Managementp. 300
Progress Not marked complete
◇ Bookmark lesson Mark lesson complete Related questions in this lesson 1 Configuration status and versions 1 Progress and bookmarks p. 300 · PDF 304
3-3-2 Change Management Change management refers to the software configuration management process activities/tasks, in which changes to software configuration items are centrally managed and reflected in configuration management.
[Activities and tasks related to change control ] (i) Configuration control Identification and recording of change requests, analysis and evaluation of changes, approval or rejection of change requests, and implementation, verification, and release of modified software items are performed. (ii) Recording of configuration status The number of times changes are made in a project, the latest version, migration (or release) status, and such others are documented as management records and status reports. (iii) Evaluation and assessment of integrity of configuration items The functional completeness (e.g., consistency, accuracy) and the physical completeness (e.g., whether the latest technical descriptions are reflected) of software items are determined and guaranteed. (iv) Release management and delivery (or shipment) The release and delivery of software products and documentation are formally controlled. Master copies of the delivered items are maintained, with version management, for a period of retention equal to the lifespan of the software product, which is based on SLCP (Software Life Cycle Process). · 1 question
New FE Textbook Vol.2 · First Edition, April 2015