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






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






3. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






4. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






7. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






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






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






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






13. A prototype developed to explore or verify requirements.






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






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






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






17. A system trigger that is initiated by humans.






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






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






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






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






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






23. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






25. An analysis model describing the data structures and attributes needed by the system.






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






27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






28. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






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






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






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






36. An assessment of the costs and benefits associated with a proposed initiative.






37. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






38. Ability of systems to communicate by exchanging data or services.






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






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






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






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






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






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






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






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






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






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






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






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