Update cookies preferences

E-book: Real Time UML Workshop for Embedded Systems

3.50/5 (12 ratings by Goodreads)
(Chief Evangelist, IBM Internet of Things, Fairfax, VA, USA)
  • Format: PDF+DRM
  • Series: Embedded Technology
  • Pub. Date: 01-Apr-2011
  • Publisher: Newnes (an imprint of Butterworth-Heinemann Ltd )
  • Language: eng
  • ISBN-13: 9780080492230
Other books in subject:
  • Format - PDF+DRM
  • Price: 50,62 €*
  • * the price is final i.e. no additional discount will apply
  • Add to basket
  • Add to Wishlist
  • This ebook is for personal use only. E-Books are non-refundable.
Real Time UML Workshop for Embedded SystemsLarger Image
  • Format: PDF+DRM
  • Series: Embedded Technology
  • Pub. Date: 01-Apr-2011
  • Publisher: Newnes (an imprint of Butterworth-Heinemann Ltd )
  • Language: eng
  • ISBN-13: 9780080492230
Other books in subject:

DRM restrictions

  • Copying (copy/paste):

    not allowed

  • Printing:

    not allowed

  • Usage:

    Digital Rights Management (DRM)
    The publisher has supplied this book in encrypted form, which means that you need to install free software in order to unlock and read it.  To read this e-book you have to create Adobe ID More info here. Ebook can be read and downloaded up to 6 devices (single user with the same Adobe ID).

    Required software
    To read this ebook on a mobile device (phone or tablet) you'll need to install this free app: PocketBook Reader (iOS / Android)

    To download and read this eBook on a PC or Mac you need Adobe Digital Editions (This is a free app specially developed for eBooks. It's not the same as Adobe Reader, which you probably already have on your computer.)

    You can't read this ebook with Amazon Kindle

This practical new book provides much-needed, practical, hands-on experience capturing analysis and design in UML. It holds the hands of engineers making the difficult leap from developing in C to the higher-level and more robust Unified Modeling Language, thereby supporting professional development for engineers looking to broaden their skill-sets in order to become more saleable in the job market.

It provides a laboratory environment through a series of progressively more complex exercises that act as building blocks, illustrating the various aspects of UML and its application to real-time and embedded systems. With its focus on gaining proficiency, it goes a significant step beyond basic UML overviews, providing both comprehensive methodology and the best level of supporting exercises available on the market. Each exercise has a matching solution which is thoroughly explained step-by-step in the back of the book. The techniques used to solve these problems come from the author’s decades of experience designing and constructing real-time systems. After the exercises have been successfully completed, the book will act as a desk reference for engineers, reminding them of how many of the problems they face in their designs can be solved.

*Tutorial style text with keen focus on in-depth presentation and solution of real-world example problems

*Highly popular, respected and experienced author

*CD includes test version of the popular Rhapsody tool, allowing engineers to capture and work out the exercises in the book

Reviews

"As you might expect, there are plenty of UML diagrams. Real-time UML specifications are used throughout, consistent with the purpose of the book. Designers with UML expertise who want to understand how to address real-time applications will find this book useful, as will those in the real-time world who need to understand how to bring UML to bear on the design problem." --William Wong, Electronic Design

Preface xiii
Audience xiv
Goals xv
Where to Go After the Book xv
Evaluate UML on ARM xv
Acknowledgments xvii
About the Author xix
What's on the CD-ROM? xxi
Introduction
1(34)
Basic Modeling Concepts of the UML
1(4)
Structural Elements and Diagrams
5(14)
Small Things: Objects, Classes, and Interfaces
5(5)
Relations
10(7)
Big Things: Subsystems, Components, and Packages
17(2)
Behavioral Elements and Diagrams
19(12)
Actions and Activities
19(1)
Operations and Methods
20(1)
Activity Diagrams
20(2)
Statecharts
22(5)
Interactions
27(4)
Use Case and Requirements Models
31(2)
Summary
33(1)
Check Out the CD-ROM
33(2)
The Harmony Process
35(30)
Introduction
35(1)
The Harmony Development Process
36(27)
Why Process?
36(5)
Harmony Process Overview
41(2)
The Systems Engineering Harmony Workflows in Detail
43(4)
The Incremental (Spiral) Development Workflows in Detail
47(1)
Increment Review (Party!) Workflow
48(7)
Design with the Harmony Process
55(5)
Implementation
60(1)
Test
61(2)
Summary
63(2)
Specifying Requirements
65(18)
Overview
65(2)
Problem 3.1 Identifying Kinds of Requirements for Roadrunner Traffic Light Control System
67(2)
Problem 3.2 Identifying Use Cases for the Roadrunner Traffic Light Control System
69(1)
Problem 3.3 Mapping Requirements to Use Cases
69(1)
Problem 3.4 Identifying Use Cases for the Coyote UAV System
70(1)
Problem 3.5 Identifying Parametric Requirements
70(1)
Problem 3.6 Capturing Quality of Service Requirements in Use Cases
71(1)
Problem 3.7 Operational View: Identifying Traffic Light Scenarios
71(2)
Problem 3.8 Operational View: CUAVS Optical Surveillance Scenarios
73(1)
Problem 3.9 Specification View: Use-Case Description
73(1)
Specification View: State Machines for Requirements Capture
74(2)
Problem 3.10 Specification View: Capturing Complex Requirements
76(1)
Problem 3.11 Operational to Specification View: Capturing Operational Contracts
77(5)
References
82(1)
Systems Architecture
83(26)
Overview
83(2)
Problem 4.1 Organizing the Systems Model
85(5)
Problem 4.2 Subsystem Identification
90(2)
Problem 4.3 Mapping Operational Contracts into Subsystem Architecture
92(9)
Problem 4.4 Identifying Subsystem Use Cases
101(6)
Looking Ahead
107(2)
Object Analysis
109(32)
Overview
109(2)
Key Strategies for Object Identification
111(5)
Underline the Noun Strategy
113(1)
Identify the Causal Agents
113(1)
Identify Services (Passive Contributors or Server Objects)
114(1)
Identify Messages and Information Flows
114(1)
Identify Real-World Items
114(1)
Identify Physical Devices
114(1)
Identify Key Concepts
115(1)
Identify Transactions
115(1)
Identify Persistent Information
115(1)
Identify Visual Elements
115(1)
Identify Control Elements
116(1)
Apply Scenarios
116(1)
Problem 5.1 Apply Nouns and Causal Agents Strategies
116(9)
Problem 5.2 Apply Services and Messages Strategies
125(2)
Problem 5.3 Apply Real-World Items and Physical Devices Strategies
127(1)
Problem 5.4 Apply Key Concepts and Transaction Strategies
128(1)
Problem 5.5 Apply Identify Visual Elements and Scenarios Strategies
128(9)
Problem 5.6 Merge Models from the Various Strategies
137(2)
Looking Ahead
139(2)
Architectural Design
141(38)
Overview
141(6)
Problem 6.1 Concurrency and Resource Architecture
147(11)
Problem 6.2 Distribution Architecture
158(5)
Problem 6.3 Safety and Reliability Architecture
163(14)
Looking Ahead
177(2)
Mechanistic and Detailed Design
179(36)
Overview
179(1)
Mechanistic Design
180(7)
Delegation Pattern Strategy
183(2)
Interface Abstraction Pattern Strategy
185(2)
Detailed Design
187(5)
Problem 7.1 Applying Mechanistic Design Patterns---Part 1
192(4)
Problem 7.2 Applying Mechanistic Design Patterns---Part 2
196(5)
Problem 7.3 Applying Detailed-Design State Behavior Patterns
201(5)
Problem 7.4 Applying Detailed Design Idioms
206(8)
Summary
214(1)
Specifying Requirements: Answers
215(28)
Answer 3.1 Identifying Kinds of Requirements
215(1)
Answer 3.2 Identifying Use Cases for Roadrunner Traffic Light Control System
216(3)
Answer 3.3 Mapping Requirements to Use Cases
219(1)
Answer 3.4 Identifying Use Cases for Coyote UAV System
220(2)
Answer 3.5 Identifying Parametric Requirements
222(1)
Answer 3.6 Capturing Quality of Service Requirements
223(1)
Answer 3.7 Operational View: Identifying Traffic Light Scenarios
224(4)
Answer 3.8 Operational View: CUAVS Optical Surveillance Scenarios
228(3)
Answer 3.9 Specification View: Use-Case Descriptions
231(1)
Answer 3.10 Specification View: Capturing Complex Requirements
232(6)
Answer 3.11 Operational to Specification View: Capturing Operational Contracts
238(4)
References
242(1)
Systems Architecture: Answers
243(30)
Answer 4.1 Organizing the Systems Model
243(7)
Answer 4.2 Subsystem Identification
250(6)
Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture
256(11)
Answer 4.4 Identifying Subsystem Use Cases
267(6)
Object Analysis: Answers
273(44)
Answer 5.1 Apply Nouns and Causal Agents Strategies
273(18)
Answer 5.2 Apply Services and Messages Strategies
291(6)
Answer 5.3 Applying the Real-World Items and Physical Devices Strategies
297(2)
Answer 5.4 Apply Key Concepts and Transaction Strategies
299(4)
Answer 5.5 Identify Visual Elements and Scenarios Strategies
303(12)
Answer 5.6 Merge Models from the Various Strategies
315(2)
Architectural Design: Answers
317(22)
Answer 6.1 Concurrency and Resource Architecture
317(2)
Answer 6.2 Distribution Architecture
319(4)
Answer 6.3 Safety and Reliability Architecture
323(16)
Mechanistic and Detailed Design: Answers
339(18)
Answer 7.1 Applying Mechanistic Design Patterns---Part 1
339(2)
Answer 7.2 Applying Mechanistic Design Patterns---Part 2
341(5)
Answer 7.3 Applying Detailed-Design State Behavior Patterns
346(5)
Answer 7.4 Applying Detailed-Design Idioms
351(6)
Appendix A: The Roadrunner Intersection Controller System Specification
357(14)
Overview
357(1)
The Intersection Controller (IC)
357(14)
Configuration Parameters
358(3)
Intersection Modes
361(4)
The Vehicle Detector
365(1)
Vehicular Traffic Light
366(1)
Pedestrian Light and Sensor
367(1)
Front Panel Display
368(1)
Remote Communications
369(1)
Power
370(1)
Appendix B: The Coyote Unmanned Air Vehicle System (CUAVS) Specification
371(8)
Overview
371(1)
Primary CUAV System Components
371(2)
The Unmanned Air Vehicle (UAV)
371(1)
The Coyote Mission Planning and Control System (CMPCS)
372(1)
Coyote Payloads
372(1)
The Coyote Datalink Subsystem (CDS)
373(1)
Detailed Requirements
373(1)
The Unmanned Air Vehicle (UAV)
373(1)
Flight Modes
373(1)
Mission Modes
374(1)
The Coyote Mission Planning and Control System (CMPCS)
374(1)
The Coyote Reconnaissance Sensor Suite Payload (CSSP)
375(1)
The Coyote Hellfire Attack Payload (CHAP)
376(1)
The Coyote Datalink Subsystem (CDS)
377(2)
Appendix C: UML Notational Summary
379(22)
Index 401


Embedded Software Methodologist. Triathlete. Systems engineer. Contributor to UML and SysML specifications. Writer. Black Belt. Neuroscientist. Classical guitarist. High school dropout. Bruce Powel Douglass, who has a doctorate in neurocybernetics from the USD Medical School, has over 35 years of experience developing safety-critical real-time applications in a variety of hard real-time environments. He is the author of over 5700 book pages from a number of technical books including Real-Time UML, Real-Time UML Workshop for Embedded Systems, Real-Time Design Patterns, Doing Hard Time, Real-Time Agility, and Design Patterns for Embedded Systems in C. He is the Chief Evangelist at IBM Rational, where he is a thought leader in the systems space and consulting with and mentors IBM customers all over the world.
More information about ebooks More information about ebooks
Permanent link: https://www.kriso.ee/db/97800804922302e.html
Keywords: