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 error in requirements caused by incorrect incomplete missing or conflicting requirements.






2. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






5. The work that must be performed to deliver a product service or result with the specified features and functions.






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






7. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






9. A model that defines the boundaries of a business domain or solution.






10. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






11. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






13. A practitioner of business analysis.






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






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






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






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






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






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






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






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






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






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






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






25. A system of programming statements symbols and rules used to represent instructions to a computer.






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






27. Work carried out or on behalf of others.






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






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






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






31. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






34. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






36. Any recognized association of people in the context of an organization or enterprise.






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






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






39. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






46. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






48. A partial or preliminary version of the system.






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






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