Analysis Model

Chapter 4 Overview of Use-Case-Driven Process • Transform use-case model into analysis model (1/4) • Transform use-case model into analysis model (2/4) • The analysis model grows incrementally, for each iteration, select a set of use cases to describe their collaborations. • For each use case, refine each use case into more detail form and identify what classifiers and associations are needed to realize the use case. Use a collaboration to describe this use case. • Identify role(s) of each identifier in each use case. • After classes and collaboration have been identified in each iteration, collect the roles of identifiers and rewrite each use case in flow of event description form. • Transform use-case model into analysis model (3/4) • 3 stereotypes on classes used in analysis model: • Boundary class: model interaction between system and its actor. • Entity class: model information that is long-lived and often persistent. • Control class: represent coordination, sequencing, transitions, and control of other objects, or encapsulate control related to a specific use case. • A class may participate several use-case realizations, so it will several roles. Collect all roles of the class into a complete set of responsibilities for the class. • Transform use-case model into analysis model (4/4) . Process • Transform use-case model into analysis model (1/4) • Transform use-case model into analysis model (2/4) • The analysis model grows incrementally,. form. • Transform use-case model into analysis model (3/4) • 3 stereotypes on classes used in analysis model: • Boundary class: model interaction between