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. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






7. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






8. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






10. Software requirements that limit the options available to the system designer.






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






12. A group or person who has interests that may be affected by an initiative or influence over it.






13. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






16. A description of the requirements management process.






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






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






19. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






20. A measure of the profitability of a project or investment.






21. Software developed and sold for a particular market.






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






23. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






24. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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






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






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






30. A system trigger that is initiated by time.






31. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






32. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






37. A partial or preliminary version of the system.






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






39. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






40. Limitations on the design of a solution that derive from the technology used in its implementation.






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






42. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






48. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






50. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.