SWR 302 Final Exam | Questions with Verified Answers

SWR 302 Final Exam | Questions with Verified Answers Which of the following is NOT a good characteristic well written of a software requirements specification? A. Ranked B. Redundant C. Consistent D. Verifiable Which i ...

SWR 302 Final Exam | Questions with Verified Answers Which of the following is NOT a good characteristic well written of a software requirements specification? A. Ranked B. Redundant C. Consistent D. Verifiable 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 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 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 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 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 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 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 Which is not a reuse success factor? A. Organizational culture B. National culture C. Quality D. Terminology E. Repository F. Interactions 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 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 Which is NOT the helpful of product backlog? A. It helps in planning the roadmap for the 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 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 (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 To express the user task descriptions, which representation technique is NOT suitable? A. Scenarios B. User stories C. Use case specifications D. Storyboards 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 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 Requirement baselines are: A. Requirements committed to be implemented B. Requirements committed to be tested C. Requirements within scope D. Requirements out of scope 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 The voice of the customers may be derived from? A. Impact analysis B. Customer complaints C. Business rules D. The business case Why is Requirements Management important? It is due to the changes A. in technology B. in customer's expectations C. all of the mentioned D. to the environment E. in the demand of stakeholders Which technique overtaps for use in requirements elicitation and requirements validation? A. Facilitator meetings B. Prototypes C. Observations D. Interviews Which requirements should NOT be reused in the scope of cross an enterprise? A. Business rules B. Security requirements C. Constraints D. Stakeholder profiles 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 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 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) 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 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 In the V model, the user requirements are detected by A. Unittesting B. Acceptance testing C. Integration testing D. System testing 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 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 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 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 Which is NOT a purpose of the 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 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 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?