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 solution or component of a solution that is the result of a project.






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






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






4. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






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






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






9. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






12. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






14. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






15. A stakeholder person device or system that directly or indirectly accesses a system.






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






17. A stakeholder who uses products or services delivered by an organization.






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






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






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






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






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






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






24. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






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






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






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






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






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






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






34. An informal solicitation of proposals from vendors.






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






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






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






38. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






42. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






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






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






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






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






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






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






50. The area covered by a particular activity or topic of interest.