Another term commonly used for this sub-topic is
“conflict resolution.” This concerns resolving problems
with requirements where conflicts occur between two
stakeholders requiring mutually incompatible features,
between requirements and resources, or between
functional and non-functional requirements, for example.
[Kot00, Som97] In most cases, it is unwise for the
software engineer to make a unilateral decision, and so it
becomes necessary to consult with the stakeholder(s) to
reach a consensus on an appropriate trade-off. It is often
important for contractual reasons that such decisions be
traceable back to the customer. We have classified this as
a software requirements analysis topic because problems
emerge as the result of analysis. However, a strong case
can also be made for considering it a requirements
validation topic.
Another term commonly used for this sub-topic is
“conflict resolution.” This concerns resolving problems
with requirements where conflicts occur between two
stakeholders requiring mutually incompatible features,
between requirements and resources, or between
functional and non-functional requirements, for example.
[Kot00, Som97] In most cases, it is unwise for the
software engineer to make a unilateral decision, and so it
becomes necessary to consult with the stakeholder(s) to
reach a consensus on an appropriate trade-off. It is often
important for contractual reasons that such decisions be
traceable back to the customer. We have classified this as
a software requirements analysis topic because problems
emerge as the result of analysis. However, a strong case
can also be made for considering it a requirements
validation topic.
การแปล กรุณารอสักครู่..