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 analysis model that shows user interface dialogs arranged as hierarchies.






2. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






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






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






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






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






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






11. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






13. Software developed and sold for a particular market.






14. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






18. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






19. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






20. A description of the requirements management process.






21. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






22. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






23. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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 means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






32. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






35. A measure of the profitability of a project or investment.






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






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






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






39. A prototype developed to explore or verify requirements.






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






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






42. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






44. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






47. Any unique and verifiable work product or service that a party has agreed to deliver.






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






49. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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