1. Software Analysis

2. What Is Analysis, and Why?
Transform use case model into logical design, without(*) considering implementation conditions, constraints and details.
Product: The analysis model
Why do we need analysis?
Handle complexity via separation of concerns
A platform, implementation independent design that precisely reflect the requirements, that can be reused, that can sustain technological and environment changes, and that serves as the basis for stable and extensible system structure

3. Comparison Between Use Case and Analysis Models

4. Workers and Artifacts

5. Overview of Relevant UML Notations
Structural views and relationships

6. Generalization

7. Multiplicity

8. Aggregation

9. Inheritance

10. Structural Relationships

11. Class Diagram

12. Modeling Collaboration Relationship

13. Modeling Schema

14. Advanced Classes

15. Structure and Composition of Analysis Model

16. Analysis Class
An analysis class represents an abstract of one or more classes and/or subsystems in (subsequent) design
Characteristics
focuses on handling functional requirements (?**)
seldom defines and provides any interface in terms of operations and their signatures (?**)
defines attributes (high level, and recognizable from problem domain
is involved in relationships at conceptual level
always fit one of 3 basic stereotypes: boundary, control and entity  to achieve model robustness

17. Key Attributes and Subtypes of Analysis Class

18. Boundary Class Models interaction between actor and system
Models parts of system that depend on its actors - they clarify and collect requirements on the system’s boundary
Often represents abstractions of windows, forms, panes, communication interfaces, printer interfaces, sensors, terminals, and possibly APIs
Each boundary class should be related to at least one actor and vice versa

19. Example

20. Entity Class
Used to model long lived information, and thus often persistent
Models information and associated behavior of some phenomenon or concept, e.g. individual, real-life object, or real-life event
In most cases, entity class are derived from corresponding business class (domain class), but reflect the information that benefits the developers
Used to isolate changes that they represent

21. Example

22. Control Class
Represent coordination, sequencing, transactions and control of other objects
Often used to encapsulate control related to a specific use case
Also represent complex derivations and calculations, e.g. business logic, that cannot be related to any specific, long-lived information
Therefore, control classes model the dynamics of the system
Used to encapsulate, thus isolate, change to control, coordination, sequencing, transactions and complex business logic

23. Example