Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






2. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






3. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






4. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






5. An assessment of the costs and benefits associated with a proposed initiative.






6. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






7. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






8. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






9. Any effort undertaken with a defined goal or objective.






10. Any recognized association of people in the context of an organization or enterprise.






11. Software requirements that limit the options available to the system designer.






12. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






13. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






14. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






15. A description of the requirements management process.






16. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






17. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






18. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






19. A stakeholder with legal or governance authority over the solution or the process used to develop it.






20. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






21. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






22. The quality attributes design and implementation constraints and external interfaces that the product must have.






23. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






24. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






25. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






26. Creating working software in multiple releases so the entire product is delivered in portions over time.






27. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






28. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






29. Information that is used to understand the context and validity of information recorded in a system.






30. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






31. Ability of systems to communicate by exchanging data or services.






32. A non-actionable directive that supports a business goal.






33. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






34. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






35. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






36. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






37. Any unique and verifiable work product or service that a party has agreed to deliver.






38. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






39. The area covered by a particular activity or topic of interest.






40. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






41. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






42. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






43. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






44. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






45. A prototype that is continuously modified and updated in response to feedback from users.






46. A data element with a specified data type that describes information associated with a concept or entity.






47. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






48. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






49. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






50. A partial or preliminary version of the system.