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. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






4. Work carried out or on behalf of others.






5. An analysis model showing the life cycle of a data entity or class.






6. Software developed and sold for a particular market.






7. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






12. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






14. An analysis model that illustrates the architecture of the system's user interface.






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






16. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






20. A system trigger that is initiated by humans.






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






22. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






24. A prototype developed to explore or verify requirements.






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. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






27. A data element with a specified data type that describes information associated with a concept or entity.






28. An assessment of the costs and benefits associated with a proposed initiative.






29. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






32. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






33. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






34. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






36. A description of the requirements management process.






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






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






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






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






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






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






43. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






44. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






46. A structured examination of an identified problem to understand the underlying causes.






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






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






49. A system trigger that is initiated by time.






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