SWR302

E

A listed acceptance criteria to fulfil certain requirements of a user and normally written from the perspective of an end~user. This is a A. product backlog B. task C. requirement D. release E. user story F. time box

F

Which are the processes in requirements engineering? A. Elicitation B. Specification C. Analysis D. Validation E. Requirements management F. All of the mentioned

A

(15438) To depict the complex logic, which representation technique should be used? A. Decision tree B. Context diagram C. Swimlane diagram D. State-transition diagram E. Data flow diagram F. Data dictionary

D

A concept of operations document (ConOps) should not be written A. In the user's language using the user's format B. Mostly in narrative prose C. With visual forms D. Primarily in the developers technical language

D

A key tool for software designer, developer and their test team is to cany out their respective tasks is defined by: A. Technical documentation B. User document C. Software design documentation D. Requirement documentation

C

A throwaway prototype is most appropriate when: A. Users need to judge whether the requirements will enable the necessary business processes B. Have difficulty envisioning the system from the requirements alone C. all of the mentioned D. the team faces uncertainty. ambiguity. incompleteness. or vagueness in the requirements E. The gaps between customers and developers in the requirements

B

According to the SWEBOK Guide, what are the four major activities of the requirements engineering process? A. Identification, specification, construction, and testing B. Elicitation, analysis, specification, and validation C. Analysis, planning, construction, and verification D. Elicitation, planning, construction, and testing

D

As requirements are elicited, what source is most likely to impose previously unidentified user processes? A. Stakeholders B. The operational environment C. Application domain specialists D. The organizational environment

B

In the IEEE Std 1362 Concept of Operations (ConOps) Document, which of the following is fundamentally not included in the document? A. Current system or situation B. Proposed design method of system C. Justification for the nature of the change D. Operational scenarios

B

Classifying users should not base on: A. The tasks user perform during their business operations B. The knowledge user have C. User's access privilege or security levels (such as ordinary user. guest user. administrator) D. User's native language E. The features user use F. The frequency with which user use the product

A

In the IEEE Std 1362 Concept of Operations (ConOps) Document, which of the following is fundamentally not included under the Concepts for the Proposed System (Clause 5)? A. Proposed design method of system B. Operational policies and constraints C. Description of the proposed system D. Modes of operation

C

Due to the iterative nature of the requirements process, change has to be managed through the review and approval process. Which of the following is likely to require the least amount of management? A. Requirements tracing B. Impact analysis C. System definition D. Software configuration management

C

Due to the iterative nature of the requirements process. change has to be managed through the review and approval process. Which of the following is likely to require the least amount of management? A. Requirements tracing B. Impact analysis C. System definition D. Software configuration management

B

Giving a business rule" All website images must include alternative text to be used by electronic reading devices to meet accessibility requirements for visually impaired users.' This is a type of _rule. A. inferences B. constraint C. facts D. action enabler E. computation

C

Giving a condition example in specification of withdrawn money use case: "the ATM has dispensed money and printed a receipt'. This is a(n) A. exception B. precondition C. postcondition D. extension

C

Giving a statement in an Airport check-in kiosk application: "As a traveler. I want to check in for a flight so that I can fly to my destination". This is a(n)_ example A. actor B. usecase C. user story D. entity

B

Giving an example of quality requirements: "After performing a file backup, the system shall verify the backup copy against the original and report any discrepancies". This is a (an) ______ A. robustness requirement B. integrity requirement C. performance requirement D. interoperability requirement

D

Giving an example of quality requirements: 'After performing a file backup. the system shall verify the backup copy against the original and report any discrepancies'. This is a (an)— A. performance requirement B. interoperability requirement C. Robustness requirement D. Integrity requirement

D

If a requirements status is proposed then it A. Is an approved requirement that has been removed B. Is work complete C. Has been requested by an authorized source D. Is a requirement that was proposed, but not planned for implementation

A

If a requirements status is proposed then it: A. Is an approved requirement that has been removed B. Is work complete C. Has been requested by an authorized source D. Is 4 requirement that was proposed. but not planned for implementation

A

If requirements are easily understandable and defined then which software process model is best suited? A. Waterfall model B. Agile model C. Spiral model D. Prototyping model

F

Which adverbs are the causes of requirements ambiguity in documenting Software Requirement Specification? A. appropriately B. generally C. reasonably D. usually E. approximately F. all of the mentioned

C

In order to determine solutions to business problems, the business analyst applies a set of: A. Inputs and outputs B. Practices and processes C. Tasks and techniques D. Activities and tasks

