Hi all,
I can't speak highly enough of Jack Ganssle and his embedded newsletters
and articles etc.  Here's a guy who knows embedded systems.  It's his
writing that has forced me to be more critical of things like the CC
compiler example of testing a bit twice when that bit could be an Input
Port and could change between tests.  He gives seminars and if you can
attend one do it.

There's also a very good book called "Writing Solid Code" by Steve
Mguire.  Guidelines for Design don't help much if the impliemntations
are crap.  ISO900x is a good example of that.  But if you need to follow
a standard the ISO9004 (I think that's the number) is the place for
software design that has acceptance from larger firms and is sometimes
mandatory for supplying a product to a firm.

John Dammeyer


> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU] On Behalf Of Matt Pobursky
> Sent: Tuesday, April 09, 2002 4:07 PM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [pic] Software Design Guideline for Embedded Systems?
>
>
> On Tue, 9 Apr 2002 18:52:41 -0400, Tony Pan wrote:
> >Hi,
> >
> >I need to come up with a design guideline for our small design
> >team respecting writing software for microprocessor
> >applications. I believe those design guidelines are well
> >established in the industry; I want to know how people do it and
> >what kind of standards people follow. Can anyone give me some
> >inputs? Or simply direct me to a web site that contain the
> >information?
> >
> >Thanks alot!
> >
> >Tony
> >
>
> Check out the "Firmware Standards Manual" link at the top of the
> page:
>
http://www.ganssle.com/articles.htm

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.