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 continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






3. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






6. A function of an organization that enables it to achieve a business goal or objective.






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. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






9. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






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






15. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






18. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






21. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






22. A partial or preliminary version of the system.






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






24. Software developed and sold for a particular market.






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






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






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. The features and functions that characterize a product service or result.






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






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






31. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






32. A system trigger that is initiated by time.






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






34. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






35. The problem area undergoing analysis.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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