REQUIREMENTS ELICITATION REPORT
Hein Min Htike
Ang Rhu Zen
The report is about the activities done and observed before, while and after the trip to Zoo Negara. The main activities were deciding where and when to go, making the trip, arriving at the place and doing a visit, returning from the trip and activities after the visit. Initially, we were planning to visit A’ Famosa in Malacca, but it was canceled as Malacca was a big distance away from the campus, and the travelling will take most of our time. After searching on the internet about places to visit in Kuala Lumpur, we decided on visiting Zoo Negara on Saturday, which is much closer compared to Malacca and almost none of us had visited the place yet.
On Saturday morning, we met at the SA building and drove to the zoo. Having a driver who knows the routes in Kuala Lumpur, we reached Zoo Negara in about an hour. However, we had a hard time finding parking spots as it was the eve of Hari Raya. In the end, we had to park our car a long distance away from the entrance, but at least we have arrived at the zoo.
Inside the zoo, we saw different kinds of animals and there were several centers that function as a sanctuary for famous local birds, reptiles and fish. We collected data by taking pictures and interviewing a few individuals while having a break at one of the train stops. After we went to see the tigers and lions in the Mammal Kingdom, we finally left the zoo from another entrance, which was not far from where we parked. On the way back, we stopped at a Burger King in Damansara for late lunch before heading back to Nottingham. When we got back to our own home s, we saved the pictures that were taken and started on writing the report.
In the end, the problems we had on that trip was based on finding places within the zoo and wasting our time seeing some of the same attractions.
Approach to requirements elicitation
Requirements elicitation is also known as requirements gathering, which is part of the process upon enquiring the requirements of a particular system from users, customers and stakeholders. In other words, it can also be considered as consul tation with the people who are involved in the process as mentioned above. Stages of elicitation include objective setting, background knowledge, knowledge organisation and stakeholder requirements collection. There is various specific approach of requirements elicitation which includes interviewing, soft systems methods, prototyping, scenarios, and requirements reuse and participant observation. These are some of the familiar approach to requirements elicitation.
Firstly, the requirements engineer will talk about the system with numbers of stakeholders and boost the understanding of their requirements. Therefore, an interview will be conducted in order to get the necessary information. This can be done in two different ways, either through closed interviews or open interviews. Closed interviews will be conveyed by looking for answers from a pre-defined number of questions which has been set by the requirements engineer. Unlike closed interviews, open interviews let the requirements engineer to dispute with the stakeholders in an open-ended way about what they want from the system. Interviewers can never approach the interview with
disapproving ideas about what is needed and must be open-minded. Besides that, stakeholders must be given an idea about the discussion by requirements proposal or show examples of an existing system.
Secondly, scenarios technique is used for elicitation which explains the way a system is being used through stories description. It starts with an introduction of the system before the scenario starts, then the usual flow of events with some exception and information about coexisting activities. At the end of the scenario, a description of the system is being stated....