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. Limitations on the design of a solution that derive from the technology used in its implementation.






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






3. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






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






8. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






9. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






12. A description of the requirements management process.






13. The problem area undergoing analysis.






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






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






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






17. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






19. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






20. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






24. An informal solicitation of proposals from vendors.






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






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






27. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






29. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






30. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






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






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






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






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






38. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






39. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






42. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






43. A practitioner of business analysis.






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






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






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






47. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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







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