|
Key Areas: Embedded Object Oriented Design, AutoDrive, Queueing Theory
Object Oriented Design Tips
Here is an assortment of tips to keep in mind when using object
oriented design in embedded systems:
- Stay close to world real to close
- Object discovery vs. object invention
- Pick nouns as classes
- Method names should contain a verb
- Prefix adjectives when naming inheriting classes
- Do not add suffixes to class names
- Avoid one-to-one mapping from structured design
- Replace multiple get-set methods with operations
- Model classes that handle messages as state machines
- Use const whenever possible
- Restrict header file level dependency
- Don't reinvent the wheel; use STL
AutoDrive Architecture Design
This document has been developed by the engineering contractor to
define the software architecture of the AutoDrive system. The
architecture document is based on the requirements document mentioned in
the references section. The intended audience for this document is:
- Subsystem design teams for
the subsystems specified here
- AutoDrive Inc
Queueing Theory Basics
We have seen that as a system gets congested, the service delay in
the system increases. A good understanding of the relationship between
congestion and delay is essential for designing effective congestion
control algorithms. Queuing Theory provides all the tools needed for
this analysis. This article will focus on understanding the basics of
this topic.
M/M/1 Queueing System
We have already covered queueing theory basics in a previous article.
In this article we will focus on M/M/1 queueing system. As we have seen
earlier, M/M/1 refers to negative exponential arrivals and service times
with a single server. This is the most widely used queueing system in
analysis as pretty much everything is known about it. M/M/1 is a good
approximation for a large number of queueing systems.
-- EventHelix.com Team
|
