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






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






3. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






4. An informal solicitation of proposals from vendors.






5. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






6. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






7. Software developed and sold for a particular market.






8. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






10. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






11. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






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






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






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






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






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






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






21. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






22. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






26. The degree to which a set of inherent characteristics fulfills requirements.






27. A unit of work performed as part of an initiative or process.






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






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






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






31. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






33. A system trigger that is initiated by time.






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






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






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






37. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






39. Ability of systems to communicate by exchanging data or services.






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






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






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






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






44. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






47. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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