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. Software requirements that limit the options available to the system designer.






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






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






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






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






6. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






7. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






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






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






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






15. A temporary endeavor undertaken to create a unique product service or result.






16. Metadata related to a requirement used to assist with requirements development and management.






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






18. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






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






24. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






28. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






29. An informal solicitation of proposals from vendors.






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






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






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






33. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






35. A group of related tasks that support a key function of business analysis.






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






37. A system trigger that is initiated by humans.






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






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






40. Any unique and verifiable work product or service that a party has agreed to deliver.






41. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






45. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






50. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests