ipc-quartztime
Inter Process Communication based on shared memory, mutexes and signals
 All Pages
ipc-quartztime Architecture
ipc-quartztime_architecture_intro.jpeg

Influence Factors

This section describes the problem space: requirements and expected environment.

Generator

This subsection lists factors that influence the idl to target code generator.

ipc-quartztime_icon_idl.png

Target-Code

This subsection lists requirements on the target code.

ipc-quartztime_icon_mux.png
ipc-quartztime_icon_eyes.png
ipc-quartztime_icon_mismatch.png
ipc-quartztime_icon_single.png
ipc-quartztime_icon_triple.png
ipc-quartztime_icon_double.png
ipc-quartztime_icon_big.png
ipc-quartztime_icon_fast.png
ipc-quartztime_icon_fast.png
ipc-quartztime_icon_fast.png
ipc-quartztime_icon_fast.png
ipc-quartztime_icon_stop.png
ipc-quartztime_icon_match.png

Future Extensions

This subsection lists ideas for future extensions.

ipc-quartztime_icon_match.png
ipc-quartztime_icon_proxy.png

Context / Operation Environment

An example operation environment is depected here to give an impression on the number of communication partners and channels.

The above shown picture is neither intended to be complete nor to be correct. It is intended to show how the number of communication channels grows depending on the number of communication nodes.

Views

This section describes the architecture of the chosen solution.

Static View

This subsection shows modules and dependencies.

Software modules and their dependencies

Dynamic View

This subsection shows the dynamic behavior.

Runmodes

Services and Clients support the following runmodes (operation modes)

Note: There are no circles, by which a disconnected service can be re-activated. A re-activated service has to create a new service interface.

Passing attributes from Server to Client

An attribute of a service is provided within a shared memory (solves REQ-106, REQ-109 and REQ-110).

An attribute is notified to client processes via a notification flag and a notification signal - and only if the client is registered. A client has to register again after every notification (solves REQ-107 and REQ-108)

A service updates an attribute

A client observes an attribute

A client calls a method of the service

A client calls a method of a service, waiting for a response

(Solution to REQ-100 and REQ-105)

A client calls a method of a service, not waiting for a response

(Solution to REQ-100 and REQ-104)

A client calls a method of a service without response

(Solution to REQ-100 and REQ-103)

Deployment

This subsection describes to which systems ipc-quartztime is intended to be deployed.

ipc-quartztime will run on the following systems:

Concepts

This section shows concepts: recurring patterns in the software.

Accessing shared resources

This subsection lists rules to be applied whenever a process accesses shared memory.

Clients accessing shared memory

When a client accesses shared memory provided by a service, it shall

Services accessing shared memory

When a service accesses shared memory, it shall

Decisions

This section lists design decisions, alternatives and rationales.

Services

Clients

Service Broker

Quality Scenarios

This section lists use cases that describe the quality expectations on the software.

Quality goals

Appendix

Author
(c) 2013-2015 A.Warnke; Email-contact: ipc-quartztime-at-andreaswarnke-dot-de