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 stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






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






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






7. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






9. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






16. A system trigger that is initiated by humans.






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






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






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






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






21. Work carried out or on behalf of others.






22. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






23. A description of the requirements management process.






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






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






26. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






29. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






33. A system trigger that is initiated by time.






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






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






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






37. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






40. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






41. A prototype that is continuously modified and updated in response to feedback from users.






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






43. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






46. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






49. An informal solicitation of proposals from vendors.






50. A use case composed of a common set of steps used by multiple use cases.