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 stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






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






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






7. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






10. A description of the requirements management process.






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






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






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






14. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






18. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






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






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






24. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






26. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






28. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






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






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






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






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






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






38. Something that occurs to which an organizational unit system or process must respond.






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






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






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






42. A system trigger that is initiated by time.






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






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






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






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






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






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






49. Software developed and sold for a particular market.






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