A. Assess solution limitations
B. Trace requirements
C. Analyze current state
D. Plan stakeholder engagement
A. Defining a solution independent view of how a business perceives its information without applying any constraints.
B. Abstracting a 'conceptual data model' to incorporate the rules of normalization to manage data integrity and relationships.
C. Abstracting a 'physical data model' to describe the physical organization of data and its relationships within a database.
D. Defining the logical rules that govern decisions in an organization and that define, constrain, or enable organizational operations.
A. Domain SME, regulator, sponsor, project manager
B. Author, reviewer, facilitator, scribe
C. Approver, administrator, reviewer, tester
D. Customer, supplier, end user, business analyst
A. Business benefits
B. Organizational policy
C. Technological dependency
D. Market demands
A. Data flow diagram
B. Flowchart
C. Data modelling
D. Sequence diagram
A. Scope modelling
B. User stories
C. Business case
D. Lessons learned
A. analytical thinking.
B. prioritization setting.
C. encouraging participation.
D. sharing of information.
A. Value
B. Priority
C. Solution
D. Change
A. Testable
B. Concise
C. Atomic
D. Feasible
A. Complexity, stability, status
B. Penalty, benefit, cost
C. Necessary, consistent, correct
D. Necessity, validate, derive
