Lesson 4.13.1.1
4.13.1.1 Analysis Quiz: AQA Computer Science, Unit 13
20 questions
In partnership with Revision Ninja
Lesson 4.13.1.1, Analysis: 20 multiple choice questions for the AQA Computer Science (7517), Unit 13: Systematic approach to problem solving, written with Revision Ninja.
Host it live on the board and students join with a game code on their own devices, or revise alone with Free Play. The answers are revealed in the game.
The 20 questions
-
Which must happen before a problem can be solved by a computer system?
- The end user must test the interface before any design work takes place at all.
- The hardware must be bought so that the size of the problem can be measured accurately.
- The code must be written first, so that the problem can be defined afterwards from the results.
- The problem must be defined, the system's requirements established and a data model created.
-
How must the requirements of a system be established?
- By choosing the fastest programming language that is available to the team.
- By interaction with the intended users of the system.
- By running automated tests on a finished version of the program after release.
- By reading the source code of a similar system written in a previous year.
-
What may the process of clarifying requirements involve?
- Prototyping or an agile approach.
- Writing the final program code before any users have been consulted at all.
- Removing from the list any requirement that the users find difficult to explain clearly.
- A single long meeting with no feedback from the users at any stage.
-
What is a data model in the analysis stage?
- A list of the programmers who will write the code for each data structure.
- A description of the data the system must store and how the data items relate to each other.
- A diagram of the hardware on which the data will be stored by the system.
- A set of tests that checks the data entered by users when the program is run, which replaces the need for any data model at all.
-
Why is abstraction used during analysis?
- To make the program run faster by removing every variable from memory.
- To model aspects of the external world in a program by keeping only the details that matter.
- To give each program a unique name that cannot be copied by other people.
- To hide the source code so that users are not able to read the program at all, which is the main purpose of abstraction in a program.
-
Which is a benefit of establishing requirements with the intended users?
- It removes the need for any testing in the implementation stage of the project.
- It reduces the chance of building a system that does not meet the users' real needs.
- It guarantees that the finished system will cost less than any alternative solution.
- It means that users never need to be consulted again after the system has been delivered.
-
What is the main purpose of the analysis stage?
- To decide the colour scheme of the user interface for the system being built.
- To evaluate the finished system against the original budget only at the end.
- To write the code for the first working version of the program in the project.
- To define the problem, establish requirements and create a data model before a solution is designed.
-
A school wants a homework system. Which activity belongs to the analysis stage?
- Testing the system with erroneous data to see how it reacts to bad input.
- Interviewing teachers and students to find out what the system must do.
- Choosing the colours and fonts that are used on the homework screen layout.
- Writing the database query that displays homework due dates on the screen.
-
A student is asked to analyse a shop's stock system. Which is the best first step?
- Buy the server hardware that will store the stock records for the shop.
- Write the stock-checking algorithm in full before any discussion with the staff.
- Identify the users and the information they need from the system.
- Choose the programming language that the shop's staff already know well.
-
A prototype is shown to users for comments. Which stage does this support?
- Evaluation, by measuring the performance of the finished system in live use.
- Testing, by checking the final program against its specification after coding and before the program is released to the customer.
- Implementation, by writing the code for the production version of the system.
- Analysis, by clarifying the requirements with the people who will use the system.
-
Which entities should a data model for a library include?
- Program name, compiler version and total number of lines in the source code.
- Server name, IP address and router model used in the building network.
- Book, Member and Loan, each with the attributes it needs.
- Screen colour, font size and button shape for each part of the interface.
-
Which is most likely to be a requirement identified during analysis?
- The system must record each loan with a due date.
- The screen must be built using exactly two colours for the whole interface.
- The code must use a recursive function for every search the system carries out.
- The program must be compiled on one specific Linux computer in the server room.
-
A user says the system is too slow. What does this most suggest about analysis?
- The data model has too many entities for a small system to handle.
- The user has been given too much training on how to use the system.
- The program has been compiled using the wrong compiler for the platform.
- A requirement about response time was not clearly established.
-
Which deliverable from analysis would a designer need next?
- A user manual written in full for the final release of the system.
- A clear list of requirements and a data model.
- A test report showing that every test has passed without exception.
- A finished program with no remaining errors in any of its modules.
-
What is an agile approach to analysis?
- Asking only the programmers what the users need and ignoring the users themselves.
- Writing all the requirements once at the start and never changing them afterwards.
- Gathering requirements in short cycles with users, refining the requirements after each cycle.
- Testing the finished program before any requirement has been gathered from anyone.
-
Why should a data model be created during analysis?
- So that the data the system must store is identified before the solution is designed.
- So that the hardware can be bought before the data the system needs is known.
- So that the user interface can be built without consulting the users at all.
- So that testing can be skipped because the data is already assumed to be correct.
-
Evaluate: why is the analysis stage important to a software project?
- Errors in requirements are expensive to correct later, so an accurate understanding of the problem prevents wasted design and coding.
- Analysis is only needed for very small projects, because large projects are always designed first.
- Analysis replaces testing, because the requirements are assumed to be correct from the start.
- Analysis is carried out after evaluation, so it does not influence the design of the system.
-
A team builds a prototype, but users keep changing their minds. What is the best response?
- Ignore the users and build the system to the first set of requirements only.
- Refuse all further changes so that the project is finished on time and on budget.
- Accept iterative change, refining the requirements and the prototype with the users in further cycles.
- Stop the analysis and start implementation so that the users see working code sooner.
-
Which statement best describes the link between analysis and the data model?
- The data model replaces the requirements, so the requirements are no longer needed.
- The data model is a list of user interface controls rather than a description of data.
- The data model is created after implementation and is used only for testing the program.
- The data model captures the entities and relationships identified during analysis.
-
A system must serve users with different needs. What is the best analytical approach?
- Identify the different user groups and their requirements, then model the data and functions each group needs.
- Choose one user group arbitrarily and ignore all the others in the design of the system.
- Merge all users into one generic user with no particular needs or preferences at all.
- Build the system for the most powerful computer and let the users adapt to it.
Related quizzes
- Design Quiz · 4.13.1.2 · 20 questions
- Implementation Quiz · 4.13.1.3 · 20 questions
- Testing Quiz · 4.13.1.4 · 20 questions
- Evaluation Quiz · 4.13.1.5 · 20 questions
- Data types Quiz · 4.1.1.1 · 20 questions
- Entity relationship modelling Quiz · 4.10.1.1 · 20 questions
- Big Data Quiz · 4.11.1.1 · 20 questions
- Function types and first-class objects Quiz · 4.12.1.1 · 20 questions
- Data structures and abstract data types Quiz · 4.2.1.1 · 20 questions
- Breadth-first and depth-first search Quiz · 4.3.1.1 · 20 questions