[nfbcs] accessible design software

[Jim Barbour]

Hey Amanda and Everyone,

I'd like to point out that it can be extremely valuable to know what those diagrams actually look like, rather than how they translate into psuedo-code.

the primary reason that UML exists is to communicate in a consistant, easy to read, manner the basic architecture of a system or large piece of code.

This means that you may well be expected to generate or consume these diagrams, possibly with the assistance of a reader, in your employed future.  It's probably not realistic to insist that your entire team communicate in psuedo-code rather than using UML.

Take Care,

Jim

On Tue, Jul 28, 2015 at 10:27:11AM -0500, Amanda Lacy via nfbcs wrote:
> Marvin,
> 
> There's also SVG Draw by Prof. Baldwin:
> http://cnx.org/contents/0803a1bf-9c6d-435a-a5f1-e21b1dbd978c@5/If-You-Can-Imagine-It,-You-Can
> 
> If none of the suggested drawing tools work for you, you can always
> say, "I'm BLIND; I can't do pictures." How would anyone argue with
> that?
> 
> I took a software design class last semester which was full of UML and
> other diagrams. What mostly worked for me was to insist that I
> couldn't draw, and that these concepts could be represented as code. I
> might be able to dig up an example if you're interested. If you learn
> best about the structure of programs by reading code, you might
> consider this approach.
> 
> Amanda
> 
> On 7/28/15, Jude DaShiell via nfbcs <nfbcs at nfbnet.org> wrote:
> > If the output from whatever software is being used doesn't show up in some
> > form of ascii the screen reader isn't going to read it to you.  If the
> > software has example files that are ascii in nature then you have a
> > chance.  You may have to study those diagrams enough so you understand
> > what all those symbols mean if the software isn't otherwise accesible in
> > terms of input and output interfaces.  If you do end up having to do that
> > and use a text editor to create your diagrams, try to segment the diagrams
> > so for example you can use the pieces you make to build other diagrams
> > with them.  Structured programming and structured diagram building are
> > alike in this respect.  If you already are fluent in latex that's another
> > and different possible avenue for you to investigate.  If you don't have a
> > knowledge of latex, probably now isn't a good time to learn.  I think I
> > remember reading that graphvis could do some of this stuff but that was a
> > while ago and I never had exposure to the package.  Also, if you do a
> > google search for that package put a tilde in front of it ~graphvis since
> > I may not have spelled it completely correctly.
> >
> >
> >
> > --
> >
> 
> _______________________________________________
> 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/jbar%40barcore.com
>