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 state or condition the business must satisfy to reach its vision.






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






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






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






5. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






7. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






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






11. A practitioner of business analysis.






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






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






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






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






16. A system trigger that is initiated by time.






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






18. Work carried out or on behalf of others.






19. A solution or component of a solution that is the result of a project.






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






21. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






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






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






26. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






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






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






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






34. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






36. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






37. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






39. The human and nonhuman roles that interact with the system.






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






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






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






43. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






47. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






49. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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