Computer Knowledge
Software Development and Management
3,064 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
What are some of the key performance indicators (KPIs) for maintenance engineering?
-
Mean time between failures (MTBF)
-
Mean time to repair (MTTR)
-
Overall equipment effectiveness (OEE)
-
Maintenance cost per unit of production
-
All of the above
E
Correct answer
Explanation
Key performance indicators (KPIs) for maintenance engineering include mean time between failures (MTBF), mean time to repair (MTTR), overall equipment effectiveness (OEE), and maintenance cost per unit of production.
Which of the following is a common version control system used in SCM?
-
Git
-
Subversion
-
Mercurial
-
Perforce
A
Correct answer
Explanation
Git is a widely used distributed version control system that allows developers to track changes to code and collaborate on projects.
What is the role of a configuration management tool in SCM?
-
To identify and track software artifacts that need to be managed.
-
To control access to and changes of software artifacts.
-
To establish and maintain relationships between software artifacts.
-
All of the above.
D
Correct answer
Explanation
A configuration management tool helps identify and track software artifacts, control access to and changes of software artifacts, and establish and maintain relationships between software artifacts.
Which of the following is a common branching strategy used in SCM?
-
Trunk-based development
-
Feature branching
-
Release branching
-
All of the above.
D
Correct answer
Explanation
Trunk-based development, feature branching, and release branching are all common branching strategies used in SCM.
Which of the following is a common SCM best practice?
-
Regularly backing up software repositories.
-
Using a version control system.
-
Conducting code reviews.
-
All of the above.
D
Correct answer
Explanation
Regularly backing up software repositories, using a version control system, and conducting code reviews are all common SCM best practices.
What is the role of a configuration item (CI) in SCM?
-
A CI is a software artifact that is subject to configuration management.
-
A CI is a collection of software artifacts that are managed as a single unit.
-
A CI is a document that describes the configuration of a software system.
-
All of the above.
D
Correct answer
Explanation
A CI is a software artifact that is subject to configuration management, a collection of software artifacts that are managed as a single unit, and a document that describes the configuration of a software system.
Which of the following is a common SCM challenge?
-
Managing large and complex software systems.
-
Ensuring the integrity and consistency of software artifacts.
-
Coordinating changes from multiple developers.
-
All of the above.
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.
What is the primary focus of the Amber library?
-
Excited State Calculations
-
Molecular Dynamics Simulations
-
Solid-State Calculations
-
Coupled Cluster Methods
B
Correct answer
Explanation
Amber is widely used for molecular dynamics simulations of biomolecules and is popular in the field of biomolecular modeling.
Which of the following is a major research project undertaken by CMMACS?
-
Development of a mathematical model for the spread of infectious diseases
-
Simulation of the behavior of complex systems
-
Analysis of large-scale datasets
-
All of the above
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.
Which of the following is NOT a common technique for eliciting software requirements?
-
Interviews
-
Questionnaires
-
Use cases
-
Reverse engineering
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.
Which of the following is NOT a type of software requirement?
-
Functional requirements
-
Non-functional requirements
-
Business requirements
-
User requirements
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.
Which of the following is NOT a common section of a Software Requirements Specification (SRS)?
-
Introduction
-
Requirements
-
Design
-
Test plan
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.
Which of the following is NOT a common type of non-functional requirement?
-
Performance requirements
-
Security requirements
-
Reliability requirements
-
Maintainability requirements
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.
Which of the following is NOT a common technique for managing software requirements?
-
Requirements traceability matrix
-
Change control board
-
Risk management
-
Configuration management
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.
Which of the following is NOT a common tool for documenting software requirements?
-
Natural language
-
Structured natural language
-
Use cases
-
Formal specifications
D
Correct answer
Explanation
Formal specifications are a mathematical notation for expressing software requirements, but they are not a common tool for documenting requirements.