Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Analysis and Design of Real Time Systems
Topic Summary:
Created On: 14-Nov-2006 23:25
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 14-Nov-2006 23:25
User is offline View Users Profile Print this message


Brandi Carroll

Posts: 82
Joined: 22-Jul-2004

Analisys and Design of Real Time Systems

ECCI
?Escuela Colombiana de Carreras Industriales?
Bogota Columbia

[url]http://www.ecci.edu.co[/url]


1. Introduction
The introduction of the Real Time systems is an overview of the entire Real Time systems. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of those systems.

2. Architectural Representation
This section describes what real time systems architecture is for any given real time system, and how it is represented. Of the Use-Case, Logical, Process, Deployment, and Implementation Views, it enumerates the views that are necessary, and for each view, explains what types of model elements it contains.

3. Architectural Goals and Constraints
This section describes the real time systems requirements and objectives that have some significant impact on the architecture; for example, safety, security, privacy, use of an off-the-shelf product, portability, distribution, and reuse. It also captures the special constraints that may apply: design and implementation strategy, development tools, team structure, schedule, legacy code, and so on.

4. Use-Case View
This section lists use cases or scenarios from the use-case model if they represent some significant, central functionality of the final system, or if they have a large architectural coverage they exercise many architectural elements or if they stress or illustrate a specific, delicate point of the architecture.

5. Logical View
This section describes the architecturally significant parts of the design model, such as its decomposition into subsystems and packages. And for each significant package, its decomposition into parts and parts utilities. You should introduce architecturally significant parts and describe their responsibilities, as well as a few very important relationships, operations, and attributes.
5.1 Overview
This subsection describes the overall decomposition of the design model in terms of its package hierarchy and layers.
5.2 Architecturally Significant Design Packages
For each significant package, include a subsection with its name, its brief description, and a diagram with all significant classes and packages contained within the package.
For each significant part in the package, include its name, brief description, and, optionally, a description of some of its major responsibilities, operations, and attributes.
5.3 Use-Case Realizations
This section illustrates how the firmware-software actually works by giving a few selected use-case (or scenario) realizations, and explains how the various design model elements contribute to their functionality.

6. Process View
This section describes the system's decomposition into lightweight processes (single threads of control) and heavyweight processes (groupings of lightweight processes). Organize the section by groups of processes that communicate or interact. Describe the main modes of communication between processes, such as message passing, interrupts, and rendezvous.

7. Deployment View
This section describes one or more physical control networks configurations on which the firmware-software is deployed and run. It is a view of the Deployment Model. At a minimum for each configuration it should indicate the physical nodes that execute the firmware-software and their interconnections (bus, LAN, point-to-point, and so on.) Also include a mapping of the processes of the Process View onto the physical nodes.

8. Implementation View
This section describes the overall structure of the implementation model, the decomposition of the firmware-software into layers and subsystems in the implementation model, and any architecturally significant components.
8.1 Overview
This subsection names and defines the various layers and their contents, the rules that govern the inclusion to a given layer, and the boundaries between layers. Include a component diagram that shows the relations between layers.
8.2 Layers
For each layer, include a subsection with its name, an enumeration of the subsystems located in the layer, and a component diagram.

9. Data View (optional)
A description of the persistent data storage perspective of the system. This section is optional if there is little or no persistent data, or the translation between the Design Model and the Data Model is trivial.
10. Size and Performance
A description of the major dimensioning characteristics of the firmware-software that impact the architecture, as well as the target performance constraints.
11. Quality
A description of how the firmware-software architecture contributes to all capabilities (other than functionality) of the system: extensibility, reliability, portability, and so on. If these characteristics have special significance, such as safety, security or privacy implications, they must be clearly delineated.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 0 users logged in.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.