-This concludes the first part of this lesson in which - -2
-we discussed the basic object-oriented concepts. And, we started to - -3
-look at how to perform object-oriented analysis. In the second - -4
-part of the lesson, I will introduce UML, and we will - -5
-perform the object-oriented analysis steps that we just saw using - -6
-an example. A course management system so before getting to - -7
-the second part, let me introduce the example. As we - -8
-mentioned before, the first step is to start from a textual - -9
-description of the system the we need to analyze and - -10
-that we need to build. So that's exactly what I'm going - -11
-to do. I'm just going to read through this description then we'll - -12
-reuse throughout the rest of the lesson. The registration manager sets - -13
-up the curriculum for a semester using a scheduling algorithm and - -14
-the registration manager here is the registrar. So we will refer - -15
-to the registration manager both as registration manager and as registrar - -16
-in the rest of the lesson. One course may have multiple - -17
-course offerings, which is pretty standard. Each - -18
-course offering has a number, location, and a - -19
-time associated with it. Students select four primary - -20
-courses and two alternative courses by submitting a - -21
-registration form. Students might use the course management - -22
-system to add or drop courses for a - -23
-period of time after registration. Professors use the - -24
-system to receive their course offering rosters. Finally, - -25
-users of the registration system are assigned passwords which are used for - -26
-login validation. So, as you can see, this is a kind of a - -27
-high-level description of a standard course management system. So, if you ever - -28
-used a course management system, you'll - -29
-recognize some of the functionality described here. -- cgit 1.4.1