Q1) 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.
Q2) 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.
Q3) 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.
Q4) Requirement development process is:
A) Sequential process.
B) Iterative process.
C) Skipping process.
D) None of the above.
Q5) Before design, requirements must be:
A) Analyzed
B) Prioritized
C) Documented
D) All of the above.
Q6) The list of what stakeholders' need is called:
A) Customer list
B) User's requests
C) Requirements documents
D) Project lists
Q7) Most software requirements are written by:
A) Customers
B) Software engineers
C) Managers
D) All of the above.
Q8) Defective requirements can cause:
A) Project failure
B) Expensive rework
C) Late delivery
D) All of the above.
Q9) 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.
Q10) 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
Q11) 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.
Q12) 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.
Q13) Most Non-functional requirements are created by:
A) Customers
B) Managers
C) Software Engineers
D) Suppliers
Q14) Most 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.
Q15) Project manager must balance requirements with:
A) A programming languages
B) Project costs and quality
C) Hardware
D) Programmers' skills and knowledge
Q16) Common requirements problems is:
A) Treat it as a firm sequential activity.
B) Forget about hardware requirements.
C) Failure to include test data.
D) Mixing requirements with design.
Q17) Requirements must always be:
A) Verbally acceptable
B) Firm on software
C) Documented
D) None of the above.
Q18) 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.
Q19) 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.
Q20) Requirements problems can cause:
A) Project failure
B) Programming language issues
C) Functional test crash
D) Hard dish failure
Q21) 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.
Q22) 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.
Q23) Why should Requirements Engineering?
A) Reduce errors
B) Know schedule
C) Understand the needs of customers
D) All of the above.
Q24) _____ is the process of examining the technical, economic, and
organizational pros and cons of developing a new system.
A) Committee approval
B) Feasibility analysis
C) Functionality determination
D) Risk analysis
E) System request
Q25) 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
E) Tangibles
Q27) 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.
E) An analyst involved in designing databases.
Q28) According to project conditions different information is maintained
within a stakeholder list. Which of the following information items are not
relevant for every project and must not therefore be documented in every
project?
A) Field and depth of knowledge
B) Time and location availability
C) Public relevance
D) Goals and interests in relation to the project
Q29) 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
Q30) In order to collect basic factors for a system to be developed, you would
like to apply perspective based reading. Which two types of document are
most suitable for this?
A) Specification of the legacy system
B) Strategy paper for the system to be developed
C) User handbook of the legacy system
D) Advertising brochure for the system to be develop
E) A and C are the correct answers.
F) B and C are the correct answers
Q31) 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
Q32) Who are Stakeholders?
A) Stakeholders is a person or group that has an interest in the software and not
affect the software requirements.
B) Stakeholders is a person or group that has an 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.
Q33) Who are customers of the software product?
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.
Q34) Who are Software 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.
Q35) 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.
Q36) 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.
Q37) 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.
Q38) What documentation is written for business requirements?
A) User Requirements Document
B) Use-case
C) Software Requirements Document
D) Project charter
39) 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
Q40) What documentation is written for software requirements?
A) Project charter
B) Vision or Scope of the project
C) Concept of Operations
D) Software Requirements Document