Computer Knowledge

Software Development and Management

2,312 Questions

Software development and management focuses on the system development life cycle, enterprise architecture, and configuration management. It tests your familiarity with system analysis, design models, and IT project planning. This subject is essential for specialist and banking officer scale examinations.

System analysis and designSoftware development life cycleConfiguration managementEnterprise architectureObject oriented design

Software Development and Management Questions

Multiple choice

Which of the following is a common SCM challenge?

  1. Managing large and complex software systems.

  2. Ensuring the integrity and consistency of software artifacts.

  3. Coordinating changes from multiple developers.

  4. All of the above.
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Managing large and complex software systems, ensuring the integrity and consistency of software artifacts, and coordinating changes from multiple developers are all common SCM challenges.

Multiple choice

Which of the following is a major research project undertaken by CMMACS?

  1. Development of a mathematical model for the spread of infectious diseases

  2. Simulation of the behavior of complex systems

  3. Analysis of large-scale datasets

  4. All of the above
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

CMMACS has undertaken several major research projects, including the development of mathematical models for the spread of infectious diseases, simulation of the behavior of complex systems, and analysis of large-scale datasets.

Multiple choice

Which of the following is NOT a common technique for eliciting software requirements?

  1. Interviews

  2. Questionnaires

  3. Use cases

  4. Reverse engineering
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Reverse engineering is a technique for understanding the design and implementation of an existing software system, not for eliciting requirements for a new system.

Multiple choice

Which of the following is NOT a type of software requirement?

  1. Functional requirements

  2. Non-functional requirements

  3. Business requirements

  4. User requirements
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Business requirements are high-level statements of the goals and objectives of an organization, not specific requirements for a software system.

Multiple choice

Which of the following is NOT a common section of a Software Requirements Specification (SRS)?

  1. Introduction

  2. Requirements

  3. Design

  4. Test plan
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

The SRS should contain an introduction, a section on requirements, and a section on test plans, but it should not contain a section on design.

Multiple choice

Which of the following is NOT a common type of non-functional requirement?

  1. Performance requirements

  2. Security requirements

  3. Reliability requirements

  4. Maintainability requirements
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Maintainability requirements are not typically considered non-functional requirements, as they are related to the ease of modifying and updating the software system.

Multiple choice

Which of the following is NOT a common technique for managing software requirements?

  1. Requirements traceability matrix

  2. Change control board

  3. Risk management

  4. Configuration management
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Configuration management is a technique for managing the changes to the software system itself, not for managing the requirements for the system.

Multiple choice

Which of the following is NOT a common tool for documenting software requirements?

  1. Natural language

  2. Structured natural language

  3. Use cases

  4. Formal specifications
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Formal specifications are a mathematical notation for expressing software requirements, but they are not a common tool for documenting requirements.

Multiple choice

Which of the following is NOT a common technique for managing software requirements changes?

  1. Change control board

  2. Impact analysis

  3. Risk management

  4. Version control
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Version control is a technique for managing the changes to the software system itself, not for managing the changes to the requirements for the system.

Multiple choice

Which of the following is NOT a common technique for prioritizing software requirements?

  1. MoSCoW method

  2. Weighted sum method

  3. Analytical hierarchy process

  4. Pairwise comparison
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

The analytical hierarchy process is a technique for making decisions, not for prioritizing software requirements.

Multiple choice

Which of the following is NOT a common technique for tracing software requirements?

  1. Requirements traceability matrix

  2. Use cases

  3. Data flow diagrams

  4. Entity-relationship diagrams
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Entity-relationship diagrams are a technique for modeling data, not for tracing software requirements.

Multiple choice

Which of the following is NOT a common technique for managing software requirements risks?

  1. Risk identification

  2. Risk assessment

  3. Risk mitigation

  4. Risk acceptance
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Risk acceptance is a decision to accept a risk, not a technique for managing software requirements risks.

Multiple choice

Which of the following is NOT a common technique for communicating software requirements?

  1. Natural language

  2. Structured natural language

  3. Use cases

  4. Formal specifications
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Formal specifications are a mathematical notation for expressing software requirements, but they are not a common technique for communicating requirements to stakeholders.

Multiple choice

Which of the following is NOT a common technique for measuring the quality of software requirements?

  1. Completeness

  2. Consistency

  3. Correctness

  4. Traceability
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Traceability is a measure of the degree to which requirements can be traced to other artifacts, such as design documents and test cases, not a measure of the quality of the requirements themselves.

Multiple choice

In the context of software development, what does the term 'agile' methodology refer to?

  1. A flexible and iterative approach to software development

  2. A waterfall-based approach to software development

  3. A top-down approach to software development

  4. A bottom-up approach to software development
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Agile methodology is a software development approach that emphasizes flexibility, adaptability, and iterative development. It involves breaking down a project into smaller, manageable tasks and working in short cycles to deliver incremental results.