From 8a7dfa0972c83fd811a4296e7373574bea4a28d0 Mon Sep 17 00:00:00 2001 From: Nguyễn Gia Phong Date: Sun, 19 Jul 2020 20:34:40 +0700 Subject: [usth/ICT2.7] Remove Udacity transcribes --- ...- Running Example Explanation - lang_en_vs5.srt | 115 --------------------- 1 file changed, 115 deletions(-) delete mode 100644 usth/ICT2.7/P2L2 OO Software Engineering and UML Subtitles/11 - Running Example Explanation - lang_en_vs5.srt (limited to 'usth/ICT2.7/P2L2 OO Software Engineering and UML Subtitles/11 - Running Example Explanation - lang_en_vs5.srt') diff --git a/usth/ICT2.7/P2L2 OO Software Engineering and UML Subtitles/11 - Running Example Explanation - lang_en_vs5.srt b/usth/ICT2.7/P2L2 OO Software Engineering and UML Subtitles/11 - Running Example Explanation - lang_en_vs5.srt deleted file mode 100644 index 6d86101..0000000 --- a/usth/ICT2.7/P2L2 OO Software Engineering and UML Subtitles/11 - Running Example Explanation - lang_en_vs5.srt +++ /dev/null @@ -1,115 +0,0 @@ -1 -00:00:00,100 --> 00:00:02,700 -This concludes the first part of this lesson in which - -2 -00:00:02,700 --> 00:00:06,080 -we discussed the basic object-oriented concepts. And, we started to - -3 -00:00:06,080 --> 00:00:09,830 -look at how to perform object-oriented analysis. In the second - -4 -00:00:09,830 --> 00:00:12,630 -part of the lesson, I will introduce UML, and we will - -5 -00:00:12,630 --> 00:00:15,990 -perform the object-oriented analysis steps that we just saw using - -6 -00:00:15,990 --> 00:00:19,240 -an example. A course management system so before getting to - -7 -00:00:19,240 --> 00:00:22,380 -the second part, let me introduce the example. As we - -8 -00:00:22,380 --> 00:00:25,420 -mentioned before, the first step is to start from a textual - -9 -00:00:25,420 --> 00:00:27,800 -description of the system the we need to analyze and - -10 -00:00:27,800 --> 00:00:30,080 -that we need to build. So that's exactly what I'm going - -11 -00:00:30,080 --> 00:00:33,272 -to do. I'm just going to read through this description then we'll - -12 -00:00:33,272 --> 00:00:36,590 -reuse throughout the rest of the lesson. The registration manager sets - -13 -00:00:36,590 --> 00:00:40,090 -up the curriculum for a semester using a scheduling algorithm and - -14 -00:00:40,090 --> 00:00:43,600 -the registration manager here is the registrar. So we will refer - -15 -00:00:43,600 --> 00:00:47,510 -to the registration manager both as registration manager and as registrar - -16 -00:00:47,510 --> 00:00:50,500 -in the rest of the lesson. One course may have multiple - -17 -00:00:50,500 --> 00:00:52,860 -course offerings, which is pretty standard. Each - -18 -00:00:52,860 --> 00:00:55,490 -course offering has a number, location, and a - -19 -00:00:55,490 --> 00:00:59,160 -time associated with it. Students select four primary - -20 -00:00:59,160 --> 00:01:02,410 -courses and two alternative courses by submitting a - -21 -00:01:02,410 --> 00:01:05,860 -registration form. Students might use the course management - -22 -00:01:05,860 --> 00:01:08,460 -system to add or drop courses for a - -23 -00:01:08,460 --> 00:01:11,660 -period of time after registration. Professors use the - -24 -00:01:11,660 --> 00:01:15,250 -system to receive their course offering rosters. Finally, - -25 -00:01:15,250 --> 00:01:19,280 -users of the registration system are assigned passwords which are used for - -26 -00:01:19,280 --> 00:01:21,882 -login validation. So, as you can see, this is a kind of a - -27 -00:01:21,882 --> 00:01:25,440 -high-level description of a standard course management system. So, if you ever - -28 -00:01:25,440 --> 00:01:27,160 -used a course management system, you'll - -29 -00:01:27,160 --> 00:01:29,836 -recognize some of the functionality described here. -- cgit 1.4.1