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. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






3. A prototype that dives into the details of the interface functionality or both.






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






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






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






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






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






9. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






13. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






14. An assessment of the costs and benefits associated with a proposed initiative.






15. A non-actionable directive that supports a business goal.






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






17. A system trigger that is initiated by humans.






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






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






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






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






22. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






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






30. A temporary endeavor undertaken to create a unique product service or result.






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






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






33. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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






37. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






41. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






45. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






46. The process of examining new business opportunities to improve organizational performance.






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






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






49. Creating working software in multiple releases so the entire product is delivered in portions over time.






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