ÔN TẬP 2023

Question 1 of 52

Which one of the following main events are defined by the Scrum Framework?
A) Sprint Planning Meeting
B) Sprint Retrospective Meeting
C) Sprint Review Meeting
D) Mid-Sprint Status Review Meeting
E) Daily Scrum Meeting.
Correct Answer
A. A, B, C, D, E
B. A, B, C, D
C. A, C, D, E
D. A, B, C, E

Question 2 of 52
Which concept is NOT defined in the Scrum Framework?
A. Scrum Master
B. Project Manager
C. Scrum Product Owner
D. Daily Scrum

Question 3 of 52
Requirements are often changed by:
A. Managers;
B. Customers;
C. Programmers;
D. Software Engineers.

Question 4 of 52
The quality of the software product is depending on:
A. The salary of software engineers;
B. The technology of hardware;
C. The skills of managers;
D. The quality of software process;

Question 5 of 52
When the customer changes requirements, problems always happen in:
A. The Spiral model;
B. The Waterfall model;
C. The Prototype mode;
D. The incremental model.

Question 6 of 52

Which one of the following main roles are defined by Scrum Framework?

A) Scrum Tester

B) The Scrum Team

C) Scrum Manager
D) Scrum Master

E) Scrum Product Owner.

Correct Answer:

A. A, B, C, D, E
B. B, C, D, E
C. B, D, E
D. A, B, D, E

Question 7 of 52
What is the primary goal of "Verification and Validation (V & V)" in the software
development process?
A. To develop the system's specification.
B. To review and check the system's code.
C. To demonstrate that the system conforms to its specification and meets
customer requirements.
D. To design the system's architecture.

Question 8 of 52
The following describes software project management key processes:
A. Requirements, design, code, and test;
B. Design, construct, test and maintain;
C. Manage, build, and execute;
D. Plan, monitor and control;
Question 9 of 52
Which activity is commonly used as part of the "Verification and Validation (V & V)"
process?
A. Requirements gathering.
B. System architecture design.
C. Reviewing and checking the code.
D. Writing the system's specification.

Question 10 of 52
Risk management is part of
A. Project management;
B. Product management;
C. Process management;
D. Quality Management.

Question 11 of 52
Risk monitoring is
A. A Process to track risks and options to make sure it is under control;
B. A review conducted by the project manager during the planning phase;
C. A status of risks documented in a project plan;
D. A monitor device to check on risks;

Question 12 of 52
Which of the following is the requirements development sequence?
A. Elicitation, Validation, Specification and Analysis;
B. Specification, Elicitation, Validation and Analysis;
C. Elicitation, Analysis, Specification and Validation;
D. Validation, Specification, Analysis and Elicitation;

Question 13 of 52
A quality requirement depends on:
A. The quality of the requirements process;
B. The skills of customers;
C. The knowledge of users;
D. The quality of software tools.

Question 14 of 52

Question 15 of 52
What is the primary focus of "Interface design" in the software development process?
A. Identifying the system's overall structure and principal components.
B. Designing the interfaces between system components.
C. Designing each system component's internal operation.
D. Designing the system's data structures and database representation.

Question 16 of 52
What is the primary focus of "Architectural design" in the software development
process?
A. Identifying the system's overall structure and principal components.
B. Designing the interfaces between system components.
C. Designing each system component's internal operation.
D. Designing the system's data structures and database representation.

Question 17 of 52
What characterizes "plan-driven processes" in software development?
A. They involve incremental planning.
B. All process activities are planned in advance.
C. They are highly adaptable to changing customer requirements.
D. Progress is not measured against any plan.

Question 18 of 52
The large software project is difficult to manage because:
A. It requires large hardware
B. Team size and communication
C. Special tools and methods
D. Too many customer involvements.

Question 19 of 52
Who typically owns the specification of what Generic Products should do?
A. The customer
B. The software developer
C. The traffic monitoring system
D. Air traffic controllers

Question 20 of 52
Requirement’s validation is:
A. A technique to find requirements errors after design;
B. A method for testing requirements by software tools;
C. The process of testing requirements before coding.
D. A process to ensure requirements meet customer’s needs.