B

In the V model, the user requirements are detected by A. Unittesting B. Acceptance testing C. Integration testing D. System testing

D

Portability is an intemal quality attribute which could be described: A. How well the system protects against unauthorized access to the application and its data B. How quickly and predictably the system responds to user inputs or other events C. How easy it is for people to learn. remember. and use the system D. How easily the system can be made to work in other operating environments

D

Process quality and improvement relies most on which of the following? A. Product operator performance B. Human factors C. Customer preferences D. Requirements process measures

D

Product requirement validation occurs primarily after A. Testing B. Analysis C. Elicitation D. Specification

A

Requirement baselines are: A. Requirements committed to be implemented B. Requirements committed to be tested C. Requirements within scope D. Requirements out of scope

C

Requirement elicitation is communication intensive and should be aligned with: A. The cost-benefit analysis B. The business case C. The stakeholders' needs and constraints D. The requirement management plan

A

Requirements reviews: Can not be done before completion of the A. Systems definition document B. Systems specification document C. Software requirements specification document D. Baseline specification for new release

A

Requirements tracing is most likely concerned with the following: Recovering the source of requirements from: A. Software requirement back to the system requirement it supports B. Observation to elicitation technique C. Analysis into requirements specification document D. Software requirement to validation test

AD

Select the true statements (two options)- A. Verification determines whether the product of some development activity meets its requirements (doing the thing right). B. Validation determines whether the product of some development activity meets its requirements (doing the right thing) C. Verification assesses whether a product satisfies customer needs (doing the thing right). D. Validation assesses whether a product satisfies customer needs (doing the right thing)

D

Software Requirement Specification (SRS) is also known as specification of A. White box testing B. Black boxtesting C. lntegrated testing D. Acceptance testing

B

Software requirements validation should be viewed by whom and how often? A. Requirements analysts, often B. Stakeholders, often C. Customers, never D. Users, never

E

Which adverbs are the causes of requirements ambiguity in documenting Software Requirement Specification? A. reasonably B. generally C. usually D. appropriately E. All of the mentioned F. approximately

D

The BEST way to conduct a requirements validation review is to _ A. examine the system model for errors B. have the customer look over the requirements C. send them to the design team and see if they have any concems D. use a checklist of questions to examine each requirement

D

The business analysis team has put together the elicitation results documenting their understanding of the user needs. What types of requirements have they developed at this point in time? A. Maintained and reusable B. Communicated and confirmed C. Stated and unconfirmed D. Validated and confirmed

AC

The important goals of writing requirement: A. Each reader's interpretation matches what the author intended to communicate B. Each implementation of readers matches what the author intended to communicate C. Anyone who reads the requirement comes to the same interpretation as any other reader D. None of the answers

D

The requirement passed its tests after integration into the product. this is status A. approved B. implemented C. rejected D. verified E. deferred F. deleted

B

The requirements engineering process is _ A. The same for each organization and process B. lnitiated at the beginning of a project and continues to be refined throughout the lifecycle. C. A discrete fmntend activity of the software life cycle. D. A continuous process that ends when requirements are specified and documented

A

The software requirements specification should NOT be called ___ A. user requirements B. requirements document C. system specification D. product specification E. a business requirements document (BRD) F. functional specification

A

The system users have stated their needs for revised online order entry system capabilities. Her team needs the ability to perform online, remote order entry when they are traveling worldwide. What class or type of requirements best describe this need? A. Functional requirements B. Business requirements C. User requirements D. Transition requirements

D

The use of traceability tables helps to _ A. minimize miscommunication and unnecessary rework B. determine the performance of algorithm implementations C. debug programs following the detection of runtime errors D. identify, control and track requirements changes

B

The voice of the customers may be derived from? A. Impact analysis B. Customer complaints C. Business rules D. The business case

C

The work products produced during requirement elicitation will vary depending on the _ A. Stakehotders needs B. software process being used C. size of the product being built D. size of the budget

D

To express the user task descriptions, which representation technique is NOT suitable? A. Scenarios B. User stories C. Use case specifications D. Storyboards

C

To understand user tasks and goals and the business objectives with which those tasks align, the Business Analysis should discuss with users at which stage(s): A. Analysis B. Specification C. Elicitation D. Validation

C

To understand user tasks and goals and the business objectives with which those tasks align. the Business Analysis should discuss with users at which stage(s)' A. Validation B. Specification C. Elicitation D. Analysis

