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 activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






6. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






7. A partial or preliminary version of the system.






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






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






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






11. Any effort undertaken with a defined goal or objective.






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






13. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






16. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






18. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






21. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






26. A link between two elements or objects in a diagram.






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






28. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






31. A system trigger that is initiated by time.






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






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






34. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






37. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






39. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






40. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






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






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






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






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






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






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






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






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