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 model that defines the boundaries of a business domain or solution.






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






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






4. A group of related tasks that support a key function of business analysis.






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






6. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






7. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






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






12. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






13. A practitioner of business analysis.






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






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






16. An analysis model showing the life cycle of a data entity or class.






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






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






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






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






21. The product capabilities or things the product must do for its users.






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






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






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






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






26. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






28. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






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






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






35. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






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






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






40. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






43. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






47. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






48. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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