1) Understanding the problem to be solved, identifying needs, and gathering requirements. a) Analysis b) Sub-System c) Modular Design d) Expected Output 2) Creating a blueprint for how the program will function, including structure diagrams, pseudocode, and flowcharts. a) Algorithm b) Modular Design c) Design d) Flowchart 3) Writing the actual source code to implement the design. a) Coding (Development) b) Incremental Development c) Sub-System d) Structure Diagram 4) Evaluating the program using test data to ensure it works as intended and meets the requirements. a) Testing b) Decomposition c) Coding (Development) d) Pseudocode 5) Removing unnecessary detail to focus on the important aspects of a problem. a) Modular Design b) Problem Identification c) Algorithm d) Abstraction 6) Breaking down a problem into smaller, manageable parts. a) Decomposition b) Requirements Specification c) Rapid Application Development (RAD) d) Modular Design 7) A detailed list of what the software must do, based on the analysis of user needs. a) Requirements Specification b) Algorithm c) Expected Output d) Flowchart 8) Clearly defining what the issue is before attempting to solve it. a) Design b) Testing c) Pseudocode d) Problem Identification 9) A graphical representation showing how a problem is broken down into parts. a) Modular Design b) Structure Diagram c) Problem Identification d) Test Data 10) A diagram that represents the steps in an algorithm using standard symbols. a) Flowchart b) Problem Identification c) Waterfall Model d) Design 11) A readable description of what a computer program or algorithm must do, written in informal language. a) Requirements Specification b) Algorithm c) Analysis d) Pseudocode 12) Testing each version or change of a program during development to catch errors early. a) Requirements Specification b) Incremental Development c) Agile Development d) Iterative Testing 13) Sample inputs used to check if the program produces the correct outputs. a) Rapid Application Development (RAD) b) Sub-System c) Test Data d) Coding (Development) 14) The correct result that should be returned by a program when given test data. a) Requirements Specification b) User Requirements c) Expected Output d) Waterfall Model 15) A set of steps or rules to be followed in calculations or problem-solving operations. a) Algorithm b) Coding (Development) c) Iterative Testing d) Abstraction 16) Statements that describe what the user expects the software to be able to do. a) User Requirements b) Problem Identification c) Iterative Testing d) Test Data 17) A smaller part of a system that performs a specific function and contributes to the larger system. a) Design b) Decomposition c) Sub-System d) User Requirements 18) Breaking down software into modules that can be developed and tested independently. a) Analysis b) Testing c) Modular Design d) Requirements Specification 19) A software development methodology focused on iterative progress and user feedback. a) Decomposition b) Flowchart c) Agile Development d) Expected Output 20) A sequential development process with distinct phases such as analysis, design, coding, and testing. a) Requirements Specification b) Problem Identification c) Waterfall Model d) Rapid Application Development (RAD) 21) A form of software development that emphasizes quick development and iteration with user feedback. a) Algorithm b) Requirements Specification c) Rapid Application Development (RAD) d) Problem Identification 22) Building software in small increments where each builds on the previous. a) Incremental Development b) Iterative Testing c) User Requirements d) Modular Design

Unit 8 Algorithms - T1 Development life cycle - Maze Chase

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?