[Accessibility] [Accessibility-ia2] Updating the Gnome Accessibility Project Architecture.
pete at a11ysoft.com
Tue Dec 7 08:03:13 PST 2010
Actually 0..* should probably be 1...*. Or perhaps you could simply use
* at the end of each end with a note on the bottom indicating this is a
many to many relationship - or something longer and less technical like:
Each component in the AT Layer can be related to one or more of the
components in the Operating System Layer.
I just also realized that you need at least one more box on the OS Layer
side, i.e. for OS Device Subsystem, e.g. for video, keyboard, mouse.
Pete Brunet wrote:
> The diagram is in pretty good shape - though Joanmarie has a lot of
> good comments. The primary thing that struck me was the incorrectness
> of the thin lines between AT Layer and Operating System Layer.
> Perhaps you could put something like a } symbol (rotated two different
> ways) on each end of the many to many relationship - or use UML's 0..*
> at each end of a single thin line.
> Brian Cragun wrote:
>> We've been working to update the Gnome Accessibility Project
>> Architecture diagram that has been used for years. The original has
>> disappeared, and we have used the opportunity to use Open Office to
>> create a new diagram that resolves some of the contrast notation
>> issues with the original version.
>> The notation is intended to divide into layer functions, as well as
>> distinguish those parts that are Gnome, Java, and application based.
>> 1) In addition to colors, we've used an appended superscript to
>> identify Gnome parts (g) and Java parts (j).
>> 2) We've added lines to connect components to make the stacks
>> absolutely clear. In the original diagram, must is inferred simply
>> by proximity.
>> 3) We've indicated the relationship between the layers with their own
>> lines between conceptual layers.
>> 4) WeI have no idea what to do with the Tools layer. It's not
>> dependent on the apps layer. Rather, we think its just conceptually
>> a different kind of app.
>> Here is a reference link to the original diagram:
>> Your input is invited:
>> David Bolter _david.bolter at gmail.com_ <mailto:david.bolter at gmail.com>
>> to review the Mozilla part,
>> Malte Timmerman _malte.timmermann at oracle.com_
>> <mailto:malte.timmermann at oracle.com> to review the OpenOffice part, and
>> Carolyn MacLeod _Carolyn_MacLeod at ca.ibm.com_
>> <mailto:Carolyn_MacLeod at ca.ibm.com> to review the Eclipse part
>> Brian Cragun
>> IBM AbilityLab Consultant
>> Human Ability & Accessibility Center
>> www.ibm.com/able & w3.ibm.com/able
>> W:(720)-663-2801 H:(507)288-2437
> *Pete Brunet*
> a11ysoft - Accessibility Architecture and Development
> (512) 238-6967 (work), (512) 689-4155 (cell)
> Skype: pete.brunet
> IM: ptbrunet (AOL, Google), ptbrunet at live.com (MSN)
> Ionosphere: WS4G
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Accessibility