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. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






5. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






8. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






9. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






12. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






13. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






16. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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






19. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






23. The product capabilities or things the product must do for its users.






24. Work carried out or on behalf of others.






25. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






26. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






29. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






32. A system trigger that is initiated by time.






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






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






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






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






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 requirements by conducting an assessment of the stakeholder's work environment.






39. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






41. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






43. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






44. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






46. The degree to which a set of inherent characteristics fulfills requirements.






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






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






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






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