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

Multiple choice

Which methodology combines elements of both the Waterfall and Agile methodologies, allowing for some flexibility while maintaining a structured approach?

  1. Spiral

  2. Scrum

  3. Kanban

  4. Lean
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

The Spiral methodology combines elements of both the Waterfall and Agile methodologies, allowing for some flexibility while maintaining a structured approach.

Multiple choice

In the Mobile App Development Lifecycle, which phase involves testing the app's functionality, performance, and usability?

  1. Design

  2. Development

  3. Testing

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

In the Mobile App Development Lifecycle, the Testing phase involves testing the app's functionality, performance, and usability to ensure it meets the requirements.

Multiple choice

Which Agile methodology emphasizes continuous integration and continuous delivery, with frequent releases of new features and updates?

  1. Scrum

  2. Kanban

  3. Lean

  4. Extreme Programming
Reveal answer Fill a bubble to check yourself
Correct answer
Explanation

Continuous Integration/Continuous Delivery (CI/CD) is an Agile methodology that emphasizes continuous integration and continuous delivery, with frequent releases of new features and updates.

Multiple choice

Which process involves breaking down a large project into smaller, more manageable tasks or user stories?

  1. Decomposition

  2. Refactoring

  3. Iteration

  4. Prioritization
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Decomposition is the process of breaking down a large project into smaller, more manageable tasks or user stories.

Multiple choice

Which Agile methodology uses a visual board to track the progress of tasks and user stories?

  1. Scrum

  2. Kanban

  3. Lean

  4. Extreme Programming
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Kanban is an Agile methodology that uses a visual board to track the progress of tasks and user stories.

Multiple choice

Which process involves identifying and addressing potential risks and issues early in the development cycle?

  1. Risk Assessment

  2. Quality Assurance

  3. Code Review

  4. User Acceptance Testing
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Risk Assessment is the process of identifying and addressing potential risks and issues early in the development cycle.

Multiple choice

Which methodology emphasizes customer collaboration, adaptive planning, and continuous learning?

  1. Scrum

  2. Kanban

  3. Lean

  4. Extreme Programming
Reveal answer Fill a bubble to check yourself
Correct answer
Explanation

Agile is a methodology that emphasizes customer collaboration, adaptive planning, and continuous learning.

Multiple choice

Which process involves refactoring and improving the structure and design of the codebase?

  1. Decomposition

  2. Refactoring

  3. Iteration

  4. Prioritization
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Refactoring is the process of refactoring and improving the structure and design of the codebase.

Multiple choice

Which Agile methodology uses short, fixed-length iterations called sprints to deliver incremental value?

  1. Scrum

  2. Kanban

  3. Lean

  4. Extreme Programming
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Scrum is an Agile methodology that uses short, fixed-length iterations called sprints to deliver incremental value.

Multiple choice

Which process involves prioritizing tasks and user stories based on their importance and impact?

  1. Decomposition

  2. Refactoring

  3. Iteration

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

Prioritization is the process of prioritizing tasks and user stories based on their importance and impact.

Multiple choice

In Agile, what is the recommended format for user stories?

  1. As a <user role>, I want <goal> so that <benefit>

  2. I need <feature> to <achieve outcome>

  3. The system should <functionality>

  4. We require <product> to <solve problem>
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

The recommended format for user stories in Agile is 'As a , I want so that '. This format ensures that user stories are user-centric, clear, and focused on delivering value.

Multiple choice

What is the primary benefit of using story mapping in Agile requirements gathering?

  1. It helps visualize the user journey and dependencies between user stories

  2. It facilitates prioritization and sequencing of user stories

  3. It enables effective collaboration and communication among stakeholders

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

Story mapping provides a visual representation of the user journey, helps prioritize and sequence user stories, and facilitates effective collaboration and communication among stakeholders.

Multiple choice

Which of the following is NOT a recommended practice for writing effective user stories?

  1. Keep user stories concise and focused on a single goal

  2. Use clear and unambiguous language that is easy to understand

  3. Include acceptance criteria to define the conditions for a successful outcome

  4. Write user stories in a technical and detailed manner
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

User stories should be written in a concise and user-centric manner, avoiding technical jargon and detailed specifications.

Multiple choice

Which of the following is NOT a common Agile requirement gathering technique?

  1. User story mapping

  2. Joint application design (JAD) sessions

  3. Focus groups

  4. Detailed requirements specification (DRS) documentation
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Detailed requirements specification (DRS) documentation is not a common Agile requirement gathering technique. Agile emphasizes flexibility and adaptability, and detailed requirements documentation can be too rigid and time-consuming.

Multiple choice

What is the primary benefit of using Agile user stories over traditional requirements specifications?

  1. User stories are easier to understand and communicate to stakeholders

  2. User stories allow for greater flexibility and adaptability to changing requirements

  3. User stories help prioritize and focus on the most valuable features

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

Agile user stories offer several benefits over traditional requirements specifications, including ease of understanding, flexibility, adaptability, and prioritization of valuable features.