1Requirements & system planning

• 1.1System planning and enterprise architecture

  Covers the four layers of enterprise architecture (EA)—BA (business architecture), DA (data architecture), AA (application architecture), and TA (technical architecture)—and the judgment skill of aligning IT planning with business strategy and, from the gap between the current state (As-Is) and the target state (To-Be), making the optimal planning decision in light of return on investment.

• 1.2The requirements definition process

  Covers requirements elicitation, drawing requirements out of stakeholders; requirements analysis, organizing requirements and resolving contradictions; the difference between functional requirements and non-functional requirements; requirements traceability, tracking the correspondence between requirements and deliverables; and the judgment skill of properly building consensus on requirements, including change management during development.

• 1.3Business modeling

  Covers the characteristics of representative business-modeling notations—DFD (data flow diagram) for depicting the flow of business, the E-R diagram for data structure, UML (use case diagrams, etc.) for the interaction between the system and users, and BPMN for the overall flow of a business process—and the judgment skill of choosing the notation appropriate to the purpose of contrasting the current business (As-Is) against the desired business (To-Be).

• 1.4Defining non-functional requirements

  Covers using the non-functional requirements grade, which systematically organizes non-functional requirements such as performance, reliability, availability, and security, and the judgment skill of translating easily-vague non-functional requirements into measurable indicators and building stakeholder consensus on them to prevent rework.