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 specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






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






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






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






10. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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






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






15. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






18. A partial or preliminary version of the system.






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






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






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






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






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






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






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






26. A fixed period of time to accomplish a desired outcome.






27. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






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






31. A state or condition the business must satisfy to reach its vision.






32. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






36. A stakeholder who provides products or services to an organization.






37. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






40. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






41. A system trigger that is initiated by humans.






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






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






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






45. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






47. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






49. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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