Question 1 of 50 0.
2 Points
Defective requirements can cause:
A. Project failure;
B. Expensive rework
C. Late delivery
D. All of the above;
Question 2 of 50 0.2 Points
What are business requirements describe?
A. Software product features from the user point of view
B. Software product functions from the user point of view
C. Describe high level purposes and needs that the software product will satisfy
D. Software product capabilities from the user point of view
Question 3 of 50 0.2 Points
Before design, requirements must be:
A. Analyzed;
B. Prioritized;
C. Documented
D. All of the above;
Question 4 of 50 0.2 Points
In theory, most requirements:
A. Focus on what the customer think;
B. Clearly describe testing procedures and data;
C. Are related to business outcomes;
D. Never change.
Question 5 of 50 0.2 Points
Why are Requirements Important?
A. Because if you follow the requirements, the implementation of projects planned
over
B. Because if you follow the requirements at the project delayed
C. Because if you follow the requirements, the project will make full functions
over
D. All of the above.
Question 6 of 50 0.2 Points
A quality requirements 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 7 of 50 0.2 Points
Requirement development process is:
A. Sequential process.
B. Iterative process
C. Skipping process;
D. None of the above.
Question 8 of 50 0.2 Points
During requirements phase, Most customers are:
A. Knowledgeable about requirements process;
B. Understand Software Engineering;
C. Confuse between “Needs” and “Wants”;
D. Familiar with software process
Question 9 of 50 0.2 Points
Where do Requirements come from?
A. Business Requirements – User Requirements – System Requirements – Software
Requirements
B. Project Requirements – User Requirements – System Requirements – Software
Requirements
C. Business Requirements – Manager Requirements – System Requirements – Software
Requirements
D. Business Requirements – User Requirements – Quality Requirements – Software
Requirements
Question 10 of 50 0.2 Points
What are system requirements describe?
A. They are describe of all functional, non-functional requirements that the
systems must do to meet business and user needs
B. They are describe the table that user need to do with the system to accomplish
a business function
C. They are describe high level purposes
D. All Right
Question 11 of 50 0.2 Points
A functional requirements can be:
A. Traced to a module of the software;
B. Defined by a supplier;
C. Organized by customers;
D. Monitored by hardware;
Question 12 of 50 0.2 Points
Before requirement elicitation, software engineer must
A. Focus on project planning;
B. Know who are the stakeholders.
C. Understand managers’ goals and objectives;
D. Estimates the software schedules;
Question 13 of 50 0.2 Points
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 14 of 50 0.2 Points
What are requirements analysis?
A. Describe high level purposes and needs that the software product will satisfy
B. A method of obtaining a precise formal specification from the informal and
often not ambiguous requirements with customers
C. The techniques of deciding which features are appropriate for the product based
on stakeholders’ needs
D. All right
Question 15 of 50 0.2 Points
Which of the following is NOT a reason why an effective systems analyst needs to
know how an organization works?
A. Some analysts take time to specialize in a specific industry
B. Knowing the people who work for a company increases an analyst's effectiveness
C. An organization may require an analyst to make management decisions
D. An analyst with deep understanding in a type of business can solve complex
problems
Question 16 of 50 0.2 Points
Common requirements problems is:
A. Treat it as a firm sequential activities;
B. Forget about hardware requirements
C. Failure to include test data;
D. Mixing requirements with design.
Question 17 of 50 0.2 Points
Requirements problems can cause:
A. Project failure;
B. Programming language issues;
C. Functional test crash;
D. Hard dish failure
Question 18 of 50 0.2 Points
Requirements Engineering comprises:
A. wants analysis – requirements analysis – requirements specification
B. needs analysis – Engineering analysis – requirements specification
C. needs analysis – requirements analysis – systems specification
D. needs analysis – requirements analysis – requirements specification
Question 19 of 50 0.2 Points
When requirements go wrong, what could happen from among the following?
A. The system may cost more than projected
B. The system may be delivered later than promised
C. The system will become unreliable and prone to errors
D. All of the above.
Question 20 of 50 0.2 Points
Requirements priority is based on:
A. What must be implemented first;
B. A random program that perform prioritization score;
C. A business process;
D. None of the above.
Question 21 of 50 0.2 Points
During requirements phase, Software Engineer needs to:
A. Ask for solutions;
B. Collect all data to prepare for testing;
C. Ask for outcomes;
D. Gather all customer’s wishes;
Question 22 of 50 0.2 Points
Requirements 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 23 of 50 0.2 Points
Most Non-functional requirements are created by:
A. Customers;
B. Managers;
C. Software Engineers;
D. Suppliers
Question 24 of 50 0.2 Points
Requirements Management consists of:
A. Requirements Baseline – Requirements Analysis – Requirements Traceability
B. Requirements Baseline – Requirements change Management – Requirements
Traceability
C. Requirements Elicitation – Requirements change Management – Requirements
Traceability
D. Requirements Elicitation – Requirements Specification – Requirements
Traceability
Question 25 of 50 0.2 Points
Who are Developers?
A. Who interact directly or indirectly with the software product
B. Who write the requirements and communication them to the software developers
C. Who design, implement and maintain software products
D. All of the above.
Question 26 of 50 0.2 Points
What documentation is written for business requirements?
A. User Requirements Document
B. Use – case
C. Software Requirements Document
D. Project charter
Question 27 of 50 0.2 Points
Requirements must always be:
A. Verbally acceptable;
B. Firm on software;
C. Documented;
D. None of the above.
Question 28 of 50 0.2 Points
Most software requirements are written by:
A. Customers;
B. Software engineers;
C. Managers;
D. All of the above.
Question 29 of 50 0.2 Points
What documentation is written for user requirements?
A. Vision or Scope of the project
B. Functional specification
C. User requirements Document
D. Software Requirements Document
Question 30 of 50 0.2 Points
The functionality of the system or what the information system will do is called
the _____ of the system.
A. Business need
B. Intangibles
C. Requirements
D. Sponsors
Question 31 of 50 0.2 Points
An elicitation technique was classified by one of your project colleagues on the
basis of its characteristics as follows:
The technique may be classified as a questioning technique with respect to the
direction of activity, as an individual-orientated technique with respect to the
activity partner, as an analytical technique with respect to the nature of the
activity and as a neutral technique with respect to the frame of reference of the
activity.
To which of the following elicitation techniques does the given classification fit?
A. Questionnaire
B. Contextual Inquiry
C. Prototyping
D. Interview
Question 32 of 50 0.2 Points
What are Requirements Engineering?
A. A method of obtaining a precise formal specification from the informal and
often not ambiguous requirements with customers
B. A method of obtaining a precise formal specification from the informal and
often vague requirements with customers
C. A method of obtaining a precise formal specification from the informal and
often clear requirements with customers
D. None of the above.
Question 33 of 50 0.2 Points
Why should Requirements Engineering?
A. reduce errors
B. know schedule
C. understand the needs of customers
D. All of the above.
Question 34 of 50 0.2 Points
Requirements development is:
A. A process of analyzing requirements.
B. A method of obtaining requirements;
C. A technique of gathering what the customer needs;
D. All of the above.
Question 35 of 50 0.2 Points
What documentation is written for software requirements?
A. Project charter
B. Vision or Scope of the project
C. Concept of Operations
D. Software Requirements Specification Document
Question 36 of 50 0.2 Points
Who are Stakeholders?
A. Stakeholders is a person or group that has a interest in the software and not
affect the software requirements
B. Stakeholders is a person or group that has a interest in the software and
influence the software requirements
C. Stakeholders is a person or group that has a regardless in the software and
influence the software requirements
D. All of the above.
Question 37 of 50 0.2 Points
The list of what stakeholders’ need is called:
A. Customer list;
B. User’s requests;
C. Requirements documents
D. Project lists;
Question 38 of 50 0.2 Points
The steps Requirements Development consists of:
A. Requirements Specification - Requirements Elicitation – Requirements Analysis –
Requirements Verification & Validation
B. Requirements Specification - Requirements Analysis - Requirements Elicitation –
Requirements Verification & Validation
C. Requirements Elicitation – Requirements Analysis – Requirements Verification &
Validation -
Requirements Specification
D. Requirements Elicitation – Requirements Analysis – Requirements Specification –
Requirements Verification & Validation
Question 39 of 50 0.2 Points
Who are customers?
A. Who fund the project or acquire a product to satisfy their organization’s
business objectives
B. Who interact directly or indirectly with the software product
C. Who write the requirements and communication them to the software developers
D. All of the above.
Question 40 of 50 0.2 Points
What are business requirements describe?
A. Software product features from the user point of view
B. Software product functions from the user point of view
C. Describe high level purposes and needs that the software product will satisfy
D. Software product capabilities from the user point of view
Question 41 of 50 0.2 Points
Business Requirements Document (BRD) consists of:
A. Vision, Goals, Objectives, System Goals
B. Vision, User requirements, Objectives, System Goals
C. System Requirements, Goals, Objectives, System Goals
D. Vision, Goals, Objectives, Performance System
Question 42 of 50 0.2 Points
The line that marks the inside, outline of the system and that sets off the system
from its environment, best defines
A. delineation mark
B. boundary
C. interface
D. scope
Question 43 of 50 0.2 Points
The strategy for eliciting information regarding the user's requirements is (are)
A. prototyping
B. asking questions
C. obtaining information from the present system
D. All of the above.
Question 44 of 50 0.2 Points
An elicitation technique was classified by one of your project colleagues on the
basis of its characteristics as follows:The technique may be classified as a
questioning technique with respect to the direction of activity, as an individual-
orientated technique with respect to the activity partner, as an analytical
technique with respect to the nature of the activity and as a neutral technique
with respect to the frame of reference of the activity.To which of the following
elicitation techniques does the given classification fit?
A. Questionnaire
B. Contextual Inquiry
C. Prototyping
D. Interview
Question 45 of 50 0.2 Points
Project manager must balance requirements with:
A. A programming languages
B. Project costs and quality;
C. Hardware;
D. Programmers’ skills and knowledge.
Question 46 of 50 0.2 Points
Consider the statement: “When a user enters the wrong password 3 times, the system
should alert the security company.” What kind of a requirement is this?
A. Functional
B. Non-Functional
C. Known Requirement
D. None of the mentioned
Question 47 of 50 0.2 Points
The willingness and ability of management, employees, customers, suppliers and so-
forth of an organization to operate, use and support a proposed system is known as
A. Cost/benefit analysis
B. Technological feasibility
C. Operational feasibility
D. Specification feasibility.
Question 48 of 50 0.2 Points
When requirements go wrong, what could happen from among the following?
A. The system may cost more than projected
B. The system may be delivered later than promised
C. The system will become unreliable and prone to errors
D. The system may not meet user requirements
E. All of the above.
Question 49 of 50 0.2 Points
Requirements development is:
A. A process of analyzing requirements.
B. A method of obtaining requirements;
C. A technique of gathering what the customer needs;
D. All of the above.
Question 50 of 50 0.2 Points
Requirements 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;
