??? 04/02/05 02:06 Read: times |
#90846 - Hardware documentation? (different) Responding to: ???'s previous message |
for large projects, usually separate because you have different types of engineers working on the different pieces. for example, maybe the hardware group puts out an Interface Control Document for an item, and the software group refers to it and accounts for it in their design. also, you would expect the hardware to change less than the software, changes being much more difficult, and at some point the hardware will be frozen where the software does not have to be (you can upload patches, and upgrade software before and after h/w assembly, etc.) re medical devices, i think there has been some discussion about those on this site before, you may want to search just for "medical". james |
Topic | Author | Date |
Firmware Documenation and Planning | 01/01/70 00:00 | |
Firmware doc | 01/01/70 00:00 | |
Code Complete | 01/01/70 00:00 | |
Some tips | 01/01/70 00:00 | |
my experience and methods | 01/01/70 00:00 | |
I use similar methods | 01/01/70 00:00 | |
I agree... | 01/01/70 00:00 | |
Read Jack Ganssle | 01/01/70 00:00 | |
Will check this out | 01/01/70 00:00 | |
mil-std-2167 | 01/01/70 00:00 | |
Hardware documentation? | 01/01/70 00:00 | |
Hardware documentation? (different)![]() | 01/01/70 00:00 |