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. An actor who participates in but does not initiate a use case.






2. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






4. An informal solicitation of proposals from vendors.






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






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






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






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






9. A partial or preliminary version of the system.






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






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






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






13. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






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






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






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






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






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






22. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






25. A system trigger that is initiated by humans.






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






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






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






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






30. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






35. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






37. A model that defines the boundaries of a business domain or solution.






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






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






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






41. A person with specific expertise in an area or domain under investigation.






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






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






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






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






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






47. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






48. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






49. Work carried out or on behalf of others.






50. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests