Shadowing Practice: SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle - Learn English Speaking with Video

Ders oluşturuluyor...
1
Suppose you are assigned a task to develop a custom software for a client.
2
Each block below represents a step required to develop the software.
3
Irrespective of your technical background, try and make an educated guess about the sequence of steps you will follow to achieve the task.
4
The correct sequence would be gather as much information as possible about the details
5
and specifications of the desired software from the client.
6
This is nothing but the requirements gathering stage.
7
Plan the programming language like Java, PHP, .NET, and database like Oracle,
8
MySQL, etc. which will best suit the project.
9
Also determine high level functions in architecture.
10
This is the design stage.
11
Actually code the software.
12
This is the build stage.
13
Next you test the software to verify that it is built as per the specifications given by the client.
14
This is the test stage.
15
Once your software product is ready, you may do some code changes to accommodate enhancements requested by the client.
16
This would be the maintenance stage.
17
All these levels constitute the waterfall method of a software development lifecycle.
18
As you may observe, testing in the model starts only after implementation is done.
19
But if you are working on a large project where the systems are complex, it's easy to miss key details in the requirements phase itself.
20
In such cases, an entirely wrong product will be delivered to the client.
21
You will have to start afresh with the project.
22
Or if you manage to note the requirements correctly but make serious mistakes in design and architecture of your software,
23
you will have to redesign the entire software to correct the error.
24
Assessments of thousands of projects have shown that defects introduced during requirements
25
and design make up close to half of the total number of defects.
26
Also, the costs of fixing a defect increases across the development lifecycle.
27
The earlier in the lifecycle a defect is detected, the cheaper it is to fix.
28
As they say, a stitch in time saves 9.
29
To address this concern, the V model of testing was developed.
30
For every phase in the development lifecycle, there is a corresponding testing phase.
31
The left side of the model is the software development lifecycle, SDLC.
32
The right side of the model is the software test lifecycle, STLC.
33
The entire figure looks like a V, hence the name V-Model.
34
In this figure, you'll find a few stages different from the waterfall method.
35
These differences, along with the details of each testing phase, will be discussed in a later tutorial.
36
Apart from the V model, there are iterative development models, where development is carried out in phases, with each phase adding a functionality to the software.
37
Each phase comprises of its own independent set of development and testing activities.
38
Good examples of development life cycles following the iterative method are Rapid Application Development, and Agile Development.
39
Before we close this tutorial, here are a few pointers.
40
You must note that there are numerous development lifecycle models.
41
The development model selected for a project depends on the aims and goals of that project.
42
Testing is not a standalone activity, and it has to adapt with the development model chosen for the project.
43
In any model, testing should be performed at all levels, right from requirements gathering all the way up to maintenance.

Bu dersin kelimeleri ve konuşma notları

Bu videoda gölgeleme çalışması için 43 cümle ve 555 kelime var. Konuşma bölümü 4:01 sürüyor. Konuşmacı dakikada yaklaşık 138 kelimelik dengeli bir hızla konuşuyor; gölgeleme için rahat bir tempo. Kelimelerin %83’i İngilizcede en sık kullanılan 3.000 kelime arasında; geri kalanına başlamadan önce bakmakta fayda var.

Bu videodaki önemli kelimeler

Videodan daha az kullanılan 15 kelime, telaffuzu ve anlamıyla:

  • requirement /ɹɪˈkwaɪɹmənt/ (isim) — gereklilik, zaruret. A necessity or prerequisite; something required or obligatory. Its adpositions are generally of in relation to who or what has given it, on in relation to whom…
  • defect /ˈdiːfɛkt/ (isim) — eksik, kusur. A fault or malfunction.
  • gather /ˈɡæðɚ/ (fiil) — toplamak. To collect normally separate things.
  • architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (isim) — mimarlık. The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.
  • specification (isim) — şartname. An explicit set of requirements to be satisfied by a material, product, or service.
  • waterfall /ˈwɔːtəfɔːl/ (isim) — şelale, çavlan. A flow of water over the edge of a cliff.
  • custom /ˈkʌstəm/ (isim) — adet, görenek. Frequent repetition of the same behavior; way of behavior common to many; ordinary manner; habitual practice; method of doing, living or behaving.
  • hence /ˈhɛns/ (zarf) — itibaren. In the future from now.
  • introduce /ˌɪntɹəˈdus/ (fiil) — tanıştırmak. To cause (someone) to be acquainted (with someone else).
  • database /ˈdeɪtəˌbeɪs/ (isim) — veritabanı, veri tabanı. A collection of (usually) organized information in a regular structure, usually but not necessarily in a machine-readable format accessible by a computer.
  • implementation /ˌɪmplɪmənˈteɪʃən/ (isim) — tatbik (obsolecent), uygulama. The process of moving an idea from concept to reality. In business, engineering and other fields, implementation refers to the building process rather than the…
  • accommodate /əˈkɑməˌdeɪt/ (fiil) — uyum sağlamak, düzenlemek. To render fit, suitable, or correspondent; to adapt.
  • adapt /əˈdæpt/ (fiil) — uydurmak, adapte etmek. To make suitable; to make to correspond; to fit or suit.
  • educate /ˈɛd͡ʒ.əˌkeɪt/ (fiil) — eğitmek. To instruct or train.
  • verify /ˈvɛɹɪfaɪ/ (fiil) — doğrulamak. To substantiate or prove the truth of something.

Dikkat edilecek telaffuzlar

  • “sh” ve “zh” sesleri: implementation /ˌɪmplɪmənˈteɪʃən/, afresh /ʌˈfɹɛʃ/
  • Uzun kelimeler — vurguyu doğru yere koyun: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, implementation /ˌɪmplɪmənˈteɪʃən/, accommodate /əˈkɑməˌdeɪt/, iterative /ˈɪt(ə)ɹətɪv/, irrespective /ɪɹɪˈspɛktɪv/

Bu videoyla nasıl çalışılır

  1. Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
  2. Normal hızda cümle cümle tekrar edin; ritminiz konuşmacıyla aynı olana kadar her cümleyi yineleyin.
  3. Kendinizi kaydedin ve orijinaliyle karşılaştırın; requirement, defect, gather gibi kelimelere özellikle dikkat edin.

Gölgeleme Tekniği Nedir?

Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.

Shadowing tekniği: adım adım eksiksiz rehberi okuyun →