Review of Object-Oriented Analysis
Traditional (i.e., predictive) software development begins with the Requirements Phase. This phase consists of two sub-phases: requirements gathering and requirements analysis.
The output of requirements gathering is a functional specification, which is summarized using a UML use-case diagram that specifies actors (users, servers, etc.) and use cases (functions or user goals).
The output of the requirements analysis phase is an analysis model. The goal of this model is to present a user's view of the system.
The analysis model typically instantiates the Entity-Controller-Boundary pattern.
Lab
Draw a use-case diagram for Netflix. (Only include the most important actors and use cases.)
Draw a class diagram showing the major Netflix entities.