Introduction- Requirements elicitation }Requirements elicitation is the usual name given to activities involved in discovering the requirements of the system. }System developers and engineers work with customers and end-users to find out about}The problem to be solved, the system services, the required performance of the system, hardware constraints, and so on. }This doesn't just involve asking
...[Show More]
Introduction- Requirements elicitation }Requirements elicitation is the usual name given to activities involved in discovering the requirements of the system.
}System developers and engineers work with customers and end-users to find out about
}The problem to be solved, the system services, the required performance of the system, hardware constraints, and so on.
}This doesn't just involve asking people what they want;
It requires a careful analysis of the organization, the application domain and business processes where the system will be used.}The objective of requirements analysis and negotiation is to establish an agreed set of requirements which are complete and consistent.
}These requirements should be unambiguous so that they can be used as a basis for system development.
}During the analysis process, missing requirements, requirements conflicts, ambiguous requirements, overlapping requirements and unrealistic requirements are normally discovered.
}If there are requirements conflicts or if the requirements proposal seems to be too ambitious, stakeholders must negotiate and agree on modifications and simplifications to the system requirements.
[Show Less]
