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. Influencing factors that are believed to be true but have not been confirmed to be accurate.






2. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






3. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






5. The work that must be performed to deliver a product service or result with the specified features and functions.






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 prototype developed to explore or verify requirements.






8. The process of examining new business opportunities to improve organizational performance.






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






10. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






11. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






13. The problem area undergoing analysis.






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






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






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






17. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






18. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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






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






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






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






26. A partial or preliminary version of the system.






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






28. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






32. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






34. An informal solicitation of proposals from vendors.






35. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






38. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






39. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






40. A description of the requirements management process.






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






42. Any recognized association of people in the context of an organization or enterprise.






43. The features and functions that characterize a product service or result.






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






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






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






47. A system trigger that is initiated by humans.






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






49. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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