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






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






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






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






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






6. A fixed period of time to accomplish a desired outcome.






7. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






8. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






10. Information that is used to understand the context and validity of information recorded in a system.






11. Software developed and sold for a particular market.






12. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






16. A data element with a specified data type that describes information associated with a concept or entity.






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






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






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






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






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






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






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






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






25. Any effort undertaken with a defined goal or objective.






26. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






29. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






32. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






34. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






36. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






41. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






44. The features and functions that characterize a product service or result.






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






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






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






48. A partial or preliminary version of the system.






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






50. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.