Answer the question
In order to leave comments, you need to log in
Is there a service or software for maintaining specifications, long lists?
Faced with the problem of scale: when maintaining long (100+) lists in the specification, the use of documents becomes very inconvenient. Large documents are difficult to quickly navigate, difficult to keep track of what has been done/not done/changed, and even more difficult to compare the document with work already done.
Important clarifications: we are not talking about a detailed description in the TOR, where the tasks are structured, hierarchical and described in general terms, and the task itself can be easily transferred, for example, in a chat - there are project management systems for this and there are many good ones. We are talking about maintaining specifications, when analysts analyze, make many similar items, and the developer does not understand (and should not) all the details of what he is doing. Or, for example, functional test cases for Enterprise applications - dimensionless documents that need to be clicked on by the tester.
A bonus to the complexity are:
1. the need to work with a document in several roles - an analyst, a developer, a tester, each of which needs something of its own and does not need someone else's at all;
2. the complexity of version control, in particular version comparison;
3. teamwork (several developers or analysts work on different parts of the document).
Now the problem is solved by maintaining in parallel the specification of a separate spreadsheet document, which indicates the names and numbering of items and service information (statuses, questions, etc.). But synchronization of the plate with the specification also requires costs and does not solve all problems.
I am looking for software for maintaining such lists, googling did not give anything.
Answer the question
In order to leave comments, you need to log in
Good afternoon!
Let me suggest a solution. This is not software, of course - I don’t know how it will solve your problems, but I’ll try anyway.
docbook document (revhistory element with attributes) + visual editor (like XMLMind) + comparison and merging (for example, Meld in Linux) + svn/git for storing and versioning.
If you have any questions - welcome
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question