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. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






4. A description of the requirements management process.






5. Software developed and sold for a particular market.






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






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






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






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






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






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






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






13. A group or person who has interests that may be affected by an initiative or influence over it.






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






15. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






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






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






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






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






23. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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






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






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






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






30. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






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






35. The problem area undergoing analysis.






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






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






38. The area covered by a particular activity or topic of interest.






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






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






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






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






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






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






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






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






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






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






49. An actor who participates in but does not initiate a use case.






50. A stakeholder with legal or governance authority over the solution or the process used to develop it.