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 function of an organization that enables it to achieve a business goal or objective.






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






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






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






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






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






8. A stakeholder who provides products or services to an organization.






9. A prototype developed to explore or verify requirements.






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






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






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






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






14. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






18. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






19. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






21. A system trigger that is initiated by humans.






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






23. Formal approval of a set of requirements by a sponsor or other decision maker.






24. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






26. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






30. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






31. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






33. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






36. The area covered by a particular activity or topic of interest.






37. Ability of systems to communicate by exchanging data or services.






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






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






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






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






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






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






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






45. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






48. A partial or preliminary version of the system.






49. Work carried out or on behalf of others.






50. A system of programming statements symbols and rules used to represent instructions to a computer.