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 structured examination of an identified problem to understand the underlying causes.






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






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






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






5. Something that occurs to which an organizational unit system or process must respond.






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






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






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






9. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






11. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






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






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






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






17. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






22. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






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






29. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






33. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






34. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






38. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






40. The human and nonhuman roles that interact with the system.






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






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






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






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






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 set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






47. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






49. A practitioner of business analysis.






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