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 type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






6. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






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. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






13. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






14. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






15. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






18. A partial or preliminary version of the system.






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






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






21. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






23. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






25. A data element with a specified data type that describes information associated with a concept or entity.






26. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






27. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






28. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






32. A group of related tasks that support a key function of business analysis.






33. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






36. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






39. A description of the requirements management process.






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






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






42. An analysis model showing the life cycle of a data entity or class.






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






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






45. A system trigger that is initiated by time.






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






47. A practitioner of business analysis.






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






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






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