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 description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






5. A system trigger that is initiated by humans.






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






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






8. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






12. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






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






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






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






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






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






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






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






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






24. An informal solicitation of proposals from vendors.






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






26. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






30. The product capabilities or things the product must do for its users.






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






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






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






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






35. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






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






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






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






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






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






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






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






46. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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







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