After this chapter the student should have acquired the following knowledge and skills: Inception process, elicitation process, introduction- requirements elicitation, requirements elicitation process, components of requirements elicitation, elicitation activities, elicitation process problems, requirements analysis and negotiation,. | Requirements Elicitation Process Lecture-6 Recap 2 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Today’s Lecture 3 Inception Process Elicitation Process Process 4 Inception Process 5 Introduction- Requirements elicitation 6 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. Requirements Elicitation Process 7 Components of requirements elicitation 8 Elicitation activities Application domain understanding Application domain knowledge is knowledge of the general area where the system is . | Requirements Elicitation Process Lecture-6 Recap 2 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Today’s Lecture 3 Inception Process Elicitation Process Process 4 Inception Process 5 Introduction- Requirements elicitation 6 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. Requirements Elicitation Process 7 Components of requirements elicitation 8 Elicitation activities Application domain understanding Application domain knowledge is knowledge of the general area where the system is applied. For Example: to understand the requirements for a railway signaling system, you must have background knowledge about the operation of railways and the physical characteristics of trains. Problem understanding The details of the specific customer problem where the system will be applied must be understood. For a railway signaling system, you must know the way in which speed limits are applied to particular track segments. Business understanding You must understand how systems interact and contribute to overall business goals. (Means, the contribution of the system in business goal) Understanding the needs and constraints of system stakeholders You must understand, in detail, the specific needs of people who require system support in their work. 9 Elicitation process problems 10 1. Application domain knowledge is not collected neatly in one place. It exists in a variety of different sources such as in textbooks, operating manuals and in the heads of the people working in that area.
