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 non-actionable directive that supports a business goal.






2. The problem area undergoing analysis.






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






4. A use case composed of a common set of steps used by multiple use cases.






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






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






7. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






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






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






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






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






18. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






19. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






20. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






36. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






39. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






41. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






42. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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






47. Work carried out or on behalf of others.






48. A temporary endeavor undertaken to create a unique product service or result.






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






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