Our organization has been clamoring for a more organized spec-making process. At the moment, we use a combination of UX Specs (created in a wireframing tool and published as PDFs), and Functional Specs (created in a writing tool, either a client such as Word or a hosted tool such as an internal Wiki). The two documents are created by separate teams on a project (the former by the UX Designer, the latter by one or more of the developers).
The key audience for this is the QA team. For now, the forms of these documents are working fine, but the fact that they are created, delivered and maintained separately is the problem. In practice, they refer to these two documents in parallel, switching back and forth to develop a full understanding of how the product they are testing is supposed to work. I am exploring ways that they can be managed as an integrated set of documents. In an ideal world, the functional spec would be able to refer to parts of the UX spec, and show those parts inline.
I am about to do a deep dive to evaluate SharePoint as a possible platform for this, as I believe it supports linking between managed documents. (And there appears to be a way to link to a particular page within a given PDF.) This is still not as integrated as I would like, but may be the best available option. Has anyone here dealt with this issue before, and if so, can you describe how you ultimately addressed it?