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 description of the requirements management process.






2. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






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






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






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






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






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






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






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






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






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






15. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






16. A partial or preliminary version of the system.






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






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






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






20. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






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






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






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






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






29. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






30. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






33. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






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






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






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






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






41. Software developed and sold for a particular market.






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






43. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






47. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






49. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






50. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.