13 OO Analysis Flashcards
OO Analysis Type?
Semiformal, Unified Process
Aim of Analysis
Deeper understanding of requirements, and description to help design and implementation
Classes of Unified Process
Entity Class, Boundary Class, Control Class
Entity Class
Models long-lived information
Boundary Class
Models interaction between software and actors. Input/Output screens and reports, often. All data contained and methods to get it.
Control Class
Models complex calculations and algorithms.
Entity class extraction steps
Functional modeling, entity class modeling, dynamic modeling
Functional modeling
Present scenarios for all use cases
Entity class modeling
Define entity classes and attributes, define class interrelationships and interactions, class diagram
Entity class modeling diagram
Class diagram
Dynamic modeling
Define operations performed on/by each class
Dynamic modeling diagram
Statechart
Scenario types
Normal and exception
Must specify responsibility of each action
Responsibility-Driven Design
Process for extracting candidate classes
Noun Extraction Method
Noun Extraction Method process
Describe product in 1 paragraph, ID nouns in it
Nouns with no physical existence
Abstract nouns, often attributes of a class
Cards with class names, attributes, methods, and classes it invokes
Class-Responsibility Collaboration cards
Depiction of target product
Statechart
Way of depicting use-case realization
Interaction diagram / sequence diagram / communication diagram
Models long-lived info
Entity / Model Class
Models I/O and reports
Boundary / View Class
Models calculations
Control(ler) Class
MVC
Model-View-Controller
Design Pattern
Template for solving common SE problems
Template for solving common SE problems
Design Pattern
Presenting scenarios for all use cases
Functional Modeling
Defining operations performed on/by each class
Dynamic Modeling
Statechart
Dynamic modeling diagram, description of target product
CRC Cards
Class-responsibility-collaboration, class name, attributes, methods, collaborators
Use Case Model
A complete set of scenarios that describe all of a system’s functional requirements
A set of scenarios that describe a system’s functional requirements
Use Case Model
Use Case Types
Brief-(1 paragraph, best scenario), Casual-(multi-paragraph, multi-scenario), Fully-Dressed-(errything)
Actor Types
Primary, supporting, offstage
Test workflow during Analysis?
Start thinking of test cases, check static and dynamic models
Software Requirements Specification
Details externally-visible parts of product, like platform, standards, and features
Details externally-visible parts of product, like platform, standards, and features
Software Requirements Specification
Sequence Diagram
Shows how objects interact with each other and in what order
Shows how objects interact with each other and in what order
Sequence Diagram
