All language subtitles for SDLC Vs STLC_ Software Development Life Cycle and Software Testing Life Cycle - English

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian Download
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:05,759 --> 00:00:10,639 suppose you were assigned a task to 2 00:00:07,600 --> 00:00:12,880 develop a custom software for a client 3 00:00:10,639 --> 00:00:15,000 each block below represents a step 4 00:00:12,880 --> 00:00:17,480 required to develop the 5 00:00:15,000 --> 00:00:19,880 software irrespective of your technical 6 00:00:17,480 --> 00:00:21,640 background try and make an educated 7 00:00:19,880 --> 00:00:25,080 guess about the sequence of steps you 8 00:00:21,640 --> 00:00:25,080 will follow to achieve the 9 00:00:25,920 --> 00:00:31,000 task the correct sequence would be 10 00:00:28,960 --> 00:00:33,160 gather as much information is possible 11 00:00:31,000 --> 00:00:36,520 about the details and specifications of 12 00:00:33,160 --> 00:00:38,399 the desired software from the client 13 00:00:36,520 --> 00:00:39,760 this is nothing but the requirements 14 00:00:38,399 --> 00:00:43,000 Gathering 15 00:00:39,760 --> 00:00:48,160 stage plan the programming language like 16 00:00:43,000 --> 00:00:51,879 Java php.net and database like Oracle 17 00:00:48,160 --> 00:00:54,520 MySQL Etc which will best suit the 18 00:00:51,879 --> 00:00:55,680 project also determine high level 19 00:00:54,520 --> 00:00:58,719 functions in 20 00:00:55,680 --> 00:01:01,480 architecture this is the design 21 00:00:58,719 --> 00:01:04,640 stage at actually code the 22 00:01:01,480 --> 00:01:07,560 software this is the build stage next 23 00:01:04,640 --> 00:01:09,960 you test the software to verify that it 24 00:01:07,560 --> 00:01:13,560 is built as per the specifications given 25 00:01:09,960 --> 00:01:16,080 by the client this is the test 26 00:01:13,560 --> 00:01:18,520 stage once your software product is 27 00:01:16,080 --> 00:01:20,640 ready you may do some code changes to 28 00:01:18,520 --> 00:01:24,680 accommodate enhancements requested by 29 00:01:20,640 --> 00:01:27,640 the client this would be the maintenance 30 00:01:24,680 --> 00:01:29,479 stage all these levels constitute the 31 00:01:27,640 --> 00:01:31,399 waterfall method of a software 32 00:01:29,479 --> 00:01:34,399 development life 33 00:01:31,399 --> 00:01:36,680 cycle as you may observe testing in the 34 00:01:34,399 --> 00:01:38,600 model starts only after implementation 35 00:01:36,680 --> 00:01:41,000 is done but if you are working on a 36 00:01:38,600 --> 00:01:43,880 large project where the systems are 37 00:01:41,000 --> 00:01:46,360 complex it's easy to miss key details in 38 00:01:43,880 --> 00:01:48,680 the requirements phase itself in such 39 00:01:46,360 --> 00:01:50,520 cases an entirely wrong product will be 40 00:01:48,680 --> 00:01:53,000 delivered to the client you will have to 41 00:01:50,520 --> 00:01:55,479 start aresh with the 42 00:01:53,000 --> 00:01:58,000 project or if you manage to note the 43 00:01:55,479 --> 00:02:00,000 requirements correctly but make serious 44 00:01:58,000 --> 00:02:02,200 mistakes in design and architecture of 45 00:02:00,000 --> 00:02:05,880 your software you will have to redesign 46 00:02:02,200 --> 00:02:08,239 the entire software to correct the 47 00:02:05,880 --> 00:02:10,319 error assessments of thousands of 48 00:02:08,239 --> 00:02:12,040 projects have shown that defects 49 00:02:10,319 --> 00:02:14,480 introduced during requirements and 50 00:02:12,040 --> 00:02:15,800 design make up close to half of the 51 00:02:14,480 --> 00:02:18,800 total number of 52 00:02:15,800 --> 00:02:21,239 defects also the costs of fixing a 53 00:02:18,800 --> 00:02:24,239 defect increases across the development 54 00:02:21,239 --> 00:02:26,760 life cycle the earlier in the life cycle 55 00:02:24,239 --> 00:02:30,000 a defect is detected the cheaper it is 56 00:02:26,760 --> 00:02:31,360 to fix as they say A Stitch in Time 57 00:02:30,000 --> 00:02:34,879 saves 58 00:02:31,360 --> 00:02:37,239 nine to address this concern the V model 59 00:02:34,879 --> 00:02:39,840 of testing was developed for every phase 60 00:02:37,239 --> 00:02:42,879 in the development life 61 00:02:39,840 --> 00:02:45,879 cycle there is a corresponding testing 62 00:02:42,879 --> 00:02:48,280 phase the left side of the model is the 63 00:02:45,879 --> 00:02:51,080 software development life cycle 64 00:02:48,280 --> 00:02:53,800 sdlc the right side of the model is the 65 00:02:51,080 --> 00:02:57,200 software test life cycle 66 00:02:53,800 --> 00:02:59,959 stlc the entire figure looks like a V 67 00:02:57,200 --> 00:03:01,959 hence the name V model in this figure 68 00:02:59,959 --> 00:03:04,599 you'll find a few stages different from 69 00:03:01,959 --> 00:03:06,519 the waterfall method these differences 70 00:03:04,599 --> 00:03:09,720 along with the details of each testing 71 00:03:06,519 --> 00:03:12,239 phase will be discussed in a later 72 00:03:09,720 --> 00:03:14,920 tutorial apart from the V model there 73 00:03:12,239 --> 00:03:17,280 are iterative development models where 74 00:03:14,920 --> 00:03:19,360 development is carried out in phases 75 00:03:17,280 --> 00:03:22,000 with each phase adding a functionality 76 00:03:19,360 --> 00:03:24,120 to the software each phase comprises of 77 00:03:22,000 --> 00:03:26,519 its own independent set of development 78 00:03:24,120 --> 00:03:28,480 and testing activities good examples of 79 00:03:26,519 --> 00:03:31,480 development life cycles following the 80 00:03:28,480 --> 00:03:34,760 iterative method are rapid application 81 00:03:31,480 --> 00:03:36,799 development and Agile 82 00:03:34,760 --> 00:03:39,400 development before we close this 83 00:03:36,799 --> 00:03:41,799 tutorial here are a few 84 00:03:39,400 --> 00:03:44,120 pointers you must note that there are 85 00:03:41,799 --> 00:03:46,640 numerous development life cycle 86 00:03:44,120 --> 00:03:48,680 models the development model selected 87 00:03:46,640 --> 00:03:50,400 for a project depends on the aims and 88 00:03:48,680 --> 00:03:53,239 goals of that 89 00:03:50,400 --> 00:03:55,680 project testing is not a standalone 90 00:03:53,239 --> 00:03:58,159 activity and it has to adapt with the 91 00:03:55,680 --> 00:04:01,319 development model chosen for the 92 00:03:58,159 --> 00:04:02,920 project in any model testing should be 93 00:04:01,319 --> 00:04:05,720 performed at all 94 00:04:02,920 --> 00:04:09,560 levels right from requirements Gathering 95 00:04:05,720 --> 00:04:09,560 all the way up to maintenance6886

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.