2004-06-28 08:57:53 Vanguard
Demand specifications and use case documents, who is the first? Do not consider iteration.
2004-06-28 09:01:49 Qingrun
Demand specifications first come first.
However, to make supplemental amendments after using an example document development.
2004-06-28 09:02:29 Qingrun
Then use an example document in the range of revisions within the requirements of the requirements specification specification, obtain the first final version.
2004-06-28 09:02:41 Qingrun
This is mainly about the problem of change.
2004-06-28 09:04:43 Vanguard
That is to say, after the use of the example document, the details of the demand specification did not take into account, right?
2004-06-28 09:05:17 Vanguard
What is the revision of the use case document?
2004-06-28 09:06:06 Qingrun
This is not a detail of modification requirements, because the demand details have been described in the use case document.
Here is the additional content of the demand document, such as performance indicators, etc., for the details of the needs, usually do not need to do more modifications.
2004-06-28 09:06:43 Qingrun
The latter is to enable all use case documents to be unified within a range.
2004-06-28 09:07:02 Vanguard
That is, the demand specification is an overview of the demand, and the specific implementation process of the needs of the need is required?
2004-06-28 09:07:13 Qingrun
Yes it is.
2004-06-28 09:07:36 Qingrun
Its name is this meaning, the demand specifications, not the needs of the needs.
2004-06-28 09:07:56 Vanguard
Understand, I often overlap the contents of the two, [: $]
