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 business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






2. 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.






3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






5. 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.






6. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






7. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






9. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






10. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






11. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






12. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






13. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






14. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






17. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






18. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






19. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






20. A prototype that dives into the details of the interface functionality or both.






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






22. 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.






23. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






24. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






25. 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






26. An informal solicitation of proposals from vendors.






27. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






28. A prototype developed to explore or verify requirements.






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






30. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






32. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






33. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






34. Limitations on the design of a solution that derive from the technology used in its implementation.






35. A model that defines the boundaries of a business domain or solution.






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






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






38. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






39. The features and functions that characterize a product service or result.






40. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






41. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






43. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






44. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






45. The set of capabilities a solution must deliver in order to meet the business need.






46. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






47. 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






48. Work carried out or on behalf of others.






49. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






50. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.