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






2. A partial or preliminary version of the system.






3. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






5. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






6. A practitioner of business analysis.






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






8. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






12. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






13. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






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






19. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






21. A system trigger that is initiated by humans.






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






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






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






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






26. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






28. Something that occurs to which an organizational unit system or process must respond.






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






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






31. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






33. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






36. A link between two elements or objects in a diagram.






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






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






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






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






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






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






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






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






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






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






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






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






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