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 problem area undergoing analysis.






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






3. A prototype that is continuously modified and updated in response to feedback from users.






4. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






5. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






6. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






7. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






9. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






11. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






14. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






15. Software developed and sold for a particular market.






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






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






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






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






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






21. A description of the requirements management process.






22. The human and nonhuman roles that interact with the system.






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






24. Work carried out or on behalf of others.






25. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






28. A practitioner of business analysis.






29. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






37. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






43. A prototype that dives into the details of the interface functionality or both.






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






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






46. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests