Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 1 00:00:01,200 --> 00:00:02,260 Here are key points 2 2 00:00:02,260 --> 00:00:04,103 to keep in mind about requirements. 3 3 00:00:05,248 --> 00:00:08,020 A long-time convention is that each requirement 4 4 00:00:08,020 --> 00:00:10,360 includes the word �shall�. 5 5 00:00:10,360 --> 00:00:12,269 If a requirement does not have the word �shall�, 6 6 00:00:12,269 --> 00:00:14,714 it is only guidance and might be helpful, 7 7 00:00:14,714 --> 00:00:17,020 however, according to standard process 8 8 00:00:17,020 --> 00:00:18,963 can be ignored by the project team. 9 9 00:00:19,927 --> 00:00:24,777 So the requirements read like, "The ABC shall do XYZ." 10 10 00:00:25,685 --> 00:00:28,200 Even though shall has been used for so long, 11 11 00:00:28,200 --> 00:00:30,300 some organizations prefer to use the slightly more 12 12 00:00:30,300 --> 00:00:34,270 natural sounding �must�, which is fine, but don't use both, 13 13 00:00:34,270 --> 00:00:35,643 pick one or the other. 14 14 00:00:37,071 --> 00:00:39,250 The requirements document typically collects 15 15 00:00:39,250 --> 00:00:42,720 related requirements together into sections, 16 16 00:00:42,720 --> 00:00:46,400 such as, functions, facilities, interfaces, 17 17 00:00:46,400 --> 00:00:48,910 documents, training, support, et cetera, 18 18 00:00:48,910 --> 00:00:49,993 whatever makes sense. 19 19 00:00:51,940 --> 00:00:54,740 If you have to prioritize requirements, 20 20 00:00:54,740 --> 00:00:57,160 use a maximum of two levels, 21 21 00:00:57,160 --> 00:00:59,183 mandatory and desirable. 22 22 00:01:00,290 --> 00:01:01,850 But be careful about this. 23 23 00:01:01,850 --> 00:01:05,763 One priority is best, just the mandatory requirements. 24 24 00:01:06,622 --> 00:01:08,994 If you use two levels, be prepared 25 25 00:01:08,994 --> 00:01:11,360 to get only the mandatory. 26 26 00:01:11,360 --> 00:01:13,053 They are usually hard enough. 27 27 00:01:14,550 --> 00:01:16,470 A second priority can be used 28 28 00:01:16,470 --> 00:01:18,360 to include non-essential requirements 29 29 00:01:18,360 --> 00:01:20,230 when a stakeholder demands they be included 30 30 00:01:20,230 --> 00:01:21,910 and you can't talk them out of it, 31 31 00:01:21,910 --> 00:01:23,793 but they inevitably confuse the team. 32 32 00:01:24,914 --> 00:01:27,731 When I have managed projects with desirable requirements, 33 33 00:01:27,731 --> 00:01:31,540 I've started by telling the team to ignore them, 34 34 00:01:31,540 --> 00:01:34,050 and then reviewed them only once in a while, 35 35 00:01:34,050 --> 00:01:36,130 such as when choosing products from vendors 36 36 00:01:36,130 --> 00:01:37,290 to see if any can be worked in 37 37 00:01:37,290 --> 00:01:41,332 with near zero disruption, which is rarely the case. 38 38 00:01:41,332 --> 00:01:43,640 If a requirement is really important, 39 39 00:01:43,640 --> 00:01:46,760 it should be made mandatory, otherwise 40 40 00:01:46,760 --> 00:01:49,691 it should be included in a separate follow-on project. 41 41 00:01:49,691 --> 00:01:52,400 Complexity is the challenge, 42 42 00:01:52,400 --> 00:01:55,203 simplicity generates great dividends. 43 43 00:01:57,440 --> 00:01:59,400 You can use a Microsoft Word table 44 44 00:01:59,400 --> 00:02:01,670 for a small number of requirements 45 45 00:02:01,670 --> 00:02:03,020 but will need an automated tool 46 46 00:02:03,020 --> 00:02:04,770 if there are more than a few dozen. 47 47 00:02:05,705 --> 00:02:08,201 A spreadsheet can work up to a few hundred 48 48 00:02:08,201 --> 00:02:10,010 and then you likely need a database 49 49 00:02:10,010 --> 00:02:12,110 or software application if there are more. 50 50 00:02:13,610 --> 00:02:16,530 You typically trace, index or cross-reference, 51 51 00:02:16,530 --> 00:02:17,960 each requirement to the deliverables 52 52 00:02:17,960 --> 00:02:21,590 that satisfy it, the tests and verifications, 53 53 00:02:21,590 --> 00:02:24,033 related documentation, et cetera. 54 54 00:02:25,610 --> 00:02:27,200 Specialized requirements applications 55 55 00:02:27,200 --> 00:02:32,200 include Doors, Jira with R4J and RMsis, and Rational. 56 56 00:02:33,970 --> 00:02:38,190 However, generalized databases like Microsoft Access 57 57 00:02:38,190 --> 00:02:41,190 or the Open Source LibreOffice Base work well 58 58 00:02:41,190 --> 00:02:42,700 if you have someone that can run it 59 59 00:02:42,700 --> 00:02:45,440 and understands requirements management. 60 60 00:02:45,440 --> 00:02:47,670 These tools are much less expensive 61 61 00:02:47,670 --> 00:02:50,570 and much more flexible, especially for generating 62 62 00:02:50,570 --> 00:02:53,033 custom entry forms and reports. 5332