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. Something that occurs to which an organizational unit system or process must respond.






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






3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






6. Information that is used to understand the context and validity of information recorded in a system.






7. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






8. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






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






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






17. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






21. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






23. A link between two elements or objects in a diagram.






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






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






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






27. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






29. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






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






36. The features and functions that characterize a product service or result.






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






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






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






40. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






42. An actor who participates in but does not initiate a use case.






43. Software developed and sold for a particular market.






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






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






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






47. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






48. A partial or preliminary version of the system.






49. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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