Requirment engineering final

exam
1. Requirements must be:
A. Abstract and broad
B. Clear, concise, and consistent (rõ ràng, ngán gọn, nhất quán)
C. Vague and incomplete
D. Costly and unrealistic

2. What is a requirement defect? (lỗi yêu cầu)

A. Correct requirements
B. Missing or conflicting requirements (Yêu cầu bị thiếu hoặc mâu thuẩn)
C. Verified (xác minh) system requirements
D. None of the above

3. What is a product vision statement (tuyên bố)

A. detailed technical document for developers

B. concise statement (Tuyên bố ngắn gọn) describing the purpose of the product
C. user manual for the software
D. contract between stakeholders
4. Which of the following is NOT a type of stakeholder in software projects?

A. Customers

B. Developers

C. Animals

D. Analysts

5. What is the goal of prototyping in requirements engineering?

A. Finalize the software design

B. Illustrate (minh họa) system functionality to stakeholders

C. Replace the final system

D. Reduce development costs

6. What document helps communicate business requirements?
A. Vision and Scope Document (tầm nhìn và phạm vi)
B. Use Case Specification
C. Database Schema
D. Software Manual
7. Requirements models are created to:
A. Validate the quality of code
B. Understand stakeholders' needs better
C. Ignore project constraints
D. Reduce system functionality

8. Who manages project budgets (ngân sách) and schedules?

A. Requirements Engineer
B. Project Manager
C. System Architect
D. Developer
9. What is the primary focus (trọng tâm chính) of requirements engineering?

A. Coding and testing

B. Gathering (thu thập) and documenting(ghi chép) requirements
C. Marketing strategies
D. Budgeting projects
10. What are functional (chức năng) requirements?
A. General goals of the business
B. Features (đặc trưng) that describe what a system must do (bắt buộc phải làm)
C. Aesthetic aspects of software design
D. Financial constraints
11. What does a context diagram represent (đại diện)

A. The entire software codebase

B. External (luồng ngoài lệ) entities interacting with the system

C. Financial budgets
 D. Employee schedules

12. What does a sequence diagram show: (câu này có 2 lần xuất hiện)

A. Interaction (tương tác) between objects over time

B. Data flow between systems
C. Business rules
D. Hardware dependencies
13. Which is an elicitation (thu thập yêu cầu) technique (kĩ thuật)?
A. Joint Application Development (JAD)
B. Debugging
C. Coding guidelines
D. Deployment automation
14. Which type of error occurs when important information is not stated (không được yêu trình bày)
in requirements?
A. Errors of Omission (lỗi thiếu sót)
B. Errors of Commission
C. Errors of Clarity
D. Errors of Understanding
15. Who is primarily responsible (chịu trách nhiệm chính) for gathering requirements?
A. Project Manager
B. Requirements Engineer
C. Developer
D. Stakeholders
16. What happens if requirements are not documented (ghi chép) properly (đúng
cách)?

A. Software developers can infer the requirements accurately

B. The project scope becomes clearer

C. Misunderstandings (hiểu lầm) between users and developers increase

D. Project costs decrease

17. What is the primary purpose of requirements engineering?
A. Writing detailed software code
B. Ensuring (đảm bảo) software meets (đáp ứng) stakeholders' needs
C. Testing software for errors
D. Reducing project costs
18. Which of the following is NOT an activity in requirements development?
A. Requirement’s elicitation
B. Requirement’s analysis
C. Requirement’s coding
D. Requirement’s verification
19. What is the most common (phổ biến) cause of software project failures?
A. Poor coding practices
B. Poorly (không rõ ráng) defined requirements
C. Insufficient testing
D. Lack of skilled developers
20. The relationship that adds optional functionality (bổ sung chức năng) in a use case is called:
A. Include

B. Extend

C. Generalization

D. Aggregation

21. What is a common result of requirements defects?

A. Early project completion z

B. Reduced project costs

C. Dissatisfied (không hài lòng) customers

D. Enhanced software quality

22. What is the purpose of a context diagram?

A. Show detailed workflows
B. Define the system boundary
 C. Identify system components
D. Test system performance
23. What is a critical stakeholder role in software projects?
A. Budget allocator
B. Passive observer
C. Requirement verifier (xác minh)
D. Risk mitigator
24. Which relationship is used to include optional behavior in a use case?
A. <<include>>
B. <<extend>>
C. Generalization
D. <<optional>>
25. Which technique (kĩ thuật) is used for discovering requirements?
A. Coding
B. Debugging
C. Interviewing
D. Deployment

26. Why do stakeholders need a shared understanding?

A. To prioritize coding tasks
B. To align (tổng hợp, thống nhất) expectations (kì vọng)
C. To reduce the number of meetings
D. To avoid testing
27. What is a common reason for project delays?
A. Lack of resources
B. Poor requirements definition (định dạng, định nghĩa)
C. Skilled teams
D. Short development cycles

28. What is the main advantage (lợi thế) of interviews in eliciting (đưa ra) requirements?
A. Easy to automate

B. Captures (nắm bắt) stakeholders' detailed knowledge

C. Requires minimal effort

D. Reduces conflicts
29. What is a stakeholder in the context (bối cảnh) of software development?
A. Only the customers using the software

B. Any (bất kì) individual or group influencing (ảnh hưởng) or impacted by the software

C. Only the software engineers building the software

D. Only the end-users of the software

