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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






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






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






8. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






11. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






12. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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






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






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






22. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






23. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






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






28. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






31. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






35. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






37. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






38. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






40. Formal approval of a set of requirements by a sponsor or other decision maker.






41. A unit of work performed as part of an initiative or process.






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






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






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






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






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






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






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






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






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







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