Analysis Modeling
- •
def
- •
the process of creating models that represent the information domain, functional domain, and behavioral domain of a software system, based on gathered requirements
- •
- •
- •
role
- •
bridges the gap between the system-level description and the software design model
- •
- •
- •
elements of the analysis model
- •
scenario-based elements — Scenario-based Modeling: use-case diagrams, activity diagrams
- •
class-based elements — Class-based Modeling: class diagrams with attributes and operations
- •
behavioral elements — Behavioral Modeling: state diagrams
- •
flow-oriented elements — Flow-oriented Modeling: data flow diagrams
- •
- •
analysis rules of thumb
- •
focus on requirements visible within the problem or business domain — keep abstraction high
- •
each element should add to overall understanding of software requirements
- •
delay consideration of infrastructure and non-functional models until design
- •
minimize coupling throughout the system
- •
ensure the model provides value to all stakeholders
- •
keep the model as simple as possible
- •
- •