Software Development and Management

The customer typically has final authority over requirements and priorities since they fund the project and define business value. Business analysts gather requirements, project managers coordinate execution, and direct users provide input - but none have the customer's ultimate decision authority.

A phase gate review is a key project review marking the transition between project phases, making its completion a major milestone. A critical activity is a task on the critical path rather than a milestone, while a peer review or a test case represents individual tasks that do not signify phase transition.

Tracking defect report status through their lifecycle is a core change management function. Option B describes build automation, Option C describes configuration library management, and Option D describes versioning/baseline management - these are SCM functions but not the primary change management role.

Architecture Building Blocks (ABBs) define WHAT functionality is required at an architectural level, while Solution Building Blocks (SBBs) define WHAT specific products, components, or technologies will implement that functionality. ABBs are technology-agnostic specifications. SBBs are concrete implementations. Option A is incorrect because both can be reusable. Option B reverses the definitions. Option C has the relationship backwards.

Application systems should be described as logical groups of capabilities that work together to support business functions. This abstraction-level description is appropriate for architecture work. Computer systems (A) is too technical. Schemas (C) relate to data structure. Data-flow diagrams (D) are analysis tools, not system descriptions.

When selecting building blocks, TOGAF recommends prioritizing reusable components from the Enterprise Continuum (repository of proven assets) before developing custom solutions. This promotes consistency and reduces development effort. Custom components (B) and common systems components (D) are secondary considerations. Integration methods (C) are implementation concerns.

Qualitative criteria in application architecture evaluation include non-measurable attributes like security, maintainability, and flexibility. Security is clearly qualitative (no single metric defines 'secure'). Option A (defects per unit of code) is quantitative. Options B (cost) and E (timeline) are financial/time metrics. Option D (functionality) is about what the system does, not a qualitative quality measure.

TOGAF's architecture development method is iterative. If Application Architecture work reveals necessary changes to Business Architecture, the correct action is to revisit and refine the Business Architecture phase before proceeding. This ensures alignment. Options B, C, D, and E suggest workarounds or governance actions that skip proper iteration back to the earlier phase.

The question asks about defect status when providing "Suggestions" to the development team. Since suggestions could be given at various stages (when initially reporting, during analysis, or after reopening), and Quality Center defect workflows vary by organization configuration, the status could legitimately be New, Open/In Analysis, or Reopened depending on when the suggestion is made.

Patch management follows a three-stage lifecycle: (1) Acquiring - identifying needed patches and downloading them from vendors; (2) Testing - validating patches in a non-production environment to ensure they don't break existing functionality; (3) Installing - deploying tested patches to production systems. This sequence minimizes the risk of patch-induced downtime or security issues.

Data flow analysis studies how data is defined and used along execution paths through the code. It tracks variable definitions (where values are assigned) and uses (where values are referenced) to identify potential issues like using uninitialized variables. Option A refers to performance analysis, option B is meaningless, and option C refers to complexity metrics like cyclomatic complexity.

Typical inspection costs cover setting up resources, reviewing material, meetings, and process improvement. Writing the document itself is a development cost, not a quality control or inspection cost. Therefore, it is correctly excluded from inspection overhead.

Data flow analysis is a white-box technique that examines how data values are defined, used, and killed along execution paths through the code. It tracks the flow of data from definition to use, identifying potential issues like uninitialized variables or variables used before definition. It does not study communications (A), rate of change (B), or complexity (D).

Software engineers typically evaluate and rank tools but do not make final purchasing decisions. Their role is to identify options, assess technical fit, and make recommendations to management who authorize the actual purchase. Option A correctly describes this advisory role.