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. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






2. A fixed period of time to accomplish a desired outcome.






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






4. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






8. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






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






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






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






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






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






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






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






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






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






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






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






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






22. A prototype developed to explore or verify requirements.






23. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






27. The number of employees a manger is directly (or indirectly) responsible for.






28. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






31. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






33. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






35. The features and functions that characterize a product service or result.






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






37. An analysis model that shows user interface dialogs arranged as hierarchies.






38. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






39. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






40. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






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






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






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






48. A description of the requirements management process.






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






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