Real Time System Design - Algorithms

Real Time Systems Design

Real-Time Algorithms
Ariana BITU, 1st Year MIT
Real Time characteristics II
At a high level of abstraction, three major components can be identified inside a RTS:
Master subsystem – main component which interacts with its slaves through a number of inputs and outputs, providing an interface to the application
Slave subsystem – controlled by master, represents the application itself or the environment that requires RT
Operating subsystem – initializes and monitors the entire system by various commands, especially in extreme situations.
Real Time characteristics III
When developing a RTOS one must consider:
Time – as a main design principle
Flexibility/Predictability balance assurance – adaptation to a dynamic environment, yet awareness of time constraints
Resource management – considering time, adaptability, correctness, safety, tolerance constraints.
Real Time characteristics IV
A RTOS must provide:
A model with all types of time constraints
A programming language
Planning and resource management
Communication protocols
Memory management protocols
Clock and inter-process synchronization mechanisms
StarUML modeling
Bibliography
Comparison of different uml tools: - Tincy Rani, Sushil Garg
http://staruml.sourceforge.net/en/
RT Characteristics, http://bigfoot.cs.utt.ro/~cami/sptr/caract-str.html
RT Algo, http://bigfoot.cs.utt.ro/~cami/sptr/distr-elec.html
http://staruml.sourceforge.net/docs/user-guide(en)/ch02.html

Real Time characteristics
A Real Time system is one that depends not only on the result of the application, but on the moment of time that is made available, thus the main characteristics of such a system being Time.
Considering the system's time constraints, there are two main categories :
Critical RTS – hard real time systems
Non-critical RTS – soft real time systems
StarUML modeling
UML Tool comparison
StarUML vs ArgoUML
Pros
Cons
-includes a number of features that supports the cognitive needs object - oriented software designers and architects.
-supports open standards extensively
UML, XMI, SVG, OCL and other.
-is a 100% Pure Java application.
This allows ArgoUML to run on all platforms for which a reliable port of java2 platform is available.
-is an open source product, which
allows extending or customizing.

- Not fully supports UML 2.0.
- Can't Undo! Developers of argoUML must be so optimistic that people (especially Software Developers) never do mistakes.
-Written in Java, so run comparatively
slower than starUML.
-Lack of formatting options

ArgoUML pros and cons:
Contents
StarUML description
UML Tool comparison
Real Time characteristics
StarUML modeling
StarUML description
Star UML is an open source project to develop fast, flexible, extensible and freely-available UML/MDA platform running on Win32 platform.
StarUML is mostly written in Delphi. However, StarUML is multi-lingual project and not tied to specific programming language, so any programming languages can be used to develop StarUML. (for example, C/C++, Java, Visual Basic, Delphi, JScript, VBScript, C#, VB.NET, ...).
UML Tool comparison - II
StarUML vs ArgoUML
Pros
Cons
-Supports most of the diagrams specified in UML 2.0.
-Very rich feature set and formatting options.
-Ability to generate source code from the UML diagram.
-Reverse engineer the existing code into UML diagrams.
-Supported languages: C++, C# and Java.
-Fast load time/execution time compared with other UML tools.
-Familiar Visual Studio like user interface.
-Supports exporting diagrams into JPG / XMI formats
-Does not support exporting diagrams into SVG format.

StarUML pros and cons:
StarUML description - II
StarUML makes a clear conceptual distinction between models, views and diagrams.
A model is an element that contains information for a software model
A view is a visual expression of the information contained in a model
A diagram is a collection of view elements that represent the user's specific design thoughts.

A project is the basic management unit in StarUML. A project can manage one or more software models. It is the top-level package that always exists in any software model. In general, one project is saved in one file.
StarUML description - III
StarUML supports the following diagrams:
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
Statechart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
Composite Structure Diagram

Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
7/2/2014






#

Click to edit Master title style
Click to edit Master text styles






Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
7/2/2014
#

7/2/2014

#
Click to edit Master title style
7/2/2014
#

Click to edit Master title style
7/2/2014

#
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
Click to edit Master text styles
Click to edit Master title style
7/2/2014

#
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Click to edit Master title style
Click to edit Master text styles
7/2/2014

















#
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
7/2/2014
#

Click to edit Master title style
Click to edit Master subtitle style
7/2/2014

















#


Click to edit Master title style
Click icon to add picture
Click to edit Master text styles





7/2/2014
#

Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
7/2/2014

#
Click to edit Master title style
Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
7/2/2014

#