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 assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






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






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






7. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






10. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






16. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






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






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






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






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






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






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






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






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






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






29. The problem area undergoing analysis.






30. A prototype developed to explore or verify requirements.






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






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






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






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






35. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






37. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






38. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






40. Any effort undertaken with a defined goal or objective.






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






42. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






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






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






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 state or condition the business must satisfy to reach its vision.