Timeline for What does your Technical Documentation look like?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2011 at 17:22 | vote | accept | Rachel | ||
| Jan 2, 2011 at 18:37 | comment | added | Zekta Chan | +1 for Architecture documents is very essential for large project. Since they'll small pieces are scattering around, which make it very hard (if not impossible) to understand solely from code for new comers. | |
| Dec 23, 2010 at 17:48 | comment | added | Justin Ethier | From my experience it is more about using standard templates, document structure, etc than about data formats or software. | |
| Dec 23, 2010 at 17:10 | comment | added | Rachel | Ok thanks. That's mostly what I use but I was wondering if there was some other standardized software for technical documentation | |
| Dec 23, 2010 at 15:20 | comment | added | Justin Ethier | I use Word to write the documents, and Visio to prepare any diagrams for them. You could use other software if you want, these tools just happen to work the best for me, and are (mostly) accepted by the team. | |
| Dec 23, 2010 at 15:06 | comment | added | Rachel |
What sort of software do you use for your formal design documents?
|
|
| Dec 23, 2010 at 14:54 | history | edited | Justin Ethier | CC BY-SA 2.5 |
added 15 characters in body; added 468 characters in body; edited body
|
| Dec 23, 2010 at 14:48 | history | answered | Justin Ethier | CC BY-SA 2.5 |