4 ms·
> I've never experienced a situation where a software design document meaningfully improved the overall process. If you don't have a document, then how do you
by RaftPeople 19d ago
> I've never experienced a situation where a software design document meaningfully improved the overall process.
If you don't have a document, then how do you make sure that internal team A and internal team B and internal team C and external vendor D and external vendor E all create the correct things so the entire system actually works?
- cryptonector 19d agoAt Sun we didn't use design docs for this. We used architecture docs instead. These were of the form of PSARC cases with materials such as: - interfaces lists, with attached commitment levels - interface contracts where interface commitment levels do not otherwise allow teams A, B, and C to use each other's interfaces. That's much better than design docs. The difference between architecture and design -at Sun anyway- was this: - architecture is only about interfaces - design is about details like algorithms
- RaftPeople 19d agoI was thinking in terms of a broad usage of "design" which tends to match what you wrote about architecture.
- cryptonector 19d agoOften people mean "architecture" when they say "design", yeah.