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. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






2. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






3. The features and functions that characterize a product service or result.






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






5. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






6. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






7. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






12. A partial or preliminary version of the system.






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






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






15. A function of an organization that enables it to achieve a business goal or objective.






16. A stakeholder who uses products or services delivered by an organization.






17. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






20. A system trigger that is initiated by time.






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






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






23. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






28. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






32. A practitioner of business analysis.






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






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






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






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






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






38. Software developed and sold for a particular market.






39. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






41. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






42. The number of employees a manger is directly (or indirectly) responsible for.






43. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






49. The problem area undergoing analysis.






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