Recommendations: 1) Don't use "class" for a class name... really don't. use "Course" or something appropriate. Never use keywords as class names or in parts of class names. 2) If it has to do with the class directly, then put it into that class. i.e. I'd put public static GetStudent() into the Student class. 3) Remember the "has-a" and "is-a" relationship. Curriculum has Courses. Courses have Students. I don't think you have a problem that requires inheritance here, so don't worry about the "is-a" relationship. 4) When you have problems getting started, it helps greatly to do the UML, even if it's sloppy who cares as long as you get a better understanding of the problem. Use a pencil and paper, don't worry about visio or other fancy tools. Pencils are twice as fast as visio - easy. 5) I presume that this is a student assignment? I'll give you a hint here, what you have is a nested problem, if you solve the Course/Students relationship, then you solved the Curriculum/Courses relationship. Curriculum -Courses +Add(Course) +Remove(Course) +this[index] Course -Students +Add(Student) +Remove(Student) +this[index] +GetCourse(fromDB) Student -StudentInfo() //Info that I'm not going to go through. +GetStudent(fromDB) Scott P
“It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.” -Edsger Dijkstra