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 NOT a common type of technical documentation?

  1. System architecture documentation

  2. Design documentation

  3. Implementation documentation

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

User manuals are not typically considered a type of technical documentation. They are primarily intended for end-users and provide instructions on how to use the software, rather than technical details about its implementation or design.

Multiple choice

Which of the following is NOT a recommended practice for writing effective software documentation?

  1. Use technical jargon and complex terminology.

  2. Provide clear and concise explanations.

  3. Use visuals and examples to illustrate concepts.

  4. Organize the documentation in a logical and structured manner.
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Using technical jargon and complex terminology is not a recommended practice for writing effective software documentation. It can make the documentation difficult to understand and may lead to confusion or errors.

Multiple choice

Which of the following is NOT a recommended practice for managing software documentation?

  1. Regularly review and update the documentation.

  2. Keep the documentation in a central and accessible location.

  3. Translate the documentation into multiple languages.

  4. Ignore user feedback and suggestions.
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Ignoring user feedback and suggestions is not a recommended practice for managing software documentation. User feedback is valuable for identifying areas where the documentation can be improved and for ensuring that it meets the needs of the users.

Multiple choice

Which of the following is NOT a best practice for implementing legal technology?

  1. Getting buy-in from stakeholders

  2. Creating a clear implementation plan

  3. Providing adequate training to users

  4. Ignoring the needs of users
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Ignoring the needs of users is not a best practice for implementing legal technology. It is important to consider the needs of users when selecting and implementing legal technology tools.

Multiple choice

Which of the following is NOT a common risk management tool?

  1. Risk Matrix

  2. Bow-Tie Diagram

  3. Monte Carlo Simulation

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

SWOT Analysis is a strategic planning tool, not a specific risk management tool.

Multiple choice

Which of the following is a common system analysis technique?

  1. Use case analysis

  2. Data flow diagramming

  3. Entity-relationship modeling

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

Use case analysis, data flow diagramming, and entity-relationship modeling are all common system analysis techniques used to gather and analyze requirements.

Multiple choice

Which of the following is a common system design technique?

  1. Object-oriented design

  2. Structured design

  3. Agile development

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

Object-oriented design, structured design, and agile development are all common system design techniques used to translate requirements into a technical solution.

Multiple choice

Which of the following is NOT a key element of an effective quality control corrective action plan in fashion?

  1. Identifying the root cause of defects

  2. Implementing corrective actions to eliminate the root cause

  3. Verifying the effectiveness of corrective actions

  4. Documenting the corrective actions and their results
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Verifying the effectiveness of corrective actions is not a key element of an effective quality control corrective action plan in fashion, as it is assumed that the corrective actions will be effective once implemented.

Multiple choice

Which of the following is an example of an agile documentation artifact?

  1. Project charter

  2. Business requirements document

  3. User story

  4. Technical design document
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

User stories are concise descriptions of user needs and requirements, written from the perspective of the end user.

Multiple choice

Which agile documentation artifact is used to capture and prioritize project requirements?

  1. Product backlog

  2. Sprint backlog

  3. User story map

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

The product backlog is a prioritized list of all features and requirements for the product, used to guide development efforts.

Multiple choice

Which agile documentation artifact is used to visually represent the flow of user stories through the development process?

  1. User story map

  2. Sprint backlog

  3. Release plan

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

User story maps are visual representations of the user journey, helping teams understand the relationships between user stories and the overall product vision.

Multiple choice

Which agile documentation artifact is used to track the progress of a sprint and visualize the remaining work?

  1. Burndown chart

  2. Sprint backlog

  3. User story map

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

Burndown charts are graphical representations of the work remaining in a sprint, helping teams monitor progress and identify potential risks.

Multiple choice

Which agile documentation artifact is used to capture and document lessons learned during a retrospective?

  1. Retrospective notes

  2. Sprint backlog

  3. User story map

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

Retrospective notes are used to document key insights, actions, and improvements identified during a retrospective.

Multiple choice

Which agile documentation artifact is used to capture and document the technical architecture of a software system?

  1. Technical design document

  2. User story map

  3. Sprint backlog

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

Technical design documents provide detailed information about the system's architecture, components, and interfaces.

Multiple choice

Which agile documentation artifact is used to capture and document the acceptance criteria for user stories?

  1. Definition of Done

  2. User story map

  3. Sprint backlog

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

The Definition of Done defines the criteria that must be met for a user story to be considered complete.