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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






4. A fixed period of time to accomplish a desired outcome.






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






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






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






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






9. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






10. A non-actionable directive that supports a business goal.






11. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






13. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






16. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






18. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






23. Work carried out or on behalf of others.






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






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






26. Software developed and sold for a particular market.






27. A measure of the profitability of a project or investment.






28. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






29. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






32. A system trigger that is initiated by humans.






33. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






35. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






36. A person with specific expertise in an area or domain under investigation.






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






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






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






40. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






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






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






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






49. A description of the requirements management process.






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