D

Which activities are NOT belong to requirements status tracking? A. Tracking the status distribution of all requirements B. Recording the status of each requirements C. Defining possible statuses D. Tracking individual requirements versions

A

What does allocation try to satisfy in the assigning of responsibility to components? A. Requirements B. Validation C. External interfaces D. Testing

D

What is a best practice for change control? A. Submit multiple changes at one time B. Open and honest communication C. Give overviews of the changes D. Hold change meetings

B

What is a software engineer most likely to resolve by making a unilateral decision? A. Differences between incompatible features B. Differences between developer perception and developer reality C. Differences between requirements and resources D. Differences between functional and non-functional requirements

B

What is a software requirements specification (SRS) document? A. A document listing the time it takes to execute the existing manual processes B. A document detailing software requirements and specifications C. A document which features instructions for how to install new software and test it for errors D. A document used while testing the software code for validity

D

What is considered the traditional means or requirements elicitation? A. Scenarios B. Observations C. Prototypes D. Interviews

B

What is the most common type of scenario elicitation technique? A. The prototype B. The use case C. The facilitator meeting D. Observation

A

What is the most important attribute of a requirement? A. Identifier B. Source C. Verification procedure D. Priority

D

What should the software requirements specification (SRS) writer avoid placing in the SRS environment of the SRS? A. External interfaces B. Performance or functionality C. Attributes or classification D. Either design or project requirements

D

Which dimension of requirement classification is critical for consideration of tolerant design? A. Whether the requirement is functional or non-functional. B. Whether the requirement is a high or low priority. C. Whether the requirement is on the product or process. D. Whether the requirement is volatile or stable.

B

Which document is used to derive the software requirements specification? A. The System Definition Document B. System Requirements Specification C. IEEE 1362 Concept of Operations D. IEEE 1016 Software Design Descriptions

D

Which is (are) the skills of business analyst on Agile project? A. Understanifing of the business area that the project is involved with B. Understanding of the agile development process C. Ability to document requirements formally or informally demnding on the need of the project D) All of the mentioned E. Ability to facilitate a team to consensus on scope. design decisions. and implementation decisions

B

Which is NOT a purpose ofthe software prototype technique? A. Clarify, complete, and validate requirements B. Specific technologies, tools, languages, and databases that must be used or avoided C. Create a subset that will grow into the ultimate product D. Explore design alternatives

D

Which is NOT a technique to find missing requirements? A. Check boundary values for missing requirements B. Trace system requirements, user requirements, event-response lists, and business rules to their corresponding functional requirements to make sure that all the necessary functionality was derived. C. Create a checklist of common functional areas to consider for your projects D. Check a list of tasks corresponding with end users E. Decompose high-level requirements into enough detail to reveal exactly what is being requested

F

Which is NOT belong to the case of use case traps? A. Including data definitions in the use cases B. Including design in the use cases C. Highly complex use cases D. Use cases that users don't understand E. Too many use cases F. Depicts detail the use case story

C

Which is NOT describe the correct purpose of requirements elicitation? A. Collect, discover. extract. and define requirements B. Discover business. user. functional. and nonfunctional requirements. along with other types of information C. Collect. discover. extract. and define exactly what are the outputs of project. D. Identify the needs and constraints of the various stakeholders for a software system.

C

Which is NOT the advantage of Agile methods? A. adapt with the requirements changes of stakeholders B. modify what already exists, enrich the initial features, add new ones, and correct defects that were discovered C. puts considerable effort into trying to get the full requirements set 'iight" early on. D. the development team could add a small set of functionalities based on priorities established by the customer E. breaking the development of software into short cycles

B

Which is NOT the helpful of product backlog? A. It helps in planning the roadmap forthe product B. It helps in managing the demands of stakeholders C. It helps in determining what to prioritize first. Team ranks the item and then builds value. D. It helps in re-ranking the features so that more value can be added to the product- E. It is prepared so that estimates can be given to each and every feature

B

Which is NOT the most important characteristics of product backlog? A. Ranking of features is done based on business value, technical value, risk management or strategic fitness. B. Lowest ranking items are decomposed into smaller stories during release planning so that they can be completed in future iterations C. Highest ranking items are decomposed into smaller stories during release planning so that they can be completed in future iterations D. Multiple teams can work on a single product backlog. E. Each product should have one product backlog which can have a set of large to very large features.

A

Which is NOT the reuse barrier? A. Organizational culture B. Inconsistent organization C. Writing style D. Ownership E. Projecttype

