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






2. Work carried out or on behalf of others.






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






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






5. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






6. A type of data model that depicts information groups as classes.






7. An actor who participates in but does not initiate a use case.






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






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






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






11. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






14. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






16. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






18. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






19. Formal approval of a set of requirements by a sponsor or other decision maker.






20. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






21. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






22. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






24. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






25. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






26. A group or person who has interests that may be affected by an initiative or influence over it.






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






28. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






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






33. The degree to which a set of inherent characteristics fulfills requirements.






34. A practitioner of business analysis.






35. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






36. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






41. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






42. A unit of work performed as part of an initiative or process.






43. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






45. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






46. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






48. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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