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. A model that defines the boundaries of a business domain or solution.






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






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






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






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






6. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






10. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






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






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






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






19. A partial or preliminary version of the system.






20. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






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






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






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






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






28. A prototype developed to explore or verify requirements.






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






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






31. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






32. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






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






36. The problem area undergoing analysis.






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






38. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






40. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






42. A practitioner of business analysis.






43. The set of capabilities a solution must deliver in order to meet the business need.






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






45. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






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






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






50. Limitations on the design of a solution that derive from the technology used in its implementation.