D

Which is NOT the type of internal quality? A. Verifiability B. Modifiability C. Efficiency D. availability E. Scalability

A

Which is NOT the type of requirements development tools? A Requirement Management tools B. Elicitation tools C. Modeling tools D. Prototyping tools

B

Which is not a reuse success factor? A. Organizational culture B. National culture C. Quality D. Terminology E. Repository F. Interactions

B

Which is the benefits of the reuse requirements technique? A. to estimate implementation effort if you have data available from implementing the same requirements on a previous project. B. All of the mentioned answers C. improve functional consistency across related members of a product line or among a set of business applications D. Faster delivery, lower development costs, consistency both within and across applications, higher team productivity, fewer defects, and reduced rework. E. save review time, accelerate the approval cycle, and speed up other project activities, such as testing

D

Which is(are) the skills of business analyst on Agile project? A. Understanding of the business area that the project is involved with B. Understanding of the agile development process C. Ability to facilitate a team to consensus on scope, design decisions, and implementation decisions D. All of the mentioned E. Ability to document requirements formally or informally depending on the need of the project

B

Which of the following is NOT a good characteristic well written of a software requirements specification? A. Ranked B. Redundant C. Consistent D. Verifiable

A

Which of the following is NOT a type of software requirement? A. Complexity B. Performance C. Functionality D. External Interface

B

Which of the following is most true about a non-functional requirement? A. Describes functions software is to execute B. Acts to constrain the software solution C. Is highly sensitive to the system architecture D. Is derived from hardware requirements

B

Which of the following is not embedded design that would be written in the SRS? A. Partitioning of software into modules B. Specify logical requirements for the software C. Describe the flow of information or control between modules D. Choose data structures

C

Which of the following is the technical manager not responsible for? A. Determining the adequacy of the requirements specifications. B. Controlling the volatility of the requirements and manage change history. C. Re-estimating the cost and schedule of the project when the requirements change. D. Negotiating requirements changes between the acquirer (customer) and the developer.

C

Which of the following phrases most closely approaches verifiable language? A. "A good operability" B. "Well enough" C. "According to Standard X" D. "Usually acceptable"

A

Which of the following property is least critical to the interaction between process actors and the requirements process? A. The education of the actor B. The nature of their 'stake' in the process C. The requirements they elicit D. Process actor identification

C

Which of the following requirement properties would be considered an emergent property of a software program? A. The fault detection system of the software B. The programming language of the system C. The reliability of the software D. The number of lines of code

B

Which of the following you should be based on when you estimate the projectsize and effort? A. Function points (Jones 1996b;IFPUG 2010) B. All of the mentioned answers C. The number, type, and complexity of user interface elements D. Story points (Cohn 2005;McConnell 2006) or use case points (Wiegers 2006) E. Estimated lines of code needed to implement specific requirements F. The number of individually testable requirements (Wilson 1995)

A

Which of these steps in the planned change process puts the change plan into action? A. Implement the change B. Select the change agent C. Develop the change plan D. Recognize the need for change

C

Which requirements should NOT be reused in the scope of cross an enterprise? A. Business rules B. Security requirements C. Constraints D. Stakeholder profiles

B

Which requirements should NOT be reused within an operating environment or platform? A. Infrastructures of functionality needed to support certain types of requirements (such as a report generator) B. stakeholder profiles C. Constraints D. Interfaces

B

Which technique overtaps for use in requirements elicitation and requirements validation? A. Facilitator meetings B. Prototypes C. Observations D. Interviews

C

Why is Requirements Management important? It is due to the changes A. in technology B. in customer's expectations C. all ofthe mentioned D. to the environment E. in the demand of stakeholders

E

Why is Requirements Management important? It is due to the changes A. lotheenvironment B. intechnology C. in customers expectations D. in the demand of stakeholders E. All of the mentioned

B

Why is base-lining project? A. To get disagreement for all the requirements of project B. To get an agreement for each set of requirements after the team implements them C. To minimize miscommunication and unnecessary rework D. To get an agreement for all the requirements of project

B

Why is base-lining project? A. To minimize miscommunication and unnecessary rework B. To get an agreement for each set of requirements after the team implements them C. To get disagreement for all the requirements of project D. To get an agreement for all the requirements of project

A

____ is the process of examining a project to identify potential threats A. Risk assessment B. Risk resolution C. Risk monitoring 0. Risk avoidance E. Risk control