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






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






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






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






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






6. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






7. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






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






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






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






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






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






16. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






17. A system trigger that is initiated by time.






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






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






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






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






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






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






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






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






26. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






27. The degree to which a set of inherent characteristics fulfills requirements.






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






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






30. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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






34. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






35. Software developed and sold for a particular market.






36. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






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






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






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






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






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






48. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






49. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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