A. in a project team, with an "analyst" job title.
B. in any capacity, regardless of job title.
C. in a project team, regardless of job title.
D. in any capacity, with an "analyst" job title.
A. Requirements at low levels of abstraction
B. Requirements without direct ties to a particular tool
C. Requirements expressed in more detail
D. Requirements with specific references to departments
A. Output, input
B. Extend, enhance
C. Allow, prevent
D. Extend, include
A. Trace Requirements
B. Maintain Attributes
C. Prioritize Designs
D. Elicit Requirements
A. already known by stakeholders.
B. easy to use.
C. commonly used in similar initiatives.
D. popular in the industry.
A. Activity flow
B. Data and information
C. People and roles
D. Rationale
A. Acceptance and Evaluation Criteria
B. Risk Analysis and Management
C. Key Performance Indicators
D. Entity Relationship Modelling
A. Elicitation analysis
B. Conduct elicitation
C. Prepare for elicitation
D. Stakeholder collaboration
A. Problem solving
B. Conceptual thinking
C. Creative thinking
D. Systems thinking
A. Define design options
B. Define requirements architecture
C. Analyze potential value and recommend solution
D. Validate requirements
