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






2. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






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






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






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






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






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






13. A practitioner of business analysis.






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






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






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






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






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






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






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






21. The set of capabilities a solution must deliver in order to meet the business need.






22. An analysis model showing the life cycle of a data entity or class.






23. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






27. Software developed and sold for a particular market.






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






29. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






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






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






35. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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






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






40. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






41. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






42. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






43. An informal solicitation of proposals from vendors.






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






45. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






47. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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