Software Development and Management

To solve this question, the user needs to have knowledge of software development and quality management concepts. The user must identify the application of process management and quality improvement concepts to software development and maintenance.

Option A: QS14000 is not a recognized standard in software development. It is a quality management system standard for the automotive industry.

Option B: ISO 9000 is a family of quality management standards that provide guidance and tools for organizations to ensure that their products and services consistently meet customer requirements and that quality is consistently improved. However, it is not specifically focused on software development.

Option C: The Malcolm Baldrige National Quality Award is a US award for performance excellence and quality achievement, but it is not specifically focused on software development.

Option D: The Software Engineering Institute's Capability Maturity Model Integration (SEI/CMMI) is a process improvement framework that provides organizations with the essential elements of effective processes. It is specifically focused on software development and maintenance.

Therefore, the correct answer is:

The Answer is: D) SEI/CMM.

To solve this question, the user needs to know about software development and quality assurance concepts.

The process described in the question is known as Risk Management. Risk management is the process of identifying, assessing, and prioritizing risks that can affect a project or organization. In the case of software development, risk management involves identifying possible software failures or defects and evaluating the likelihood of these failures occurring.

Option A, Contingency Planning, is incorrect. Contingency planning refers to the process of developing a plan of action to respond to unexpected events or situations. While risk management may involve some contingency planning, it is not the same thing.

Option C, Configuration Management, is incorrect. Configuration management is a process that helps organizations manage changes to software, hardware, or other IT assets. While it is an important aspect of software development, it is not the same thing as risk management.

Option D, Process Improvement, is incorrect. Process improvement refers to the ongoing effort to improve the quality and efficiency of software development processes. While it may involve some risk management activities, it is not the same thing.

Therefore, the correct answer is:

The Answer is: B. Risk Management.

The definition provided describes system design or solution design functionality. A fishbone diagram (Ishikawa diagram) is a root cause analysis tool used to identify and visualize the many potential causes of a specific problem or effect. It is NOT the creative part of the design process that defines system functionality. The statement claims it is - this is False.

Use cases describe interactions between actors and a system to achieve goals. They must be traceable to at least one goal (B) - a use case without a purpose serves no function. While use cases are part of UML modeling, they are behavioral descriptions, not object-oriented constructs themselves (D). Use cases capture functional requirements regardless of implementation paradigm.

Developers are seen as creative (C) because they build and design new features, architecture, and solutions from scratch. Their primary role is creation - writing code, designing systems, and implementing functionality. This contrasts with testers who are stereotypically viewed as finding flaws in others' creations.

A requirement is a condition or capability needed by a user to solve a problem that must be met by a system. A result is an outcome of execution. A defect is a flaw. A mistake is a human action that may introduce defects. Option B matches the standard definition of a requirement.

Rails follows Agile principles like convention over configuration, DRY (Don't Repeat Yourself), and rapid iterative development. Waterfall (A) is rigid and sequential, Spiral (C) emphasizes risk analysis - neither match Rails' philosophy.

Ruby on Rails follows the Agile lifecycle model with its emphasis on iterative development, rapid prototyping, and convention over configuration. The framework supports continuous integration and frequent deployments. Waterfall is too rigid, Spiral is risk-focused, and 'A and B' is incorrect.

The Agile Manifesto values working SOFTWARE over comprehensive documentation, not 'Working Hardware'. Hardware is incorrect. The other three values (a, c, d) are correct. Since one statement is wrong, the overall answer is False.

Agile Management DOES use iterative cycles (a is wrong saying 'NotIterative'), DOES have rapid feedback (b is wrong), and DOES deliver early value (c is correct). Since statements contain clear contradictions (a and b say 'Not' to core Agile principles), the overall answer is False.

Agile Planning Phase typically involves identifying desired features, estimating their size, calculating duration based on velocity, and creating a schedule. These are core planning activities in Agile methodologies like Scrum.

Agile is a project management methodology emphasizing iterative development, adaptive planning, and rapid delivery. It's not about people management (HR), pure process management, or product design aesthetics.

Agile components are Scope (define what to build), Define (plan details), Develop (build), Evaluate (review/adapt). The D-D-D-E pattern captures the iterative cycle of defining, executing, and evaluating work.