|
|
|
Our Development Approach
Initial development for supporting computer applications, will target platforms for Microsoft based devices, followed by Android based devices and finally, Apple based devices.
Within each group, applications will target desktop/laptop PC's, Tablets and
Smartphones.Within each group, we will also take into consideration,
whether any data is required to flow between the applications on different
platforms.
Our developed software; is offered for 'free' on an "as is" basis, subject to licence agreement. We would ask that any donations be provided to your local MND/ALS support organisation for ongoing research, to find a cure for this most terrible disease.
Our software will be developed using Microsoft's Application Lifecycle
Management (ALM) tools and making use of the Microsoft Visual Studio 2010
development environment. see
Microsoft ALM
Another aspect of our approach is making use of the Microsoft Solutions
Framework (MSF) see
Microsoft MSF
and
MSF for Agile Software Development v5.0, additionally the Microsoft Operations Framework (MOF)
Microsoft MOF
Our language here on the website will not bore readers with Systems
Engineering practices or methodologies for our development activites;
rather, we will hopefully provide enough of an overview and some detail, for
non-IT people to understand what we hope to achieve. Behind the scenes, we
will make use of development products such as
Microsoft Visual Studio,
Infragistics NetAdvantage
Ultimate 2012,
Business Process Visual Architect (BP-VA),
Infragistics Quince
Pro,
vsDocman,
InstallShield,
ComponentOne
Doc-to-Help,
LogicNP ShellObjects
and other product specific Software Development Kits (SDK's)
Baseline Communications
Our design starting point requires a baseline or a 'norm' as to what
communications are available to people with no physical disabilities.
In the first
case, there is the ability for someone to speak and one or more people to
listen. This may occur in personal close proximity or over a communications
medium such as a telephone or receiving broadcast from television or radio.
The second case is where people can type a message and have it read by
one or more people. This may occur through emails, instant messaging or even
the publication of reports, papers or books.
Our aim is to develop solutions that will allow people to communicate
quickly, effectively and
with little effort, using electronically spoken and written communications, in a modern electronic world
in a manner that is close to the 'norms' above.
Baseline Computer Interaction
Additional to the understanding of "Baseline Communications",
there is a need to have an understanding of how people interact with a
standard PC, Tablet and SmartPhone. A person interacts with a computer
typically via a 'Human Interface Device (HID)'
A Human Interface Device is a type of computer device
that interacts directly with, and most often takes input from, humans and
may deliver output to humans. Typical HID's are:
- Keyboard
- Mouse, Trackball, Touchpad
- Graphics tablet
- Joystick, Gamepad
- Webcam
- Fingerprint Scanner
- Headset
Note: HID's are generally USB based devices, however in our context, we use
the term HID to describe any device that a person would use to interact with
a computer.
<insert image for PC interaction>
<description>
<insert Image for Tablet Interaction>
<description>
<Insert image for SmartPhone
interaction>
<description>
Understanding HID's and Baseline
Coomunications is important when we then start to look at a persons ability
to make use of them. People with physical disabilities will need to make use
of other types of specialised HID's to interact with a computer. Specialised
computer applications for people with disabilities will need to be able to
make use of many types of HID's.
For example, a person with no voice and no hand movement may need to use
a BCI device, such as the EPOC Neuroheadset. A person with no hand movement
and a good voice and good range of head movement, may need to use a Golden-I Headset.
Development Schedule
Given my current committment to look after my beloved Kathy, development
work will not begin until she is no longer by my side. Until that time, we
will continue to research, gather information, requirements and the experiences of people with disabilities.
The anticipated schedule of events are:
| Activity |
Completion Date |
| Requirements |
Dec 2012 |
| Design |
Apr 2013 |
| Develop |
Jun 2013 |
| Release |
Sep 2013 |
Development Resources
Under Construction
Microsoft Development Accessibility Resources
http://www.msdn.com/accessibility
We are making great use of the Infragistics Quince Development Collaboration
Environment and have setup an account for MNDcommunicate participants to
share their ideas and requirements. This is a secure account and requires a userid and password to access.
http://quince.infragistics.com/
Douglas McLaren Livingstone
Contact us for more info
|
|
|
|
|