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






2. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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






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






10. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






14. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






17. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






18. Ability of systems to communicate by exchanging data or services.






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






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






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






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






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






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






25. The features and functions that characterize a product service or result.






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






27. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






28. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






29. The problem area undergoing analysis.






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






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






32. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






34. A system trigger that is initiated by humans.






35. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






40. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






42. A system trigger that is initiated by time.






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






44. The set of processes templates and activities that will be used to perform business analysis in a specific context.






45. The area covered by a particular activity or topic of interest.






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






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






48. A stakeholder who provides products or services to an organization.






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






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







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