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 state or condition the business must satisfy to reach its vision.






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






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






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






5. A stakeholder who uses products or services delivered by an organization.






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






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






8. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






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






14. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






18. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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 matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






23. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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 description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






33. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






38. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






39. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






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






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






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






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






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






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






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






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






50. Work carried out or on behalf of others.