30. What is the cost of fixing (chi phí sửa lỗi) a defect after release (giải phóng, phát hành)
compared to during requirements?
A. 10-50 times more
B. 100-200 times more
C. Equal cost
D. 2-3 times more
31. Why is defining (định nghĩa) a product scope (phạm vi sản phẩm) important?
A. To include all possible features
B. To ensure (đảm bảo) stakeholders understand project limitations (giới hạn dự án)
C. To reduce stakeholder involvement
D. To speed up development
32. What role supports the system's design constraints (các ràng buộc về thiết kế)?
A. Tester
B. Architect (kỹ sư)
C. Stakeholder
D. Project Sponsor
33. Which of the following is NOT a requirements elicitation technique (kĩ thuật thu thập yêu cầu)?
A. Brainstorming
B. Use Case Analysis
C. System Deployment
D. Prototyping
34. Which of the following is NOT typically included in a product vision?
A. Business goals
B. Target customers
 C. Development timeline
D. Competitive differentiation

35. Requirements are important because:

A. They increase the project cost B.
b. They serve as a communication channel (là kênh giao tiếp)
C. They ensure the project is delayed
D. They reduce customer satisfaction
36. Who prioritizes (ưu tiên) requirements based on business needs?
A. Developer
B. Requirements Engineer
C. Stakeholders
D. Project Manager
37. Which role prioritizes requirements in a project?
A. Architect
B. Project Manager
C. Tester
D. Stakeholder
38. Which is a common reason for software project failures?
A. Clear communication
B. Effective teamwork
C. Defective requirements
D. Good management
39. Requirements are descriptions (mô tả) of:
A. Project deadlines
B. Necessary and sufficient properties of a product or service
C. Marketing strategies
D. Developer tools
40. Which of the following is NOT a reason for poor requirements engineering?
A. Misunderstanding of customer needs
B. Early involvement (sự tham gia) of stakeholders
C. Lack of training in writing requirements
 D. Conflicting requirements

41. Which model illustrates (minh họa) data relationships (mối quan hệ dữ liệu)?
A. State Diagram
B. Use Case Diagram
C. Entity-Relationship Diagram (ERD)
D. Sequence Diagram
42. What is the first step (bước đầu tiên) in requirements engineering (kĩ thuật)?
A. Design implementation
B. Design implementation (xác định)
C. Coding
D. Testing
43. What are the key elements (yếu tố chính) of use cases?
A. Actors, goals, interactions
B. Coding standards
C. Testing scenarios
D. Data flow diagrams
44. The primary goal of business requirements (yêu cầu kinh doanh) is to:
A. Enhance technical knowledge
B. Define project coding standards
C. Describe business goals and needs
D. Set employee expectations
45. What is a use case
A. A sequence of system steps
B. A description of system behavior (mô tả hành vi)
C. A detailed test plan
D. A user interface prototype
46. Which relationship shows shared functionality (chức năng)?
A. <<include>>
B. <<extend>>
C. Generalization
 D. <<inherit>>

47. A prototype in software development helps to:

A. Minimize user feedback
B. Demonstrate (minh họa) system capabilities (khả năng)
C. Skip requirements gathering
D. Eliminate stakeholders' involvement
48. What is the primary task of a Requirements Engineer?
A. Write code
B. Gather and document requirements
C. Build prototypes
D. Manage project teams
49. What does a use case diagram illustrate?
A. Financial breakdown
B. Stakeholders' technical knowledge
C. Interaction between actors and the system
D. Quality assurance policies
SHORT ANSWER
1. What is the purpose of a context diagram in requirements analysis?
Defines system boundaries and external interactions.
2. What is the difference between "include" and "extend" relationships in use case diagrams?
Include: Mandatory behavior reused by multiple use cases.
Extend: Optional behavior triggered under specific conditions.
3. Why do poorly written requirements often lead to project delays?
They cause misunderstandings, rework, and scope changes.
4. List three elements of a product vision statement
Target audience, Key needs, Unique value proposition
Identify the Functional and Non-Functional Requirements in sentences 5 and 6. For each Non-
Functional Requirement, specify the category (eg: Security, Usability...) it belongs to
5. The system shall allow users to log in using a valid username and password. The system
shall provide responses to user actions within 2 seconds.
Functional: log in using username and password
Non-Functional: responses to user actions within 2 seconds (Security)
6. The application must support at least 100 simultaneous users without performance
degradation and generate monthly financial reports in PDF format that can be
downloaded by administrators.
Functional: generate monthly financial reports
Non-Functional: support at least 100 simultaneous users (Usability)
7. Describe "errors of omission" and provide an example.
Errors of omission: Missing necessary information in requirements or design.
Example: Omitting a password reset feature in a user authentication system.
8. What are the key objectives of requirements engineering?
The goal of requirements engineering is to ensure the software meets stakeholder
needs.
9. Why is it important to identify stakeholders in a software project?
To understand needs, set priorities, and ensure project success.
10. What is the difference between a vision and a scope document?
A vision document outlines overall goals and objectives, while a scope document
defines specific boundaries and deliverables.
11. List two challenges of using questionnaires for requirements gathering.
Limited depth of responses, Limited control.
12. Explain why brainstorming is useful in requirements elicitation.
Encourages creativity, generates diverse ideas, and uncovers hidden requirements.
13. What skills are essential for requirements engineer?
Analytical skills
Communication skills
Technical understanding
Stakeholder management
 Attention to detail
14. Why is early stakeholder engagement critical in requirements engineering?
Ensures alignment, Reduces risks, Improves quality, Saves time and cost, Builds trust
15. What is an error of omission?
An error of omission is failing to include essential information, actions, or
requirements
16. List name 3 requirements elicitation techniques?
Interviews
Workshops
Surveys/Questionnaires
17. What is included in product scope?
Core functions
Technical requirements
Design elements
Compliance requirements
Usage context
Exclusions
18. Who resolves requirement conflicts?
Requirement conflicts are resolved by the project manager or a designated
requirements manager, often involving stakeholders and the development team.