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
What is the term used for a short, focused meeting held daily in Agile and Lean Thinking?
-
Daily stand-up meeting
-
Sprint planning meeting
-
Sprint review meeting
-
Sprint retrospective meeting
A
Correct answer
Explanation
Daily stand-up meetings are held daily in Agile and Lean Thinking to allow team members to share their progress, identify any blockers, and coordinate their work.
What is the term used for a cross-functional team in Agile and Lean Thinking?
-
Scrum team
-
Kanban team
-
Feature team
-
All of the above
D
Correct answer
Explanation
In Agile and Lean Thinking, cross-functional teams are self-organizing teams that consist of members with different skills and expertise to work together on a specific project or feature.
What is the term used for a visual representation of the flow of work items in Agile and Lean Thinking?
-
Kanban board
-
Scrum board
-
Task board
-
All of the above
D
Correct answer
Explanation
Kanban boards, Scrum boards, and task boards are all visual representations of the flow of work items used in Agile and Lean Thinking.
Which of the following is NOT a typical phase in the Information Lifecycle Management process?
-
Information Creation
-
Information Storage
-
Information Archiving
-
Information Destruction
C
Correct answer
Explanation
Information Archiving is not a typical phase in the ILM process. Instead, it is a specific storage strategy used to manage inactive information.
Which of the following is a key principle of Agile methodology?
-
Iterative and incremental development
-
Comprehensive planning and documentation
-
Big Bang approach to software development
-
Strict adherence to predefined requirements
A
Correct answer
Explanation
Agile methodology emphasizes iterative and incremental development, where the software is developed in small, manageable increments, allowing for flexibility and adaptability to changing requirements.
What is the primary focus of a Sprint in Agile methodology?
-
To complete a specific set of user stories
-
To conduct extensive testing and quality assurance
-
To create detailed project documentation
-
To gather requirements from stakeholders
A
Correct answer
Explanation
A Sprint in Agile methodology is a fixed-length iteration, typically lasting one to four weeks, during which a team focuses on completing a specific set of user stories or features.
Which of the following is a key practice in Continuous Delivery?
-
Continuous integration and testing
-
Manual testing and validation
-
Big Bang releases
-
Infrequent deployments
A
Correct answer
Explanation
Continuous Delivery emphasizes continuous integration and testing, where code changes are integrated and tested frequently, allowing for early detection and resolution of issues.
Which of the following is NOT a common Agile development tool?
-
Jira
-
Microsoft Project
-
Trello
-
Asana
B
Correct answer
Explanation
Microsoft Project is a traditional project management tool, while Jira, Trello, and Asana are popular Agile development tools designed to support iterative and collaborative development.
What is the primary focus of a Sprint Retrospective in Agile methodology?
-
To review and improve the Sprint process
-
To create a detailed plan for the next Sprint
-
To assign tasks to team members
-
To generate project reports
A
Correct answer
Explanation
The Sprint Retrospective is a meeting held at the end of each Sprint in Agile methodology, where the team reflects on the Sprint process, identifies areas for improvement, and plans for the upcoming Sprint.
Which of the following is a key principle of Continuous Delivery?
-
Frequent and reliable software releases
-
Big Bang releases
-
Infrequent deployments
-
Manual testing and validation
A
Correct answer
Explanation
Continuous Delivery emphasizes frequent and reliable software releases, enabling rapid delivery of value to customers and reducing the risk of major failures.
Which of the following is NOT a common Agile development methodology?
-
Scrum
-
Kanban
-
Waterfall
-
Extreme Programming (XP)
C
Correct answer
Explanation
Waterfall is a traditional software development methodology, while Scrum, Kanban, and Extreme Programming (XP) are popular Agile development methodologies.
Which of the following is NOT a key role in Agile methodology?
-
Product Owner
-
Scrum Master
-
Project Manager
-
Development Team
C
Correct answer
Explanation
Project Manager is a traditional role in waterfall methodology, while Product Owner, Scrum Master, and Development Team are key roles in Agile methodology.
Which of the following is NOT a common section of a technical report?
-
Abstract
-
Introduction
-
Methods
-
Results
-
Discussion
E
Correct answer
Explanation
The discussion section is not typically included in a technical report. The discussion section is usually found in research papers, where it is used to discuss the implications of the research findings.
Which of the following is NOT a common reliability improvement technique?
-
Redundancy
-
Fault Tolerance
-
Preventive Maintenance
-
Design for Reliability
C
Correct answer
Explanation
Preventive maintenance is a maintenance strategy that involves periodic inspection and servicing of a system to prevent failures, while the other options are common reliability improvement techniques.
Which of the following is NOT a common reliability modeling technique?
-
Fault Tree Analysis
-
Markov Chains
-
Bayesian Networks
-
Monte Carlo Simulation
D
Correct answer
Explanation
Monte Carlo simulation is a general-purpose simulation technique that can be used for a variety of applications, including reliability modeling, but it is not a specific reliability modeling technique like the other options.