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 link between two elements or objects in a diagram.






2. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






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






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






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






9. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






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






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






15. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






19. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






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






26. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






30. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






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






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






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






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






38. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






41. The degree to which a set of inherent characteristics fulfills requirements.






42. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






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






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






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






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






50. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.