Software Development and Management

Phase B Business Architecture focuses on describing the baseline and target architectures, selecting tools and viewpoints, and addressing stakeholder concerns. Defining business requirements happens in earlier phases (Preliminary/Phase A), making D the exception.

Business Process Models, Use-Case Models, Class Models, and Information Exchange Matrix are all modeling techniques for capturing business aspects. The Traceability Matrix is a requirements management tool for tracking requirements to implementations, not a business modeling tool.

The question asks which is NOT a suggested step for gap analysis. All the options listed (Process Gap, Tools Gaps, Financial Gaps, Information Gaps) are valid gap types that should be analyzed. Since none of them should be excluded from gap analysis, E (none of the above) is correct.

Defect Management focuses on tracking logged defects after they're found, not preventing them upfront. The process includes defect prevention activities, management reporting, and tracking - but deliverable base-lining is a configuration management activity, not part of defect management workflow.

Phase B (Business Architecture) of TOGAF ADM receives inputs from the Preliminary Phase and Phase A. These include refined business goals, Architecture Principles, and the existing baseline architectures (Technology and Application). All listed items are valid inputs to Business Architecture work.

Phase B steps include developing baseline descriptions, selecting building blocks, identifying reference models/tools, and creating architecture models. Conducting external expert workshops is not a documented TOGAF ADM step - this would be part of stakeholder engagement, not a formal ADM phase step.

Business Architecture outputs include Business Services, Functions, Processes (with measures), and updated requirements. Key business goals are INPUTS to Phase B from Phase A, not outputs. The phase delivers architecture descriptions, not the goals themselves.

Defect management involves preventing defects, managing the lifecycle of found defects, and providing management visibility. Deliverable base-lining (A) is a configuration management practice for version control, not part of tracking and resolving defects. Prevention (B), reporting (C), and process management are all core to defect management. Option D (None of the above) is incorrect since A is indeed not included.

TOGAF ADM Phase A (Architecture Vision) focuses on preparation: establishing the project (A), scoping (B), reviewing principles (D), and identifying business goals (E). Creating detailed architecture models (C) happens in later phases (B, C, D) when developing specific domain architectures. Phase A is about vision and preparation, not detailed modeling. The marked answer C is correct - modeling is not a key step in Phase A.

The Architecture Vision phase (Phase A) outputs include: approved statement of architecture work (A), architecture principles (C), refined business goals (D), and the plan (E). Gap analysis results (B) are produced in Phase E (Opportunity and Solutions) or Phase F (Migration Planning) when comparing baseline to target architectures. Gap analysis is not an early phase output - it requires defined target and baseline architectures that don't exist yet in Phase A.

Object export and import in Ab Initio facilitates concurrent development by allowing developers to export object definitions from the repository to .SIF archive files, which can then be imported into other projects or environments, enabling parallel work without conflicts.

In a Documentum workflow template, an activity element represents a specific task or step in the business process that needs to be completed.

An ETL developer can identify and report defects during all stages of development, including requirements walkthroughs, code reviews, and unit testing phases.

ETL developers can and should identify defects throughout the development lifecycle: during requirement walkthroughs (logic gaps, unclear specs), code walkthroughs (implementation errors, logic flaws), and unit testing (functional bugs, edge cases). Each phase catches different classes of defects.