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 responsible for assessing the quality of and identifying defects in a software application.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






17. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






19. An assessment of the costs and benefits associated with a proposed initiative.






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






21. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






24. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






25. A description of the requirements management process.






26. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






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






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






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






32. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






34. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






37. A non-actionable directive that supports a business goal.






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






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






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






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






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






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






44. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






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






49. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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