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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






3. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






4. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






5. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






7. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






8. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






9. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






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






16. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






18. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






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






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






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






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






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






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






29. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






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






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






34. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






37. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






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






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






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






45. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






50. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s