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. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






6. A non-actionable directive that supports a business goal.






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






8. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






9. Any unique and verifiable work product or service that a party has agreed to deliver.






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






11. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






12. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






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






17. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






19. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






20. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






22. The area covered by a particular activity or topic of interest.






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






24. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






27. A partial or preliminary version of the system.






28. A use case composed of a common set of steps used by multiple use cases.






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






30. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






35. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






38. A system trigger that is initiated by humans.






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






40. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






44. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests