Software Development and Management

Scrum, XP, and Lean Development are all Agile methodology types. Scrum uses sprints and roles, XP emphasizes engineering practices, and Lean focuses on eliminating waste and delivering value.

SDD (Software Design Document or System Design Document) is typically authored by a System Analyst to describe the system architecture and design details. While developers may contribute, the SDD is primarily a system analyst's responsibility.

SDD (Software Design Document or System Design Document) is a technical document written by a System Analyst that describes system architecture, design components, and technical specifications. Developers implement from it, Business Analysts focus on requirements, and Test Managers use it for test planning.

ISO/IEC 12207 'Systems and software engineering - Software life cycle processes' is the standard that defines software life cycle processes including acquisition, supply, development, operation, maintenance, and disposal. This matches the question precisely. 12119 covers software package quality requirements, 14143 is about function point analysis, 15271 relates to IT service management, 15504 covers process capability assessment, and 15939 addresses measurement processes.

Framework Manager is the Cognos BI product used to model metadata and create the semantic layer for reporting. Cognos Datamanager is for data integration, Cognos Metrics Manager is for scorecard metrics, and Cognos Metric Designer is also for metric design - none of these are the primary metadata modeling tool.

Report Studio is the Cognos tool designed for creating professional dashboard reports with visual components like gauges, lists, and graphs. It provides the flexibility to create executive-facing dashboards with multiple visualization types. Cognos Connection is for portal access, Cognos SDK is for development, and Metric Studio is for scorecard-style monitoring.

Analysis Studio is designed for interactive data exploration and analysis. It allows users to drill through data, discover patterns, and perform ad-hoc analysis that leads to new questions. Cognos Planning is for budgeting, TM1 is for financial modeling, and Query Studio is for simpler querying without deep analysis capabilities.

Event Studio is designed for event-driven notifications and actions in Cognos. When a condition is met (like product returns exceeding 10), it can automatically send emails and run reports to specified recipients. Metric Studio tracks KPIs over time but isn't designed for conditional event-based alerts with actions.

Metric Studio is the IBM Cognos component specifically designed for creating scorecards and monitoring KPIs over time. It provides the framework for defining metrics, setting thresholds, and visualizing performance trends. Cognos Planning is for budgeting and forecasting, TM1 is for multidimensional analysis, and Analysis Studio is for ad-hoc data exploration.

Event Studio (formerly Event Management Service) is designed for event lifecycle management - creating, managing, and monitoring event-based tasks and alerts. Report Studio is for reports, Query Studio for ad-hoc queries, Metric Studio for scorecards.

Continuous Integration is a software development practice where developers integrate code frequently, often daily. Each integration is verified by automated builds and tests to detect integration errors early. It is a practice, not a tool (A) or a lifecycle phase (C).

The main objectives of Continuous Integration are reducing integration problems and enabling faster delivery of software. By integrating frequently and automating builds/tests, teams catch bugs early and release more quickly. Both decreasing integration time and speeding up delivery are core goals.

Luntbuild, Gump, and CruiseControl are all CI/CD tools that automate build and test processes. Ant is a build tool (like Make) but not specifically a Continuous Integration tool - it's used by CI tools but isn't one itself. CI tools orchestrate builds, tests, and reporting.

CI automates application builds, testing (including white box testing), and deployment. Configuration management (C) is typically handled separately - while related, it's not a core CI automation target. CI focuses on the integration-build-test-deploy pipeline.