A. Trace requirements
B. Validate requirements
C. Verify requirements
D. Manage requirements
A. requirements classification schema.
B. requirements allocation.
C. requirements architecture.
D. requirements traceability.
A. Concise and consistent
B. Timely and segmented
C. Bi-directional and iterative
D. Detailed and verbal
A. system documents, business rules, organizational policies, and regulations.
B. system limits, business models, organizational structures, and principles.
C. system costs, business revenues, organizational designs, and rules.
D. system names, business contacts, organizational forms, and protocols.
A. Prioritization
B. Observation
C. Estimation
D. Reviews
A. regulator,
B. sponsor.
C. end user.
D. domain subject matter expert.
A. Project manager
B. Business analyst
C. Programmer
D. Project sponsor
A. plan the business analysis approach
B. identify the stakeholders.
C. review the project charter.
D. discover the requirements.
A. A user story with inputs and outputs
B. A benchmarking report with industry comparisons
C. A business model canvas with financial estimates
D. A checklist with a standard set of quality elements
A. Value
B. Priority
C. Solution
D. Change
