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 quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






4. A stakeholder who uses products or services delivered by an organization.






5. A function of an organization that enables it to achieve a business goal or objective.






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






7. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






9. A stakeholder person device or system that directly or indirectly accesses a system.






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






11. The problem area undergoing analysis.






12. A system trigger that is initiated by time.






13. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






14. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






15. A partial or preliminary version of the system.






16. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






17. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






18. Work carried out or on behalf of others.






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






20. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






21. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






22. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






26. A link between two elements or objects in a diagram.






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






28. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






29. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






31. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






32. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






34. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






35. The work that must be performed to deliver a product service or result with the specified features and functions.






36. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






38. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






40. A shared boundary between any two persons and/or systems through which information is communicated.






41. A measure of the profitability of a project or investment.






42. The set of processes templates and activities that will be used to perform business analysis in a specific context.






43. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






46. A person with specific expertise in an area or domain under investigation.






47. A set of requirements grouped together in a document or presentation for communication to stakeholders.






48. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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