Cargando…

Modeling and analysis of real-time and embedded systems with UML and MARTE : developing cyber-physical systems /

Modeling and Analysis of Real-Time and Embedded Systems with UML and MARTE explains how to apply the complex MARTE standard in practical situations. This approachable reference provides a handy user guide, illustrating with numerous examples how you can use MARTE to design and develop real-time and...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autores principales: Selic, Bran (Autor), G�erard, S�ebastien (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Amsterdam : Elsevier, [2014]
Colección:MK/OMG Press.
Temas:
Acceso en línea:Texto completo
Tabla de Contenidos:
  • Machine generated contents note: pt. I INTRODUCTION TO MARTE
  • ch. 1 An Overview of MARTE
  • 1.1. Introduction
  • 1.2. Why model?
  • 1.3.A simple example
  • 1.4. What does MARTE add to UML?
  • 1.5. Conceptual foundations and design principles
  • 1.5.1. Foundational concepts: Applications, platforms, and deployment
  • 1.5.2. Foundational concepts (1): Resources, brokers, services, usages
  • 1.5.3. Foundational concepts (2): Physical data types and values
  • 1.5.4. Foundational concepts (3): Time and timed behavior
  • 1.5.5. Foundational concepts (4): Class/instance unification [Advanced]
  • 1.5.6. Core design principle (1): Support for concern-specific representations [Advanced]
  • 1.5.7. Core design principle (2): Composite stereotypes [Advanced]
  • 1.5.8. Core design principle (3): Modularity for scalability [Advanced]
  • 1.6. Standard use cases for MARTE
  • 1.6.1. Use case (1): Application modeling
  • 1.6.2. Use case (2): Modeling platforms
  • 1.6.3. Use case (3): Specifying deployment
  • 1.6.4. Use case (4): Analyze model
  • 1.6.5. Use case (5): Create a new analysis profile
  • 1.6.6. Use case (6): Configure product variant
  • 1.6.7. Use case (7): Extend MARTE
  • 1.7. Tool support for MARTE
  • 1.8. Summary
  • References
  • pt. II FOUNDATIONS
  • ch. 2 An Introduction to UML Profiles
  • 2.1. Introduction
  • 2.2. The two kinds of profiles
  • 2.3. How profiles work
  • 2.3.1. Metamodels
  • 2.3.2. The stereotype concept
  • 2.3.3. First-class language concepts
  • 2.3.4. Profile packages
  • 2.3.5. Using stereotypes in models
  • 2.3.6. Under the hood: How stereotypes are implemented
  • 2.3.7. Denotational and annotational properties of stereotypes
  • 2.3.8. Multibased stereotypes
  • 2.4. Conventions related to the use of profiles
  • 2.4.1. Default values of omitted stereotype properties
  • 2.4.2. Transitivity of class stereotypes to elements representing instances
  • 2.4.3. Inheritance of stereotype applications
  • 2.5. Model libraries for profiles
  • 2.6. Specializing profiles
  • 2.7. Summary
  • References
  • ch. 3 MARTE Foundations: Specifying Non-functional Properties
  • 3.1. Introduction
  • 3.2. The modeling of physical data types in MARTE
  • 3.3. How to use the MARTE standard physical types
  • 3.3.1. Time types, time values, and time expressions
  • 3.4. Adding new physical data types [Advanced]
  • 3.4.1. Step 1: Defining the physical units and their concrete representation
  • 3.4.2. Step 2: Defining the unit type (Dimension) of the physical type
  • 3.4.3. Step 3: Defining the new physical type
  • 3.5. Specifying probabilistic values for physical data types [Advanced]
  • 3.6. Specifying required and offered values
  • 3.7. Summary
  • References
  • ch. 4 MARTE Foundations: Modeling Time and Resources
  • 4.1. Introduction
  • 4.2. Modeling with time and clocks
  • 4.2.1. Two alternatives for dealing with time values
  • 4.2.2. MARTE models of time
  • 4.2.3. Base concepts for explicit reference clock modeling
  • 4.2.4. Modeling clocks
  • 4.2.5. The ideal clock
  • 4.2.6. Associating behavior with time
  • 4.2.7. Timed constraints
  • 4.2.8. Modeling timers and timeouts
  • 4.3. Modeling resources
  • 4.3.1. Conceptual framework for representing resources
  • 4.3.2. Modeling resources
  • 4.3.3. Modeling resource services
  • 4.3.4. Modeling resource usages
  • 4.4. Summary
  • References
  • pt. III MODELING REAL-TIME SYSTEMS WITH MARTE
  • ch. 5 Modeling Software Applications
  • 5.1. Introduction
  • 5.2. Distinguishing characteristics of "real-time" applications
  • 5.3. Application modeling foundations
  • 5.3.1. Software resources
  • 5.3.2. Software resource services
  • 5.4. Dealing with concurrency
  • 5.4.1. Modeling concurrent tasks
  • 5.4.2. Modeling synchronization mechanisms
  • 5.4.3. Modeling task communications mechanisms
  • 5.5. Dealing with timeliness
  • 5.5.1. Modeling clocks and timers via the implicit approach
  • 5.5.2. Associating time with services and service invocations [Advanced]
  • 5.5.3. Modeling cyclical behaviors
  • 5.6. Dealing with asynchrony and hardware interfacing
  • 5.6.1. Modeling interrupt sources and interrupt handling
  • 5.6.2. Modeling signal-based notifications
  • 5.7. Dealing with resource limitations (Specifying platform requirements)
  • 5.8. Summary
  • References
  • ch. 6 Modeling Platforms
  • 6.1. Introduction
  • 6.2. What is a platform?
  • 6.3. Why model platforms?
  • 6.4. MARTE approach to modeling platforms
  • 6.4.1. Platform modeling
  • core concepts
  • 6.4.2. Modeling processing resources
  • 6.4.3. Modeling storage resources
  • 6.4.4. Modeling communications resources
  • 6.4.5. Modeling concurrency resources
  • 6.4.6. Modeling synchronization resources
  • 6.4.7. Modeling hardware devices and interrupt sources
  • 6.4.8. Modeling concepts for physical platform modeling
  • 6.5. Platform modeling guidelines
  • 6.5.1. Specifying offered quality of service using NFP_Constraint
  • 6.5.2. How detailed should a platform model be?
  • 6.5.3. Platforms: Class-based or instance-based models?
  • 6.5.4. The acceptable platform design pattern [Advanced]
  • 6.6. Summary
  • References
  • ch. 7 Modeling Deployment
  • 7.1. Introduction
  • 7.2. The two primary use cases for deployment modeling
  • 7.3. The assign and allocate stereotypes
  • 7.4. Specifying required and provided QoS values via deployment
  • 7.5. Granularity and meaning of deployment specifications
  • 7.6. Capturing multiple deployment variants
  • 7.7. Limitations of the UML approach to modeling deployment [Advanced]
  • 7.8. Summary
  • References
  • ch. 8 Modeling Cyber-Physical Systems: Combining MARTE with SysML
  • 8.1. Introduction
  • 8.2. The SysML profile
  • 8.3. Why use SysML and MARTE together?
  • 8.4. Methods of combining SysML and MARTE
  • 8.5.Common scenarios of joint use of SysML and MARTE
  • 8.5.1. Use case: Supplementing SysML requirements with MARTE NFP specifications
  • 8.5.2. Use case: Transitioning between models at different levels of abstraction
  • 8.5.3. Use case: Engineering analysis of a SysML model using MARTE analysis facilities
  • 8.6. Summary
  • References
  • pt. IV SYSTEM ANALYSIS WITH MARTE
  • ch. 9 Foundations for Model-Based Analysis
  • 9.1. Introduction
  • 9.2. The demand
  • supply analysis pattern
  • 9.3. Model-based design analysis
  • 9.3.1. Design models versus analysis models
  • 9.3.2. Design space exploration with MARTE-based model analysis
  • 9.3.3. Instance versus class models for analysis
  • 9.4. GQAM concepts
  • 9.4.1. The analysis context
  • 9.4.2. Specifying demand: Workload
  • 9.4.3. Specifying the supply side: Scenarios and steps
  • 9.4.4. Platforms
  • 9.4.5. Defining timing constraints using time observers
  • 9.5. Summary
  • References
  • ch. 10 Model-Based Schedulability Analysis
  • 10.1. Introduction
  • 10.2. Basic SAM concepts
  • 10.2.1. Analysis context
  • 10.2.2. Specifying workloads for schedulability analysis
  • 10.2.3. Specifying platforms for schedulability analysis
  • 10.3. An example of schedulability analysis
  • 10.3.1.A simple ABS system
  • 10.3.2. Schedulability analysis example
  • 10.3.3. Creating a platform model for analysis
  • 10.3.4. Creating workload descriptions
  • 10.3.5. Defining analysis contexts
  • 10.3.6. Performing a rate monotonic schedulability analysis
  • 10.4. Summary
  • References
  • ch. 11 Model-Based Performance Analysis
  • 11.1. Introduction
  • 11.2. Concepts of performance analysis
  • 11.3. MARTE performance analysis example
  • 11.4. Key stereotypes for performance analysis
  • 11.5. Construction of a simple Pmodel, and bottleneck analysis
  • 11.5.1. Creating a QN model
  • 11.6. More complex annotations
  • 11.6.1. Parameterized values
  • 11.6.2. NFP types
  • 11.6.3. Message handling delays
  • 11.6.4. Logical resources
  • 11.6.5. Importation of external operations
  • 11.6.6. Required values and other sources of values
  • 11.7. Modeling with multiple scenarios
  • 11.8. The typical performance analysis process
  • 11.9. Summary
  • References
  • pt. V EXTENDING MARTE
  • ch.
  • 12 Extending MARTE [Advanced]
  • 12.1. Introduction
  • 12.2. How to add missing modeling capabilities to MARTE
  • 12.3. Extending the MARTE domain-specific language
  • a case study
  • 12.3.1.A quick overview of AADL
  • 12.3.2. Mapping of AADL concepts to MARTE
  • 12.3.3. Extending multiple base classes
  • 12.3.4. Selecting base classes for stereotypes
  • 12.4. Who should define language extensions?
  • 12.5. Summary
  • Appendices
  • Appendix A The Value Specification Language (VSL)
  • A.1. Why VSL?
  • A.2. Where to apply VSL
  • A.3. Quick (abbreviated) VSL user guide
  • A.3.1. Modeling structured data types with VSL [Advanced]
  • A.3.2. VSL expressions
  • A.4. Alternatives to VSL
  • A.4.1. The Alf language
  • A.4.2. SysML parametrics and physical types
  • A.5. Summary
  • References
  • Appendix B MARTE Library Types
  • Quick Reference
  • B.1. Introduction
  • B.2. The MARTE library primitive types
  • B.3. The MARTE library measurement units
  • B.4. The MARTE library basic NFP types
  • B.5. The MARTE library time types
  • B.6. Other MARTE library types
  • References
  • Appendix C MARTE Stereotypes
  • Quick Reference
  • References.