I hope that I am not abusing this forum. But I feel that people that make this community have much more than just Perl expertise. My question is, "What are requirement documents?" I think I know that there are typically: "Requirement Document", "Detailed Design Document" and that's about it right? What else it there? What is "traceability and a traceability matrix"? What document do the test plans belong? Who should write these documents? On the monster job site they list this as on of the skills of a software engineer.

The ability to create functional and technical design specifications for development efforts is an essential skill for software engineers.

What are functional and technical design specifications?

Does any know of any good books or web-sites that define these documents? I need this information to deal with a every increasing contentious atmosphere here at my work. As the deadlines go racing by and my "team" has failed to produce a deliverable product, I wonder if this is due to attitude of the project leadership that "documentation" is a luxury that we didn't have time for.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.