PART TWO

“MODELING”
 Chapter 04

“PRINCIPLES THAT GUIDE PRACTICE”

No Diagrams
 Chapter 05

“UNDERSTANDING REQUIREMENTS”
SafeHome control panel
UML use case diagram for SafeHome home security
function
UML activity diagrams for eliciting requirements
Class diagram for sensor
UML state diagram notation
 Chapter 06

“REQUIREMENTS MODELING: SCENARIOS,

INFORMATION, AND ANALYSIS CLASSES”
The requirements model as a bridge between the
system description and the design model
Input and output for domain analysis
Elements of the analysis model
Preliminary use-case diagram for the SafeHome system
Activity diagram for Access camera surveillance via the
Internet— display camera views function
Swimlane diagram for Access camera surveillance via the
Internet—display camera views function
Tabular representation of data objects
Relationships between data objects
Class diagram for the system class
Class diagram for FloorPlan
A CRC model index card
A composite aggregate class
Multiplicity
Dependencies
Packages
 Chapter 07

“REQUIREMENTS MODELING: FLOW,

BEHAVIOR, PATTERNS, AND WEBAPPS”
Context-level DFD for the SafeHome security function
Level 1 DFD for SafeHome security function
Level 2 DFD that refines the monitor sensors process
State diagram for SafeHome security function
Process activation table for SafeHome security function
State diagram for the ControlPanel class
Sequence diagram (partial) for the SafeHome security
function
UML sequence diagram for the Actuator-Sensor pattern
UML Class diagram for the Actuator-Sensor pattern
Data tree for a SafeHomeAssured.com component
Activity diagram for the takeControlOfCamera() operation
 Chapter 08

“DESIGN CONCEPTS”
Translating the analysis model into the design model
Modularity and software cost
Design class for FloorPlan and composite aggregation for the class
Dimensions of the design model
Interface representation for Control Panel
A UML component diagram
A UML deployment diagram
 Chapter 09

“ARCHITECTURAL DESIGN”
Data-centered architecture
Data-flow architecture
Main program/subprogram architecture
Layered architecture
Architectural context diagram
Architectural context diagram for the
SafeHome security function
UML relationships for SafeHome security function
archetypes
Overall architectural structure for SafeHome with
top-level components
An instantiation of the security function with
component elaboration
Context-level DFD for the SafeHome security function
Level 1 DFD for the SafeHome security function
Level 2 DFD that refines the monitor sensors transform
Level 3 DFD for monitor sensors with flow boundaries
First-level factoring for monitor sensors
Second-level factoring for monitor sensors
First-iteration structure for monitor sensors
Refined program structure for monitor sensors
 Chapter 10

“COMPONENT-LEVEL DESIGN”
Elaboration of a design component
Structure chart for a traditional system
Component-level design for ComputePageCost
Following the OCP
Layer cohesion
Collaboration diagram with messaging
Refactoring interfaces and class definitions for PrintJob
UML activity diagram for computePaperCost()
Statechart fragment for PrintJob class
Flowchart constructs
Decision table nomenclature
 Chapter 11

“USER INTERFACE DESIGN”

The user interface design process
Swimlane diagram for prescription refill function
Preliminary screen layout
Mapping user objectives into interface actions
The interface design evaluation cycle
 Chapter 12

“PATTERN-BASED DESIGN”
Pattern-based design in context
A pattern organizing table
 Chapter 13

“WEBAPP DESIGN”
Quality requirements tree
A design pyramid for WebApps
Design representation of content objects
Hierarchical structure
Grid Structure
Hierarchical structure
Network structure
The MVC Architecture
Creating an NSU
Summary of the OOHDM method.
Partial conceptual schema for SafeHomeAssured.com
THE END
Thanks To Respected SIR “HUSSAIN SALEEM”