Question 21 of 52
When a test failed, Tester must:
A. Document the results and prepare corrective actions;
B. Report to the manager on the software engineer responsible for the code;
C. Blame the software engineer for the failure
D. Run the test again and hope it will not fail again.

Question 22 of 52
To succeed in the globalization age, the business must:
A. Apply information technology to business
B. Use personal computers
C. Use mainframe computer systems
D. Buy more hardware

Question 23 of 52
The large software project is difficult to manage because:
A. It requires large hardware
B. Team size and communication
C. Special tools and methods
D. Too many customer involvements.
Question 24 of 52
Requirements are often changed by:
A. Managers;
B. Customers;
C. Programmers;
D. Software Engineers.

Question 25 of 52
The quality of the software product is depending on:
A. The salary of software engineers;
B. The technology of hardware;
C. The skills of managers;
D. The quality of software process;

Question 26 of 52
Software products must be tested because
A. They may contain defects.
B. They may have the virus;
C. It is required by the industry;
D. It will keep tester to have jobs

Question 27 of 52
To succeed in the globalization age, the business must:
A. Apply information technology to business
B. Use personal computers
C. Use mainframe computer systems
D. Buy more hardware

Question 28 of 52
The large software project is difficult to manage because:
A. It requires large hardware
B. Team size and communication
C. Special tools and methods
D. Too many customer involvements.

Question 29 of 52
The best software organization:
A. Purchases a lot of hardware to improve software performance;
B. Move into on-line business to expand its market;
C. Focus on hiring the best programmers to do more coding;
D. Controls their project to meet defined quality goals.

Question 30 of 52
Risk management is part of 2D. Quality Management.
A. Project management;
B. Product management;
C. Process management;

Question 31 of 52
Risk monitoring is
A. A Process to track risks and options to make sure it is under control;
B. A review conducted by the project manager during the planning phase;
C. A status of risks documented in a project plan;
D. A monitor device to check on risks;

Question 32 of 52
The following describes software project management key processes:
A. Requirements, design, code, and test;
B. Design, construct, test and maintain;
C. Manage, build, and execute;
D. Plan, monitor and control;

Question 33 of 52
Project monitoring must focus on:
A. Risks;
B. Hardware;
C. Network connection;
D. Programming language

Question 34 of 52
In Scrum, where are the customer requirements stored?
A. In the Product Backlog
B. In the Sprint Backlog
C. In a database
D. In a Scrum Product Requirement Specification
Question 35 of 52
Beside technical skills, most software companies need people:
A. That have experiences;
B. Can fix hardwares, if needed;
C. Willing to work for less money;
D. Have degrees in Economic and Finance.

Question 36 of 52
Software projects are difficult to manage because:
A. Software size and complexity;
B. Programmers do not like to be managed;
C. It involves too many complex technologies;
D. Most managers do not understand software.

Question 37 of 52
UML is stands for....
A. United Modelling Language
B. United Modifier Language
C. Unified Modifier Language
D. Unified Modelling Language

Question 38 of 52
In software testing, V & V is
A. The testing company
B. Verification and Validation
C. The level of testing
D. The first step in the testing technique

Question 39 of 52
SDLC stands for
A. Software Development Life Cycle
B. System Development Life cycle
C. Software Design Life Cycle
D. System Design Life Cycle

Question 40 of 52
The following is NOT a process element:
A. a. Unix operating system
B. b. Coding
C. c. Verification
D. d. Modeling

Part 2 of 2 - PART 2 - SHORT ANSWER

Question 41 of 52
SDLC stands for……………………………………………………………………….
,
SDLC stands for Software Development Life Cycle (SDLC)
Question 42 of 52
What are SDLC models available?

,
Several Software Development Life Cycle (SDLC) models are available, and each
model follows a specific process to ensure the successful development of software.
Some common SDLC models include:
Waterfall Model
Iterative Model
Incremental Model
Agile Model
Spiral Model
V-Model (Verification and Validation Model)
Scrum
RAD (Rapid Application Development)
Big Bang Model

