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 work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






4. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






6. A prototype developed to explore or verify requirements.






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






8. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






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






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






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






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






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






16. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






17. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






18. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






19. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






22. A practitioner of business analysis.






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






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






25. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






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






31. A system trigger that is initiated by humans.






32. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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