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 validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






6. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






7. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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 specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






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






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






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






19. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






20. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






21. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






22. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






26. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






29. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






32. A shared boundary between any two persons and/or systems through which information is communicated.






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






34. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






35. A practitioner of business analysis.






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






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






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






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






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






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






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






43. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






47. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






48. A type of data model that depicts information groups as classes.






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






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







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