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. The features and functions that characterize a product service or result.






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






3. A prototype developed to explore or verify requirements.






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






5. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






8. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






9. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






10. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






12. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






14. A prototype that dives into the details of the interface functionality or both.






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






16. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






19. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






20. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






23. A system trigger that is initiated by humans.






24. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






25. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






28. A function of an organization that enables it to achieve a business goal or objective.






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






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






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






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






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






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






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






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






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






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






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






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






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. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






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






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






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






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






50. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet







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