Even if you never write a requirements specification, it’s important, as a software architect, to know what separates the good ones from the bad. Learn the fundamentals of writing a good spec and then pass on what you’ve learned to other members of your development team.”
- Designing software architectures, Part 1 the importance of process
- Designing software architectures, Part 2 the role of the architect
- Designing software architectures, Part 3 how to write a requirements specification
Brajeshwar posted this article
on Fri, Dec 17th, 2004 at 10:09 am
Categorized under Management








Comments Post Yours
There are no response so far. You can follow any responses to this entry through the RSS feed. You can skip to the end and leave a response. Pinging is currently not allowed.
Post yours