Patterns for a system-design...

[Tobias Mauderer]

Hi,



For an assignment in our studies we got the following assignment: We have to
design a fictitious system by using several design patterns and
architectural styles, e.g. client-server, broker, blackboard (of course only
those who fit to the system).



The system-description is the following:



This system is designed to allow advanced communication between foot
soldiers in a group, and to provide

instant information about the battle field from the battle control center to
the group commander.

Since the system will be used in battle conditions where the need for fast
and reliable communication is

important, it must swiftly react on changing conditions in its operating
environment. It must also protect

the integrity of its users (the soldiers) and ensure their safety.



System description



System functionality

The environment for the system is small portable terminals carried by foot
soldiers. These terminals use

wireless communication both between each other and between them and the main
commanding central.

The communication among the terminals, as well as between the terminals and
the commanding central,

has to be encrypted so that the information is not revealed to the enemy.
The encryption technique used

can be changed arbitrarily in order to increase the protection of the
communicated data.

The terminals shall be continuously updated with commands and status of
other squads in their area.

The terminals shall be able to pin point their position with the aid of a
GPS system and also be able to

distribute that information within the own squad and to the battlefield
information system.

The system shall support the transmission of both written and spoken
messages between the commanding

officer of the group and the commanding central. The commanding central
normally only communicates

with the commanding officer.

The carrier/operator of a terminal may not always be in communication range.
If one terminal is not

within communication range from the commanding central, it shall be possible
to relay through other

terminals in order to reach the commanding central.

The system shall be able to handle maps and guide single carriers or a group
of carriers from and to locations

on the map. If enemies are detected in one area, the command central shall
be able to give the

terminals new coordinates to where they shall move, and the system shall
guide the group to that location.

Members in a group may be eliminated by the enemy and if the commander is
eliminated, a new commander

in the group is normally appointed based on rank. The terminals must have
knowledge about the

rankings of their carriers, so that the roles of the terminals reflect the
roles of the carriers. If a terminal

detects that its carrier has been eliminated, the system shall automatically
adjust its rankings.



Quality requirements/goals

The system shall be able to communicate both internally (among terminals)
and externally (between

command central and terminals) with limited bandwidth (currently secure
radio communication with a

bandwidth of unencrypted data of 9600 bps).

The system must have response times below 1,5 seconds for any command
executed.

The communication delay may not exceed 2 seconds.

The system shall always remain updated among the terminals; no information
(messages, commands,

movement data) must be lost in a battle situation. The time between
detection of a disabled group commander

and the automatic adjustment of terminal roles should be less than 30
seconds.

The system will be run on small portable computers designed for rough
environments. The computers

will have limited memory resources and especially limited computational
power.



System usage

The system shall be used by foot soldiers in a battle situation to send and
receive tactical information

and decisions within the squad and from the commanding central.

The commanding central can distribute information to all terminals in a
group, but normally only communicates

with the commanding officer's terminal. If the group changes commanding
officer, the commanding

central must be informed about it, but communication will transparently be
rerouted to the

terminal of the new commanding officer.



Of course we don't expect a complete solution, but may be you can give us
some tips or approaches, about which patterns/architectural styles we should
consider in this assignment.



It would be also nice to know for us, which application/tools are the best
currently for modelling-purposes (MS Visio or are there better ones?).



Thank you a lot,



Tobias

[David Postill]

In article <2rtl19F1f6tirU1@uni-berlin.de>, on Tue, 28 Sep 2004 19:23:20 +0200, "Tobias Mauderer"
<tobimau@gmx.net> wrote:

| Hi,
|
| For an assignment in our studies we got the following assignment:

How about you do your own homework. That's why your professor (who may
even read this newsgroup) assigned it to *you*.

<davidp />

--
David Postill

[EventHelix.com]

>It would be also nice to know for us, which application/tools are the
best
>currently for modelling-purposes (MS Visio or are there better ones?).

You can use EventStudio 2.0 for modeling the system.
http://www.eventhelix.com/EventStudio/

- EventHelix