AAQ Computing: Application Development (F160) - LO4.3

What is the main benefit of abstraction in software design?

• It hides unnecessary complexity and highlights key elements.
• It adds technical jargon to designs.
• It encrypts user data.
• It ensures faster compilation.

Answer explanation

Abstraction removes details to focus on what matters.

When is pattern recognition particularly useful?

• When writing legal documents.
• When identifying similarities between different problems.
• When setting up hardware.
• When measuring performance.

Answer explanation

Pattern recognition helps reuse solutions and speed up development.

Which method breaks a system into testable components?

• Modularisation.
• Abstraction.
• Parsing.
• Compression.

Answer explanation

Modularisation helps manage, test, and build systems efficiently.

What is the first step in bottom-up design?

• Define the full system.
• Create mock-up diagrams.
• Write the final report.
• Build smaller functional components.

Answer explanation

Bottom-up starts with building small parts that integrate into the whole.

What does parsing requirements involve?

• Breaking down user needs into structured specifications.
• Collecting financial data.
• Ignoring edge cases.
• Building flowcharts.

Answer explanation

Parsing structures raw input into something developers can use.

What is a possible disadvantage of abstraction?

• It slows development.
• It can remove important technical details.
• It increases errors.
• It uses excessive memory.

Answer explanation

Excess abstraction may hide critical implementation info.

When would pattern recognition be inappropriate?

• When dealing with unique problems.
• When refactoring code.
• When designing interfaces.
• When using Agile tools.

Answer explanation

Unique problems may not benefit from pattern-based solutions.

What is one feature of top-down design?

• Starts with a broad overview and refines it.
• Focuses on testing first.
• Requires no planning.
• Begins with module coding.

Answer explanation

Top-down begins with an overview and breaks it into parts.

How does bottom-up modularisation aid software reuse?

• It rewrites existing components.
• It ignores similarities.
• It forces code duplication.
• It builds reusable components that integrate easily.

Answer explanation

Bottom-up is ideal for assembling systems from tested, reusable parts.

What is a risk of depending too much on pattern recognition?

• Patterns may not suit the new problem.
• It increases testing.
• It encourages originality.
• It limits user feedback.

Answer explanation

Inappropriate reuse can introduce flaws in new solutions.