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 stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






6. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






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






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






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






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






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






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






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






17. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






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






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






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






24. A prototype that is continuously modified and updated in response to feedback from users.






25. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






28. A group of related tasks that support a key function of business analysis.






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






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






31. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






34. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






35. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






39. The problem area undergoing analysis.






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






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






42. A partial or preliminary version of the system.






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






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






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






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






47. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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