Question 43 of 52
The goal of the ……………….phase is to translate the design of the system into code
in a given programming language.
,
Implementation

Question 44 of 52
……………………………………………………………………….requirements are
constraints on the services or functions offered by the system such as timing
constraints, constraints on the development process, standards, etc.
,
Non-functional Requirements
Question 45 of 52
Coding phase is followed by
………………………………………………………………………..
,
Testing phase

Question 46 of 52
………………………………………………………………………. is a list of ‘to do’
items which the Scrum team must tackle. They may be feature definitions for the
software, software requirements, user stories or descriptions of supplementary tasks
that are needed, such as architecture definition or user documentation.
,
A Product Backlog

Question 47 of 52
What are the main roles defined by the Scrum Framework? What are the fundamental
activities of a software process? What are universal management activities in project
management?
,
Main Roles Defined by the Scrum Framework:

Scrum Master:Facilitates Scrum processes, removes impediments, and supports

team collaboration.
Product Owner: Maximizes product value by managing the product backlog and
making priority decisions.
Development Team: Delivers a potentially shippable product increment during
each Sprint.
Fundamental Activities of a Software Process:
Requirements and Analysis: Understand and document the needs and expectations
of stakeholders.
Design: Create a blueprint or plan for the software structure and functionality.
Coding/Implementation: Write the actual code based on design specifications.
Testing: Evaluate the software to identify and fix defects, ensuring it meets
requirements.
Deployment: Release the software for use in a production environment.
Maintenance: Make updates, fix bugs, and address evolving needs after deployment.
Universal Management Activities in Project Management:
Planning: Develop a roadmap for the project, including scope, schedule, resources,
and risks.
Organizing: Structure the team, define roles, and establish communication channels.
Leading/Motivating: Provide direction, guidance, and support to the team to achieve
project goals.
Controlling/Monitoring: Track progress, identify deviations, and take corrective
actions.
Communicating: Ensure clear and effective communication among team members
and stakeholders.
Closing: Complete and close out the project, including documentation and post-
project evaluation.

OR
Initiating
Planing
Executing
Monitoring &Controling
CLOSE

Question 48 of 52
What are the activities of design process?
,
The design process in software development involves creating a blueprint or plan for
how the software will be structured and function. The activities in the design process
may vary based on the chosen design methodology, but here are common activities
associated with the software design phase:
Architectural Design
High-Level Design
Detailed Design
Database Design
User Interface (UI) Design
Component-Level Design
Algorithm Design
Interface Design
Error Handling and Exception Design
Security Design
Performance Design
Documentation
Review and Validation
Prototyping
Component selection and design

Question 49 of 52
What are the software project management activities?
,
Project planning
Risk management
People management
Reporting
Proposal writing
Question 50 of 52
What factors influence software project management?
,
Several factors influence software project management, and understanding these
factors is crucial for successful project planning and execution. Some key factors
include:
Factors influencing project management
• Company size
• Software customers
• Software size
• Software type
• Organizational culture
• Software development processes
• These factors mean that project managers in different
organizations may work in quite different ways.

Question 51 of 52
*What are the stages of testing?
,
Typically, a commercial software system has to go through three stages of testing:
1. Development testing, where the system is tested during development to discover
bugs and defects. System designers and programmers are likely to be involved in the
testing process.
2. Release testing, where a separate testing team tests a complete version of the
system before it is released to users. The aim of release testing is to check that the
system meets the requirements of the system stakeholders.
3. User testing, where users or potential users of a system test thesy stem in their own
environment. For software products, the “user” may be an internal market-ing group
that decides if the software can be marketed, released andsold.Acceptance testing is
one type of user testing where the customerformally testsa system to decide if it
should be accepted from the system supplier or if further development is required.

Question 52 of 52
*What are the type of software risk?
,
Software risks are potential problems or challenges that may impact the success
of a software project. These risks can manifest in various forms and stages of the
software development life cycle. Here are common types of software risks:
Risk Identification
Risk Analysis
Risk Planning
Risk Monitoring
_Risk management