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 organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






5. A fixed period of time to accomplish a desired outcome.






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






7. A type of data model that depicts information groups as classes.






8. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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






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






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. A stakeholder who uses products or services delivered by an organization.






15. A person with specific expertise in an area or domain under investigation.






16. An analysis model describing the data structures and attributes needed by the system.






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






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






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






20. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






23. A group or person who has interests that may be affected by an initiative or influence over it.






24. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






25. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






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






33. Software requirements that limit the options available to the system designer.






34. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






37. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






38. A description of the requirements management process.






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






40. The human and nonhuman roles that interact with the system.






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






42. A prototype developed to explore or verify requirements.






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






44. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






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






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