Why elicitation and analysis is difficult process in requirement engineering process? Explain.

 Requirement elicitation and analysis or eliciting and understanding requirements from system stakeholders is a difficult process in requirement engineering for several reasons:-

  • Stakeholders often don't know what they want from a computer system except in the most general terms. They may find it difficult to articulate what they want the system to do, they may make unrealistic demands because they don't know what is and isn't feasible.
  • Stakeholders in a system naturally express requirements in their own terms and with implicit knowledge of their own work. Requirements engineers without experience in their customer's domain may not understand these requirements.
  • Different stakeholders with diverse requirements may express their requirements. Requirement engineers have to discover all potential sources of requirements & discover commonalities and conflicts.
  • Political factors may influence the requirements of a system. Managers may demand specific system requirements because these will allow them to increase their influence in the organization.
  • The economic & business environment in which the analysis takes place is dynamic. It inevitably changes during the analysis process. The importance of particular requirements may change. New requirements may emerge from new stakeholders who were not originally consulted.

Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

Discuss classification or taxonomy of virtualization at different levels.