All language subtitles for 6. Requirements Attributes

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
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
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
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
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
pl Polish
pt-BR Portuguese (Brazil)
pt-PT Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
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 1 00:00:01,150 --> 00:00:04,560 Here are the key attributes of requirements. 2 2 00:00:04,560 --> 00:00:08,400 First, they identify what the project needs, 3 3 00:00:08,400 --> 00:00:10,263 not how it will be done. 4 4 00:00:11,560 --> 00:00:13,550 For example, you only need to know 5 5 00:00:13,550 --> 00:00:15,890 how many students the school will hold, 6 6 00:00:15,890 --> 00:00:18,723 the color of the classrooms is not a cost driver. 7 7 00:00:19,890 --> 00:00:21,600 While it's true that missing requirements 8 8 00:00:21,600 --> 00:00:24,320 is the typical problem, you don't want to overload 9 9 00:00:24,320 --> 00:00:26,330 the planning requirements with detail 10 10 00:00:26,330 --> 00:00:28,953 that does not drive time and cost. 11 11 00:00:30,540 --> 00:00:31,900 The detailed design requirements, 12 12 00:00:31,900 --> 00:00:34,620 or how the project level requirements will be achieved, 13 13 00:00:34,620 --> 00:00:37,953 are defined later as the first step in execution. 14 14 00:00:40,300 --> 00:00:45,023 Second, requirements identify the needs, not the wants. 15 15 00:00:46,060 --> 00:00:48,550 There's an old business analyst expression: 16 16 00:00:48,550 --> 00:00:51,573 users know what they want, not always what they need. 17 17 00:00:52,680 --> 00:00:56,300 Users will try to define the solution they want upfront; 18 18 00:00:56,300 --> 00:00:59,890 however, the best way to create the best solution 19 19 00:00:59,890 --> 00:01:02,320 is to gather all the needs first 20 20 00:01:02,320 --> 00:01:05,460 and then let a good team consider them all together 21 21 00:01:05,460 --> 00:01:07,923 and develop the best way to meet them as a group. 22 22 00:01:09,650 --> 00:01:11,540 One of the most useful techniques 23 23 00:01:11,540 --> 00:01:13,940 is to keep asking the why question 24 24 00:01:13,940 --> 00:01:16,753 until they dig down deep and tell you the real need. 25 25 00:01:18,070 --> 00:01:21,447 For example, the user says, "I need a Rolls Royce." 26 26 00:01:22,490 --> 00:01:23,757 Why? 27 27 00:01:23,757 --> 00:01:24,807 "I have to have one." 28 28 00:01:25,690 --> 00:01:26,837 Why? 29 29 00:01:26,837 --> 00:01:28,367 "Well, I need to travel." 30 30 00:01:29,239 --> 00:01:30,073 Why? 31 31 00:01:31,187 --> 00:01:34,330 "Well, I need to attend a meeting across town once a month." 32 32 00:01:34,330 --> 00:01:37,393 A-ha, that's the requirement. 33 33 00:01:39,194 --> 00:01:41,810 A good requirement set will also define 34 34 00:01:41,810 --> 00:01:45,563 the project boundary, what is in as well as what is out. 35 35 00:01:46,640 --> 00:01:50,140 For example, which sites are in, which departments, 36 36 00:01:50,140 --> 00:01:52,740 the amount of training, how much support, et cetera. 37 37 00:01:53,960 --> 00:01:55,580 And if anything is out of scope, 38 38 00:01:55,580 --> 00:01:58,900 saying so in the requirements also helps define what is in, 39 39 00:01:58,900 --> 00:02:01,770 making the project boundary clear. 40 40 00:02:01,770 --> 00:02:02,980 For example, if training and support 41 41 00:02:02,980 --> 00:02:05,253 is not included, write that down. 42 42 00:02:07,380 --> 00:02:09,700 When finished, the key features 43 43 00:02:09,700 --> 00:02:11,690 of a good requirement set are: 44 44 00:02:11,690 --> 00:02:14,200 they are complete, not missing anything 45 45 00:02:14,200 --> 00:02:16,223 that will drive cost or schedule; 46 46 00:02:17,420 --> 00:02:21,270 they're consistent, no requirement contradicts another - 47 47 00:02:21,270 --> 00:02:24,480 this is where the business analysts can really help; 48 48 00:02:24,480 --> 00:02:29,480 and provable, each requirement must be provable 49 49 00:02:29,700 --> 00:02:32,713 by some demonstration, test, or analysis. 50 50 00:02:33,740 --> 00:02:36,740 In other words, it's not specific enough for a requirement 51 51 00:02:36,740 --> 00:02:38,910 to say a building must be secure, 52 52 00:02:38,910 --> 00:02:40,880 since that's too fuzzy to build 53 53 00:02:40,880 --> 00:02:43,073 or see how to prove it at the end. 54 54 00:02:44,260 --> 00:02:47,030 If the customer wants industrial security level five 55 55 00:02:47,030 --> 00:02:50,660 door locks, then that is what the requirement should say. 56 56 00:02:50,660 --> 00:02:52,620 That's clear enough to build 57 57 00:02:52,620 --> 00:02:55,790 and be provable at the end of the project. 58 58 00:02:55,790 --> 00:02:58,530 We'll look at the door locks, examine the model numbers, 59 59 00:02:58,530 --> 00:02:59,460 and ensure they all meet the 60 60 00:02:59,460 --> 00:03:01,940 industrial security level number five standard. 61 61 00:03:01,940 --> 00:03:04,663 The requirement is provable. 5318

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