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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






5. A link between two elements or objects in a diagram.






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






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






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






9. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






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






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






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






16. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






18. An analysis model that illustrates the architecture of the system's user interface.






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






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






21. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






24. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






27. The process of examining new business opportunities to improve organizational performance.






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






29. The human and nonhuman roles that interact with the system.






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






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






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






33. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






34. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






35. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






37. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






38. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






46. A practitioner of business analysis.






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






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






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






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