Take responsibility for assuring that your students are able to discuss intelligently what the object-oriented approach is even if you emphasize traditional structured analysis and design in their courses. Do not wait until the end of the course to introduce and discuss the object-oriented approach. The differences should be discussed early in the semester to set the stage for comparisons throughout the course. The life cycle concept, project management, user involvement, feasibility assessment, requirements modeling, iteration, and prototyping remain crucial concepts in both approaches. Emphasize that several key modeling constructs are similar in both approaches, particularly during the earlier stages of systems analysis.
Structured analysis uses business events to decompose the system into processes.
The object-oriented approach uses business events to decompose the system into use cases. Make sure students see how applicable these concepts are to both approaches. Finally, despite the many similarities, make sure your students understand the fundamental differences in the object-oriented approach. When it comes to modeling object interactions as opposed to functions and procedures, some major differences emerge. These differences may seem difficult at first, but most students will catch on quickly and accept that two different approaches can coexist in many organizations today.