Home Page Icon
Home Page
Table of Contents for
Notational Summary
Close
Notational Summary
by Bruce Powel Douglass
Real Time UML: Advances in The UML for Real-Time Systems, Third Edition
Copyright
Dedication
Praise for Real Time UML, Third Edition
The Addison-Wesley Object Technology Series
The Component Software Series
Figure List
About the Author
Foreword to the Third Edition
Foreword to the Previous Editions
Preface to the Third Edition
Audience
Goals
Preface to the Second Edition
Audience
Goals
Preface to the First Edition
Goals
Audience
Organization
Examples
Acknowledgments
1. Introduction to the World of Real-Time and Embedded Systems
1.1. What Is Special about Real-Time Systems?
1.2. Time, Performance, and Quality of Service
1.2.1. Modeling Actions and Concurrency
1.2.2. Modeling Resources
1.2.3. Modeling Time
1.2.4. Modeling Schedulability
1.2.5. Modeling Performance
1.3. Systems Engineering vs. Software Engineering
1.4. What Do We Mean by Architecture?
1.5. The Rapid Object-Oriented Process for Embedded Systems (ROPES) Process
1.5.1. Model-Driven Development (MDD)
1.5.2. The ROPES Spiral in More Detail
1.6. MDA and Platform-Independent Models
1.7. Scheduling Model-Based Projects
1.7.1. Why Schedule?
1.7.2. Estimation
1.7.3. BERT and ERNIE
1.7.3.1. Constructing Estimates: The BERT Approach
1.7.3.2. Improving Estimation Capability: The ERNIE Method
1.7.4. Scheduling
1.8. Model Organization Principles
1.8.1. Why Model Organization?
1.8.2. Specific Model Organization Patterns
1.9. Working with Model-Based Projects
1.10. Looking Ahead
1.11. Exercises
1.12. References
2. Object Orientation with UML 2.0—Structural Aspects
2.1. Object Orientation with UML
2.2. Small Things: Objects, Classes, and Interfaces
2.2.1. Objects
2.2.2. Classes
2.2.2.1. Attributes
2.2.2.2. Methods and Operations
2.2.3. Notation
2.2.4. Interfaces
2.2.5. Messaging
2.3. Relations
2.3.1. Associations
2.3.2. Aggregation
2.3.3. Composition
2.3.3.1. Stereotypes
2.3.4. Generalization
2.3.5. Dependency
2.3.6. Structural Diagrams
2.3.7. Mapping Objects to Code
2.4. Big Things: Packages, Components, and Subsystems
2.4.1. Model Organization: Packages
2.4.2. Structured Classes: Composites, Parts, Ports, and Connectors
2.4.2.1. Ports: Connecting Outside the Box
2.4.3. Components
2.4.4. Subsystems
2.4.5. Deployments: Nodes and Nonesuch
2.4.6. So, Nodes or Classes?
2.4.7. Architectural Hierarchy
2.5. Advanced: UML Metamodel of Structural Elements (for the Advanced Modeler)
2.6. Additional Notations and Semantics
2.7. Looking Ahead
2.8. Exercises
2.9. References
3. Object Orientation with UML 2.0—Dynamic Aspects
3.1. Behavior and the UML
3.2. Types of Behavior
3.2.1. Simple Behavior
3.2.2. State Behavior
3.2.3. Continuous Behavior
3.3. Behavior Primitives: Actions and Activities
3.4. Behavior and the Single Object
3.4.1. Basic Statechart Elements
3.4.1.1. State Features
3.4.1.2. Transitions
3.4.1.3. Events
3.4.1.4. Guards
3.4.1.5. Action Execution Order
3.4.2. And-States
3.4.3. Pseudostates
3.4.3.1. Initial Pseudostate
3.4.3.2. Branches and Junctions
3.4.3.3. Choice Points
3.4.3.4. History
3.4.3.5. Forks and Joins
3.4.3.6. Submachines, Entry, and Exit Points
3.4.4. Inherited State Models
3.4.5. Ill-Formed Statecharts
3.4.6. Cardiac Pacemaker Example
3.4.7. Protocol State Machines
3.4.8. Activity Diagrams
3.5. Interactions
3.5.1. Sequence Diagrams
3.5.1.1. Partial Ordering
3.5.1.2. Interaction Operators
3.5.1.2.1. Alternatives, Branches, Options, and Loops
3.5.1.2.2. Parallel and Critical Regions
3.5.1.2.3. Assert, Consider, Ignore?
3.5.1.3. Sequence Diagram Decomposition
3.5.2. Timing Diagrams
3.6. Summary
3.7. Exercises
3.8. References
4. UML Profile for Schedulability, Performance, and Time
4.1. UML Profiles
4.1.1. Stereotypes
4.1.2. Tagged Values
4.1.3. Profiles
4.2. “RT UML” Profile
4.2.1. General Resource Model Subprofile
4.2.2. Time Modeling Subprofile
4.2.3. Concurrency Modeling Subprofile
4.2.4. Schedulability Modeling Subprofile
4.2.5. Performance Modeling Subprofile
4.2.6. Real-Time CORBA Subprofile
4.3. Looking Ahead
4.4. Exercises
4.5. References
5. Requirements Analysis of Real-Time Systems
5.1. Requirements
5.2. Use Cases
5.2.1. Actors
5.2.2. Use Cases and Text
5.2.3. Use Case Relations
5.2.4. Using Use Cases
5.2.5. Identifying Use Cases
5.3. Detailing the Use Cases
5.3.1. Scenarios for Use Cases
5.3.1.1. Sequence Diagrams for Requirements Capture
5.3.1.2. Capturing QoS Requirements on Sequence Diagrams
5.3.2. Statecharts
5.3.3. Activity Diagrams
5.3.4. Timing Diagrams
5.4. Looking Ahead
5.5. Exercises
5.6. References
6. Analysis: Object Domain Analysis
6.1. The Object Discovery Process
6.2. Connecting the Object Model with the Use Case Model
6.3. Key Strategies for Object Identification
6.3.1. Underline the Noun Strategy
6.3.2. Identify the Causal Objects
6.3.3. Identify Services (Passive Contributors)
6.3.4. Identify Messages and Information Flows
6.3.5. Identify Real-World Items
6.3.6. Identify Physical Devices
6.3.7. Identify Key Concepts
6.3.8. Identify Transactions
6.3.9. Identify Persistent Information
6.3.10. Identify Visual Elements
6.3.11. Identify Control Elements
6.3.12. Apply Scenarios
6.4. Identify Object Associations
6.5. Object Attributes
6.6. Discovering Candidate Classes
6.7. Class Diagrams
6.7.1. Associative Classes
6.7.2. Generalization Relationships
6.7.2.1. Positioning Features in the Inheritance Tree
6.8. Looking Ahead
6.9. Exercises
6.10. References
7. Analysis: Defining Object Behavior
7.1. Object Behavior
7.1.1. Simple Behavior
7.1.2. State Behavior
7.1.3. Continuous Behavior
7.2. Defining Object State Behavior
7.2.1. Cardiac Pacemaker Example
7.2.1.1. How Communications Work
7.2.1.2. How Pacing Works
7.2.2. Calculator Example
7.2.2.1. Calculator Class
7.2.2.2. CharParser Class
7.2.2.3. Tokenizer Class
7.2.2.4. Evaluator Class
7.2.2.5. NumberStack and OperatorStack Classes
7.2.2.6. Stimulator Class
7.2.3. Event Hierarchies
7.3. Interactions
7.3.1. Sequence Diagrams
7.3.1.1. CardioNada Scenarios Example
7.3.1.2. Calculator Scenario Example
7.4. Defining Operations
7.4.1. Types of Operations
7.4.2. Strategies for Defining Operations
7.5. Looking Ahead
7.6. Exercises
7.7. References
8. Architectural Design
8.1. Overview of Design
8.2. What Is Architectural Design?
8.2.1. Logical Architecture
8.2.2. Physical Architecture
8.2.3. Subsystem and Component View
8.2.4. Concurrency and Resource View
8.2.5. Distribution View
8.2.6. Safety and Reliability View
8.2.7. Deployment View
8.2.8. Physical Architecture Issues
8.2.9. Software Architecture Issues
8.3. Software Meets Hardware: Deployment Architecture in UML
8.4. Concurrency and Resource Design
8.4.1. Representing Threads
8.4.2. System Task Diagram
8.4.3. Concurrent State Diagrams
8.4.4. Defining Threads
8.4.5. Identifying Threads
8.4.6. Assigning Objects to Threads
8.4.7. Defining Thread Rendezvous
8.4.8. Sharing Resources
8.4.9. Assigning Priorities
8.5. Looking Ahead
8.6. Exercises
8.7. References
9. Mechanistic Design
9.1. What Is Mechanistic Design?
9.2. Mechanistic Design Patterns
9.3. The Observer Pattern
9.3.1. Abstract
9.3.2. Problem
9.3.3. Pattern Structure
9.3.4. Collaboration Roles
9.3.5. Consequences
9.3.6. Implementation Strategies
9.3.7. Sample Model
9.4. The Proxy Pattern
9.4.1. Abstract
9.4.2. Problem
9.4.3. Pattern Structure
9.4.4. Collaboration Roles
9.4.5. Consequences
9.4.6. Implementation Strategies
9.4.7. Sample Model
9.5. Reliable Transaction Pattern
9.5.1. Abstract
9.5.2. Problem
9.5.3. Pattern Structure
9.5.4. Collaboration Roles
9.5.5. Consequences
9.5.6. Implementation Strategies
9.5.7. Sample Model
9.6. Smart Pointer Pattern
9.6.1. Abstract
9.6.2. Problem
9.6.3. Pattern Structure
9.6.4. Collaboration Roles
9.6.5. Consequences
9.6.6. Implementation Strategies
9.6.7. Related Patterns
9.6.8. Sample Model
9.7. Guarded Call Pattern
9.7.1. Abstract
9.7.2. Problem
9.7.3. Pattern Structure
9.7.4. Collaboration Roles
9.7.5. Consequences
9.7.6. Implementation Strategies
9.7.7. Sample Model
9.8. Container Pattern
9.8.1. Abstract
9.8.2. Problem
9.8.3. Pattern Structure
9.8.4. Collaboration Roles
9.8.5. Consequences
9.8.6. Implementation Strategies
9.8.7. Sample Model
9.9. The Rendezvous Pattern
9.9.1. Abstract
9.9.2. Problem
9.9.3. Pattern Structure
9.9.4. Collaboration Roles
9.9.5. Consequences
9.9.6. Implementation Strategies
9.9.7. Related Patterns
9.9.8. Sample Model
9.10. Looking Ahead
9.11. Exercises
9.12. References
10. Detailed Design
10.1. What Is Detailed Design?
10.2. Data Structure
10.3. Associations
10.4. Operations
10.5. Visibility
10.6. Algorithms
10.7. Exceptions
10.8. Summary
10.9. Exercises
10.10. References
11. Special Topic: C4ISR Architecture and the UML
11.1. Introduction
11.2. What Is C4ISR?
11.3. Required Products of C4ISR
11.3.1. AV-1 Overview and Summary Information
11.3.2. The AV-2 Integrated Dictionary
11.3.3. OV-1 High-Level Operational Concept Graphic
11.3.4. OV-2 Operational Node Connectivity Description
11.3.5. OV-3 Operational Information Exchange Matrix
11.3.6. SV-1 System Interface Description
11.3.7. TV-1 Technical Architecture Profile
11.4. Supporting Products
11.4.1. OV-4 Command Relationships Chart
11.4.2. OV-5 Operational Activity Model
11.4.3. OV-6a Operational Rules Model, SV-10a Systems Rules Model
11.4.4. OV-6b Operational State Transition Description, SV-10b Systems State Transition Description
11.4.5. OV-6c Operational Event-Trace Description, SV-10c Systems Event Trace Description
11.4.6. OV-7 Logical Data Model
11.4.7. SV-3 Systems-Systems Matrix
11.4.8. SV-4 Systems Functionality Description
11.4.9. SV-5 Operational Activity to Systems Function Traceability Matrix
11.4.10. SV-6 Systems Data Exchange Matrix
11.4.11. SV-7 Systems Performance Parameters Matrix
11.4.12. SV-8 Systems Evolution Description
11.4.13. SV-9 Systems Technology Forecast
11.4.14. SV-11 Physical Schema
11.5. Summary
11.6. Acknowledgments
11.7. References
Notational Summary
Search in book...
Toggle Font Controls
Playlists
Add To
Create new playlist
Name your new playlist
Playlist description (optional)
Cancel
Create playlist
Sign In
Email address
Password
Forgot Password?
Create account
Login
or
Continue with Facebook
Continue with Google
Sign Up
Full Name
Email address
Confirm Email Address
Password
Login
Create account
or
Continue with Facebook
Continue with Google
Prev
Previous Chapter
11. Special Topic: C4ISR Architecture and the UML
Appendix . Notational Summary
Add Highlight
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click
here
login for view all page.
Day Mode
Cloud Mode
Night Mode
Reset