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






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






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






4. A non-actionable directive that supports a business goal.






5. A solution or component of a solution that is the result of a project.






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






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






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






9. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






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






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






14. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






15. A partial or preliminary version of the system.






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






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






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






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






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. An informal solicitation of proposals from vendors.






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






23. Work carried out or on behalf of others.






24. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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






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






29. A description of the requirements management process.






30. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






33. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






37. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






38. A practitioner of business analysis.






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






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






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






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






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






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






45. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






47. A type of data model that depicts information groups as classes.






48. Software developed and sold for a particular market.






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






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







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