about summary refs log tree commit diff
path: root/usth/ICT2.7/P1L5 Requirements Gathering Subtitles/3 - Choosing Good Questions Solution - lang_en_vs3.srt
blob: 3c29d6b9ce4bfea2aa46b141bcb86fec128b3a5a (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
1
00:00:00,450 --> 00:00:03,260
The last question is almost never a reasonable one. For one

2
00:00:03,260 --> 00:00:05,660
thing, the client should not need to know or care about

3
00:00:05,660 --> 00:00:08,412
how many lines of code make up the program's source code.

4
00:00:08,412 --> 00:00:09,910
In forming requirements, you should avoid

5
00:00:09,910 --> 00:00:11,940
implementation specific questions that do not

6
00:00:11,940 --> 00:00:15,290
directly interface with the user. The first question is very relevant

7
00:00:15,290 --> 00:00:18,830
in some situations. For example, a graphic sentence with video game or

8
00:00:18,830 --> 00:00:21,630
performance is key. However, you should not write any operating system

9
00:00:21,630 --> 00:00:25,620
specific code unless absolutely needed, and should strive to make your code

10
00:00:25,620 --> 00:00:28,070
platform independent whenever possible. The

11
00:00:28,070 --> 00:00:30,990
second question, however, is very relevant.

12
00:00:30,990 --> 00:00:32,870
Now that you've thought a bit about what you might ask of

13
00:00:32,870 --> 00:00:35,810
the client requesting this program, let's watch Alvin, one of Udasea's

14
00:00:35,810 --> 00:00:39,850
engineers, asking his own questions. He'll be speaking with Lauren, the client.