Assume you have a small team of people involved in development of various projects over the time. Projects come and go, some of them exist in parallel, some of them go and come back later again etc.
Say, the team does not have any formal tools for defining and tracking project requirements and bugs. One of the vialble (IMO) approaches would be to utilize a simple blogging engine for that purpose. That could be done in the following way:
The engine must support tags and multi-tag search. It also must support multiple users of course.
Every project is associated with a specific tag, e.g. project DreamViewer is associated with a tag DreamViewer or tag projDreamViewer.
Few more tags are introduced to reflect different types of posts:
1. Use-case - the post defines a use case (actors, goal, steps, extentions etc.). It could refer (just by providing a URL) to some “Feature-request” post describing the need in some feature in a couple of sentences. It als can refer to other related, more specific or more generic use cases.
2. Test-case - the post defines a test case, a scenario of testing. It could refer to a use case that produced this test case.
3. Bug - self-explanatory. It may refer to a test case, that was used to identify the bug.
4. Feature-request - short description of some feature to be implemented. Could refer to some use case describing associated scenario.
5. Specification - some (primarily non-functional) specification, for example database design.
6. Note - just any kind of note, used to communicate some message to other team members.
Some tags may also be introduced for statuses (e.g. statusOpen), priorities (e.g. pHigh), team members (JohnDoe) etc.
Comments to different posts could contain discussion, additions to the original post, status change notes etc.
While such a solution is very light and do not pretend to be comprehensive in any way, it may become a good replacement for completely ad-hoc cowboy-style management of requirements and bug tracking.