Functional Decomposition Technique: Authenticate Student/Log-in Select Course Retrieve Available Sections Validate and Register Display Outcome The benefits of of this technique are shown in the ease of use. It maps directly to each use-case step, and it is easy to follow. It's designed for procedural implementation. This technique also comes with a few flaws. Logic and data tend to entabgled and the boundaries between them becomes blurred. Also, when the requirements of the projects change, it become harder to extend or reuse this technique. Object-Oriented decomposition Technique: Student class (Attributes: studentID, enrolledSections, completedCourses) (Methods: authenticate(), hasPrerequisite(), hasScheduleConflict(), enrollInSection()) Course class (Attributes: courseID, prerequisiteCourses, sections) (Methods: getAvailableSections()) Section class (Attributes: sectionID, capacity, enrolledStudents, scheduleTime) (Methods: isFull(), addStudent()) RegistrationSystem class (Methods: login(), findCourse(), listSections(), register(student, section)) provide 5 sentences of feedback