[nfbcs] Assistance needed from Programmers

Tue Aug 19 20:26:12 UTC 2014

Complexity of code: use of hierarchy input process output diagrams 
constructed by the programmer as memory aides along with corresponding 
interface narratives may go a long way toward helping comprehension of 
individual systems.  These are systems analysis tools more usable than 
some others like data flow diagrams.  Data flow diagrams can be done 
with any spreadsheet able to handle hyperlinks in cells provided each 
link becomes a part of the diagram in that the item type which is the 
graphic that is drawn is followed in the text label of the link by what 
that graphic contains.  When each of those links is activated they 
should connect to the link that gets the next or previous connection 
from the object in question that a programmer can determine in say a 
logic data flow diagram showing impact relationships of two adjacent 
parts of the system.  By adjacent I mean the first system that will be 
impacted by something happening in another part of the system.  
Depending on what happens these diagrams will differ.  These connections 
would be shown by process flow arrows which are one of the data flow 
diagram's symbols in both logical and physical data flow diagrams.

On Mon, 21 Apr 2014, David W Bundy wrote:

> I have received an inquiry from an employer related to challenges being
> encountered by one of their programmers who is blind. I thought some of the
> long-time programmers on the list might have some tips that may help him
> address these issues.  Below is the information that was provided to me
> (with identifying information removed).  I have some ideas about some of
> these, but would welcome any feedback any of you may have.
> 
>  
> 
>  
> 
> ?        Complexity of Code ? Employee needs to be able to navigate through
> thousands of lines of code, identify key components and understand how they
> relate to other parts of the system, including impacts to  other company
> systems
> 
>  
> 
> ?        Software Limitations ? Because of the JAWS software limitations,
> employee is unable to:
> 
> ?  Interpret graphical documentation, such as:
> 
> -          Diagrams
> 
> -          Scope and design documents
> 
> -          Technical specifications
> 
> -          Concept Diagrams, etc.
> 
> The requirement for additional explanations exists when supporting text is
> not adequate for interpretation  
> 
> ?  View communications with reference to graphical documents or embedded
> information, such as:
> 
> -          Email communication
> 
> -          Project documentation
> 
> -          Reference materials
> 
> Each document must be revised for employee to be able to receive it. This
> includes technical specifications which can be in excess of a hundred pages
> 
> ?  View PowerPoint presentations 
> 
> PowerPoint presentations have to be modified to include words on all images
> to describe the image  
> 
> ?  View Roles documentation 
> 
> Due to the software inability to review documentation associated with roles,
> employee must schedule personal interviews with employees in specific I/S
> roles to support the understanding of those roles and the various
> responsibilities
> 
> ?  Maneuver through the Quality Center software to do research
> 
> Unable to access this web-based application  
> 
> ?  Participate in Meetings/Training presentations that include images or
> graphics 
> 
> Any training or meeting that employee attends must have every image
> explained and a soft copy available so he can follow along. Instances where
> computer based training would be assigned to assist with training,
> additional explanation or alternate training material must be provided  
> 
>  
> 
>  
> 
> PC Hardware/Software already in place:
> 
> Specialized software/hardware and associated licenses are required for
> employee to interpret text or screen displays.
> 
> The following items have been purchased and installed:
> 
> ?         New PC purchased to handle specialized software (March 2013)
> 
> 
> ?         Braille Display purchased (May 2013)
> 
> ?         Upgrade to JAWS Interpretation version of software (October 2013)
> 
>  
> 
>  
> 
> Code Walk-Thru and Other Meetings
> 
> I/S provides accommodations to assist employee in meetings by preparing a
> soft copy and sending to him via email so he can view other's changes in a
> walk through. He is also provided with a laptop/PC for his participation in
> the meeting. In order for employee to conduct a code walk through, since he
> is unable to point out his changes, he must speak to them from memory.  
> 
>  
> 
>  
> 
>  
> 
> Work Assignments
> 
> Every project that is initiated, the first person we try to fit into an
> assignment is this employee .  He is able to do very elementary assignments
> and requires a lot of direction and guidance through the system.  While he
> is able to code from very detailed specifications, he is unable to maneuver
> well through the massive amount of code in our systems. Also, he is unable
> to do the necessary research to support an effort during systems testing.
> In I/S development, assignments are different with each project.  We are not
> in the same program elements time and time again.  This is a challenge for
> the employee .  In order for him to maneuver through a program, he pretty
> much has to memorize it.    
> 
>  
> 
>  
> 
>  
> 
> David W Bundy
> 
> Columbia, SC
> 
> bundy at pobox.com
> 
> (803) 447-7629
> 
>  
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/jdashiel%40shellworld.net
> 
> 

jude <jdashiel at shellworld.net>