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. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






4. A stakeholder with legal or governance authority over the solution or the process used to develop it.






5. The number of employees a manger is directly (or indirectly) responsible for.






6. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






8. A function of an organization that enables it to achieve a business goal or objective.






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






10. A stakeholder person device or system that directly or indirectly accesses a system.






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






12. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






14. Any effort undertaken with a defined goal or objective.






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






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






17. An analysis model that illustrates the architecture of the system's user interface.






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






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






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






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






22. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






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






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






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






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






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






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






32. A system of programming statements symbols and rules used to represent instructions to a computer.






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






34. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






36. An informal solicitation of proposals from vendors.






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






38. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






39. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






40. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






41. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






42. An analysis model describing the data structures and attributes needed by the system.






43. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






44. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






47. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






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