REQUIREMENTS ELICITATION

Flashcards generated from lecture notes on system requirements and analysis, covering topics such as sources of requirements, the Kano model, and elicitation techniques.

Name some examples of stakeholders as a source for requirements.

Users,

sponsors,

developers,

authorities,

customers.

Give examples of documents that serve as a source for requirements.

Company-, Domain-, project-related documents, product and process descriptions, legal and regulatory documentation.

Name other systems that can serve as a source for requirements.

Legacy systems,

competitor systems,

comparable systems used in other organizations.

Categories of Elicitation Techniques

Gathering

Questioning

Collaboration

Observation

Artifact-based

Design & idea-generating

List some elicitation techniques

Interview, workshops, questionnaire, crowd-based RE, observation, artefact-based, system archaeology, field observation, feedback analysis, apprenticing, reuse of requirements, design & idea-generating, creativity, design, brainstorming, analogy technique, scenarios & storyboards.

What are the three categories of system features according to the Kano Model?

Delighters (excitement factors, unconscious requirements),

Satisfiers (performance factors, conscious requirements),

Dissatisfiers (basic factors, subconscious requirements).

Describe the process of interviewing users and other stakeholders to gather requirements.

Prepare detailed questions, meet with stakeholders, document answers, and follow up.

Differentiate between open-ended and close-ended questions in the context of requirements gathering.

Open-ended questions encourage discussion, while closed-ended questions aim to get specific facts.

Describe the purpose and structure of workshops as a collaboration technique for requirements elicitation.

Workshops involve a structured meeting of stakeholders and experts to define and refine requirements.

Why is it important to prioritize requirements during the requirements analysis phase?

Prioritizing requirements helps manage limited resources, avoid scope creep, and determine project iterations.

Why is it important to prioritize requirements?

Limited resources and the need to justify system scope, scope creep, the need to make sure high priority requirements are in early iterations.

What are some challenges of Requirements Analysis?

Stakeholders may not know what they want, use their own terms, have conflicting needs, and organizational or political factors may impact requirements.