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. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






6. A prototype developed to explore or verify requirements.






7. A practitioner of business analysis.






8. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






12. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






14. An informal solicitation of proposals from vendors.






15. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






18. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






22. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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






26. A person with specific expertise in an area or domain under investigation.






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






28. Software developed and sold for a particular market.






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






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






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






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






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






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






35. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






36. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






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






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






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






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






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






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






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






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






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






50. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.







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