CM2-13 Yazılım Yaşam Döngüsünün CM2 ile Optimizasyonu

15.4.2019

2 Gün

Halime ORHON

BİLKENT OTEL VE KONFERANS MERKEZİ

4100,00 TRL

EĞİTİM YERİ :

BİLKENT OTEL VE KONFERANS MERKEZİ

İhsan Doğramacı Bul. No:6 Bilkent 06800 Ankara-Türkiye

ÜCRETLERİMİZE KDV DAHİL DEĞİLDİR. ÖDEMELERDE %18 KDV UYGULANACAKTIR.

CM2-13 YAZILIM YAŞAM DÖNGÜSÜNÜ CM2 İLE YÖNETMEK

This course describes how the CM2 model for configuration management and integrated process excellence can be applied to software.

The challenge boils down to what you believe. You either expect software code to come out right-the-first-time, or you do not.

The process you put in place will be designed accordingly. The CM2 model is designed to ensure that code comes out right-the-first-time.

This does not mean software development is not an iterative process. It is where the iterations take place that is most important.

With CM2, the customer and the developer gain a good grasp of what the overall product is going to be at an early point in its lifecycle.

With CM2, the development effort is led by a cross-functional team whose members have the full range of needed expertise.

The same members serve as the change review board. Change decisions are made quickly and, if approved, implemented promptly.

CM2 is a waterfall model with spiraling at each level. It excels at ensuring that software design definition is clear, concise and valid.

Source code is not written until the design to be achieved by that code has been documented, validated and released by its co-owners.

PROGRAMIN İÇERİĞİ

ABOUT CM AND BASIS FOR THE CM2 MODEL

  • A. An Organization Runs on Requirements
  • B. Structuring of Requirements
  • C. Corrective Action, Causes and Solutions
  • D. Design Basis for the CM2 Model

DEVELOPMENT AND CHANGE PROCESS MODEL

  • E. Proven CM2/IPE Development Process
  • F. Dual Cycles of Project Management
  • G. CM2 Closed-Loop Change Process

SOFTWARE DEVELOPMENT METHODOLOGIES

  • H. Defining System User Requirements
  • I. Software Design Definition with UML
  • J. Development Using Waterfall vs Spiral
  • K. Agile Software Development Process

THE MISSING LINK: DESIGN BASIS VIEWS

  • L. Defining the High-Level Requirements
  • M. Software End-Item Hierarchy & Baseline
  • N. Software Development Cost Estimates

KİMLER KATILABİLİR

Yazılım dünyasındaki tüm yöneticiler, mühendisler, uzmanlar; yazılım değişiklik ve konfigürasyon uzmanları

EĞİTMEN

Halime ORHON

 Halime Orhon

captchaImage