Software Development and Management

In a formal review process, the sequence is Planning -> Kick-off -> Preparation -> Review meeting -> Rework -> Follow-up. Rework immediately follows the review meeting, where the author addresses issues identified. Option D correctly identifies Rework as the next activity.

In Quality Center and ALM, a Release represents a complete set of changes to one or more applications that are packaged together for distribution. This could be a software version, a patch bundle, or a feature set that moves through the testing lifecycle as a unit. Cycles are subdivisions within releases, while Libraries and Baselines are different QC concepts.

CMR is the standard tool used for implementing components to production environments. The other options (PRC, SSR, IMR) represent different tools that serve other purposes in the development lifecycle rather than production implementation.

The V-Model (Validation and Verification) requires testing to begin in parallel with development. Each development phase has a corresponding testing phase. Waterfall and Linear models separate testing after development, while Spiral is iterative but doesn't mandate concurrent testing.

In technology lifecycle management, 'Contained' represents technologies that are currently deployed and require ongoing maintenance support, but are not strategic or recommended for new implementations. This category helps organizations manage their existing technology footprint while limiting further investment in non-strategic components.

In technology lifecycle management, 'Declining' identifies technologies approaching end-of-life that require migration planning. These systems remain operational but represent increasing technical and business risk. Organizations should plan to transition away from declining components to more modern, supported alternatives.

Selecting components from the reference architecture provides strategic advantages beyond meeting immediate requirements: consistency, maintainability, supportability, and alignment with organizational standards. While functional requirements are necessary, they're insufficient alone - the reference architecture embodies enterprise best practices and supports long-term architectural evolution.

Gap analysis is the formal technique used to compare baseline (current state) and target (future state) architectures. It identifies what technology capabilities exist today, what's needed tomorrow, and the deltas that must be addressed. Requirements analysis happens earlier. Impact analysis assesses change consequences. Architecture audits review compliance.

TOGAF's four core architecture domains are Business Architecture (process/organization), Data Architecture (information structures), Application Architecture (software portfolio), and Technology Architecture (hardware/infrastructure). Systems Architecture is NOT a separate TOGAF domain - it's a subset or alternative term that falls within Technology Architecture, not a pillar alongside the others.

TOGAF is specifically designed for Enterprise IT Architecture - organization-wide technology strategy and planning across business, data, applications, and technology. It's too high-level for software architecture (individual systems). It doesn't address human/organizational design directly. BPM for SOA is a methodology, not an architecture planning level.

TOGAF's Architecture Development Method (ADM) organizes work into phases. Phase A is Architecture Vision, B is Business Architecture, C is Application Architecture, and D is Technology Architecture. Phase D explicitly focuses on defining the technology components needed to support the application components defined in Phase C.

Technology architecture models should address technical concerns: security mechanisms, network/hardware topology, communications protocols, and standards compliance. The executive management view (strategic/business-focused, high-level KPIs) adds minimal value to detailed technology architecture modeling - executives don't need nor use low-level technical diagrams.

Technology Architecture deliverables include the gap analysis report (A), requirements traceability (B), technology architecture models/diagrams (C), and technical specifications for building blocks (D). Architecture contracts (E) are formal governance agreements that come AFTER architecture is defined - they're not part OF the Technology Architecture content itself, but rather the mechanism to implement it.

Serviceability refers to how easily a system can be diagnosed, repaired, or upgraded while operational. It focuses on maintenance capabilities like identifying faults and applying fixes without downtime. Availability (A) is about uptime, manageability (B) is about administration ease, extensibility (C) is about adding features, and usability (E) is about user experience.